[00:01] <Darxus> RAOF: I don't understand the question.
[00:02] <RAOF> Darxus: Those tests are presumably enabled in the Ubuntu packages, yes? If so, when the package is built for Ubuntu they'll be run, and presumably *pass*. You could check out the buildlog of the Ubuntu GTK package to see if that's happening.
[00:03] <Darxus> RAOF: Ah, yes, interesting, thanks.
[00:03] <Darxus> But it sounds like my problem is just that I'm using dpkg-buildpackage -rfakeroot instead of a build target.
[00:04] <Darxus> Yeah, just booting into quantal and running it there, without the chroot, got past that problem :/
[00:37] <Darxus> Uploaded and rebult:  https://launchpad.net/~darxus/+archive/wayland-gtk-quantal
[00:37] <Darxus> Thanks for your help.
[00:59] <Darxus> Would it work to just run the build through dbus-launch?
[00:59] <Darxus> (To fix my problem with building in a chroot.)
[01:48] <ml|vacation>  /12
[01:50] <ml|vacation> ugh!
[04:21] <pitti> Good morning
[05:23] <didrocks> good morning
[05:24] <pitti> bonjour didrocks, ça va?
[05:25] <didrocks> gutent morgen pitti! Ça va bien, et toi?
[05:25] <pitti> Je suis bien, merci!
[05:25] <pitti> I hope to get udisks2 to succeed today, on https://jenkins.qa.ubuntu.com/view/Quantal/view/AutoPkg%20Test/
[05:26] <pitti> this page becomes a real joy to look at :)
[05:26] <pitti> (tabix is fixed upstream already)
[05:26] <didrocks> hehe, you are in the green business, right? :)
[05:26] <pitti> J'aime la couleur vert!
[05:27] <pitti> (or is it "verte" in this case, as couleur is female?)
[05:30] <didrocks> verte dans ce cas, oui :)
[05:56] <RAOF> Damnit! gdb, give a reasonable backtrace!
[05:57] <RAOF> Is anyone else seeing semi-regular crashes in libdbus, with a backtrace full of ??s that can't be retraced?
[05:57] <RAOF> I'm starting to suspect some form of memory corruption.
[05:57] <pitti> I think I looked at backtraces like that
[05:58] <RAOF> They look something like http://paste2.org/p/2200544 ?
[06:01] <RAOF> gwibber-service is fond of crashing there, as is tomboy & banshee.
[06:20] <didrocks> RAOF: I think you got the right bug # :)
[06:21] <didrocks> RAOF: I see a compiz task, anything needed on their end?
[06:21] <didrocks> I see the xserver-xorg-video-intel to be fix released
[06:22] <RAOF> didrocks: I don't believe so, no. I'll invalidate the compiz tasks.
[06:23] <didrocks> RAOF: hum, is it really fix released into the distro?
[06:24] <didrocks> I find all the status change and revert quite puzzling :)
[06:24] <RAOF> didrocks: I'm unsure; tjaalton knows more. I think there was at least *one* fix released to the distro; I don't know if that's all of it.
[06:24] <tjaalton> let me check that
[06:25] <didrocks> I think jasoncwarner is more or less up to date
[06:25] <didrocks> so if he's still experiencing it…
[06:40] <didrocks> tjaalton: any hint?
[06:41] <tjaalton> didrocks: reopened, no idea as of yet
[06:42] <didrocks> tjaalton: ok, thanks :)
[06:42] <didrocks> I confirmed I have it regularly
[06:42] <tjaalton> how regularly?
[06:42] <didrocks> like, after 5/6 suspend
[06:42] <tjaalton> ok
[06:42] <didrocks> I didn't get it in the last week because I didn't suspend as much before rebootin
[06:42] <didrocks> rebooting*
[06:43] <tjaalton> I tried to reproduce it by turning the screen off/on with xrandr, but I'm hitting _other_ bugs that way
[06:43] <tjaalton> and different ones depending on the intel generation..
[06:43] <tjaalton> talk about frustration
[06:43] <didrocks> "nice"
[06:43] <didrocks> tjaalton: turning the screen off/on, I didn't get it, really suspsend/resume
[06:44] <tjaalton> ok, wonder what it's doing differently then..
[06:44] <didrocks> yeah, I'm not sure, maybe turning the screen off/on can triggers it as well, just never experienced it that way
[06:45] <tjaalton> it's not just the dpms cycle then, different bug that way
[06:45] <tjaalton> but I'll script suspend/resume and try to hit it while xtracing compiz..
[06:45] <didrocks> you, and resume, basically, you end up either with:
[06:45] <didrocks> - black screen, and if you kill gnome-screensaver, sometimes the background
[06:45] <didrocks> - or just the background
[06:46] <didrocks> you have to kill compiz and starts metacity
[06:46] <tjaalton> oh if you just have the background, then it's the same I get with xrandr
[06:46] <didrocks> restarting compiz doesn't work
[06:46] <tjaalton> or maybe not
[06:46] <didrocks> glxgears works
[06:46] <tjaalton> a vt-change resumes it
[06:46] <didrocks> no, it doesn't have any impact here
[06:46] <tjaalton> this with snb, 965gm hangs properly
[06:46] <didrocks> but some other games, more gl demanding don't
[06:47] <didrocks> I really have to reboot to put back the driver in a good "gl state"
[06:47] <didrocks> hum, I have an x220, let me see what chipset
[06:47] <tjaalton> yeah that metacity thing is what I've mostly seen
[06:47] <tjaalton> snb
[06:47] <tjaalton> same as on my t420s
[06:47] <didrocks> 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
[06:47] <didrocks> if this is snb :)
[06:47] <tjaalton> still running precise there, and seeing this
[06:47] <tjaalton> yep
[06:47] <didrocks> yeah, I got it once or twice in precise
[06:47] <didrocks> but really rare
[06:47] <didrocks> a lot more in quantal
[06:48] <tjaalton> another sandybridge on quantal, 965m on quantal
[06:48] <tjaalton> thumper said he's seeing it on every login or so
[06:48] <tjaalton> and I couldn't reproduce it with the new unity stack
[06:48] <didrocks> ok, should be put the bug on the release tracker list?
[06:48] <tjaalton> just the normal way, ie. not that frequently
[06:48] <tjaalton> yeah
[06:48] <didrocks> seems quite important
[06:48] <didrocks> doing it then, thanks!
[06:48] <tjaalton> yes, oem-important too
[06:49] <didrocks> tjaalton: when I'm in that state
[06:49] <didrocks> can I give you any relevant info?
[06:49] <tjaalton> don't think so, we have the trace from compiz being hung, xserver waiting
[06:49] <didrocks> ok
[06:49] <tjaalton> need to know what compiz was doing
[06:49] <tjaalton> and ttbomk xtrace should tell that
[06:50] <didrocks> ttbomk?
[06:50] <tjaalton> to the best of my knowledge :)
[06:50] <didrocks> oh, didn't know that one :)
[06:50] <didrocks> ok, I'll try that
[06:58] <chrisccoulson> good morning everyone
[06:58] <jibel> after using my desktop for a while, all the indicators become very slow, I mean when I click on an indicator it takes several seconds to display the menu. Is it a known issue ?
[06:59] <didrocks> jibel: not that I noticed/saw. Maybe check with larsu when he's online?
[06:59] <didrocks> hey chrisccoulson
[06:59] <didrocks> if not, we can add it to the release list
[06:59] <didrocks> bug*
[06:59] <jibel> didrocks, ok, will do. thanks
[06:59] <chrisccoulson> hey didrocks, how are you?
[07:00] <didrocks> chrisccoulson: I'm good, thanks! yourself? how was your flight?
[07:00] <chrisccoulson> didrocks, uneventful ;)
[07:00] <didrocks> heh, no strike, nothing then? :)
[07:00] <didrocks> chrisccoulson: as you are with the thunderbird guys, can we remove the chat buttons please please please? ;)
[07:00] <chrisccoulson> heh
[07:01] <jibel> and also I got bug 1047117 with this morning's updates
[07:01] <ubot2> Launchpad bug 1047117 in libgnome "package libgnome2-bin not installed failed to install/upgrade: trying to overwrite /usr/share/man/man1/gnome-OPEN.1.gz , which is also in package libgnome2-0 2.32.1-2ubuntu1" [High,Confirmed] https://launchpad.net/bugs/1047117
[07:05] <didrocks> ah, let me look :)
[07:06] <didrocks> I see seb128 runs away on vacation after breaking post-beta1! :-)
[07:18] <didrocks> jibel: fixed
[07:19] <jibel> didrocks, fantastic !
[07:48] <mvo> pitti: do you think the recent updates in https://code.launchpad.net/~mvo/aptdaemon/support-change-credentials-on-add-repo/+merge/112098 are sufficient? I would love to merge/upload this soon(ish)
[07:49] <pitti> mvo: guten Morgen, wie gehts?
[07:49]  * pitti looking
[07:49] <mvo> pitti: guten morgen! gut, danke
[07:49] <mvo> pitti: und selbst ?
[07:50] <tjaalton> didrocks: btw, do you use the screen locker when suspending?
[07:50] <didrocks> tjaalton: right, but even trying to kill it from tty1, doesn't change anything (perhaps just from the black background to the wallpaper, but I'm unsure)
[07:51] <didrocks> meaning, compiz is locked
[07:51] <pitti> mvo: gut, danke!
[07:51] <tjaalton> didrocks: yeah I know, you can unlock it and then you see the mouse cursor changing. I was just thinking of how to best reproduce it
[07:51] <tjaalton> ran 11 cycles without the lock screen, now trying with it
[07:52] <didrocks> let's hope that will help triggering it :)
[07:53] <tjaalton> indeed
[07:53] <pitti> mvo: MP updated
[07:53] <pitti> mvo: odd, I didn't get mail with your recent reponse
[07:54] <tjaalton> meh, testing with fwts doesn't lock the screen when it suspends
[07:54] <mvo> pitti: cool, thanks, I will fix the remaining bits next
[07:55] <pitti> mvo: as for the integration test caes with apt, that's harder to set up of course (writing an apt conf file and running apt-get, etc.); but as long as you tested it manually, that's fine
[07:55] <pitti> I don't think it needs to block this, it was just a question
[07:56] <mvo> pitti: thanks, its a good point, I'm not sure I will manage to find time for it currently but I do think it would be really good to have
[08:11] <chrisccoulson> didrocks, oh, are you getting compiz hangs when resuming from suspend too?
[08:12] <pitti> hey chrisccoulson, how are you? made it to Warsaw?
[08:12] <didrocks> chrisccoulson: yeah, seems we can start an union :)
[08:12] <chrisccoulson> hey pitti, i'm good thanks. how are you?
[08:12] <pitti> I'm fine, thanks!
[08:12] <chrisccoulson> i got to warsaw ok :)
[08:12] <chrisccoulson> didrocks, yeah, i keep getting that here :(
[08:13] <didrocks> chrisccoulson: do you have any particular way to trigger it more so that tjaalton can debug?
[08:13] <chrisccoulson> didrocks, not really. it's quite random
[08:13] <tjaalton> chrisccoulson: what hw do you have?
[08:13] <chrisccoulson> tjaalton, intel
[08:13] <tjaalton> which generation :)
[08:14] <tjaalton> sandybridge, ivy-, ironlake, 965, earlier?
[08:19] <dpm> hi pitti, good morning and a quick question: I've got a 12.04 pc where jockey fails to install the nvidia driver. What's the best way to manually install nvidia and uninstall nouveau?
[08:19] <pitti> dpm: how does it fail?
[08:19] <pitti> dpm: "sudo apt-get install nvidia-current" should suffice
[08:23] <RAOF> dpm: Careful; there are reasons other than Jockey bugs why Jockey might not offer to install the driver :)
[08:23] <pitti> that's why I ask -- whether it doesn't detect it, or whether it tries to install but the pacakge fails
[08:25] <dpm> pitti, at the end of the process, jockey tells me that it could not install the driver and that I should look at /var/log/jockey.log (will look at it in a minute). Installing the driver manually works (the installation part), but then I get into a black screen. Which is weird, as this is a fresh install on a computer where 12.04 + nvidia has been working before
[08:26] <pitti> perhaps you can pastebin jockey.log
[08:28] <dpm> pitti, can't get into the pc right now, it's got wireless network only and I cannot get into it through the command line, might take me a few minutes
[08:29] <pitti> dpm: wifi should be fine; we configure system connections by default now, so if you are in a VT you shold still have wifi
[08:30] <dpm> ah, cool, let me try
[08:34] <tjaalton> didrocks: 30 cycles with the screenlocker, and before that maybe 20 without
[08:35] <didrocks> waow, seems that you are in a luckier hw
[08:35] <didrocks> chrisccoulson: yo uhave an x220 as well?
[08:35] <didrocks> tjaalton: isn't sandybridge the mixed nvidia/intel one?
[08:35] <dpm> man, I can't believe I can't get into the GRUB menu, I've been hammering the shift key for 2 minutes
[08:35] <didrocks> tjaalton: I only have the intel card here
[08:35] <tjaalton> didrocks: no, sandybridge is a codename for the intel part. you can have it with optimus or without
[08:36] <didrocks> ah ok ;)
[08:37] <tjaalton> and I tested this with a dell v1450 on quantal, will try with the thinkpad on precise next
[08:37] <didrocks> tjaalton: maybe you can try on a live quantal on the thinkpad?
[08:38] <dpm> RAOF, so on that computer I've got several issues: when the nouveau driver is used, the system becomes extremely slow, to a point that's unusable (mouse moves in increments that are minutes long). Any ideas what it could be, or how to fix that until I can install nvidia?
[08:39] <tjaalton> didrocks: that's possible yes
[08:40] <didrocks> tjaalton: I think you will have higher chance to trigger it that way
[08:41] <didrocks> and beta1 live image is soooo shiny :)
[08:42] <tjaalton> :)
[08:43] <tjaalton> didrocks, chrisccoulson: do you use amd64 or i386? how much memory?
[08:44] <didrocks> tjaalton: amd64, 8Go of memory
[08:44] <tjaalton> nice
[08:44] <didrocks> GB*
[08:44] <didrocks> quite new, yeah ;)
[08:44] <tjaalton> hmm no i386 images at all
[08:45] <tjaalton> i'm all amd64 as well
[08:46] <dpm> pitti, http://pastebin.ubuntu.com/1190411/ (the pc has got an integrated ati graphics card using fglrx, not sure if that interferes with the nvidia card I'm trying to get working now). Right now even after having installed nvidia-current manually, it seems to be loading nouveau or something else
[08:47] <pitti> dpm: hm, this log doesn't even have an attempt of installing the driver
[08:48] <tjaalton> dpm: guess you need to disable the integrated one from bios
[08:48] <pitti> dpm: so it might very well conflict with the ati card; can you disable that in the BIOS? what does lspci show?
[08:50] <dpm> tjaalton, pitti, unfortunately, I can't. But this system has been working in the past, with the nvidia card and the 'non-disableable' ati integrated chip
[08:50] <RAOF> dpm: If you're using fglrx, no other video driver will work.
[08:50] <dpm> aaah
[08:50] <RAOF> dpm: Same as nvidia; if you're using nvidia, no other video driver will work.
[08:50]  * dpm uninstalls fglrx
[08:50] <RAOF> That should fix it :)
[08:52] <tjaalton> oh, missed that part.. :)
[08:54] <dpm> RAOF, just out of interest, though, any clue about nouveau's slowness (to the point that it's unusable)? That happened also during the LiveCD install (thus no fglrx installed), I had to remove the nvidia card and do the install with the integrated ati one
[08:55] <dpm> (it all works after uninstalling fglrx, thanks for the help, guys!)
[09:10] <RAOF> dpm: Without logs it's not clear what's happening; if I had to guess, I'd suspect that something went dolally and you're using the llvmpipe software renderer rather than nouveau.
[09:27] <dholbach> hiya
[09:27] <dholbach> can somebody take a look at https://code.launchpad.net/~logan/ubuntu/quantal/notify-osd/debian-merge/+merge/118465?
[09:28] <dholbach> also https://code.launchpad.net/~bcurtiswx/ubuntu/precise/telepathy-glib/0.18.2-0ubuntu1/+merge/117176 maybe
[09:52] <ritz> chrisccoulson, ping
[09:56] <vuntz> pitti: may I suggest simplifying the NEWS entries for pygobject? I think it lists all changes, even the ones that are, well, useless to know about :-)
[09:57] <vuntz> pitti: (ChangeLog is there for people interested in all the details)
[09:57] <vuntz> (hi!)
[09:57] <pitti> vuntz: hm, I already take out stuff like "bump configure version"; I do like to describe the actual changes in succint form, with bug refs
[09:57] <pitti> vuntz: oui, et bonjour! ça va?
[09:59] <vuntz> bien, bien :-)
[09:59] <vuntz> pitti: "Update .gitignore"? :-)
[09:59] <pitti> vuntz: right, I forgot to take that out
[10:00] <vuntz> pitti: "tests: Replace deprecated assertEquals() with assertEqual()"
[10:00] <vuntz> pitti: I also see at least three lines about pep8 in the 3.3.1 entry
[10:01] <vuntz> pitti: of course, what you do is already much better than a "git shortlog" (which many tarballs have as NEWS...)
[10:02] <pitti> vuntz: still, thanks for pointing out; I'll apply more care next tiem
[10:03] <vuntz> it's never easy to find the right level of details, especially since pygobject is developer-oriented (compared to apps)
[10:03] <vuntz> anyway. I'm glad to see so much love given to pygobject
[10:03] <vuntz> pitti: you rock :-)
[10:04] <vuntz> oh, btw, an alternative is to provide a short paragraph highlighting the important bits for distributors
[10:05] <vuntz> (and keep the longer list, which can be useful for hackers)
[10:53] <tjaalton> didrocks: heh, locking the screen doesn't work on the beta1 live :)
[10:54] <didrocks> jibel: known? ^
[10:54] <didrocks> ah, on the live
[10:54] <didrocks> yeah, I think you have no ubuntu password
[10:54] <didrocks> so desactivated
[10:54] <tjaalton> right
[10:54] <didrocks> you should be able to force it in g-c-c
[10:54] <tjaalton> it's activated there
[10:54] <tjaalton> by default
[10:54] <didrocks> interesting
[10:55] <didrocks> idea
[10:55] <didrocks> tjaalton: create another user in the live system
[10:55] <didrocks> log with it
[10:55] <didrocks> you should have a normal session then
[10:56] <tjaalton> yep, setting the passwd wasn't enough
[10:56] <didrocks> starting with a fresh user will hopefully do it
[10:57] <tjaalton> same thing
[10:57] <tjaalton> but I'll just trace it from precise, should be the same bug :)
[10:57] <tjaalton> it=compiz
[10:58] <didrocks> hoping you will trigger it easily on it, I just had it once there
[10:58] <didrocks> (on precise)
[10:59] <tjaalton> we'll see
[10:59] <tjaalton> probably easier if I have two sessions open
[11:01] <tjaalton> ha, first cycle :D
[11:01] <didrocks> \o/
[11:01] <tjaalton> so I'd say something has changed for the better.. but still
[11:03] <didrocks> well, I never experienced that on precise apart from one time, so it's really random and day-of-the-week related :)
[11:05]  * MCR1 hates day-of-the-week related bugs, because he always hits those while noone else can reproduce them...
[11:05] <tjaalton> screen lock had nothing to do with it, had it off for this session
[11:07] <didrocks> ok, at least, it's safe then :)
[11:07] <tjaalton> hehe, yes
[11:12] <tjaalton> interesting that switching to another running session after resume immediately suspends the machine again
[11:12] <tjaalton> both precise and quantal
[12:04] <jibel> didrocks, not to my knowledge
[12:05] <jibel> urgh, today's updates broke my netboot again :(
[12:05] <jibel> *netbook
[12:08] <jibel> bug 1047306
[12:08] <ubot2> Launchpad bug 1047306 in unity "[Quantal] [Intel Atom] Unity 2012/09/07 updates broke it all" [Critical,Confirmed] https://launchpad.net/bugs/1047306
[12:20] <mpt> JohnLea, bug 668382
[12:20] <ubot2> Launchpad bug 668382 in software-center "Unclear warning before removing critical packages" [Medium,Triaged] https://launchpad.net/bugs/668382
[12:21] <JohnLea> mpt; bug 1047315
[12:21] <ubot2> Launchpad bug 1047315 in ayatana-design "Dash - All applications which are a dependency of Ubuntu Desktop should not have an uninstall button in their preview " [High,Fix committed] https://launchpad.net/bugs/1047315
[12:22] <didrocks> jibel: hum, unity didn't change since beta1
[12:22] <didrocks> jibel: do you have the list of things you updated?
[12:22] <didrocks> meaning, you didn't test beta1 on that netbook?
[12:23] <jibel> didrocks, yes pasting a list of this morning's updates
[12:23] <jibel> didrocks, to question 2 - no, I need this machine
[12:24] <didrocks> so, it can be a previous unity version which is guilty, right?
[12:24] <jibel> didrocks, no, it was broken, then fixed, then broke again today
[12:24] <didrocks> "nice"
[12:25] <didrocks> jibel: well, not today, but on Monday I guess
[12:25] <didrocks> (you didn't update since monday, right?)
[12:25] <didrocks> as it's the last unity upload
[12:25] <jibel> didrocks, bug 1042211 was my original report
[12:25] <ubot2> Launchpad bug 1042211 in mesa "[quantal] [regression] [i915] Corrupted display, desktop and menus don't repaint correctly using Mesa 9.0 (8.0.4 works)" [Critical,Incomplete] https://launchpad.net/bugs/1042211
[12:26] <jibel> didrocks, something broke between the 4th and 7th
[12:26] <didrocks> jibel: please paste the list of your updates
[12:26] <didrocks> I see no unity/compiz/nux uploads meanwhile
[12:26] <didrocks> so maybe a mesa/xorg thing
[12:30] <jibel> didrocks, apt history https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1047306/+attachment/3298087/+files/history.log
[12:30] <ubot2> Launchpad bug 1047306 in unity "[Quantal] [Intel Atom] Unity 2012/09/07 updates broke it all" [Critical,Confirmed]
[12:31] <didrocks> jibel: yeah, so no unity/nux/compiz
[12:31] <didrocks> but mesa
[12:31] <didrocks> I think we know who to turn to :)
[12:32] <didrocks> jibel: do you have time to rollback some mesa package to confirm?
[12:32] <didrocks> jibel: anyway, I'm adding that and will ping RAOF/bryceh about those
[12:33] <jibel> didrocks, ack, I'll downgrade the mesa stack
[12:33] <didrocks> jibel: thanks, keep me in touch
[12:33]  * didrocks targets for quantal
[12:38] <didrocks> tjaalton: ^
[12:38] <didrocks> you might be interested as the upload :)
[12:38] <didrocks> uploader*
[12:38] <didrocks> should I assign this to you?
[12:40] <tjaalton> meh
[12:40] <tjaalton> maybe, but it's weekend now, nothing upstream unless 13b8eb64523a70af30b576271886a737f51dbe40 would fix anything
[12:40] <tjaalton> now/soon
[12:40] <didrocks> tjaalton: If jibel confirms the downgrade is working, should we rather revert?
[12:41] <didrocks> the chipset is quite common
[12:41] <didrocks> and breaking that for the week-end…
[12:41] <tjaalton> that would reopen bug 1046933
[12:41] <ubot2> Launchpad bug 1046933 in mesa "glsl/linker: array buffer overrun [CVE-2012-2864]" [Undecided,New] https://launchpad.net/bugs/1046933
[12:41] <tjaalton> though that could be added back
[12:42] <didrocks> tjaalton: the CVE commit would be easy to backport you think?
[12:42] <tjaalton> a oneliner
[12:42] <didrocks> not really big apparently, yeah :)
[12:43] <didrocks> tjaalton: can you handle it or do you want me to do it?
[12:44] <tjaalton> either way
[12:44] <tjaalton> did beta already have the same unity/compiz?
[12:45] <tjaalton> ok saw the backscroll
[12:45] <didrocks> tjaalton: yeah, I confirmed this
[12:45] <didrocks> look at the list of upgrade
[12:45] <didrocks> attached to the bug
[12:45] <didrocks> seems that mesa is the only obvious possible offender, right?
[12:46] <tjaalton> ok
[12:49] <didrocks> tjaalton: don't put too much pressure on you, if you can't catch what's wrong, we can go the easy way on the revert + the patch
[12:49] <didrocks> hoping that jibel will confirm that with the older mesa stacks, it works
[12:49] <tjaalton> we'll see
[12:51] <didrocks> tjaalton: should he revert to 9.0~git20120821.c1114c61-0ubuntu1 or 9.0~git20120821.c1114c61-0ubuntu2?
[12:51] <didrocks> as 9.0~git20120821.c1114c61-0ubuntu2 was never published in beta1
[12:52] <didrocks> tjaalton: ignore my question :)
[12:52] <tjaalton> it wasn't?
[12:52] <tjaalton> ah
[12:52] <didrocks> was puzzled by the "superseeded" date on launchpad :)
[12:52] <tjaalton> well, three commits to src/mesa/drivers/dri/i915 since the previous snapshot..
[12:52] <didrocks> could have been worse… :)
[12:53] <tjaalton> "mesa: Use a new, more specific hook for shader uniform changes."
[12:53] <tjaalton> sounds plausible
[12:53] <didrocks> shader making an app segfault, sounds too familiar :)
[12:56] <dholbach> I asked earlier, maybe now somebody can take a look at https://code.launchpad.net/~logan/ubuntu/quantal/notify-osd/debian-merge/+merge/118465?
[12:56] <dholbach> and https://code.launchpad.net/~bcurtiswx/ubuntu/precise/telepathy-glib/0.18.2-0ubuntu1/+merge/117176 maybe :)
[12:56] <tjaalton> I can build a test package and if that doesn't work, a revert is possible unless Sarvatt can figure out the cause
[12:57] <didrocks> dholbach: I'll find someone to review them
[12:57] <didrocks> tjaalton: sure
[12:57]  * dholbach hugs didrocks
[12:57]  * didrocks hugs dholbach
[12:57] <didrocks> robru: hey!
[12:59] <zyga> (repost from #ubuntu-unity): hey everyone, I have just noticed that classic desktop in 12.10 has wrong order of window control buttons -> in unity that order is [x] [-] [o] while in classic mode they are [x] [o] [-] -- is this by design?
[13:00] <jibel> didrocks, tjaalton I downgraded mesa to 9.0~git20120821.c1114c61-0ubuntu2 and the machine is back to a working state
[13:00] <didrocks> thanks jibel :)
[13:00] <jbicha> zyga: that's probably my fault, is there a bug # for that?
[13:01] <tjaalton> jibel: ok do you have a beefy machine to build mesa on?
[13:01] <jbicha> I use gnome-shell too much :|
[13:01] <tjaalton> i guess atom is 32bit?
[13:01] <zyga> jbicha, not that I know, I wanted to ask before reporting it
[13:01] <zyga> jbicha, on gnome-panel? or on metacity?
[13:02] <jbicha> I can fix it without a bug
[13:02] <zyga> k, thanks!
[13:02] <zyga> :)
[13:02] <zyga> tjaalton, there are 64bit versions of atom
[13:02] <tjaalton> jibel: are you on amd64?
[13:03] <tjaalton> I actually have one too, but not with that generation of gfx
[13:04] <tjaalton> jibel: ping? I can build mesa for you in 5min if you do
[13:04] <jibel> tjaalton, i386
[13:04] <tjaalton> duh
[13:04] <jibel> why would i run 64bit on a netbook with 2G of ram
[13:05] <tjaalton> hmm wonder how long it takes to build a i386 schroot
[13:05] <zyga> jibel, to get more registers, atom has no out of order execution or register renaming IIRC and really suffers from performance as a side effect
[13:06] <jibel> yeah, performance on a netbook
[13:07] <tjaalton> ok mk-sbuild is running..
[13:08] <didrocks> don't tell bad thing about netbooks… It happened that unity built faster on one of mine even if I dputed at the same time to a ppa :)
[13:08] <didrocks> (and it was inside a pbuilder)
[13:09] <tkamppeter> pitti, can you upload cups-filters to Debian and to Quantal? Thanks.
[13:10] <sbte> larsu, hi, is there a way yet to connect to the messaging menu entry of an application? (not a source)
[13:18] <tjaalton> jibel: building
[13:28] <tjaalton> jibel: test packages being copied to http://koti.kapsi.fi/~tjaalton/lp1047306
[13:29] <tjaalton> should be enough to just get liblg1-mesa-dri and -glx
[13:34] <tjaalton> jibel: ping? please test
[13:37] <larsu> sbte, what do you mean? Any application can appear in the messaging menu
[13:37] <tjaalton> ok I'm gone ->
[13:38] <tjaalton> didrocks: I'll check here in 30min
[13:38] <didrocks>  tjaalton: ok, thanks :)
[13:38] <sbte> larsu, yes, but if the entry is clicked, I don't know what signal is emitted
[13:38] <sbte> if any
[13:39] <larsu> sbte, ah! no, you don't get a signal, the messaging menu will execute the "Exec" line from the .desktop file
[13:39] <larsu> (same for the shortcut actions)
[13:40] <jibel> tjaalton, thanks. testing
[13:40] <sbte> larsu, why not let the application handle it?
[13:43] <larsu> sbte, you can handle it, as long as your application is single-instance (which it really should be if you want to integrate with the messaging menu)
[13:43] <sbte> larsu, it is
[13:43] <larsu> sbte, why exactly do you need it?
[13:44] <sbte> larsu, to unhide it
[13:44] <larsu> sbte, do you use GApplication? (or GtkApplication)
[13:44] <larsu> if it is single instance, you can wake up the main instance and unhide it
[13:44] <sbte> larsu, no, we're stuck with gtk2 because of a bugged gtk3 version in precise
[13:45] <larsu> sbte, precise doesn't have the new libmessaging-menu
[13:45] <didrocks> hey kenvandine!
[13:45] <larsu> sbte, you're using libunique then?
[13:45] <kenvandine> hey didrocks
[13:46] <sbte> larsu, no dbus
[13:46] <didrocks> kenvandine: how are you?
[13:46] <kenvandine> good
[13:46] <kenvandine> and you?
[13:46] <kenvandine> have a good vacation?
[13:46] <didrocks> yeah, were great! thanks :)
[13:46] <didrocks> small question on notify-osd
[13:46] <kenvandine> you missed all the fun :)
[13:46] <larsu> sbte, oh you're doing it manually. Well, just unhide your main instance when the application is started again. Where's the problem?
[13:46] <didrocks> heh, I heard about that
[13:47] <didrocks> I prepared a lot before leaving for the gsettings transition
[13:47] <didrocks> that was the fun on itself TBH :)
[13:47] <kenvandine> hehe
[13:47] <sbte> larsu, we also support multi-instance emesene
[13:47] <didrocks> does notify-osd has some merge-upstream like branches, or not?
[13:47] <sbte> in which case the messaging menu would fail I guess
[13:47] <sbte> it will start a new instance
[13:47] <kenvandine> didrocks, no
[13:48] <larsu> sbte, how should that work with the messaging menu? We don't support putting the same application into the menu multiple times.
[13:48] <kenvandine> merge from trunk i think
[13:48] <sbte> larsu, in precise you did
[13:48] <kenvandine> it's the old way we did DX packages
[13:48] <larsu> sbte, ... anymore
[13:48] <kenvandine> we've hardly touched it in several cycles
[13:48] <sbte> larsu, if you just let the application handle the signal then it can be supported
[13:49] <sbte> otherwise we have to drop the messaging menu and use indicators only, but we don't want that
[13:49] <didrocks> kenvandine: ah ok, so trunk has the packaging?
[13:50] <larsu> sbte, you want emesene to appear multiple times in the messaging menu?
[13:50] <larsu> sbte, how would that be useful?
[13:50] <larsu> sbte, how would the user know which menu item starts which instance?
[13:50] <sbte> larsu, well, if you're logged in to google talk and msn
[13:51] <larsu> sbte, emesene needs two windows and two processes for that?
[13:51] <sbte> larsu, by setting a different label?
[13:51] <sbte> larsu, yes
[13:51] <larsu> sbte, the label comes from the .desktop file
[13:51] <sbte> it's a single session client
[13:51] <sbte> on purpose
[13:51] <jibel> tjaalton, mesa 9.0~git20120903.e1673d20-0ubuntu2 doesn't fix the issue
[13:51] <larsu> sbte, what's the purpose?
[13:51] <sbte> larsu, that we can support all features msn has
[13:52] <sbte> we're the only client that actually still does it
[13:52] <larsu> sbte, yeah and that's pretty cool. But you said you need two instances of emesene running to be logged into msn anf gtalk
[13:52] <sbte> yes
[13:53] <larsu> sbte, again, why?
[13:54] <larsu> sbte, the messaging menu always pulls the label from the .desktop file, so that it is the same no matter if the application is running or not
[13:54] <kenvandine> didrocks, no, trunk doesn't
[13:54] <kenvandine> but the packaging branch is based on trunk
[13:54] <kenvandine> so you can merge back from trunk i think
[13:54] <sbte> larsu, well, it has always worked fine for me anyway in precise and earlier
[13:55] <larsu> sbte, when you started your system without emesene running, did you have two entries of it in the messaging menu?
[13:55] <sbte> anyhow, since it's not possible to do this I'll just mess a bit with dbus and see how far I can get
[13:56] <sbte> larsu, no, because we don't set it in the messaging menu before starting emesene
[13:56] <didrocks> ah ok, thanks kenvandine :)
[13:57] <larsu> sbte, hm, it's much more useful to have it in there when the application is not running. And it would be consistent with all other apps
[13:57] <larsu> sbte, you could always have different .desktop files for the gtalk and msn versions, that might solve your problem
[13:58] <sbte> larsu, not if someone wants to login with two gtalk accounts for example
[13:58] <sbte> anyhow
[13:58] <sbte> I'll ask our packager to register emesene to show in the menu
[13:59] <sbte> or should we create the config files at startup?
[13:59] <larsu> sbte, it'll show up in the menu starting from the first call to messaging_menu_app_register, so after a user started it for the first time
[14:00] <sbte> larsu, yes, but you were talking about showing it when starting the system right
[14:00] <larsu> sbte, yes, from then on, it will always show up
[14:00] <larsu> (until you call _unregister() )
[14:00] <sbte> ah
[14:00] <larsu> sbte, that's by design: we only want applications in there that a user actively uses
[14:01] <larsu> sbte, in quantal the menu will not even be visisble by default
[14:01] <sbte> larsu, good to know
[14:01] <sbte> thanks
[14:02] <larsu> sbte, the only thing you should do is add "X-MessagingMenu-UsesChatSection: true" to the .desktop file if you want to get signals from the global online status
[14:02] <larsu> which I assume you do want for emesene
[14:03] <sbte> larsu, it seemed to work just fine without it
[14:03] <larsu> sbte, actually, you're right. But you should add it nevertheless because the chat section will only show up when at least one application is configured to use it
[14:04] <sbte> larsu, ok
[14:04] <sbte> larsu, thanks for the new API btw, it's a lot better than the old one
[14:05] <larsu> sbte, glad to hear :)
[14:05] <sbte> 300 lines of code to about 100
[14:05] <sbte> :P
[14:05] <larsu> sbte, let me know if you run into any troubles or bugs, it's all fairly new
[14:05] <sbte> larsu, I will
[14:05] <sbte> I now know where to find you ;P
[14:05] <larsu> :)
[14:06] <sbte> anyhow, I got to go, so cya
[14:06] <larsu> ciao
[14:11] <tjaalton> jibel: crap, thanks for testing
[14:12] <tjaalton> didrocks: you can revert to the previous one now
[14:12] <jibel> tjaalton, yw. let me know if you need other tests
[14:13] <tjaalton> jibel: not before next week :/
[14:13] <didrocks> tjaalton: sure, no issue in reintroducing this CVE?
[14:14] <didrocks> I just dget the previous version without changing anything, right?
[14:16] <tjaalton> didrocks: you can apply the cve fix if you like :)
[14:16] <didrocks> tjaalton: ok, doing
[14:17] <tjaalton> thanks
[14:17] <didrocks> yw :)
[14:20] <jbicha> so who's in charge now that Seb's on holiday?
[14:23] <jbicha> hmm, ok, would anyone like to sponsor lp:~ubuntu-desktop/indicator-printers/ubuntu ?
[14:23] <didrocks> jbicha: it should be me
[14:23] <didrocks> jbicha: I'm adding that to my list
[14:23] <jbicha> didrocks: thanks :)
[14:24] <didrocks> jbicha: hum
[14:24] <jbicha> it was a trick question, I was trying to figure out who I could give extra work to...
[14:24] <didrocks> jbicha: this will have side-effects
[14:24] <didrocks> heh, I saw that :)
[14:24] <didrocks> jbicha: so, when you have a A | B
[14:25] <jbicha> didrocks: I think it matches what the other indicators do
[14:25] <didrocks> the seed will look for A first
[14:25] <didrocks> let me look at the other and if the seed operator changed
[14:25] <didrocks> before checking B, it would pull A in the seed IIRC
[14:25] <didrocks> (not apt, just the seed)
[14:26] <jbicha> fighting with the seeds is a pain
[14:26] <didrocks> and I know who wins :)
[14:26] <jbicha> ubuntu-desktop can cheat some times by keeping some things in universe
[14:27] <didrocks> ok, this should have changed
[14:27] <didrocks> because indicator-messages indeed uses that
[14:27] <mitya57> FWIW, indicator-applet Provides: indicator-renderer, so only the latter can be kept
[14:28] <didrocks> mitya57: what if you install an indicator without having any renderer?
[14:28] <didrocks> virtual package can't have a "prefered" one
[14:28] <jbicha> I'm fine with indicator-applet in the gnome remix, and since indicator-applet is in universe, it should be fine, right?
[14:29] <didrocks> jbicha: right, I think that's universe which is cheating with the seed TBH :)
[14:29] <didrocks> jbicha: sponsoring
[14:45] <jbicha> didrocks: could you also giveback clutter-1.0, I'm waiting on it to upload the next gnome-shell
[14:46] <didrocks> jbicha: done
[14:47] <didrocks> jbicha: can you look at indicator-printers?
[14:48] <didrocks> ask larsu if needed :)
[14:48] <didrocks> (it FTBFS in case yo udidn't notice)
[14:48] <larsu> didrocks, FTBFS?
[14:48] <didrocks> Fail To Build From Source
[14:49] <jbicha> ooh, it worked a week ago :(
[14:49] <didrocks> larsu: and a new acronym to your vocabulary! :)
[14:49] <didrocks> larsu: hey, btw, how are things going?
[14:49] <larsu> didrocks, oh, do you have the build log somewhere? The code hasn't been touched for a while
[14:49] <didrocks> sure
[14:49] <didrocks> a prefer arch to see the failure? ;)
[14:49] <jbicha> "dereferencing pointer to incomplete type" -- that sounds above my level
[14:49] <didrocks> (j/k)
[14:49] <didrocks> https://launchpadlibrarian.net/115063684/buildlog_ubuntu-quantal-amd64.indicator-printers_0.1.6-0ubuntu2_FAILEDTOBUILD.txt.gz
[14:49] <larsu> didrocks, thing are going good, was a bit hectic during ff, as usual ;)  How was your vacation?
[14:49] <didrocks> larsu: ^
[14:49] <larsu> thakns
[14:50] <didrocks> larsu: really nice, no 3G connexion, so relaxing :)
[14:50] <didrocks> larsu: but in the rush as soon as I'm back, especially today!
[14:50] <larsu> didrocks, yeah that's the only way to go. Leave all that internet behind ;)
[14:50] <didrocks> completely :)
[14:50] <didrocks> but Internet continued without me
[14:50] <didrocks> I'm shocked :)
[14:51] <larsu> haha
[14:52] <mterry> jdstrand, so did you actually do a security review of python-urllib3 when auditing python-requests?
[14:52] <larsu> didrocks, jbicha, I know the issue, it's because cups changed API. I'll fix it right now, should be easy
[14:52] <jdstrand> mterry: I'm happy with it from a security pov now that I patched it for cert verification
[14:52] <jbicha> larsu: :)
[14:52] <didrocks> larsu: thanks \o/
[14:52] <mterry> jdstrand, awesome, thanks!
[14:52] <jdstrand> np
[14:55] <didrocks> tjaalton: mesa revert + CVE fix uploaded FYI
[14:58] <larsu> jbicha, just pushed a fix into trunk. it's a two-line patch, do you need a release for it or are you fine backporting it?
[15:00] <jbicha> larsu: I don't know how to deal with the bzr merge thing unity & the indicators do, didrocks is expert at it though
[15:01] <larsu> jbicha, oh, don't worry about it, I'll do a release
[15:01] <didrocks> one sec
[15:01] <didrocks> let me look at the package for this one :)
[15:01] <jbicha> we'd have to bug didrocks to sponsor it anyway ;)
[15:01] <didrocks> ok, it's a merge-upstream workflow
[15:01] <didrocks> so I can handle it :)
[15:01] <larsu> didrocks, ya, seb made it
[15:01] <larsu> didrocks, cool, thanks.
[15:02] <didrocks> larsu: thanks for the quick fix!
[15:02] <larsu> didrocks, pleasure ;)
[15:07] <didrocks> larsu: beautiful builds indeed ;)
[15:07] <didrocks> uploaded
[15:23] <zyga> hey, who is working ubiquity?
[15:24] <zyga> I have just noticed a strange bug in beta1
[15:24] <zyga> with the user picture step
[15:25] <ogra_> there weere some fixes to that part recently
[15:25] <ogra_> at least wrt camera handling
[15:26] <ogra_> zyga, try #ubuntu-installer
[15:26] <zyga> ogra_, thanks
[15:26]  * ogra_ just noticed we're in -desktop 
[15:47] <tjaalton> didrocks: great, thanks
[15:48] <didrocks> yw :)
[15:54] <robru> didrocks, hi, sorry. you rang?
[15:54] <didrocks> robru: yeah, I wanted to know how busy you were :)
[15:54] <didrocks> good morning btw :)
[15:54] <robru> didrocks, good morning ;-)
[15:55] <robru> didrocks, well, I guess I'm not super-ultra-busy like everybody else is. what do you need?
[15:55] <didrocks> robru: I would appreciate if you can review a SRU proposed by bcurtiswx: https://code.launchpad.net/~bcurtiswx/ubuntu/precise/telepathy-glib/0.18.2-0ubuntu1/+merge/117176
[15:56] <didrocks> it's a telepathy-glib update
[15:56] <didrocks> so checking that the update is the right one (0.18.1 -> 0.18.2) and that it's working on your precise box :)
[15:58] <robru> didrocks, hmmmm, ok
[15:58] <didrocks> thanks :)
[15:59] <robru> didrocks, gimme a sec though
[15:59] <didrocks> robru: take your time, I'm near EOW anyway and won't sponsor it today :)
[15:59] <robru> didrocks, alright, in that case I'll get to it a bit later.
[15:59] <robru> ;-)
[16:00] <didrocks> sure :)
[16:02] <tedg> mterry, Did you see my mail about the freerdp bug?  Thoughts?
[16:03] <mterry> tedg, oh, I put it in my queue, but didn't get to it, hold on
[16:03] <tedg> mterry, NP
[16:04] <mterry> tedg, I don't see special handling for "." in that patch?
[16:05] <mterry> tedg, you do handle " " for domain, but not hostname
[16:05] <tedg> mterry, It should be "." for domain.
[16:06] <mterry> tedg, unless I'm having eye problems, look like a space to me in the patch
[16:06] <tedg> Seems also that upstream has a fix for password from the terminal.  Not sure if we want that as well.
[16:06] <mterry> tedg, I looked at that patch
[16:06] <mterry> tedg, it turns off echo
[16:06] <tedg> Yup
[16:06] <tedg> mterry, Hmm, okay.  Perhaps I uploaded the wrong version of the patch...
[16:07] <mterry> tedg, which isn't a concern for piping, and it had this odd regression where it would always print "Password:" on the console even if we piped it in
[16:07] <mterry> tedg, so I figured best to wait.  I commented to upstream about the Password: print thing
[16:07] <tedg> Uhg, yes.  Wrong version, sorry.
[16:07] <tedg> The if statement is wrong as well.
[16:12] <tedg> If it makes you feel better, I sent the wrong version upstream as well :-)
[16:12] <tedg> Bother.  Lesson in going to sleep and uploading in the morning.
[16:23] <mterry> tedg, so the patch still doesn't have any special handling for hostname, but the bug mentions wanting to have it for both domain and hostname, right?
[16:24] <tedg> mterry, No, we really only need it for domain.
[16:24] <mterry> k
[16:24] <tedg> mterry, If you don't have a hostname you're SOL
[16:24] <mterry> heh
[16:24] <tedg> mterry, The problem is that if you don't have a domain, it makes the hostname your domain.
[16:24] <mterry> right, and then waits for hostname?
[16:24] <tedg> Yup
[16:25] <tedg> Actually, without the patch it doesn't.
[16:25] <mterry> oh
[16:25] <tedg> It gets disconnected, reuses the buffer and gets it kinda right.
[16:25] <mterry> heh
[16:25] <tedg> It's literally so wrong it's right.
[16:25] <mterry> tedg, so why didn't just passing an empty string for the domain work before?
[16:25] <tedg> Which is what made it hard to realize what was happening.
[16:26] <tedg> Because scanf skips over whitespace.
[16:26] <mterry> tedg, jerk move
[16:26] <tedg> Really, it should probably use newlines and have a better parsing algorithm, but that seemed like a bit patch.
[16:26] <tedg> And would change the behavior
[16:27] <tedg> Oh, oh, we should use XML!
[16:27] <tedg> :-)
[16:27] <mterry> :)
[16:30] <tedg> mterry, Do you know a good way to take screenshots of the greeter?
[16:30] <tedg> Wanted to write up a blog post...
[16:30] <mterry> tedg, shooot...  there is a way
[16:30] <mterry> a console commadn
[16:30] <mterry> that you can run in a vt
[16:30] <mterry> but can't remember the command
[16:30] <tedg> I can run it under Xephyr, but it makes the window too big.
[16:30] <mterry> tedg, import?
[16:30] <mterry> tedg, from imagemagick
[16:31] <mterry> tedg, which, by the way, is a terrible misuse of the command import
[16:31] <mterry> I mean, the word
[16:31]  * tedg has not used that before
[16:31] <mterry> tedg, looks like it will do the job, and I recall using it like that in the past
[16:33] <mterry> tedg, anyway, the patch looks fine
[16:33] <mterry> tedg, did you want me to apply it?
[16:34] <tedg> mterry, Yes please.  I'll make one for libpam-freerdp as well so that it puts the right data in the socket.
[16:34] <tedg> Funny usecase really.  I just want to use this on xrdp for Ubuntu, which requires there to be no domain :-)
[16:43] <mterry> tedg, fill out your dep3 headers in your patch next time :)
[16:44] <mterry> tedg, you still had boilerplate ones
[17:20] <davidcalle> mterry, hey
[17:20] <didrocks> have a nice week-end everyone!
[17:24] <davidcalle> mterry, thanks for the upload. By any chance, could you drop the dont_require_unreleased_unity.patch?
[17:25] <mterry> davidcalle, hello!
[17:25] <mterry> davidcalle, oh, I didn't see the Merger code in unity yet
[17:26] <mterry> davidcalle, or at least, I didn't see the MergeStrategy class in the unity source code
[17:27] <davidcalle> mterry, I believe it has been here for quite a long time, there was an issue with the effects of the method actually happening in the Dash, but it's fixed.
[17:28] <mterry> davidcalle, is the class called something different?  I just grepped the unity source for MergeStrategy and didn't see anything
[17:29] <davidcalle> mterry, found it, it's in libunity http://bazaar.launchpad.net/~unity-team/libunity/trunk/view/head:/src/unity-lens-merge-strategy.vala
[17:29] <mterry> ah
[17:29] <mterry> forgot that was a separate source
[17:30] <mterry> davidcalle, OK, sure can re-enable
[17:30] <mterry> gotta take a quick break now though, will do later
[17:31] <davidcalle> mterry, thanks, nothing urgent anyway :)
[18:17] <xnox> do we use ibus?
[18:20] <cyphermox> xnox normally no, unless you try to write in a language that requires it
[18:21] <xnox> cyphermox: ok. do we define GTK_IM_MODULE?
[18:21] <xnox> in the environment (live-cd) for example?
[18:25] <cyphermox> I haven't tried on the live cd; but yeah I think it's set when ibus is enabled
[20:42] <dupondje> new gnome-shell looks nice!
[20:42] <dupondje> some good improvements :)