[00:47] <Ampelbein> woohoo. i won $50.000.000 in a lottery. i'm just sending the $1500 the lottery-administration needs for processing my winnings ;-)
[00:48] <Ampelbein> (first spam to my 4 week-old new launchpad-emailadress)
[01:26] <hggdh> all: eeebotu is inactive due to an (unknown) issue with the LP feed
[03:53] <xtknight> debdiff for Bug 212493 has been posted.  would be grateful if it could be uploaded.  annoying mplayer pause bug :)
[05:49] <andersk> Whose bug is it that the volume control hotkeys don't work while a popup menu is open in any application?
[05:58] <andersk> Guessing gnome-settings-daemon for now (bug 356787).
[06:47] <YoBoY> andersk: could be a gtk problem... :]
[06:51] <YoBoY> or a shortcut's problem (not only volume control is déactivated, try alt+F2 for exemple)
[07:23] <bullgard4> https://bugs.launchpad.net/ubuntu/+source/gnome-utils/+bug/275535 gets me a message: "the bug has been fixed to svn now" and another one: "gnome-utils (Ubuntu) status:   Triaged → Fix Committed". How can I make good use of these two messages? I am using Ubuntu 8.04.2.
[07:32] <YoBoY> bullgard4: you can't, this issue should be fixed in the next release of gnome, but no backport for the release. if you need this patch you can try to apply yourself the patch (complicated) or you can explain in the bug report why this should be backported ( https://help.ubuntu.com/community/UbuntuBackports ) but i don't it's far more complicated ... :]
[07:34] <YoBoY> (sorry for my english) ¬_¬"
[07:47] <YoBoY> bug 356787 << confirmed, importance is Low i think
[09:16] <BUGabundo_> guud morning
[10:33] <savvas> does someone know why bug 331306 is linked to "predrag" upstream?
[10:35] <savvas> I mean.. what, or better yet who is predrag since it's a name? :P nothing in the explanation overview of the project
[11:39] <Armag3ddon> hello all
[11:42] <BUGabundo_> Armag3ddon: hi
[11:43] <Armag3ddon> anyone i can report a bug to ?
[11:43] <BUGabundo_> Armag3ddon: whats up?
[11:45] <Armag3ddon> im cool, listen i have ubuntu 9.04 the beta version is works fine but sometimes the shutdown button works as a restart
[13:50] <jurism> http://pastebin.com/m37cc52feNo I have soft lockup problem ata_aux process usage is 100%, I can login into ssh but I can not even restart server. Thank You for answers!
[13:55] <YoBoY> re
[15:29] <bddebian> Boo
[16:40] <bdmurray> mvo: could you check out the log in 331280?
[16:40] <mvo> bdmurray: sure, give me a sec
[16:41] <mvo> bdmurray: the log looks like magaio is already on jaunty, I will ask him
[16:41] <mvo> bdmurray: hm, maybe not
[16:44] <mvo> bdmurray: very inconclusive :/
[16:44] <mvo> bdmurray: I added a followup comment
[17:50] <Ampelbein> ping bdmurray: shouldn't bughelper find also private bugs if the user is in the apport-crash-bug-triagers group and a valid launchpad-cookie file is given to it?
[18:00] <bdmurray> Ampelbein: doesn't it?
[18:01] <Ampelbein> bdmurray: at least for me, no it doesn't.
[18:01] <bdmurray> Ampelbein: can you give a test case?
[18:02] <Ampelbein> sure. i'll pastebin the clue-file.
[18:05] <Ampelbein> bdmurray: http://paste.ubuntu.com/146332/
[18:05] <Ampelbein> this only finds me public bugs
[18:06] <Ampelbein> bdmurray: this is cookie: .launchpad.net  TRUE    /       TRUE    1268712041      lp      BqdK[...]lYD3rSjEk
[18:09] <Ampelbein> bdmurray: i invoke with bughelper -p pidgin --cookie=/home/andreas/.lpcookie --format=html --file=/home/andreas/Desktop/pidgin-bughelper.html -m 300000
[18:23] <bdmurray> Ampelbein: on a call at the moment will look at it soono
[18:24] <Ampelbein> np
[18:33] <thekorn> Ampelbein, not sure, but maybe I can help you, which bug should match this clue-file and is not in your result?
[18:41] <Ampelbein> thekorn: bug 356373 for example.
[18:44] <thekorn> ok, what's the result of:
[18:44] <Ampelbein> if it's important: i extracted the cookie using "Export Cookies"-plugin in firefox, then copy the launchpad-line.
[18:45] <thekorn> bugnumbers -p pidgin -m 300000 --format numbers --cookie <COOKIE>|grep 356373
[18:47] <Ampelbein> doesn't get shown there either.
[18:48] <Ampelbein> could there be something wrong with the exported cookie?
[18:48] <thekorn> Ampelbein, it works for me, so maybe your cookie you extracted is outdated
[18:48] <thekorn> Ampelbein, you can use your FF cookie directly
[18:48] <thekorn> no need to extract it
[18:49] <Ampelbein> thekorn: how that? they are stored in a sqlite database, as far as i can tell.
[18:50] <thekorn> Ampelbein, bughelper supports such cookies
[18:51] <Ampelbein> thekorn: woohoo. that works. tyvm!
[18:51] <thekorn> both types of mozilla cookies are supported: the "old" txt ones and the sqlite ones from FF3
[18:51] <Ampelbein> thekorn: consider yourself hugged!
[18:52] <thekorn> juhu :)
[18:52] <Ampelbein> ;)
[18:53] <thekorn> Ampelbein, hmm, I don't see how your clue should match this bug 356373
[18:54] <thekorn> non of the strings you are searching for are in the bugreport + comments
[18:54] <thekorn> AFAICS
[18:54] <thekorn> or maybe I'm blind and need new glasses
[18:55] <Ampelbein> thekorn: http://launchpadlibrarian.net/24908012/Stacktrace.txt there is gmarkup.c:2251 (line 3) and purple_core_quit on #11
[18:55] <Ampelbein> ah, forgot -A
[18:56] <Ampelbein> so it wouldn't have a chance to find it even if the cookie was valid...
[18:56] <thekorn> Ampelbein, yes, you forgot -A
[18:57] <Ampelbein> thekorn: thanks again
[18:58] <thekorn> no problemo
[19:15] <railk> in jaunty, /etc/init.d/pulseaudio contains a bug that just made an update fail (for me): it contains the line "start-stop-daemon -p $PIDFILE --stop --retry TERM/3 --oknodo || status=$? " ... the || results in status only begin set when its non-0 -> log_end_msg exists with status 1 -> script "fails" -> update "fails". the correct version is simply to move "status=$?" onto a new line or use ";" instead of "||".
[19:18] <mrooney> hooray, #ubuntu-bugs-announce is back
[19:18] <mrooney> bdmurray: is there any room for that channel in the topic?
[19:23] <james_w> railk: is there a bug report open for this?
[19:23] <railk> i couldn't see one...
[19:24] <james_w> please file one
[19:24] <james_w> while raising it here is appreciated comments on IRC are easily lost if they are not seen by the right people at the right time
[19:26] <railk> i'm getting timeout errors from launchpad ... i got one before when apport tried to automatically file the bug
[19:26] <railk> (when the update failed)
[19:34] <railk> james_w: theres bug #336925, but thats been closed wontfix, but the reasoning for closing it is unrelated to my case...
[19:37] <james_w> railk: I'd open a new bug, that one seems sufficiently different
[19:42] <mnemo> railk: did you open a new bug? if so, what was the bug number?
[19:42] <railk> i'm doing it now... :P
[19:44] <railk> 357201
[19:46] <railk> i checked https://launchpadlibrarian.net/24923521/pulseaudio_0.9.14-0ubuntu17.diff.gz and it still contains the line i believe to be causint the problem
[19:47] <mnemo> railk: thanks
[19:48] <james_w> railk: it's good if you can also give the symptoms in the bug report, as well as what you believe is the cause
[19:48] <james_w> it means that others can follow your reasoning, and have to spend less time thinking it through
[19:48] <james_w> obviously providing a fix is very much appreciated :-)
[19:49] <railk> well the failed upgrade is kinda the only symptom i have :P
[19:50] <james_w> the log from that would be useful
[19:50] <railk> i tried to find it
[19:50] <james_w> /var/log/dist-upgrade if it was update-manager dist-upgrade
[19:51] <james_w> /var/log/apt/term.log if not
[19:51] <james_w> (I think)
[19:51] <mvo> james_w: right
[19:51] <james_w> presumably if you are correct then "/etc/init.d/pulseaudio stop && /etc/init.d/pulseaudio start" would exhibit the behaviour
[19:51] <railk> well it wasn't a dist-upgrade... just found it term.log
[19:52] <railk> among all the otehr stuff like the previously failed dist-upgrade :P
[19:52]  * james_w -> dinner
[19:52] <railk> well you'd have to check the result too
[20:43] <blup> Hello i have just installed ubuntu 9.04 beta and dureing installation the mouse pointer was invisible. After installation the mouse pointer is still invisible and i have to enable the "ctrl" key in order to see where it is. The mouse works great but the pointer is invisible. Any idea about how to fix this?
[20:44] <mnemo> blup: what graphics card do you have?
[20:44] <blup> sapphire/ati radeon hd 2600 pro pci-e
[20:45] <blup> not installed the driver yet anyway
[20:46] <mnemo> blup: never heard of that issue before... please file a bug on it
[20:46] <mnemo> and use the "ubuntu-bug" script to file the bug if possible
[20:46] <mnemo> that way information about your graphics card gets attached to the bug automatically
[20:46] <blup> i did it useing the "system testing" anyway without the mouse worlking it's so stressing useing the computer
[20:47] <blup> ubuntu-bug is a gui interface? or have i to open a terminal?
[20:47] <mnemo> terminal
[20:47] <mnemo> and run "ubuntu-bug xorg"
[20:49] <blup> with this report i can't write a message to the developers saying "my mouse pointer is invisible"
[20:49] <mnemo> blup: you can add stuff to the report
[20:50] <blup> it just goes in auto and then just let me see the content before send it
[20:50] <mnemo> blup: you can always edit the bug
[20:50] <hggdh> and ubuntu-bug <package> is the best option -- all necessary data is usually collected
[20:50] <hggdh> automagically
[20:51] <blup> done
[20:51] <blup> i have to register...ok thanx i hope that the ubutnu team will fix it :)
[20:52] <blup> Thank you all. bye
[21:25] <lacqui> is there a way to find out what 'configure' command was used to build a package?
[21:26] <bdmurray> lacqui: look at the build log - what package is it?
[22:00] <lacqui> (sorry, computer was taken over by wife)
[22:00] <lacqui> the package is file-roller, for bug #357257
[22:01] <lacqui> which is apparently invalid now anyway :P
[22:02] <pedro_> it's a duplicate of an already known one, which is going to be fixed shortly
[22:02] <lacqui> but for future reference, how do i get the build log of an installed package?
[22:04] <maxb> You go to its source package page in launchpad, choose a version, choose a build, and then choose to see the buildlog