[00:00] <anakron> HI all
[04:50] <artfwo> Hi! May I ask, what package is currently used for reporting kernel bugs?
[04:51] <bdmurray> linux
[04:51] <artfwo> ah, thanks :)
[05:19] <wishie> i have an issue with hotkey-setup on hardy 64bit, which loosely relates to bug #33045
[05:20] <wishie> some of my 'special' keys are mapped wrong, and 2 of them dont work. id like to know how i can fix this
[06:23] <dholbach> good morning
[07:40] <hggdh> morning dholbach
[07:48] <dholbach> hi hggdh, hi thekorn
[07:49] <thekorn> good morning dholbach !
[08:35] <persia> pedro: Thank you.
[09:55] <hggdh> anyone here running Evolution 2.23.90 (Intrepid)?
[10:01] <mouz> Should I as a triager nominate bug 259942 for a release? Should I set a milestone?
[10:05] <hggdh> mouz, its a regression... james_w did the previous update, perhaps he can state this
[10:07] <hggdh> mouz, at least you can tag it 'regression'
[10:08] <mouz> hggdh: ok i'll do that and wait for james_w 's reply. thanks.
[10:09] <hggdh> Intrepid had the patch as of 1:2.23.5-0ubuntu1
[10:10] <hggdh> it seems to have been dropped on 1:2.23.6-0ubuntu1
[10:37] <james_w> mouz, hggdh: we just patched it out for hardy
[10:38] <james_w> this capplet is now upstream, and we dropped most of the patches to follow them
[10:38] <james_w> it's ok to forward that bug upstream if there wasn't one already
[10:38] <james_w> you can milestone it for intrepid as well if you like, as we can always just patch it out again
[11:47] <aetern> hidy
[11:47] <aetern>  8-)
[12:01] <aetern> so, what is wrong with hardy heron, intrepid ibex ubuntu versions? My laptop freezes sometimes, i can't do anything... earlyer versions of ubuntu hadn't this error... Using asus f5 x50m model, amd turion 64(mobile thechnilogy mk - 36), 1GB of rams, NV geforceGo 6100.
[13:24] <hggdh> pedro_, ping
[13:24] <pedro_> hggdh: hello
[13:25] <hggdh> hi, good morning... a question: are you running Evolution 2.23.90?
[13:26] <hggdh> pedro_, ^^
[13:26] <pedro_> hggdh: sadly, yes
[13:26] <hggdh> :-)
[13:26] <hggdh> could you please click on Help/Report a Problem?
[13:26] <pedro_> It deleted my a big part of my emails :-/
[13:26] <pedro_> s/my/me
[13:26] <hggdh> same here...
[13:26] <pedro_> hggdh: let me try
[13:27] <hggdh> for me it does not open LP, and I was wondering if it is a screw-up on my side
[13:28] <pedro_> blah is not working
[13:28] <hggdh> AH!
[13:28] <hggdh> OK, then I did not mess up my system :-)
[13:28] <hggdh> I think this may have been due to the changes on LP
[13:28] <pedro_> I get this on the CLI :
[13:28] <pedro_> Usage: apport-gtk [options]
[13:28] <pedro_> apport-gtk: error: no such option: --package evolution --pid 7919
[13:29] <pedro_> are you getting the same?
[13:29] <hggdh> I did not get any output :-(
[13:29] <hggdh> I will test again (I was prepping a change to 03_lpi.patch to take out bug buddy)
[13:30] <hggdh> thank you, pedro_ . I will open a bug on this later this evening (now I have to get to my contract)
[13:31] <pedro_> hggdh: you're welcome, thanks for let me know about it ;-)
[13:32] <hggdh> just for grins, I ran apport-gtk --help -- it may be that it is now required to have the equal sign on long options (--package=evolution --pid=xxxx)
[14:20] <lumn0t> I'm looking for some help with hunting down enough information to report a bug.  My issue is described in a LaunchPad question currently (https://answers.launchpad.net/ubuntu/+source/gnome-power-manager/+question/38900), but I think the larger issue has gone beyond the question.
[14:22]  * lumn0t prods the channel.
[14:25] <lumn0t> Hello? Hello?
[14:27] <LaserJock> hmm, maybe everybody is out to lunch :-)
[14:27] <chmac> I'm trying to file a bug against dhclient, but it's saying "There is no package name 'dhclient' published in Ubuntu"
[14:27] <chmac> Even though when I click "Choose" it lists dhclient as an option
[14:27] <chmac> It says "not uploaded" underneat dhclient
[14:27] <chmac> Anyone know how / where I file the bug?
[14:28] <ogra> dhcp3-client
[14:28] <LaserJock> dhcp3-client
[14:28]  * LaserJock ^5s ogra 
[14:28] <ogra> :)
[14:28] <chmac> :)
[14:29] <lumn0t> Responses! Horrah!
[14:30] <chmac> Oh dear, I've just realised, I'm using NetworkManager 0.7, perhaps that's the issue...
[14:30] <chmac> Hmm
[14:30] <chmac> No, it's not, I tested that already I think...
[14:31] <lumn0t> Problem: GNOME settings seem borked.  Two obvious symptoms of this are gnome-power-manager had issues and GNOME themes will not apply.  This is being discussed in a LaunchPad question (https://answers.launchpad.net/ubuntu/+source/gnome-power-manager/+question/38900).
[14:32] <LaserJock> yeah, that's pretty funky
[14:32] <lumn0t> Not sure what package to file a bug against.
[14:33] <LaserJock> seb128 or pedro_ would probably be good people to ask
[14:34] <lumn0t> Is privmsg the best way to direct this, then?
[14:34] <pedro_> lumn0t: for the GNOME Themes issue is gnome-settings-daemon running?
[14:34] <pedro_> is a known issue that it's crashing quite a lot
[14:34] <lumn0t> Ah.
[14:35] <pedro_> that could be why the themes are not being applied
[14:35] <pedro_> for the gnome-power-manager tedg is the right person since he's the maintainer ;-)
[14:35] <lumn0t> gnome-settings-daemon is indeed running.
[14:35] <pedro_> he should be online shortly
[14:36] <pedro_> lumn0t: are you running Intrepid or Hardy?
[14:46] <lumn0t> Hmm.
[14:46] <lumn0t> gnome-settings-daemon does seem to be the culprit.  Reinstalling the package has brought themes back.
[14:49] <pedro_> well reinstalling it shouldn't make any difference, unless your installation was broken
[14:50] <pedro_> we don't have any bugs regarding that and the only issues with themes are in Intrepid with some g-s-d crashes
[14:50] <LaserJock> pedro_: it seems to be a problem in a 8.04-> latest updates
[14:50] <LaserJock> that question has at least 3-4 Hardy users with the same problem, I'd suspect a bad SRU
[14:51] <lumn0t> ..er.. Yes.  But the installation was *not* broken before some relatively recent update.  I was hoping to help find what it was that broke both gnome-power-management and gnome-settings-manager.
[14:51] <pedro_> could be but there's no new g-s-d package since april
[14:52] <pedro_> s/april/may
[14:52]  * pedro_ looking at the sru list
[14:56]  * lumn0t wonders where the sru list is.
[14:56] <pedro_> lumn0t: http://people.ubuntu.com/~sbeattie/sru_todo.html
[14:57] <lumn0t> And I'm curious that if there was some common cause to both gnome-power-manager and gnome-settings-daemon getting squirrelly, if something else may have been affected that I have not noticed yet.
[15:02] <lumn0t> I don't recall when I first saw the symptoms, but the LaunchPad question was opened 7-11, so the update that may have caused the issue dates from before then.
[15:16] <lumn0t> Would something that affected gnome-settings-daemon have affected the "configuration defaults" for gnome-power-manager that the reinstall of g-p-m resolved?
[16:02] <bddebian> Boo
[16:04] <ogra> bee
[16:05] <wishie> i have an issue with hotkey-setup on hardy 64bit, which loosely relates to bug #33045
[16:06] <wishie> could i possibly get some help with this issue ? i need to know how to edit /usr/share/hotkey-setup/hp.hk file, so it works on my laptop, and doesnt cause crashes (like it currently does)
[16:26] <Awsoonn> Hugday is on the wiki!
[16:27]  * Awsoonn runs before the tomatoes are thrown 
[19:16] <bdmurray> james_w: do you know something about "No handlers could be found for logger 'bzr'"?
[20:02] <afflux> huh. I just got the notice that bug 259311 was marked as a dup of bug 250506. Why is that?
[20:07] <bdmurray> afflux: its in the activity log
[20:08] <afflux> oh, well. I didn't see that it actually wasn't marked anymore. Woops :)
[20:08] <bdmurray> it was quick! 10 seconds
[20:09] <afflux> isn't that minutes?
[20:09] <bdmurray> minutes / seconds - whatever ;)
[20:09] <afflux> yup, quick anyway ;)
[20:17] <nullack> Im not an IRC guru - how do I snipe what chans hes on?
[20:19] <jpds> nullack: /whois should be enough, assuming he doesn't have the +i (invisible) usermode on.
[20:19] <nullack> Ping Ampelbein : Thanks for your email I got mixed up with bugs Im sorting it out. The particular bug is a wontfix, its by design a non issue
[20:24] <persia> Note that even +i people can be found if they share channels in common with the person running /whois
[20:24] <Ampelbein> nullack: oh, ok. just saw the mail and thought i'd quickly set duplicate status, haven't checked anymore. will do that next time.
[20:24] <nullack> Its not duplicate - I was suffering from multiple bug syndrome and made an error Im fixing it
[20:27] <Ampelbein> got that. happens sometimes.
[20:44] <james_w> bdmurray: your ~/.bzr.log is probably not writeable for your user
[20:45] <james_w> it's a pain to try and give a better message for though, as it's a library that gives the warning, and doesn't give much indication when it has.
[20:46] <bdmurray> james_w: but it is! unless cron needs different permissions
[20:48] <james_w> bdmurray: it may be something else then, but that's the usual reason for the message
[20:48] <james_w> this is your users crontab, and you're not sudoing?
[20:48] <james_w> i.e. the process is run as your user?
[20:48] <bdmurray> james_w: it's weird because I'm not even using bzr
[20:48] <james_w> oh, what are you using?
[20:49] <bdmurray> its, just a bash script and python script
[20:49] <sbeattie> bdmurray: but python-launchpad-bugs tries to determine what version it is via bzrlib
[20:49] <bdmurray> I'll pastebinit
[20:49] <bdmurray> sbeattie: ah, winner!
[20:50] <bdmurray> sbeattie: did you fix it?
[20:50] <james_w> does it exec() bzr for that?
[20:52] <bdmurray> looks like it import bzrlib.branch
[20:52] <sbeattie> bdmurray: no, that's as far as I got in digging into the problem.
[20:52] <james_w> I wouldn't have thought that this triggered that message, but I may well be wrong
[20:55] <bdmurray> james_w: Do you have any ideas then?
[20:56] <sbeattie> bdmurray: did you look in your .bzr.log file on rookery?
[20:56] <james_w> bdmurray: no, sorry, I'm a bit stumped
[20:57] <james_w> I've only ever seen this be a permission error
[21:00] <bdmurray> There is a message about using 'bzr upgrade' for bughelper
[21:01] <sbeattie> james_w: I get it the same message, even though it successfully wrote to to my .bzr.log
[21:02] <sbeattie> bdmurray: mine contains nice tracebacks from each run because it's trying to do bzr operations on the cwd, which for me was $HOME and thus contains no bzr metadata.
[21:04] <sbeattie> Odd: 0.089  Plugin name __init__ already loaded
[21:05] <james_w> that's odd
[21:06] <james_w> well, the last message happens on every run, but the rest is odd
[21:12] <sbeattie> james_w: note that this is showing up on rookery, which is a dapper install.
[21:12] <bdmurray> but it now has bzr 1.6 I think
[21:14] <bdmurray> sbeattie: I noticed the same thing on cranberry though
[21:14] <bdmurray> which is hardy
[21:14] <chrisccoulson> bug 131846 from the hug day list is an intersting one
[21:15] <bdmurray> I've seen a duplicate of that
[21:15] <chrisccoulson> the reporter says that gnome-panel ignores their $PATH env variable when it is defined in ~/.bashrc
[21:15] <chrisccoulson> i have a customised $PATH defined in /etc/environment, and it uses that
[21:15] <sbeattie> bdmurray: curious. I don't see it on my hardy machine.
[21:15] <chrisccoulson> so i'm wondering if it's actually a bug in gnome-panel
[21:15] <bdmurray> sbeattie: are you up to bzr 1.6 though?
[21:16] <sbeattie> nope
[21:17] <sbeattie> I'm eating distro dogfood not bzr dogfood.
[21:18] <bdmurray> chrisccoulson: oh, that's the bug I'm thinking of ;)
[21:18] <bdmurray> I can recreate it
[21:19] <chrisccoulson> how do you set your $PATH environment? Do you define it in ~/.bashrc too?
[21:19] <bdmurray> oh, my .zshrc
[21:19] <bdmurray> :)
[21:19] <bdmurray> but it's in my ~/.bashrc too fwiw
[21:19] <jpds> zsh FTW.
[21:21] <chrisccoulson> i'll try modifying another users .bashrc on my machine in a bit and see if i can recreate it too. but gnome-panel searches all of the folders in my $PATH environment, which is defined in /etc/environment (so I've done it a bit different to you)
[21:21] <chrisccoulson> that might mean it isn't a bug in gnome-panel
[21:22] <chrisccoulson> for example, i have a load of apps installed in /opt/bin. i can run them no problem by pressing ALT+F2 and typing the program name, so I'm not seeing this issue
[21:37] <chrisccoulson> bdmurray: referrring to bug 131846 again - i think the issue because /bin/sh (symlinked to /bin/dash) is the shell used when the session loads. Dash appears to ignore ~/.bashrc when it loads, which would explain why gnome-panel doesn't search the full $PATH on your machine, but does search it on mine (because I have $PATH defined elsewhere).
[21:37] <chrisccoulson> i'#ve just tried it here by modifying my bashrc. after i've modified $PATH and launch a new bash shell, the new $PATH takes effect. if i then exit and launch dash, it doesn't take effect
[21:39] <bdmurray> If I start dash and echo $PATH I see /home/brian/bin there
[21:39] <chrisccoulson> hmmmm, that's strange
[21:39] <chrisccoulson> do you start dash from within a bash session which already has the environment set correctly?
[21:40] <bdmurray> yeah, I guess that isn't right
[21:41] <chrisccoulson> what you could do is launch a terminal (bash), then clear your $PATH environment by typing (PATH=""). once you've done this, launch dash using '/bin/dash' and then inspect the environment
[21:42] <chrisccoulson> actually, that doesn't behave as expected. $PATH is still empty after loading dash
[21:42] <chrisccoulson> a better way of verifying it might be to temporarily set the /bin/sh sym-link back to /bin/bash. i'll try that on my intrepid VM in a bit
[21:45] <sbeattie> chrisccoulson: you probably want /bin/dash -l
[21:47] <sbeattie> though that's not reading /etc/environment here.
[21:49] <chrisccoulson> thanks for the clarification sbeattie
[21:53] <dupondje> https://bugs.launchpad.net/ubuntu/+bug/260208
[21:53] <dupondje> there :p
[21:53] <dupondje> a fresh bug :p
[21:56] <chrisccoulson> sbeattie / bdmurray - i can confirm on intrepid that dash ignores the ~/.bashrc file. i set my users shell to /bin/dash, and when I open gnome-terminal, by customised entries are not there. however, if I launch a bash shell, they all appear there
[21:56] <chrisccoulson> i'll re-assign that bug from gnome-panel to dash, if we want dash to look at ~/.bashrc
[21:56] <bdmurray> I don't think that is right
[21:57] <chrisccoulson> which bit?
[21:57] <bdmurray> reassinging it
[21:57] <bdmurray> I'd ask seb128 about as he is probably most familiar with the package and our diff from upstream
[21:58] <chrisccoulson> no problem. i had a quick look in the source for gnome-panel, and it does appear to correctly search $PATH when it launches an application. the problem is that it's environment isn't correct as it is spawned from dash
[22:00] <chrisccoulson> i'll catch seb128 when he's on here next and speak to him about it.
[22:48] <Pimpy> hi there, need support if possible for my crash for compiz,real after a few seconds on boot on desktop- have 8800gt, 8.10 alpha4
[22:48] <Pimpy> nvidia official driver ver 177