[00:43] <thekorn> bdmurray, sure
[00:43] <thekorn> oh, it's actually a post mortem ACK ;)
[00:43] <bdmurray> thekorn: yeah, I found the irclog of when we talked about it earlier ;-)
[00:44] <thekorn> bdmurray, thanks for doing all the house keeping here
=== yofel_ is now known as yofel
[07:01] <Damascene> good morning
[07:01] <Damascene> does any one get stack when go to guest session and then chose switch user?
[08:06] <Damascene> any help with guest session problem?
[08:06] <kklimonda> Damascene: define "stack"
[08:06] <Damascene> user > guest session >switch> user = crash
[08:06] <kklimonda> it works fine here
[08:06] <Damascene> stuck maybe :)
[08:06] <Damascene> user > guest session >switch(don't close)> user = crash
[08:08] <Damascene> I mean stuck not crash
[08:08] <kklimonda> of course it almost never restores the screen when I switch users for me - I have to type xgamma -gamma 1.0 blindly
[08:08] <kklimonda> s/for me//
[08:08] <Damascene> really?
[08:08] <Damascene> so it's known?
[08:08] <kklimonda> sure
[08:09] <kklimonda> at least if you have the same problem :)
[08:09] <Damascene> no need to report then. it's already reported. right?
[08:09] <kklimonda> no idea, check bug 555870
[08:09] <ubot4`> Launchpad bug 555870 in gnome-screensaver (Ubuntu) (and 1 other project) "Gamma values are not being set properly after a second fade out resulting in a black screen (affects: 1) (heat: 10)" [High,In progress] https://launchpad.net/bugs/555870
[08:09] <kklimonda> but it's not going to get fixed probably
[08:09] <Damascene> why?
[08:10] <kklimonda> because we lack manpower
[08:10] <Damascene> it should be disabled then
[08:10] <kklimonda> it's not broken for everybody
[08:10] <kklimonda> half of the reason why it's not getting fixed
[08:10] <Damascene> mmm
[08:12] <Damascene> that bug does not seem related
[08:12] <Damascene> I'll try to switch user now
[08:14] <Damascene> strange now it didn't happen
[08:14] <Damascene> only happens sometimes maybe
[09:28] <om26er> Its seems like gnome bug watches are now enabled. Good thing
[09:30] <nigelb> om26er, except for the mail floor
[09:30] <nigelb> *flood
[09:30] <nigelb> it got enabled yday
[09:47] <om26er> nigelb, ah, was not here. The advantage here is now I dont have to subscribe to all upstream bug reports.
[09:48] <nigelb> ah
[12:00] <ombra> hi, i've found on my ubuntu 9.10 exactly this bug: http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/
[12:14] <jfi> Hello, I have registered 2 bugs few days ago that I no more reproduced since I update my lucid ubuntu. I guess the bug status should be changed, maybe a triager can quickly take a look?
[12:14] <jfi> bug #558759
[12:14] <ubot4`> Launchpad bug 558759 in synaptic (Ubuntu) "Freeze when using "File>Save markings as" (affects: 2) (heat: 12)" [Undecided,New] https://launchpad.net/bugs/558759
[12:14] <jfi> bug #546136
[12:14] <ubot4`> Launchpad bug 546136 in udev (Ubuntu) "Removable storage device not detected as block device (affects: 4) (heat: 20)" [Undecided,Confirmed] https://launchpad.net/bugs/546136
[12:33] <bencrisford> jfi: so the bugs do not affect you in lucid?
[12:34] <jfi> bencrisford, I confirm that the 2 bugs do not affect me (since I updated my lucid this morning)
[12:35] <bencrisford> jfi: oh, ok i see, if they affect an earlier build but no longer affect anything then i *think* it should be invalid
[12:35] <bencrisford> however, if it still affects karmic (or earlier)
[12:35] <jfi> bencrisford, #546136  does not affect karmic
[12:36] <bencrisford> ok
[12:36] <jfi> I have a computer under karmic and my usb drive is ok
[12:36] <jfi> the bug has been introduced during lucid alpha
[12:36] <bencrisford> ok, im not sure what the status should be to be honest, i misunderstood and thought you meant that since you upgraded from karmic it has stopped affecting you
[12:36] <bencrisford> i understand now
[12:37] <bencrisford> but like i say, im not sure
[12:37]  * bencrisford tries to find an appropriate wiki page
[12:37] <kermiac> if a bug is fixed in lucid but still an issue for karmic it should be "fix released"
[12:37] <kermiac> https://wiki.ubuntu.com/Bugs/Status
[12:37] <jfi> kermiac: that's not my case, let me resume it:)
[12:37] <jfi> karmic: no bug
[12:38] <jfi> lucid alpha and beta: bug
[12:38] <jfi> uptodate lucid (this morning): no bug
[12:38] <kermiac> for both or just 546136?
[12:38] <jfi> for #546136
[12:38] <jfi> I did not test the other issue on karmic
[12:40] <kermiac> 546136 should be fix released if the issue is not present in karmic
[12:40] <jfi> Ok, I did the test of 558759 on karmic and I don't reproduce it
[12:40] <kermiac> is not present in lucid
[12:41] <kermiac> 546136 should be fix released if the issue was present in karmic but is not present in lucid
[12:42] <kermiac> 558759 should be invalid if you can't reproduce & it wan't fixed by an update. just explain that you can no longer reproduce & it may have been a configuration issue
[12:43] <jfi> ok, thanks for the explanation kermiac
[12:44] <kermiac> np jfi. the wiki page I linked above has all the relevant info regarding bug status :)
[12:51] <jfi> nice way to say 'rtfm' :-)
[12:51] <kermiac> jfi: nice explanation on the bug reports :)
[12:53] <kermiac> well, I wan't exactly trying to say rtfm... I just thought the wiki page would come in handy for future reference ;)
[12:55] <yofel> new info on bug 504956, any JS hackers here that actually understand that? ^^
[12:55] <ubot4`> Launchpad bug 504956 in launchpad-gm-scripts "partially hidden comment in bug report (affects: 6) (dups: 2) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/504956
[12:56] <nigelbabu> yofel, for now, avoid highlighting
[13:00] <yofel> I know, it's disabled here, but it sure would be nice to have it working...
[13:00] <nigelbabu> oh, that way :)
[14:15] <mdevenish> Anyone else having problems with the latest version of gwibber (2.30.0.1-0ubuntu1) and displaying messages from twitter, bug #565250
[14:15] <ubot4`> Launchpad bug 565250 in gwibber (Ubuntu) "Gwibber doesn't display messages (affects: 2) (heat: 12)" [Undecided,New] https://launchpad.net/bugs/565250
[14:18] <nigelbabu> mdevenish, can try deleting your account and adding again?
[14:22] <mdevenish> nigelbabu: tried that, but still have same problem. Tried refresh, but still doesn't work.
[14:28] <nigelbabu> mdevenish, please set the bug to confirmed and also add that you've tried deleting your twitter account and adding back
[14:33] <mdevenish> nigelbabu: ok, done that.
[14:33] <nigelbabu> mdevenish, thank you.  someone should get to it on monday or so
=== thekorn__ is now known as thekorn
[14:56] <shadeslayer> hi,is there a app to triage bugs? i dont like opening my web browser :P
[14:57] <shadeslayer> something apart from bughugger as its not working here
=== bencrisford is now known as bencrisford_
=== bencrisford_ is now known as bencrisford
[17:34] <MichealHForums> .away
=== yofel_ is now known as yofel
[18:35] <Tiibiidii> last week i tried upgrading my wubi install to lucid... unfortunately it broke, i tried to find a solution asking around to no avail... in the end i decided to file a bug report... but, even if i never did it before, now i'm giving up trying to fix it and will instead do it the quick and dirty way: reinstalling ubuntu... the problem is:
[18:36] <Tiibiidii> my bug report is only a summary of what i did, what it happened to me and what i tried... without any file attached whatsoever
[18:37] <Tiibiidii> (usually i always use ubuntu-bug to collect these, but i obviously couldn't do that with an unbootable system)
[18:37] <mccolgan> that's an interesting predicament :-/
[18:38] <Tiibiidii> so, before reinstalling i'm going to at least provide some hopefully useful files
[18:38] <Tiibiidii> aside from grub.cfg, what should i fetch from my dead system?
[18:39] <Tiibiidii> (ah, yes... it's a grub2 bug afaik... didn't mention that before)
[18:51] <Tiibiidii> as of now, i've only found this page concerning debugging the boot process: https://wiki.ubuntu.com/DebuggingKernelBoot unfortunately  it's only referring to kernel bugs
[18:52] <jpds> Tiibiidii: Oh that.
[18:53] <jpds> Tiibiidii: I think that's because grub2 can't read beyond a certain number of bits.
[18:53] <Tiibiidii> mhn, i don't think that's the problem
[18:53] <Tiibiidii> that was a karmic bug
[18:53] <Tiibiidii> in lucid it's been solved
[18:53] <jpds> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/477104
[18:53] <ubot4`> Launchpad bug 477104 in lupin (Ubuntu Karmic) (and 6 other projects) "After 9.10 grub update can not boot into Wubi install (affects: 162) (dups: 11) (heat: 834)" [Undecided,Fix committed]
[18:53] <Tiibiidii> yesyes
[18:53] <Tiibiidii> that's the very reason i decided to upgrade early to lucid :D
[18:54] <jpds> Oh right, sorry.
[18:54] <Tiibiidii> (trust me, even a grub2 dev believed that was the issue... and i went all the way to check the version provided with lucid... it doesn't have that issue anymore)
[18:54] <Tiibiidii> nope
[18:55] <Tiibiidii> but do you know what files could be useful to debugging/triaging it?
[18:55] <Tiibiidii> (aside from grub.cfg)
[18:57] <jpds> No, I personally don't use Wubi.
[18:58] <Tiibiidii> ok, thanks anyway
[19:00] <Tiibiidii> (i'll attach the output of lspci, not sure if it'll help... the kernel never kicks in, so maybe that's not truly relevant)
=== radoe_ is now known as radoe
[21:21] <incorrect> can i ask if i have a bug to report here?