[09:20] <gema> hi, can I subscribe to the mailing list (ubuntu-bugcontrol@lists.launchpad.net) without being part of the bug-control?
[09:21] <gema> I'd like to start a thread about defect analysis and gather opinions and that list strikes me as the right one to do that
[10:06] <gema> well, I sent the email
[10:06] <gema> I hope it goes through
[12:24] <hggdh> gema: subscription to the Bug Control mailing list is restricted to the members
[12:24] <hggdh> gema: and good morning (or afternoon, as it may be)
[12:24] <pedro_> bom dia hggdh :-)
[12:24] <hggdh> buen dia pedro_ :-)
[12:26] <hggdh> actually, I see no reason to have the ML restricted to members
[12:26] <hggdh> hum
[12:26] <hggdh> we should discuss this
[12:28] <gema> morning, hggdh and pedro_
[12:28] <gema> I sent an email, did it arrive?
[12:28] <pedro_> buenos dias gema
[12:28] <gema> buenos dias pedro_
[12:29] <hggdh> gema: I just moderated it, should be on its merry way
[12:29] <gema> cool, thanks!
[12:31] <jibel> hggdh, pedro_ gema good morning
[12:31] <gema> morning jibel
[12:31] <jibel> hggdh, crash reports are sent to the list and may contain private information.
[12:31] <hggdh> jibel: bon jour monsier
[12:31] <hggdh> jibel: oh yes
[12:32] <pedro_> jibel, Bon après-midi to you :-)
[12:32] <gema> jibel: the archive shows the emails
[12:32] <gema> I mean, if that is the case, are you making sure they don't get archived?
[12:32] <hggdh> now, that's a good question...
[12:33]  * hggdh expects everything gets archived
[12:33] <jibel> pedro_, Buenas tardes señor :)
[12:34] <jibel> gema, indeed, that's what I was thinking while I pressed enter
[12:34] <hggdh> darn! we live among poliglotes!
[12:34] <hggdh> aye, all there
[12:36] <hggdh> oh boy, 29 messages to moderate on the server-bugs list... and I am pretty sure it is all spam.
[12:36]  * hggdh goes clean some spam
[12:37] <gema> hggdh: what about using some software for that? I have heard there are pretty good spam filters out there :P
[12:39] <hggdh> gema: these are the left overs
[12:39] <gema> ahh, ok :)
[14:29] <RedSingularity> mvo: Any idea what can cause the "install update" button not to function?
[14:32] <RedSingularity> mvo: the user is saying that clicking the button has no effect. Seems to work under root though.
[14:37] <mvo> RedSingularity: hello! is there any more info on this available? anything in ~/.xsession-errors or the terminal that u-m was started in?
[14:37] <mvo> RedSingularity: it should log some sort of info when this happens :/
[14:38] <ogra_> and is the user actually an admin user ? :)
[14:38] <ogra_> or doesnt PK bind to that anymore ?
[14:42] <RedSingularity> mvo: will ask.  One more thing.  When the main.log doesnt give a specific package, like 'ubuntu-desktop', thats being held back, what package can I start looking in for the 'trail' of errors?
[14:43] <mvo> RedSingularity: I usually start from the last entriy and work my way back
[14:44] <RedSingularity> mvo: ah good.  Thanks :)
[14:44] <mvo> RedSingularity: but it can be a bit hard to follow, do you have a specific example? we can have a look together (or you can have a look and I double check the results, whatever you prefer) :)
[14:44] <RedSingularity> mvo: let me have a look for an example...
[14:45] <mvo> no rush
[14:50] <RedSingularity> mvo: bug 831799 is an example.  Look at the ERROR part in the main log.  NO package is mentioned.
[14:51] <ubot4> Launchpad bug 831799 in update-manager (Ubuntu) "update-manager error after painful upgrade from 10.04 to 10.10 (affects: 2) (heat: 19)" [Undecided,Incomplete] https://launchpad.net/bugs/831799
[14:51] <RedSingularity> mvo: looks like i narrowed it to libavcodec52.  Not sure if thats correct.
[14:52] <mvo> RedSingularity: thanks, let me have a look
[14:59] <mvo> RedSingularity: right, so I suspect its actually " Installing libavutil50 as Depends of libswscale0" the libswscale0 that has a breaks on mplayer, but I haven't look closer where this mplayer comes from and/or if its a problem of the archive or of a third party site
[15:00] <mvo> RedSingularity: lateron, mplayer is rather unhappy about libswscale0 and libavcodec52, the combination seems to be deadly :)
[15:12] <RedSingularity> mvo: does the mplayer error 'branch' to those two packages?  Is it possible to branch multiple ways in these apt logs?
[15:16] <mvo> RedSingularity: they are definitely confusing, let me re-look at this to make sure I'm not missing something
[15:21] <RedSingularity> mvo: I followed it to libavcodec52. Maybe it branched to the other package too though.
[17:28] <jploz> hello out there!
[17:29] <Abhijit> hi jpds
[17:29] <Abhijit> jploz,
[17:30] <jploz> I've one general question regarding bugs and different ubuntu versions: Image a package which is packaged with different versions in several ubuntu releases
[17:30] <jploz> that is (for example) version 0.1 in Lucid, 0.2 in Natty etc.
[17:31] <jploz> Now, I've some bug reports related to version 0.1
[17:31] <jploz> these are fixed in version 0.2 of the package
[17:32] <jploz> Question: how to handle such szenario? What'd the correct bug status in Ubuntu?
[17:33] <micahg> jploz: https://wiki.ubuntu.com/Bugs/Responses#Fixed_in_Development_release_while_still_existing_in_a_previous_release
[17:33] <jtaylor> jploz: you should evaluate if the bug is important enough for a stable release update
[17:33] <jtaylor> https://wiki.ubuntu.com/StableReleaseUpdates
[17:33] <jploz> Let's say it is important enough.
[17:34] <jtaylor> then follow the instructions on that wiki page
[17:34] <jploz> Can I track the status of the bug over several ubuntu release?
[17:34] <jtaylor> yes you need to nominate it for a series
[17:34] <micahg> only bug control can nominate
[17:34] <jploz> ah
[17:34] <micahg> jploz: you can request a nomination here though
[17:34] <jploz> this makes things clearer
[17:36] <jploz> what is the recommended way? Nominate bugs for each series? Or just set them to "Fix released" as soon as a new version (that fixes the bug) is out?
[17:42] <micahg> jploz: if it's known fixed in the devel release it should be fix released, if it no longer affects the devel release (invalid) with a nomination for a previous series if worth SRUing
[17:44] <jploz> what does it take to become a member of bug control?
[17:45] <micahg> jploz: https://launchpad.net/~ubuntu-bugcontrol
[17:46] <jploz> ok, so for the beginning I could ask for nominations here, right?
[17:52] <micahg> jploz: yes
[17:52] <micahg> jploz: are you planning on fixing any of these?
[17:59] <jploz> @micahg: I'm asking because of the package `sbackup`. Lucid has version 0.10.5 with many bug reports and some of them are severe, Maverick has version 0.11.x which is quite a rewrite and fixes most of them. Many of the old bugs are "Won't fix" because it is impossible to port patches from 0.11 to 0.10. However, some (most annoying) of the old bugs could get fixed, therefore my questions.
[17:59] <meetingology`> jploz: Error: "micahg:" is not a valid command.
[17:59] <jploz> micahg: I'm asking because of the package `sbackup`. Lucid has version 0.10.5 with many bug reports and some of them are severe, Maverick has version 0.11.x which is quite a rewrite and fixes most of them. Many of the old bugs are "Won't fix" because it is impossible to port patches from 0.11 to 0.10. However, some (most annoying) of the old bugs could get fixed, therefore my questions.
[18:00] <jtaylor> maybe a backport would be appropriate
[18:00] <jtaylor> via ubuntu-backports
[18:01] <jtaylor> https://wiki.ubuntu.com/UbuntuBackports
[18:03] <jploz> Thanks to everyone. This solved my questions. Thanks a lot. Bye
[18:06] <micahg> jploz: jtaylor, yes sbackup would be a fine candidate for backports
[18:06] <micahg> jploz: I was just going to suggest if you're going to fix it, you can ask for bug tasks in #ubuntu-motu
[18:07] <micahg> if it's just that someone else could fix it if they like, just ask for a nomination here
[18:10] <jploz> micahg: bug tasks?
[18:11] <micahg> jploz: where you can set statuses/and or take it to work on it on a per release basis
[18:13] <niclas> Hi, if I need help to report a bug is this the place to ask? Or should I ask in a different room maybe? Don't know which package to file the bug against.
[18:14] <jploz> micahg: ok, thanks to you. I got the differences now (I did a SRU some times ago already). thank you. bye
[19:25] <dust_> hi - i got a bug in kubuntu beta2 concerning kleopatra kgpg and gnupg - but i don't know how and where to file it
[19:27] <micahg> yofel: ^^
[19:27] <yofel> what's the bug?
[19:28] <dust_> starting watchgnupg out of kmail adds the following lines to gnupg.conf:
[19:28] <dust_> debug-level basic
[19:28] <dust_> log-file socket:///home/dust/.gnupg/log-socket
[19:29] <dust_> wheter on the commandline or in kgpg - it doesn't start without outcommenting these lines again - kleopatra doesn't show the keys anymore but starts
[19:31] <dust_> this is what kgpg or gpg on the commanline sais:
[19:31] <dust_> gpg: /home/dust/.gnupg/gpg.conf:248: argument not expected
[19:31] <dust_> gpg: /home/dust/.gnupg/gpg.conf:249: invalid option
[19:33]  * yofel wonders why gpg log viewer is greyed out for him o.O
[19:35] <dust_> you've got to install kleopatra - i guess then also watchgnupg is installed
[19:35] <dust_> ?!?
[19:36] <yofel> watchgnupg was installed, kleopatra indeed wasn't
[19:40] <yofel> dust_: I don't quite understand why the config file says the entries were added with gpgconf, but even gpgconf --check-config errors out
[19:41] <yofel> I can confirm the issue though
[19:42] <dust_> well where to file this issue? - launchpad -  bugs.kde.org ?
[19:43] <yofel> dust_: start by filing it against kleopatra https://bugs.kde.org/enter_bug.cgi?product=kleopatra&format=guided
[19:43] <dust_> ok
[19:43] <dust_> thanks
[19:59] <dust_> yofel: it's filed - i hope it's clear enough - need link?
[20:01] <yofel> found it
[20:04] <dust_> ok gn8 - got to go to bed now :) thanks again for your help