[01:58] <RAOF> Huh. Has jockey-gtk broken? The package no longer contains anything but the .desktop file.
[01:58] <RAOF> Ah, software-sources.
[01:59] <RAOF> You know, Software Sources→Additional Drivers is not the most obvious place to find that :)
[02:47] <TheMuso> RAOF: I'd agree with that.
[02:47] <TheMuso> s/I'd/I/
[04:15] <pitti> Good morning
[05:03] <didrocks> good morning
[05:03]  * mterry waves at didrocks
[05:07] <didrocks> hey mterry
[05:08] <RAOF> Yo!
[05:28] <pitti> bonjour didrocks! est-ce que tu vas mieux aujourd'hui?
[05:30] <didrocks> pitti: guten morgen! Well, it's different, but still coughing a lot and I have to blow my noise quite frequently :/
[05:30] <pitti> RAOF: right, jockey-gtk is deprecated in favor of ubuntu-drivers-common and the UI in s-properties
[05:30] <didrocks> I hope that for next Monday, it will be ok
[05:31] <RAOF> pitti: It should probably no ship the useless desktop file :)
[05:33] <pitti> Mais oui, ce n'etait pas [intended]
[05:33] <pitti> my French only goes so far..
[05:34] <pitti> there's no jockey-gtk.install any more and nothing in debian/rules, hmm
[05:34] <didrocks> pitti: "voulu" :)
[05:35] <pitti> didrocks: ah, is that from "vouloir" ("want")?
[05:35] <didrocks> right ;)
[05:35] <pitti> merci!
[05:35] <didrocks> de rien :-)
[05:35] <pitti> RAOF: err, it doesn't?
[05:36] <pitti> it just has changelog and copyright
[05:38] <RAOF> pitti: http://paste2.org/p/2272726 ? Has it simply failed to delete its conffile?
[05:39] <pitti> ooh; I think that was dropped ages ago, apparently without proper cleanup
[05:39] <pitti> RAOF: right
[06:20] <didrocks> desrt: just tested your patch, working great! :-)
[06:21] <didrocks> desrt: so, you don't condemn the guilty developer it seems :)
[06:35] <desrt> didrocks: meh
[06:35] <desrt> didrocks: all of the other gobject property functions accept you confusing _ and -
[06:36] <desrt> this one may as well work the same
[06:36] <desrt> didrocks: comment on bug?
[06:39] <didrocks> desrt: will do
[07:52] <didrocks> needs rebooting, brb
[07:53] <asac> hola
[07:54] <asac> running bleeding edge and very fresh quantal install ... unity launcher does not remember "lock to launcher"
[07:54] <asac> e.g. after relogging all my customizations seem to be gone
[07:54] <asac> let me see if its also about order or if it just forgets NEW items
[07:55] <asac> hrmf
[07:55] <asac> now it remembered it
[07:55] <asac> guess someone fixed it underneath :)
[07:56] <Laney> morning
[08:00] <Laney> oh my
[08:00] <Laney> didrocks: did the scope of that remote disabling bug change again?
[08:02] <didrocks> Laney: indeed, it did change
[08:02] <didrocks> Laney: so cutting all online connexions now
[08:03] <Laney> ...
[08:03] <Laney> do we have to do it like that this release? :(
[08:22] <seb128> hey desktopers
[08:22] <seb128> hey didrocks, Laney
[08:22] <Laney> hey
[08:22] <Laney> how are you?
[08:23] <seb128> good, though I wish the UI changes would settle and stop at this point
[08:23] <seb128> you?
[08:23] <didrocks> salut seb128!
[08:23] <Laney> same :P
[08:23] <didrocks> seb128: I think we all wish :)
[08:24] <Laney> also this room is really cold for some reason
[08:24]  * Laney runs some builds to warm up
[08:25] <didrocks> Laney: yesterday, the weather was really like the one you had in UK apparently here
[08:25] <didrocks> Laney: today, blue sky… no cloud
[08:25] <didrocks> quite impressive :)
[08:25] <seb128> we have sun here
[08:25] <Laney> it's actually like that here
[08:26] <seb128> but it's chilly outside
[08:26] <seb128> well, it gets colder when you have a clear sky
[08:26] <Laney> not sure how cold it is outside, but this room is on the wrong side of the house for morning sun anyway
[08:26] <didrocks> 23°C with any heater inside :) 16 outside (19 this afternoon), it's ok :)
[08:26] <Laney> errrr
[08:26] <Laney> seb128: you won't believe this
[08:27] <Laney> https://launchpad.net/~laney/+archive/webkit2/+packages
[08:27] <seb128> Laney, we found our new webkit maintainer \o/ only a true maintainer could build the beast :p
[08:27] <didrocks> Laney: you didn't try armhf yet! :-)
[08:27]  * seb128 hides
[08:27] <Laney> haha
[08:27] <chrisccoulson> good morning everyone
[08:28] <chrisccoulson> hah, unlucky ;)
[08:28] <Laney> Ubuntu doesn't have maintainers™ ⓒ ⓡ
[08:28] <chrisccoulson> lol
[08:28] <Laney> yeah, telling that to chrisccoulson :P
[08:28] <chrisccoulson> i can't help but feel insulted when people say that ;)
[08:29] <didrocks> hey chrisccoulson
[08:29] <chrisccoulson> i should just change the maintainer field of firefox to my name ;)
[08:29] <chrisccoulson> hey didrocks
[08:32] <seb128> chrisccoulson, good morning, how are you?
[08:33] <chrisccoulson> hi seb128. i'm good thanks, how are you?
[08:33] <seb128> I'm good thanks
[08:34] <chrisccoulson> mmm, pot of coffee is ready :)
[08:34]  * Laney is asking for an arm PPA to try it there
[08:36] <tkamppeter> pitti, hi
[08:36] <pitti> hello tkamppeter
[08:38] <tkamppeter> pitti, it is about bug 1052897. CUPS has dropped its broadcasting/browsing feature and now the cupsd.conf files of the users have a lot of obsolete entries which prevent CUPS 1.6.1 from starting. See comment #3 and the following comments.
[08:38] <ubot2> Launchpad bug 1052897 in system-config-printer "Printer sharing via CUPS broadcasting dropped in CUPS 1.6.x" [High,Fix committed] https://launchpad.net/bugs/1052897
[08:38] <pitti> err, why was that dropped?
[08:38] <pitti> in a .1 version?
[08:39] <pitti> tkamppeter: so I guess that requires some conffile surgery in postinst if the conffile is modified
[08:39] <tkamppeter> pitti, the problem is the correct handling of the config file. If I let postinst simply remove/comment out the offending lines, there will appear conffile questions.
[08:39] <pitti> tkamppeter: no, there shouldn't
[08:40] <tkamppeter> pitti, it was dropped from 1.6.0 on already, so with the 1.5.x -> 1.6.x transition.
[08:40] <pitti> tkamppeter: if the conffile is unmodified, the new version will just ship the fixed one
[08:40] <pitti> and if it's modified, you'll get the question anyway
[08:42] <tkamppeter> pitti, but when I let postinst delete lines in the user's cupsd.conf, the file gets modified, causing the question.
[08:42] <pitti> tkamppeter: no, you must only do this if it is alraedy modified
[08:43] <tkamppeter> pitti, so I check first if there are offending lines, which would mean that the user's modified file got conserved and if so, I remove the lines?
[08:44] <pitti> tkamppeter: well, I'd hope that the default conffile in 1.6.1 is already correct?
[08:44] <pitti> tkamppeter: so an unmodified file should not have any offending lines
[08:45] <tkamppeter> pitti, yes, this I have already taken care of.
[08:45] <tkamppeter> pitti, and this means that every file with offending lines is a modified user file which got conserved.
[08:47] <tkamppeter> pitti, is it also correct to do the removal in postinst? Or has it to be preinst?
[08:48] <pitti> tkamppeter: postinst is better
[08:48] <tkamppeter> pitti, yes, otherwise the old default file with offending lines could be there, causing a modification when the user did not modify anything.
[08:49] <pitti> it needs to be done before #DEBHELPER#, i. e. before starting cupsdd
[08:50] <tkamppeter> pitti, OK, I will do so.
[08:59] <seb128> http://launchpadlibrarian.net/117489924/pam-xdg-support_0.1-0ubuntu1_source.changes
[08:59] <seb128> \o/
[08:59] <seb128> XDG_RUNTIME_DIR coming :p
[08:59] <didrocks> heh
[09:02] <chrisccoulson> seb128, will that fix https://crash-stats.mozilla.com/report/index/76fc48c3-05c0-4bfe-87f0-10ec62120926 ? ;)
[09:03] <seb128> chrisccoulson, if desrt is not lying yes ;-)
[09:05] <chrisccoulson> excellent :)
[09:05] <chrisccoulson> although, there's only around 2 of those per week ;)
[09:05] <seb128> chrisccoulson, well, that's only for nfs and ecryptfs users
[09:05] <seb128> which are not most of users
[09:09] <pitti> OMFGbuilt! https://launchpad.net/ubuntu/+source/glib2.0/2.33.14-1ubuntu6
[09:10] <pitti> but at the price of making tests non-fatal on arm; with our current arm builders that's a lost cause
[09:11] <bkerensa> :D
[09:11] <seb128> pitti, \o/
[09:12] <seb128> pitti, bien joué ! ;-)
[09:12] <pitti> seb128: the "fun" thing is that it failed twice even without fatal tests (gcc ICE)
[09:12] <pitti> so perhaps we need to disable the compilation stage as well :)
[09:12] <seb128> lol
[09:12] <didrocks> pitti: I saw that, I had to grab it this morning for some desrt's linked experiment! Congrats :)
[09:14] <RAOF> seb128: You'll be happy to know that I know the cause for a large majority of colord crashes.
[09:14] <RAOF> seb128: You'll be less happy to know that fixing it in precise will involve a significant rewrite.
[09:14] <seb128> RAOF, hey
[09:15] <seb128> RAOF, :-(
[09:15] <RAOF> Basically because libsane is the worst library ever.
[09:15] <seb128> RAOF, ken suggested it was just an init to libdbus threading
[09:15] <RAOF> seb128: Yeah, I've got a package that fixes that in the precise-proposed unapproved queue already; I suggested that fix to Ken :)
[09:16] <RAOF> But that's not all the bugs.
[09:16] <RAOF> Most of the rest of the bugs appear to be aborts and crashes in libc, which I'm pretty sure is because libsane leaks fds, so colord/colord-sane slowly runs out of fds until it crashes.
[09:17] <seb128> urg
[09:17] <RAOF> Indeed.
[09:17] <seb128> do we need libsane? can't we just use colord for screen and printing coloring? ;-)
[09:18] <RAOF> Scanners are kinda important in the colour management world :)
[09:18] <RAOF> This will be not abhorrent to fix in Quantal, because colord-sane is already a separate dbus-activated binary; I'll just make it do exactly one sane probe, then die and be respawned for the next probe.
[09:18] <seb128> ok
[09:18] <seb128> thanks a lot for looking into those
[09:19] <RAOF> But precise doesn't have the split-out colord-sane, so to fix it there requires first splitting out a colord-sane.
[09:19] <RAOF> Or disabling sane support, I guess.
[09:19] <seb128> "fun"
[09:19] <seb128> I would suggest the second option
[09:20] <seb128> I doubt it's a very used feature anyway in its current form
[09:21] <RAOF> Yeah, would certainly be safest.
[09:21] <RAOF> In that we *know* we're breaking that support, but are pretty unlikely to break anything else :)
[09:22] <seb128> it's not like that support was working great anyway
[09:22] <seb128> it ends up to segfaults :-(
[09:22] <pitti> so, I guess at that point I can upload glib 2.34.0 to Debian and Ubuntu
[09:23] <RAOF> seb128: Well, it works fine for a couple of hours at least! :)
[09:23] <seb128> pitti, \o/
[09:24] <pitti> seb128: I kept 2.33.14 in -proposed in the hope of getting that into b2, but that's moot now
[09:24] <seb128> RAOF, when are those fds leaked? like how often does it happen, does it happen if you don't make use of color calibration?
[09:25] <seb128> pitti, yeah, no chance of that to happen
[09:25] <pitti> it's only making a difference on arm anyway
[09:26] <RAOF> seb128: They're openned on either sane_open() or sane_get_devices(), an not freed in sane_exit(), which is on a timer to probe for new scanner devices, because libsane doesn't give you notifications.
[09:26] <seb128> "on a timer" :-(
[09:26] <RAOF> seb128: Also, it sane_open/get_devices/sane_exit because sane has an internal device cache which gets out of sync with the actual devices available.
[09:26] <seb128> how nice...
[09:27] <RAOF> Yeah, if sane wasn't a horrible library, colord wouldn't have to poll it.
[09:27] <seb128> let's get your workaround of exiting and respawing every time in quantal
[09:28] <seb128> we can discuss turning the backend off in precise later
[09:28] <seb128> I want to see first how much reports we still get after the currently waiting SRU
[09:29] <seb128> doh
[09:29] <seb128> I wonder if https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1047431 is a gtk issue :-(
[09:29] <ubot2> Launchpad bug 1047431 in gedit "gedit crashed with signal 5 in _XReply()" [High,Confirmed]
[09:29] <seb128> #10 0x00007fe53cb70534 in gdk_x11_atom_to_xatom_for_display (atom=0x81, display=0x7fe52c00c990) at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkproperty-x11.c:244
[09:29] <seb128>         name = 0x1fa4c50 "_NET_SUPPORTING_WM_CHECK"
[09:30] <seb128> hitting a BadWindow Xerror
[09:34] <dpm> thanks pitti for the donation! \o/
[09:34] <pitti> dpm: my pleasure, great and crazy idea!
[09:34] <dpm> :-)
[10:08] <geser> to fix a FTBFS with "Only <glib.h> can be included directly." the right fix is to do as the error says, right?
[10:10] <pitti> geser: correct
[12:46] <jbicha> didrocks: what? Design changed the opt-out back to "Include online search results" ?
[12:46] <didrocks> jbicha: indeed
[12:46] <didrocks> jbicha: that's why I sent the email ASAP
[12:46] <didrocks> and have done the additional lenses changes
[12:47] <didrocks> (which impacted quite a lot of lenses)
[12:47] <didrocks> jbicha: all lenses by default and the wikipedia one from extras are supporting it now
[12:49] <jbicha> will that be disabling the gwibber lens too?
[12:51] <didrocks> jbicha: yeah, all online connexions
[12:52] <didrocks> (see the bug report, I updated it for it removing the specific part for the shopping and other lens contents)
[12:54] <jbicha> ok, thanks!
[12:54] <didrocks> jbicha: I gave a screenshot to jono, do you need it?
[12:55] <didrocks> jbicha: exactly the same, but with the string change
[12:55] <jbicha> I think I'll be fine without it
[13:02] <didrocks> thanks jbicha :)
[13:02] <didrocks> and sorry again ;)
[13:02] <pitti> there, have a built glib 2.34.0: https://launchpad.net/ubuntu/+source/glib2.0/2.34.0-1ubuntu1
[13:03] <seb128> pitti, pitti 1 - 0 glib ;-)
[13:04] <pitti> yeah, the second half of that game went in my favour :)
[13:04] <seb128> pitti, wait, glib doesn't give up that easily, I'm sure it will take its revanche at some point
[13:04] <seb128> ;-)
[13:05] <pitti> no doubt
[13:05] <geser> it teams up with other packages to hit pitti from behind?
[13:06]  * desrt raises an eyebrow
[13:06]  * pitti tosses a piece of chocolate to desrt
[13:06] <desrt> yum
[13:07] <desrt> glib troubles?
[13:07] <pitti> nah, just took 9 uploads/20 builds to get the damn thing building :)
[13:07] <pitti> it's more like "arm builder troubles"
[13:07] <pitti> it's hitting other packages as well
[13:07] <pitti> but as glib has such a large and pedantic test suite, it hits it particularly hard
[13:14] <desrt> i choose to believe that having a large and pedantic testsuite is a positive thing :)
[13:18] <didrocks> jcastro_: hey, around?
[13:18] <didrocks> kenvandine: hey! how are you?
[13:19] <tkamppeter> pitti, fixed CUPS package uploaded to Quantal, thank you for the help.
[13:19] <pitti> tkamppeter: thanks, no worries :)
[13:23] <jcastro_> didrocks, yep
[13:24] <didrocks> jcastro_: so, I think you heard about bug #1054746 :)
[13:24] <ubot2> Launchpad bug 1054746 in gwibber "[FFe] [UIFe] No easy way to disable online-fetched results in lenses" [Undecided,In progress] https://launchpad.net/bugs/1054746
[13:25] <jcastro_> whoa!
[13:25] <didrocks> jcastro_: I have a branch for the ask* team to support the options in 3 of their online scope in their lens help
[13:25] <jcastro_> ok, that's mark tully iirc?
[13:25] <didrocks> jcastro_: can you ensure they review it so that we can push the change :)
[13:25] <didrocks> jcastro_: yeah, I think you know them, right?
[13:25] <jcastro_> I do
[13:25] <didrocks> excellent!
[13:26] <jcastro_> should I add an Affects also to their lens in launchpad?
[13:26] <didrocks> jcastro_: it's done, isn't it? I only found AskUbuntu Lens Remove
[13:26] <didrocks> oupss, without Remove, thanks launchpad :)
[13:26] <jcastro_> oh, I see it
[13:26] <didrocks> (first line)
[13:26] <jcastro_> ok, on it!
[13:26] <didrocks> thanks!
[13:26] <didrocks> the MR is attached to the bug
[13:27] <didrocks> now ken's turn, where is ken? :-)
[13:27] <jcastro_> kenvandine, hey, get to work
[13:27] <didrocks> heh
[13:29] <didrocks> jcastro_: oh, in case they ask, they will need libunity trunk (they can use the package in the staging ppa)
[13:31] <jcastro_> ok
[13:32] <didrocks> thanks again :)
[13:33] <seb128> jcastro_, be nice with the man for his birthday
[14:04] <kenvandine> i think i was just bit by the same problem robru had yesterday
[14:04] <kenvandine> screen went to sleep... and wouldn't wake up
[14:04] <kenvandine> but did accept input
[14:05] <kenvandine> well... only showed me the wallpaper
[14:05] <kenvandine> but if i typed it was entering text in the file i had open in vim :)
[14:06] <seb128> kenvandine, I wonder if that's the same issue tjaalton is tracking
[14:07] <didrocks> happy birthday kenvandine!
[14:07] <tjaalton> I might have something to test shortly..
[14:07] <didrocks> sounds really like the same
[14:08] <didrocks> tjaalton: we are talking about the critical one we discussed 2 weeks ago, right?
[14:08] <didrocks> (the one impacting precise and quantal)
[14:08] <kenvandine> thx :)
[14:08] <kenvandine> this is the first time i have seen it
[14:08] <tjaalton> didrocks: still the same. upstream noticed there was a race in the uxa pageflip code, so I'm now building a snapshot of -intel that people can try
[14:08] <kenvandine> i tried to get unity back by running setsid unity and unity --replace
[14:08] <kenvandine> nothing worked
[14:09] <kenvandine> i assume video driver
[14:09] <didrocks> tjaalton: oh, excellent news!
[14:09] <kenvandine> yeah, intel driver
[14:09] <didrocks> kenvandine: you are quite lucky
[14:09] <didrocks> kenvandine: really getting it a lot for the past 3 months here :)
[14:09] <kenvandine> robru googled for his password :)
[14:10] <didrocks> kenvandine: yeah, basically, all opengl is screwed
[14:10] <didrocks> you can run metacity though
[14:10] <kenvandine> ah, i didn't try that
[14:10] <kenvandine> tjaalton, what is the bug #?
[14:10] <tjaalton> 96744
[14:10] <tjaalton> uh
[14:11] <tjaalton> 966744
[14:11] <didrocks> kenvandine: see the top critical bug for the desktop team on http://reports.qa.ubuntu.com/reports/rls-mgr/rls-q-tracking-bug-tasks.html :p
[14:11] <kenvandine> ok :)
[14:12] <kenvandine> so that says with suspend
[14:12] <kenvandine> mine never suspended
[14:12] <kenvandine> it was plugged in and left alone for 30m
[14:12] <didrocks> kenvandine: seems a recent change is triggering it more when the screensaver is kicking in
[14:12] <kenvandine> probably same bug... but might not be just suspend that triggers it
[14:13] <kenvandine> yeah
[14:13] <didrocks> I wonder if compiz became more effective and we are triggering the race more…
[14:13] <didrocks> kenvandine: so, I have a gift for you!
[14:13] <didrocks> kenvandine: do you mind reviewing https://code.launchpad.net/~didrocks/gwibber/disable-online-search-support/+merge/126613?
[14:13] <didrocks> kenvandine: you need libunity trunk
[14:15] <kenvandine> didrocks, how urgent is that? i have 27 new packages to upload for webapps :)
[14:15] <kenvandine> i think i will be very busy for my birthday
[14:15] <tjaalton> didrocks: oh well, now it hangs on login, progress! :)
[14:16] <didrocks> kenvandine: very urgent, like for start of next week? :-)
[14:16] <didrocks> kenvandine: chill out, there is time until next unity release ;)
[14:16] <didrocks> tjaalton: with the patched version? :/
[14:16] <tjaalton> yeah
[14:16] <kenvandine> humm... nothing in the gwibber lens is really "online"
[14:17] <didrocks> kenvandine: it fetches the content from online sources, isn't it?
[14:17] <didrocks> twitter and so on
[14:18] <davidcalle> kenvandine, fetching icons and images is (but I'm not sure it's in the scope of this setting).
[14:18] <kenvandine> nope... gwibber-service does
[14:18] <kenvandine> it mostly loads the icons from the gwibber avatar cache
[14:18] <kenvandine> but the image thumbnails are loaded online
[14:19] <didrocks> kenvandine: hum, so you need that in the scope and in the service, right?
[14:19] <didrocks> kenvandine: maybe I should let you dealing with the service part :)
[14:19] <kenvandine> well, i wonder if this setting really applies to the gwibber lens/scope
[14:19] <didrocks> kenvandine: it does
[14:20] <didrocks> kenvandine: explicitely asked by design
[14:20] <didrocks> kenvandine: all online connexion initiated/accessed through the dash/lenses
[14:20] <kenvandine> ok, so then that would be just loading those thumbnails
[14:21] <didrocks> kenvandine: so please review it when you have time, I can help on the service side is needed, but I will surely be less effective than you
[14:35] <seb128> mterry, howdy
[14:35] <mterry> seb128, hello
[14:35] <seb128> mterry, can you chase the design guys about their workitems on the unity-greeter blueprint?
[14:35] <seb128> mterry, or just mark them postponed if you think that's right
[14:35] <mterry> seb128, guh they have so far been unresponsive the two times I did  :)
[14:36] <mterry> seb128, yeah, I'll try to figure out status myself.  Will be faster  :)
[14:36] <seb128> mterry, maybe just postpone the lot then?
[14:36] <seb128> mterry, thanks
[14:37] <seb128> Sweetshark, hey, you still have some 11 workitems for quantal, can you go through the list and update the status of those than should be postponed? like you have some "needs-packaging" bugs on there, it's late for that this cycle...
[14:37] <mterry> seb128, just postponed them.  I haven't seen any of these design outputs.
[14:37] <seb128> mterry, ok, makes sense
[14:38] <seb128> thanks
[14:45] <Sweetshark> seb128: how do I WI that is actually a bug kinked to a blueprint? unlink it?
[14:45] <Sweetshark> s/do I /do I postpone/
[14:47] <Sweetshark> seb128: the rest is mostly done I guess, I justs didnt get around to verify them.
[14:52] <kupcsik> Hi, I'm using 12.04 LTS. I would like to overclock my ivy brdige i5-3570k. I set it to 4.5 Ghz +0.1 V, works well in windows. but in Linux the maximum recognized frequency is 3.4Ghz. That means the turbo boost doesn't work neither. What could be the problem?
[14:53] <ogra_> kupcsik, support is in #ubuntu
[14:53] <kupcsik> ahh ok, sorry
[14:53] <ogra_> this channel is for packaging and fixing desktop packages
[16:07] <mitya57> oh, alacarte on quantal is harmful
[16:07] <mitya57> it empties ~/.local/menus/applications.menu
[16:08] <mitya57> which makes most of DEs fail to start :(
[16:21] <Sweetshark> jasoncwarner_: ping?
[16:21] <mitya57> whoops, that seems to be a *very* old bug:
[16:21] <mitya57> https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/97449/comments/5
[16:22] <ubot2> Launchpad bug 97449 in alacarte "[apport] alacarte crashed with ExpatError in parseFile()" [Medium,Expired]
[16:29] <seb128> Sweetshark, you have a "Unlink a bug" on the blueprint page
[16:29] <seb128> Sweetshark, https://blueprints.launchpad.net/ubuntu/+spec/desktop-p-libreoffice-lo-menubar-polish/+unlinkbug for example
[16:30] <seb128> Sweetshark, or you can probably nominated the bug for q and r and put it wontfix for q if you think it's going to be fixed in r
[16:44] <seb128> some days I hate linux
[16:44] <seb128> came back again to find a blank screen
[17:41] <tjaalton> ok, if there are folks who can reproduce the compiz hang with intel on dpms cycle, please test the driver in http://kernel.ubuntu.com/~tjaalton/lp966744/
[17:42] <tjaalton> amd64 build available
[17:42] <robru> tjaalton: ok, I'm a bit busy right now but I'll get to it within an hour
[17:42] <tjaalton> sure
[17:57] <robru> ok tjaalton, so you want me to install those three debs, reboot, and then try to reproduce the issue?
[17:58] <tjaalton> robru: just the intel driver
[17:58] <tjaalton> I removed the kernel image, that was for earlier testing
[17:58] <tjaalton> logout should be enough
[17:58] <tjaalton> robru: you can reproduce it every time the screensaver blanks the screen?
[17:59] <tjaalton> *can you
[17:59] <robru> tjaalton: couldn't reproduce it by manually locking the screen, but if I leave my computer unattended for 5 minutes, then I'd come back to the blank screen of death. every time.
[18:00] <tjaalton> right
[18:00] <tjaalton> you can change the timeout to 1 minute
[18:00] <robru> yeah
[18:00] <tjaalton> to speed up the testing
[18:01] <robru> ok, new driver installed, just need to log out. brb
[18:07] <robru> tjaalton: ok, just booted in. gimme a sec to re-enable the screen lock
[18:07] <tjaalton> no need to enable screen lock, just the timer to blank the screen :)
[18:07] <tjaalton> but either way is fine
[18:08] <robru> ok, set for 1 minute either way, will let you know what happens
[18:08] <sarnold> can you use xset dpms force on ; xset dpms force off ; to toggle it immediately?
[18:09] <tjaalton> no
[18:09] <tjaalton> won't trigger the bug here, but others :)
[18:09] <tjaalton> won't trigger _this_ bug I mean
[18:10] <robru> ok, so i did see the screen lock dialog just now, and it did unlock the screen successfully. gimme a few more minutes to try a few different things though
[18:10] <tjaalton> sure
[18:10] <tjaalton> but sounds good..
[18:18] <robru> tjaalton: yeah, I can't seem to reproduce it anymore. yay! ;-)
[18:18] <tjaalton> robru: phew, thanks
[18:18] <robru> thanks ;-)
[18:21] <sarnold> kenvandine: btw, typo "additionnal" in hromium-codecs-ffmpeg description
[18:26] <kenvandine> :)
[18:26] <kenvandine> sarnold, i should be doing an upload soon, i'll fix that
[18:26] <sarnold> kenvandine: thanks :)
[18:26] <sarnold> (it sure doesn't feel worthy of a bug report, but if you're in irc anyway :)
[18:29] <kenvandine> sarnold, ok, i've fixed it in the packaging branch
[18:29] <kenvandine> so it won't get forgotten :)
[18:29] <kenvandine> thx
[18:29] <sarnold> thanks kenvandine :)
[18:30] <kenvandine> np
[18:30] <robru> hey jbicha, any word on gdm/gnome-session?
[18:37] <jbicha> robru: that was fixed last night
[18:37] <robru> jbicha: I'm getting an error when I try to dist-upgrade
[18:37] <robru> The following packages have unmet dependencies:
[18:37] <robru>  gir1.2-mutter-3.0 : Depends: libmutter0 (>= 3.6) but 3.5.92-0ubuntu1 is installed
[18:37] <robru> E: Unmet dependencies. Try using -f.
[18:39] <robru> Oh, -f seems to be working this time. I thought it didnt' before.
[18:39] <robru> hmmm
[19:24] <kenvandine> tjaalton, i tested you intel driver, with 1 minute sleep on
[19:24] <kenvandine> although i had only hit the bug once (probably because i had the timeout set for 1 hour)
[19:25] <kenvandine> i have let it timeout a bunch of times
[19:25] <kenvandine> no problems
[19:25] <tjaalton> kenvandine: thanks!
[19:25] <kenvandine> tjaalton, thank you
[22:27] <Sweetsha1k> http://www.commitlogsfromlastnight.com/
[22:37] <robru> Sweetsha1k: LOL
[22:39] <highvoltage> heh
[22:45] <xnox> Sweetsha1k: in general quite repetitive =))))