=== asac_ is now known as asac
* bcurtiswx waves to room00:12
* micahg waves back00:12
* BUGabundo leans over but gives up half the way, and goes back to naruto00:14
=== BUGabundo1 is now known as BUGabundo
=== kakemann_ is now known as kakemann
kakemannHi! Can someone set bug #399617 and bug #398304 to wishlist?01:23
ubot4Launchpad bug 399617 in audacious-plugins "Please merge audacious-plugins 2.1-1 (universe) from Debian unstable (main)" [Undecided,Confirmed] https://launchpad.net/bugs/39961701:23
ubot4Launchpad bug 398304 in audacious "please merge audacious 2.1-1(universe) from debian unstable(main)" [Undecided,Confirmed] https://launchpad.net/bugs/39830401:23
Ampelbeinkakemann: done01:29
jander99hello again.  How should I deal with dist-upgrade bugs from one unsupported release to another unsupported release? Example bug #15619202:57
ubot4Launchpad bug 156192 in cupsys "Kubuntu upgrade from 7.04 to 7.10 fail after error on cupsys package" [Undecided,New] https://launchpad.net/bugs/15619202:57
micahgjander99: evaluate the error specifically and see if it was already corrected in a later release02:58
=== hggdh_ is now known as hggdh
* lajjr help03:18
* lajjr says goodbye Be Safe All.03:20
micahgdoes one need debug symbols installed to allow apport retracer on LP to retrace?06:28
micahgping bcurtiswx ^^^06:34
jander99off topic, friend of mine and myself make the prediction Shuttleworth will name 10.10 Motley Mongoose.06:35
* micahg is still wondering if 10.04 or 10.10 will be LTS06:36
jander99I think 10.10 is the safer bet considering Gnome 306:36
micahgnah, that wouldn't do it06:36
micahgit whether or not debian will work with ubuntu on the release06:37
micahgGnome 3 might be in 10.04 anyways06:37
jander99Better start getting those patches upstream so they stop complaining Ubuntu doesn't give back. x.x06:37
* micahg just triages at this point06:37
jander99Speaking of which, I'm still trying to wrap my head around how to deal with bugs during upgrade from one unsupported release to another unsupported release.  You mentioned trying to figure out if it had been fixed, but I'm not really sure where to look or how to test.  Sometimes one-off upgrade bugs happen and they get reported but at this point it would take so much effort to even attempt to reproduce it :(06:39
micahglook at the bug itself, not the fact that it was an upgrade06:39
micahgfor example06:39
micahgthe cupsys issue06:40
micahglook at the actual error and what caused it06:40
micahgand see if something was closed in the cupsys pacakge with that error06:40
micahga lot of times these things show up during upgrades, but could show up as regular updates as well06:41
jander99Gotcha.  Found another cupsys bug #243887 describing something similar, but with a different method.06:44
ubot4Launchpad bug 243887 in cupsys "cupsys failure during do-release-upgrade from 7.04 to 7.10" [High,Triaged] https://launchpad.net/bugs/24388706:44
jander99both bugs have a 'subprocess pre-installation script returned error exit status 1' on cupsys_1.3.2-1ubuntu7-i386.deb06:46
micahgyou have to look in the DpkgTerminal log to see the real cause of that06:48
micahgdon't bother asking for one if it's not attached06:51
micahgthere doesn't seem to be much infor for the cupsys bug as far as I can tell06:52
jander99Indeed.  I keep reading through the long copy/paste and don't see really anything that jumps out.  The only thing between the two bugs I've linked is the version of the cupsys package.06:54
micahgwhere's the original06:54
jander99bug 15619206:55
ubot4Launchpad bug 156192 in cupsys "Kubuntu upgrade from 7.04 to 7.10 fail after error on cupsys package" [Undecided,New] https://launchpad.net/bugs/15619206:55
micahgah, I found the dupe, bug 15663406:56
ubot4Launchpad bug 156634 in cupsys "cupsys error while upgrading to kubuntu 7.10" [High,Fix released] https://launchpad.net/bugs/15663406:56
micahgmark the one you were working on a dupe of the fix released06:57
micahguse the text on the reponses page06:57
jander99And another out of my queue heh.06:59
micahgyou duped the wrong bug07:00
micahgyou were supposed to mark it a dupe of 15663407:00
micahgthe one that the fix was released...07:01
jander99oh, sorry. I didn't see that. Let me change it.07:01
jander992am here :-\07:01
micahgthat's why I said I found the one to dupe above :)07:01
micahgit's 1AM for me07:01
jander99aw cant edit my comment.07:03
micahgjust change the dup #07:03
micahgi've done that on occasion07:03
jander99I did. 156634 should show 6 dupes now.07:04
jander99And my "queue" is all the "New / Undecided" bugs sorted by least recently changed.  Maybe one day I'll even catch up! :-)07:05
micahgok, if you like doing those07:05
jander99I figure they are good to learn on, and I can help tidy up at the same time.07:06
micahgbut we really could use help with the recent ones as well07:07
micahgso that fixes can get into karmic07:07
micahgit's up to you07:07
jander99Well I'd like to make sure I "know the ropes" as it were before helping out with the more important ones.  Call these old bugs a proving ground until I get a good rhythm going.07:09
=== micahg1 is now known as micahg
=== yofel_ is now known as yofel
=== ogra_ is now known as ogra
TrijntjeHi all. I have a problem with an encrypted usb device. On ubuntu 8.04 i can mount it using 'sudo cryptsetup luksOpen /dev/sdf crypti'. On ubuntu 9.04 this gives: Command failed: cannot acces device. I could file a bugreport on this, but it would simply be: it does not work. Not very helpful. Is there a way to get cryptsetup to give a more verbose output?11:29
LaibschCan anyone help me understand the following screen corruption when running xxdiff on a hardy host, forwarded over ssh to a Karmic laptop? http://picpaste.com/xxdiff-corrupted.png Is this likely a bug in libqt3-mt?14:46
TrijntjeHi all. I have a problem with an encrypted usb device. On ubuntu 8.04 i can mount it using 'sudo cryptsetup luksOpen /dev/sdf crypti'. On ubuntu 9.04 this gives: Command failed: cannot acces device. I could file a bugreport on this, but it would simply be: it does not work. Not very helpful. Is there a way to get cryptsetup to give a more verbose output?14:51
=== pace_t_zulu_ is now known as pace_t_zulu
james_wTrijntje: I suspect that /dev/sdf is no longer where your usb device ends up, have you confirmed this is the assigned location?15:02
Trijntjejames_w: yes, I checked with dmesg |grep sd. And luksDump works fine on the device, so i'm sure i have the right one15:03
james_wis it not /dev/sdf1 you want?15:05
james_wthe next thing I would do is strace the process15:06
Trijntjejames_w:on my laptop with 8.04, it works fine with /dev/sdf15:07
TrijntjeI will see what i can find out using strace, once i've read the manual. I've never used it before. Thanks for your help15:08
james_wTrijntje: "sudo strace -o /tmp/strace.txt cryptsetup luksOpen /dev/sdf crypti"15:16
james_wthen look at the end parts of /tmp/strace.txt for some idea of what it is doing when it hits the error15:17
Trijntjejames_w: it magically works now, i can open the device.15:23
james_wit works under strace but not without15:23
james_wor it just started working?15:23
Trijntjejames_w: Ill keep using strace to open it a while to see if i can capture the failure. It works now both with and without strace15:24
* Laibsch is looking for help in triaging bug 40177616:00
ubot4Launchpad bug 401776 in xxdiff "screen corruption" [Undecided,New] https://launchpad.net/bugs/40177616:00
LaibschI don't even know what package that bug is likely in16:01
=== WelshDragon is now known as Fluffles
Trijntjejames_w: It stoped working again, so i now have a strace file16:12
Trijntjeit looks like when it fails, i thinks the device is busy: open("/dev/sdf", O_RDONLY|O_EXCL|O_SYNC|O_DIRECT|O_LARGEFILE) = -1 EBUSY (Device or resource busy)16:12
james_wit's opening it with O_EXCL, so it just means something else has opened it16:13
james_wpresumably some service on the system16:13
james_wor fuser I expect16:14
james_wTrijntje: when you have a failure "sudo fuser /dev/sdf"16:15
james_wand "sudo fuser -m /dev/sdf"16:16
james_wand see if you can catch anything with the device open16:16
Trijntjejames_w: Those two command give no output16:18
Trijntjejames_w: so that means the usb drive is in use correct?16:23
james_wthe EBUSY suggests that it is16:23
james_wfuser is supposed to tell you what is using it16:23
james_wbut it may just be a very short-lived process or something16:23
Trijntjevery shord lived. I've done sudo fuser; cryptsetup; fuser and still no output16:24
Le-Chuck_ITAHi all, please can someone triage https://bugs.edge.launchpad.net/ubuntu/+source/poppler/+bug/39426617:28
ubot4Launchpad bug 394266 in poppler "Very bad quality from evince printing pages which have been printed to pdf using firefox" [Undecided,New]17:28
Le-Chuck_ITAor take a look at least17:31
Le-Chuck_ITAbug #39426617:33
ubot4Launchpad bug 394266 in poppler "Very bad quality from evince printing pages which have been printed to pdf using firefox" [Undecided,New] https://launchpad.net/bugs/39426617:33
Le-Chuck_ITAno bot for bugs?17:33
pedro_Le-Chuck_ITA, i'm looking into it now17:33
pedro_Le-Chuck_ITA, no need to repeat the same again though17:34
pedro_Le-Chuck_ITA, confirmed, got the same with poppler version from git master, will send  that upstream17:45
Le-Chuck_ITAI did not want to repeat pedro, wanted the bot to pop up :)17:46
Le-Chuck_ITApedro_: thank you17:47
pedro_Le-Chuck_ITA, np, thanks  for following up ;-)17:47
KamusinI have a question, I saw a report that say about a synaptic problem in feisty and I can't reproduced in Jaunty. Actually is marked like confirmed (like two years ago) so what can I do, what status have to be marked?19:47
jander99What bug number is it Kamusin?19:48
Kamusinjander99,  bug number is 8442319:48
jander99You tried to reproduce this step by step and synaptic was able to gracefully reload the sources.list file in Jaunty?19:55
yofelbug 8442319:57
ubot4Launchpad bug 84423 in synaptic "[feisty] Synaptic closes when changing sources.list manually while synapitc is runing" [Medium,Confirmed] https://launchpad.net/bugs/8442319:57
Kamusinjander99, that is correct sir, without any problems (and another friend too)19:58
yofelcan't reproduce it in karmic either19:59
yofelKamusin: should I close the bug or will you do it?20:01
jander99I went one step further and proved edit, reload also updates Synaptics repository list under Setting > Repositories20:01
Kamusinyofel,  I don't have superpowers for do it hehe20:02
jander99I'd say close with Fix Released, correct yofel?20:02
yofelI'll do it, mom20:02
Kamusinshall you yofel , :)20:02
yofelKamusin: Note: you *can* edit the bug status by clicking on the arrow beside the package name ;)20:03
jander99yofel: I'm new here, would that be the proper response in this situation? Confirm the bug doesn't exist and mark Fix Released after leaving a comment stating said bug doesnt exist in current stable release?20:03
Kamusinyofel,  yep and  in the other hand is good know what status have to be marked for those reports ;)20:08
yofeljander99: actually I would rather use https://wiki.ubuntu.com/Bugs/Responses#Old%20untouched%20bugs in a newer bug. In *this* bug I think closing it would be better since feisty was EOLed and we have multiple people that can't reproduce the bug20:08
micahgyeah, fix released is only if we know a new ubuntu package was released to fix it20:09
yofeljander99: Kamusin: If you're new here, you should check out https://wiki.ubuntu.com/BugSquad/KnowledgeBase20:11
yofelI found it really helpful20:12
jander99Thanks yofel. As micahg knows I've been going through old new bugs, and each one seems different20:16
Kamusinyofel, ;)20:16
micahgjander99: it took me 200-300 bugs to be comfortable and I still have questions on occasion20:16
=== paul_ is now known as Elbrus
kakemannmicahg, Hi! I was browsing over some thunderbird bugs today, and saw your name in a couple, and I think I found an upstream bug for them. Can you take a look at them?20:30
micahgmaybe in a little bit20:31
micahgyou can leave them here and I'll look a little later20:31
kakemannsure, i'll just paste them here20:32
* micahg is working right now...20:32
kakemannbug 320057 upstream https://bugzilla.mozilla.org/show_bug.cgi?id=45013420:32
ubot4Launchpad bug 320057 in thunderbird "Thunderbird hangs for 10secs when auto-completing address" [Undecided,Confirmed] https://launchpad.net/bugs/32005720:32
ubot4Mozilla bug 450134 in Address Book "Investigate possible performance improvement for autocomplete by using the directory search facilities" [Normal,Resolved: fixed]20:32
kakemannbug 322256 upstream https://bugzilla.mozilla.org/show_bug.cgi?id=7913020:33
ubot4Mozilla bug 79130 in Networking: NNTP "Threads with an expired (or cancelled) message will show the unread thread indicator, even when all are read, and expired/cancelled message causes incorrect unread count of newsgroup" [Normal,Assigned]20:33
ubot4Launchpad bug 322256 in thunderbird "uncorrect unread count for news folders" [Undecided,Confirmed] https://launchpad.net/bugs/32225620:33
micahgthanks kakemann20:33
kakemannnp :)20:33
yofelanybody an idea what's going on with apports retracer? All karmic crashes I reported are tagged 'apport-failed-retrace' :/ just like bug 40188220:39
ubot4Launchpad bug 401882 in compiz "compiz.real crashed with SIGSEGV" [Undecided,New] https://launchpad.net/bugs/40188220:39
micahgyofel: I've seen some succeed21:13
micahgmaybe not21:13
jander99Looking at bug 159100, hibernate doesnt conflict with acpi-support according to its Conflicts dependencies.21:23
ubot4Launchpad bug 159100 in hibernate "Remove from archive / Conflict with "acpi-support"" [Undecided,New] https://launchpad.net/bugs/15910021:23
micahgright, that's the question jander9921:25
jander99booting up my VM to see what happens when I install it21:26
micahgjander99: this is more of a question for the package maintainer21:26
micahgyou can find them and ping them if you want21:26
jander99Maintainer is listed as MOTU21:27
jander99Should I head over to #-motu and see what they think?21:27
micahgbut you can also see who does most of hte uplaods for the packages21:27
micahgall the maintainers should be set to motu21:28
jander99looking at the version history in launchpad as well, for any clues21:29
jander99micahg: Here's another question your way.  What to do with a bug related to a now-unsupported architecture (PowerPC)21:45
micahgjander99: powerpc is community supported22:15
=== BUGabundo1 is now known as BUGabundo
=== BUGabundo1 is now known as BUGabundo

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!