[00:00] <Hobbsee> azimout: nothing.  it's in the right place.
[00:00] <bdmurray> to the bug report? do nothing.  You might check with someone in #ubuntu-x about the status of that package
[00:00] <azimout> fair enough, thanx
[00:34] <Palintheus> can someone mark Bug 299915 as wishlist for me?
[01:42] <knevah> Anyone know anything about rhythmbox 0.11.6 (8.10) crashing a LOT... I have some traces, and I'm thinking about logging a big, although there's lots of people talking about issues with rhythmbox in forums.,..
[02:23] <andresmujica> bdmurray: ping
[02:56] <bucket529> Bug 308758, the deb is in debian unstable...where's the web page to see if it's slated for import into Jaunty?
[04:13] <duanedesign> is there anyone here associated with the docs team?
[04:28] <LaserJock> duanedesign: what are you needing
[04:28] <LaserJock> ?
[04:30] <venugr> I am facing a problem in ubuntu 8.10 is this the right forum to discuss to see if it a potential bug
[04:30] <venugr> I have ubuntu 8.10 upgraded from previous version on my Dell XPS 1530 laptop
[04:30] <venugr> problem is the with the keyboard
[04:31] <venugr> sometimes key I type doesnot get recognized
[04:31] <venugr> I dont see this problem with  windows partition
[04:31] <venugr> happens only in ubuntu
[04:31] <venugr> any idea what drivers will have to be updated
[04:32] <venugr> thank you for any help
[04:32] <venugr> or kindly point me to the right forum
[04:33] <duanedesign> https://wiki.ubuntu.com
[04:33] <duanedesign> sorry not it
[04:34] <duanedesign> http://ubuntuforums.org/
[04:34] <duanedesign> the people on there will be more than willing to help you
[04:35] <venugr> thank you very much
[04:35] <crimsun> venugr: can you describe the problem in more detail, please? does it only occur on certain intrepid kernels?
[04:35] <venugr> I will try there
[04:36] <venugr> I only tried the kernel version with ubuntu 8.10
[04:36] <venugr>  2.6.27-9-generic #
[04:37] <venugr> crimsum: I am willing to try different kernels let me know
[04:37] <crimsun> venugr: also, do using any of the irq-related kernel command line options resolve the symptom?
[04:37] <crimsun> e.g., irqpoll, noapic, nolapic, acpi=off
[04:38] <venugr> I did not try as I am a just have user level knowledge
[04:38] <crimsun> venugr: I recommend at least trying the intrepid-proposed kernel (2.6.27-10-generic for you)
[04:39] <venugr> ok let me try it thank  you crimsum
[04:39] <crimsun> venugr: if you're using GNOME, you'll need to enable System> Administration> Software Sources> Updates> Pre-released updates
[04:39] <venugr> yes I am using GNOME
[04:39] <venugr> I will try it right away
[04:40] <crimsun> venugr: if it's still reproducible in -10 without any of the irq-related options, please file a bug using Launchpad affecting the linux source package
[04:40] <venugr> ok
[04:50] <andresmujica> http://dag.wieers.com/blog/when-bugtracking-systems-are-being-fenced
[06:48] <thekorn> good morning :)
[06:50] <maco> hiya
[06:52] <LaserJock> maco: still up?
[06:54] <maco> yes, of course
[06:54] <maco> sun's not up yet
[06:54] <LaserJock> :-)
[06:54] <maco> <-- nocturnal
[06:54] <LaserJock> I am as well, but don't get to be these days
[07:09] <dholbach> good morning
[07:09] <maco> hiya
[07:28] <maco> asac: you around?
[07:29] <maco> i think bug 306611 is really 2 bugs
[07:30] <maco> i think there's a NM bug causing NM to uncheck "Enable Networking" (i'm seeing that too) and that the driver issue is separate
[07:30] <maco> i think that because i can "ifconfig wlan0 up && iwconfig wlan0 essid helloworld && dhclient wlan0" just fine when it's in that state
[07:40] <crimsun> way past my bedtime
[07:40] <maco> sun's not up yet
[07:40] <maco> not bedtime yet
[07:41] <crimsun> i suppose i can install gutsy in the vm and test the firefox packages
[07:42] <crimsun> maco: you also don't go to work at 5am
[07:52] <crimsun> maco: yeah, confirmed separate bugs on at least intrepid and jaunty
[07:57] <LaserJock> alright, I've had enough fighting with sabayon, I'm off to bed
[07:57] <maco> haha
[10:40] <asac> maco: ?
[10:42] <BUGabundo_work> hi asac
[10:42] <asac> hi BUGabundo_work
[10:46] <asac> BUGabundo_work: no didnt came back tonight ... still on jetlag ;)
[10:47] <BUGabundo_work> xeee
[10:48] <BUGabundo_work> that's tuff
[10:48] <BUGabundo_work> how many time zones?
[10:50] <asac> BUGabundo_work: hmm ... -9
[10:54] <BUGabundo_work> you re from somewhere in europe, right?
[12:41] <BUGabundo_work> maco remember that friends laptop I told you about, that sound wouldn't work for headphones?
[12:41] <BUGabundo_work> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/308700
[12:41] <BUGabundo_work> crimsun: ping
[13:14] <Hew> an IM username in a stacktrace isn't "private" information, right?
[13:25] <Hew> I'll take the lack of alarm as a sign that this is the case :-). I'm fairly sure anyway.
[13:37] <BUGabundo_work> I wouldn't consider it Hew
[13:37] <BUGabundo_work> but some users might
[13:39] <Hew> BUGabundo_work: Yea neither, seeing as email addresses are all over Launchpad already. I'm pretty sure Private is just meant to avoid disclosing passwords and bank details etc. Thanks for your reply.
[13:44] <BUGabundo_work> Hew well I wouldn't even like to disclosure in the CLEAR my email.... LP tries to hide them, but not always
[14:00] <gnomefreak> anyone know of PIM bugs or gpg bugs that have been filied recently in Jaunty?
[14:02] <BUGabundo_work> ahh what a lovelly error message I got from seahorse while trying to add a ssh key to a remote server
[14:03]  * BUGabundo_work apologises for the wrong window
[14:04] <gnomefreak> BUGabundo_work: can you pastebin it as long as no private info is in error?
[14:04] <BUGabundo_work> just a sec, and I''ll try to reproduce it
[14:04] <BUGabundo_work> seahorse exploded too
[14:04] <BUGabundo_work> lol
[14:04] <BUGabundo_work> runing it in dbg now to catch the backtrae
[14:05] <gnomefreak> im hoping its as simple as pinentry-gtk2 being borked
[14:05] <BUGabundo_work> it got updated a week ago
[14:05] <BUGabundo_work> I remember seeing it on apt-log
[14:06] <gnomefreak> it is
[14:06] <gnomefreak> ha -qt works
[14:07] <BUGabundo_work> gnomefreak: http://paste.ubuntu.com/87077
[14:08] <BUGabundo_work> and now that I'm running it o gdb I can't close the damn window
[14:14] <gnomefreak> BUGabundo_work: is it the key that is causing it?
[14:15]  * gnomefreak thinks seahorse uses pinentry-gtk2
[14:15] <gnomefreak> if so that is the problem
[14:18] <CarlFK> if anyone finds multi head X bug, it is likely this: https://bugs.freedesktop.org/show_bug.cgi?id=18160#c8
[14:19] <Hew> BUGabunto_work: I've had the exploding seahorse one too, when you search for remote keys. It's very known.
[14:20] <BUGabundo_work> Hew: we are keeping it on #u+1. join us there
[14:20] <Hew> BUGabunto_work: Oh, and fixed as of 2.24.1-0ubuntu1, forgot about that..
[15:04] <CarlFK> https://bugs.freedesktop.org/show_bug.cgi?id=18160#c8 and my own broke box confirm bug 302548
[15:04] <CarlFK> so should I mark it confirmed? (not sure who should really be doing that)
[15:13] <duanedesign> f the bug cause and effect are the same yes confirm it and leave all the info you can to help fix the bug
[15:21] <duanedesign> attach your /var/log/Xorg.0.log
[15:22] <duanedesign> CarlFK: see Bryces comments
[15:22] <duanedesign> on bug #302548
[15:24] <CarlFK> ok, I am confused.  what do the 4 things at the top mean?
[15:25] <CarlFK> x.org x server - confirmed.  ... xorg.server (ubuntu) incomplete
[15:47] <duanedesign> CarlFK: the 4 things at the top are the different packages associated with the bugs
[15:49] <CarlFK> duanedesign: I was wondering why each one gets a different status
[15:49] <Palintheus> CarlFK: if you look at assigned to, they are reported against different distros/bugtrackers
[15:51] <duanedesign> I think the best thing to do there would be to try and provide the additional information requested in the comments
[15:51] <CarlFK> Palintheus: i guess the status should be 2: status of report, status of fixes
[15:51] <CarlFK> duanedesign: did you read all the references?
[15:52] <CarlFK> duanedesign: the request came from a bot, so not alot of thought went into it
[15:57] <duanedesign> CarlFK: An X bug at minimum should have /var/log/Xorg.0.log and the output of lspci -nn | grep VGA
[15:58] <duanedesign> CarlFK: https://wiki.ubuntu.com/X/Reporting
[15:58] <CarlFK> Ill take that as a no.
[15:59] <CarlFK> before adding 'stuff' one should read what has already been posted and take that into account
[16:00] <duanedesign> Canned response or not the people who triage those bugs feel it is nescessary.
[16:01] <duanedesign> If that information has been posted add that comment
[16:02] <duanedesign> CarlFK: even if you feel the info is not important to the problem, it will move the bug forward and get the status changed form incomplete
[16:03] <duanedesign> CarlFK: before adding 'stuff' one should read what has already been
[16:04] <duanedesign>                 posted and take that into account
[16:04] <duanedesign> you could always make that a bug :)
[16:04] <duanedesign> I better get back to work CarlFK, I hope I helped.
[16:05] <CarlFK> thanks
[16:06] <duanedesign> CarlFK: thank you,  for taking the time to help with the bug reports
[16:06] <CarlFK> duanedesign: you're welcome
[19:01] <chrisccoulson> boo
[19:01] <chrisccoulson> it's quiet in here tonight?
[19:02] <BUGabundo> bar
[19:02] <chrisccoulson> lol
[19:02] <chrisccoulson> ooh, i wanted to speak to you about something actually BUGabundo
[19:02] <chrisccoulson> i forgot what it was though
[19:02] <BUGabundo> shoot
[19:02] <BUGabundo> ohh
[19:03] <chrisccoulson> that was it
[19:03] <chrisccoulson> you opened a bug yesterday and added a gnome-do task to it
[19:03] <chrisccoulson> can't remember the bug number off the top of my head
[19:03] <BUGabundo> some one was around here the other day asking about X.org version... unintentional I lied to the guy
[19:03] <BUGabundo> I'll get it
[19:03] <BUGabundo> just a sec
[19:04] <chrisccoulson> bug 308551
[19:04] <BUGabundo> bug 308551
[19:04] <chrisccoulson> lol
[19:04] <BUGabundo> FF awesome bar on its best
[19:04] <chrisccoulson> it's not obvious with launchpad, but when you assign an additional source package, you should click the "Also affects distribution" button, select "Ubuntu" and pick the source package name
[19:05]  * BUGabundo wonders if is there a way to query FF history DB from console or pidgin plugin
[19:05] <BUGabundo> wasn't that what I did?
[19:05] <chrisccoulson> i noticed you added an upstream gnome-do task, by clicking on "Also affects project"
[19:05] <BUGabundo> yes...
[19:05] <BUGabundo> I first filed it against G-DO
[19:05] <BUGabundo> on its own LP project BTS
[19:05] <BUGabundo> and not Ubuntu package
[19:05] <BUGabundo> 'cause I have the PPA version
[19:05] <chrisccoulson> the problem with that is, if the project is registered on launchpad, the project maintainers get all of the bug traffic once you've added the upstream tasl
[19:06]  * BUGabundo checks apt-cache policy
[19:06] <chrisccoulson> and we can't re-assign them to another package once an upstream task has been added
[19:06] <BUGabundo> ok... my bad.. my version was from archive
[19:06] <chrisccoulson> thats ok. it's just something to bear in mind, and it isn't obvious from the launchpad UI how to do it
[19:07] <BUGabundo> I know how to do it
[19:07] <chrisccoulson> that's ok, i wasn't sure ;)
[19:07] <BUGabundo> I file or comment on many bugs daily
[19:07] <BUGabundo> I have several of my projects on LP to
[19:07] <BUGabundo> *too
[19:08] <BUGabundo> as I said before, I really meant to do what I did, 'cause I thought I was using the PPA version
[19:08]  * BUGabundo thinks its time to comment that PPA
[19:08] <chrisccoulson> thats ok, i didn't know at first
[19:08] <BUGabundo> so I filed against LP.net/do BTS
[19:09] <chrisccoulson> that bug is fixed for you now though isn't it? i tried last night with the update gtk-sharp2 packages, and it worked ok
[19:11] <BUGabundo> yeah
[19:11] <BUGabundo> G-DO already works
[19:11]  * BUGabundo checks if it is closed
[19:12] <BUGabundo> Fix released
[19:50] <MrKanister> Hi. The bug #117771 seems to be fixed (as the second last comment says - one year ago). I wonder if I can mark it as "fix released" with a comment from https://wiki.ubuntu.com/Bugs/Responses#Bugs%20resolved%20after%20update%20or%20config%20change ?
[19:59] <pedro_> MrKanister: isn't that a duplicate of bug 151787 ?
[20:00] <pedro_> MrKanister: it seems it now gives you a gtkfilechooser for the unknown mime types instead of presenting that dialog with the download
[20:00] <pedro_> MrKanister: did you tried to reproduce it that way?
[20:02] <MrKanister> pedro_: Thanks for your answer. I didn't know about the duplicate and so I'm going mark te bug as one. I will have a look at the upstream bug. Thanks
[20:05] <pedro_> MrKanister: thanks you for following up, btw if you can't reproduce it anymore please also comment on the upstream report ;-)
[20:05] <pedro_> gotta run now, see you later
[21:24] <maco> asac: i wanted to ask you about a bug that was reported that i think is actually 2 bugs, one in NM, one in the kernel, because i can reproduce the NM half
[21:25] <maco> asac: crimsun said he agrees that it's probably two bugs, so i left a comment on it, but i didn't want to open a NM task without talking to you first
[21:26] <maco> BUGabundo: you pinged him at just befor 8am in our timezone. he was driving into work.
[21:46] <BUGabundo> lol maco
[22:16] <asac> maco: which bug?
[22:17] <maco> asac: bug 306611
[22:17] <maco> :(
[22:18] <maco> oh...lp is down right now, right?
[22:18] <maco> asac: ok so the bug is that after resuming from hibernate, NM claims all networking is disabled though it wasnt disabled before hibernate.  i can reproduce that much.
[22:18] <maco> the reporter also says that they can't modprobe their wireless driver
[22:19] <maco> i can't reproduce that. i can ifconfig wlan0 up and have things working again from the command line jsut fine
[22:27] <asac> maco: yeah as i said its a race
[22:27] <asac> or isnt it that bug?
[22:27] <asac> maco: there is definitly a master  bug about NM being "disabled" after resume
[22:27] <asac> you can click on it in applet with right click.
[22:29] <maco> asac: yeah. one time re-enabling networking worked, one time i had to use the CLI
[22:30] <asac> maco: there is a master for that
[22:30] <maco> ok