[01:22]  * mase_work is here and willing to help with -intel bugs. 
[02:46] <torkiano> new information for bug #348275 if asac or somebody are interested
[02:47] <torkiano> the WPA2 don't work only after computer suspend
[04:31] <cavedon> hi all
[04:31] <cavedon> I am testing ubuntu beta
[04:31] <cavedon> I have an annoying regression:
[04:32] <cavedon> when I reboot or halt, it stops at "will now halt" or "will now reboot" most of the times
[04:32] <cavedon> any idea of how to debug that?
[04:32] <cavedon> https://bugs.edge.launchpad.net/ubuntu/+bug/349778
[04:32] <kees> cavedon: check with #ubuntu-kernel it is likely a problem with the "linux" package -- the kernel itself.
[04:33] <cavedon> kees: tnx, i'll move there!
[06:40] <dholbach> good morning
[06:55] <YoBoY> good morning
[07:32] <dtchen> ara: please run the http://www.alsa-project.org/alsa-info.sh bash script and attach the output to bug 301755
[07:32] <ara> hey dtchen :-) sure, will do. I hope to see you in Barcelona ;-)
[07:44] <dtchen> ara: does raising 'PCM' and lowering 'Master' help? (try using alsamixer)
[07:45] <ara> dtchen: I'll try
[07:45] <dtchen> ara: i think i said that backwards
[07:45] <dtchen> dtchen: i.e., raising 'Master' and lowering 'PCMm'
[07:46] <ara> so, do I raise Master?
[07:46] <dtchen> yes, raise 'Master' and lower 'PCM'
[07:48] <ara> OK, I am now testing. I will let you know in an hour (here and/or a comment on the bug)
[07:48] <ara> dtchen: because crackling noise does not happen always. It usually happens: between songs, or when playing a song an a buddy enters pidgin and things like that
[07:49] <dtchen> ara: bug comment, please. i won't have access to irc for 14 hours
[07:49] <ara> dtchen: sure
[07:49] <dtchen> right. i need to see if i need to roll yet another test kernel.
[07:50] <dtchen> i'll outline test instructions after reading your comment(s)
[08:02] <ara> dtchen: and if the test kernel solved the issue, will does changes (in the kernel) arrive in the ubuntu kernel in jaunty?
[09:29] <lopos> hi
[09:29] <lopos> good job destroying open office's UI
[09:29] <lopos> can we mark this as high and fix quickly?    https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/352954
[12:39] <daywa1> hello?
[12:41] <BUGabundo> daywa1: hay
[13:05] <theseinfeld> I have a question about upstream marking. If you want to mark a bug that needs upstream forwarding, in the wiki it sais, I quote:
[13:05] <theseinfeld> <<Open an upstream task, but not assign a bug watch >>
[13:05] <theseinfeld> how do you open an upstream task? Is it the link: "Also affects project"?
[13:06] <theseinfeld> in LP
[13:06] <james_w> yes
[13:07] <theseinfeld> in that case, how do you do the last part << but not assign a bug watch >>
[13:08] <theseinfeld> once you open the "Also affects project" you need to add something there...
[13:08] <theseinfeld> or am I missing something?
[13:08] <james_w> you select the project
[13:09] <james_w> which may be auto-selected
[13:09] <james_w> then on the next bit check "I don't have a bug number right now, I would just like to mark this project as affected" or something
[13:10] <theseinfeld> there are only these options:  I have the URL for the upstream bug:, I have already emailed an upstream bug contact: and  I just want to register that it is upstream right now; I don't have any way to link it.
[13:10]  * theseinfeld is puzzled...
[13:11] <james_w> last one
[13:11] <james_w> I was just guessing what the text was
[13:12] <theseinfeld> hmm
[13:12] <theseinfeld> I will try it. I will also change the wiki for this, as it is a bit unclear...
[13:13] <james_w> thanks
[13:13] <theseinfeld> james_w, the text basically suggests that it is already upstream but there is no link "I just want to register that it is upstream right now; I don't have any way to link it."
[13:14] <theseinfeld> I am referring at the "Marking a Bug as Requiring Forwarding"
[13:14] <theseinfeld> so, basically it hasn't been reported upstream...
[13:16] <theseinfeld> james_w?
[13:16] <james_w> yeah, the wording isn't great
[13:17] <theseinfeld> should I also file agains LP?
[13:17] <theseinfeld> :D
[13:17] <james_w> sure
[13:17] <theseinfeld> ok
[13:17] <theseinfeld> thanks for the assuring help! :D
[13:19] <theseinfeld> james_w which si the best launchpad project for the bug report? launchpad-projects or launchpad-foundation?
[13:19] <theseinfeld> I am not so great with those launchpad projects :(
[13:20] <theseinfeld> or is it launchpad-report-tool (bug report tool?)
[13:20] <james_w> you can just report it on "launchpad"
[13:33] <bddebian> Boo
[13:34] <pedro_> foo
[13:35] <bddebian> :)
[14:02] <BUGabundo> pedro_: stealing my line? bah
[14:03] <BUGabundo> Fuum
[14:06] <BUGabundo> hggdh: have you seen yoboy around?
[14:08] <hggdh> BUGabundo, no, I have not
[14:15] <torkiano> hello, I'm the reporter of the bug #348275 . I have news: I can connect in kubuntu BUT not in Ubuntu. I have syslog files if anyone is interesed
[14:16] <Hobbsee> asac: ^
[14:17] <BUGabundo> torkiano: I can connect with NM on kubuntu but not Ubutnu?
[14:17] <BUGabundo> is that correct?
[14:17] <torkiano> BUGabundo, yes
[14:18] <BUGabundo> that's really strange
[14:18] <torkiano> yes, i know
[14:18] <BUGabundo> better leave it to asac
[14:19] <EagleScreen> In my university, we have a WPA-Enterprise wifi net, I can connect to it using networkmanager-kde but not with networkmanager-gnome
[14:20] <BUGabundo> nm-kde is known to be utterly broken on kde 4.2.x
[14:20] <torkiano> I use the plasma applet
[14:20] <BUGabundo> that's the one broken too
[14:21] <EagleScreen> nm-kde (KDE3) applet never has failed for me
[14:22] <torkiano> BUGabundo, well in my case is working ;)
[14:22] <BUGabundo> jaunty or ibex?
[14:23] <BUGabundo> EagleScreen: I'm talking of kde4
[14:23] <EagleScreen> current kde4 widget for nm is buggy as hell
[14:24] <torkiano> BUGabundo, in my case latest jaunty
[14:24] <torkiano> and kernel-backports installed
[14:24] <asac> Hobbsee: looking
[15:53] <santana1> hello?
[15:56] <hggdh> heh. Fast quit...
[15:57] <BUGabundo> lasted a good 2 min
[16:47] <kees> nhandler: you around to approve a feature-freeze-exception?  (bug 352801)
[16:47] <kees> er, wrong channel
[17:59] <pedro_> Ubuntu QA Meeting in ~1 minute at #ubuntu-meeting
[19:59] <askand> Is bug 35341 correctly marked as regression-potential or does something else need to be done?
[19:59] <askand> Sorry,  bug 353341
[21:07] <tawmas> Hi all! I was installing from the server CD when I encountered a gotcha. But I'm not sure if I did something stupid or I found a true problem... likely the former.
[21:08] <tawmas> what I did was to select noexec for the /var partition
[21:08] <tawmas> is that a bad idea?
[21:21] <penguin42> Hi - which package owns the session selection dialog in the gdm login? Is it gdm or something else? (IN particular this is a style/themeing issue)
[21:25] <james_w> penguin42: I'm pretty sure it's gdm
[21:26] <seb128> gdm
[21:26] <penguin42> ok
[21:27] <penguin42> the buttons aren't highlighting the current selection properly (well they almost are but you have to look hard)
[21:27] <penguin42> on a different one; after an upgrade I've just done (last was probably Sunday) - my panels have just swapped monitors
[21:36] <penguin42> hmm actually maybe ubuntu-gdm-tehem
[21:36] <penguin42> theme
[21:40] <seb128> penguin42: see bug #192009 about the panel monitor thing
[21:42] <penguin42> seb128: Yep that looks like the culprit - if I move them back to where they were will they stay there after the next reboot?
[21:43] <seb128> no idea I don't use multi monitor and didn't do this change
[21:43] <penguin42> ok; you really should - it makes for a much more exciting selection of bugs :-)
[21:47] <BUGabundo> humm how can I debug totem slow down?
[21:47] <BUGabundo> $ totem --debug doesn't print anything
[21:49] <BUGabundo> seb128: is totem one of yours ?
[21:50] <seb128> BUGabundo: nothing is specifically mine, it's written by GNOME
[21:50] <seb128> BUGabundo: I look at its bugs though
[21:51] <BUGabundo> I have an inicial bug at 353444
[21:51] <BUGabundo> but not details that will help determine why it slows down
[21:51] <BUGabundo> 2 more users on +1 confirmed they see the same
[21:51] <seb128> bug #353444
[21:54] <bdmurray> bryce: regarding bug 353197 does that crash have anythign to do with the nvidia driver?
[21:54] <seb128> BUGabundo: I don't understand the description, do you get the same issue with totem-xine?
[21:54] <penguin42> seb128: Is there anything that I could do to help #58977 ?   It looks like it needs some specification changes - or have those happened?
[21:55] <seb128> bug #58977
[21:55] <BUGabundo> seb128: vlc and mplayer work fine
[21:55] <BUGabundo> let me see if I have xine
[21:55] <seb128> penguin42: no clue I don't use xinerama don't do X and use compiz
[21:55] <BUGabundo> seb128: instaling now
[21:55] <bryce> bdmurray: yes, when you see _nv######() that indicates a crash inside proprietary nvidia code
[21:56] <penguin42> seb128: Ah apologies, you were first responder on it
[21:56] <bdmurray> bryce: awesome, that's what I was thinking
[21:56] <bryce> bdmurray: fwiw those kinds of crashes are impossible for us to do anything with
[21:56] <bdmurray> bryce: right - I was guessing as much too
[21:57] <penguin42> bryce: You having any luck stabilising the intel stuff up?  Jaunty is a lot flakier than intrepid so far, I'm guessing the GEM stuff?
[21:57] <bdmurray> bryce: Do you have a standard reply for those?
[21:58] <bryce> bdmurray: no I just dump them in the appropriate nvidia- bin
[21:58] <bryce> bdmurray: I suppose there is some value in the aggregate for judging relative stability/bugginess of -nvidia in general
[21:59] <bryce> I don't triage nvidia-*, so don't have any stock replies, nor check for dupes, etc.
[22:00] <bryce> penguin42: mostly I've been focusing on xserver stabilization in general.  -intel just has so many bugs it's hard to even know where to start
[22:00] <bryce> penguin42: I did spend the whole day yesterday just on 8xx bugs
[22:00] <bryce> penguin42: so if you're an 855 or 865 user, it should be more stable now.  I haven't any 8xx hardware so can't verify that myself.
[22:01] <bdmurray> bryce: How do you know which nvidia- package to use?
[22:01] <penguin42> bryce: Ah, I'm 945G
[22:09] <bryce> bdmurray: sometimes the bug reporter says which one they installed.  If not, put into nvidia -180 and if anyone does bug triaging there some day they can sort it out better
[22:09] <bdmurray> Ah, I found it in boot.dmesg
[22:09] <bdmurray> [   25.065260] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  180.37  Fri Mar  6 00:32:38 PST 2009
[22:09] <bdmurray> 180 I'm reckoning
[22:09] <bryce> yep that looks like -180
[22:15] <BUGabundo> bryce: can you please provide me with the X debuging wiki link?
[22:16] <bryce> wiki.ubuntu.com/X
[22:17] <BUGabundo> found it https://wiki.ubuntu.com/X/Backtracing
[22:18] <BUGabundo> user is having trouble with resume on nvidia
[22:19] <penguin42> hmm that's useful - the signals and location of the core is useful