ametheusGuys, I'm suddenly not sure about bug 80849800:51
ubot4Launchpad bug 808498 in gnome-terminal (Ubuntu) "default LS_COLORS are annoyingly unreadable (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/80849800:51
ametheusIt's either an opinion, or a tiny design fix00:52
ametheuswhat do you think?00:52
ametheusWell, serves me right for late-night bug management.01:01
ametheusDo drop me a line; I'd like some feedback on my bug gardening skills.01:02
=== pedro_ changed the topic of #ubuntu-bugs to: Ubuntu Bug Squad - next meeting 8/11/11 | http://wiki.ubuntu.com/BugSquad | Documentation: http://wiki.ubuntu.com/HelpingWithBugs | Want to report a bug? Read https://help.ubuntu.com/community/ReportingBugs | User support (not related to triage) is in #ubuntu
om26erwhy do I see 'launchad bug tracker' confirming bugs these days?13:31
pedro_om26er, http://blog.launchpad.net/bug-tracking/automatic-confirmation13:33
om26erpedro_, reading, thx :)13:35
=== bambee_ is now known as bambee
=== deryck is now known as deryck[lunch]
RedSingularityjibel: bug 802409.  Did you notice that on previous versions or just oneric?17:16
ubot4Launchpad bug 802409 in update-manager (Ubuntu) "Do not propose to dist-upgrade without a network connection (affects: 1) (heat: 158)" [Undecided,New] https://launchpad.net/bugs/80240917:16
=== deryck[lunch] is now known as deryck
bdmurrayAmpelbein: thanks for the idea regarding search-bugs and all of ubuntu18:14
bdmurrayRedSingularity: what's going on in bug 798529?19:16
ubot4Launchpad bug 798529 in update-manager (Ubuntu) "package update-manager-kde 1:0.150.2 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 139 (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/79852919:16
bdmurrayRedSingularity: specifically what are you trying to find out?19:17
RedSingularitybdmurray: I was looking for the state of that package he has.  I meant to ask for the output of 'dpkg -s update-manager-kde'  Not sure why I used 'apt-cache' :/20:03
bdmurrayRedSingularity: right but why?20:03
RedSingularitybdmurray: TermLog was showing a config error with that package.20:04
bdmurraySetting up update-manager-kde (1:0.150.2) ...20:04
bdmurraySegmentation fault20:04
bdmurraydpkg: error processing update-manager-kde (--configure): subprocess installed post-installation script returned error exit status 13920:04
bdmurrayIt looks to me like it crashed20:05
* RedSingularity looking20:06
RedSingularitybdmurray: hmmm, but it was in the process of installing, correct?20:07
bdmurrayRedSingularity: yes update-manager-kde was in the process of installing and something crashed - what we really need is an apport-crash report not an apport-package report20:08
bdmurrayThank you for taking the time to report this bug and helping to make Ubuntu better.  Reviewing your log files attached to this bug report it seems that a package failed to install due to a segmentation fault in application being used by the package installation process.  Unfortunately, this bug report isn't very useful in its current state and a crash report would be much more useful.  Could you try recreating this issue by enabling appo20:09
yofelbdmurray: you're obviously not using an IRC client that handles the IRC character limit properly :P (you got cut off "by enabling appo...")20:11
bdmurrayI have no limits!20:11
RedSingularitybdmurray: I believe I was going to have the user reconfigure the package with 'dpkg' and see if it cleaned it up.  It seemed like an isolated case to me.  I will ask for the crash log though.20:12
bdmurrayThere are a surprising number of segfaults during package installations20:12
RedSingularityBest way would be to enable apport?  No other quick command to temporarily run a apport service?20:13
bdmurray'sudo service apport start force_start=1' and then trying to install  the same package again?20:13
RedSingularitybdmurray: and thats it!  ;)20:14
bdmurraywe don't people on stable releases enabling apport!20:14
bdmurraysuprising = 143 so far20:15
RedSingularitybdmurray: that number just for natty?20:16
bdmurrayno all releases20:17
RedSingularitybdmurray: having the user run that command will take him through the steps for a new report?  If so you think its better to close the original or just dupe the 2?20:19
yofelnew report, as update-manager is not what crashed20:20
bdmurrayRedSingularity: no they'll need to repeat the operation too20:20
bdmurrayRedSingularity: here is the complete comment20:21
RedSingularitybdmurray: ok thanks.  Doing it now.20:22
RedSingularityyofel: What package assignment would be more appropriate in that case?20:26
yofelwell, there are 3 things that can possibly crash looking at the postinst script: pycompile, which, dash. So one if them depending on the crash report (apport will assign it)20:26
yofel*one of them20:27
RedSingularityyofel: which log are you reading that from?20:32
yofelno log, the log said " update-manager-kde (--configure): subprocess installed post-installation script" -> post-installation script is /var/lib/dpkg/info/update-manager-kde.postinst (here for you to read: http://paste.kde.org/100309)20:33
yofelso 3 things can crash: pycompile from line 6, which from line 5, or the shell itself20:34
RedSingularityyofel: ohhhh ok.  I never looked at that before.  Thanks much!20:35
yofelRedSingularity: tip, for non-crash errors in the scripts (like exit status 1 which tells you nothing), it helps to add '-x' to the first line for debugging as that'll print what the script does. (ONLY for debugging, and  mostly if you can reproduce it yourself)20:37
yofelsince that requires editing of the script, nothing the general user should do20:37
RedSingularityyofel: so the -x would go under #!/bin/sh ?20:40
RedSingularityunder that line i mean20:40
yofeleither add 'set -x' or use '#/bin/sh -x'20:41
yofeler, '#!/bin/sh -x'20:41
RedSingularityAnd then run the program again or just execute the script manually?20:43
yofelmanually would be best, or run dpkg --configure. dpkg -i would overwrite the script again. (so debugging failures on install can be tricky :/)20:44
=== yofel_ is now known as yofel
jmburgessHello! I'm new to debugging and just had a quick question. I've been using the Bug's need a bugwatch site to find some low hanging fruit to get started (http://reports.qa.ubuntu.com/reports/launchpad-database/unlinked-bugwatch.html) and as I go through them I want to check off the ones that don't have an appropriate upstream bug link in the comments...what is a good way to do that?23:18

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