[02:55] <blkperl> can someone look at bug 886427 and look at /etc/init.d/oidentd and confirm my ticket :)
[02:55] <Guest29594> Launchpad bug 886427 in oidentd (Ubuntu) "oidentd doesn't have a status option in the init script (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/886427
[07:56] <ankit> Hi, I have recently joined the Ubuntu bug squad so I am a bit confused regarding the actions one should take during the triaging process
[07:58] <ankit> For example take bug #886450. In it the Gvim and Emacs hang when started unmaximized. I was unable to reproduce the bug but the reporter is sure that he is having this bug.
[07:58] <Guest29594> Launchpad bug 886450 in vim (Ubuntu) "Gvim hangs with blank window if not maximized (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/886450
[07:58] <ankit> Now, I want to know what should be done now
[07:59] <ankit> Should it be reported to Vim and Emacs bug database
[07:59] <ankit> Or anywhere else
[07:59] <ankit> It surely is not due to the window manager since changing the window manager causes the bug to persist.
[09:51] <elgaton> Hi, could someone please set the importance of bug 879109 and bug 884210 to "High" and of bug 884132 and bug 884135 to "Wishlist"? Thanks!
[09:52] <Guest29594> elgaton: Bug 879109 on http://launchpad.net/bugs/879109 is private
[09:52] <Guest29594> elgaton: Bug 884210 on http://launchpad.net/bugs/884210 is private
[09:52] <Guest29594> elgaton: Bug 884132 on http://launchpad.net/bugs/884132 is private
[09:52] <Guest29594> elgaton: Bug 884135 on http://launchpad.net/bugs/884135 is private
[09:59] <elgaton> No, they are public - ignore the messages above, it's a bug.
[11:33] <toros> hi!
[11:38] <toros> just a quick question: I am working on a presentation about Ubuntu (I will present it on a Free Software conference, mostly for highly technical audience), and I want to encourage them to test the development version of Ubuntu and to report bugs. Is it okay if I tell them, that if they have questions about what information should be included in the bugreport, they should come here (#ubuntu-bugs channel on IRC) and ask for your assistance?
[11:58] <mewerner_arand> toros: That's one of the purposes of this channel, yes, although it's more often that specific information is requested by bug triagers on LP, make sure to point at the bugreporting pages at the wiki as well...
[13:09] <ankit> Where are the bugs related to vim reported
[13:10] <ankit> I just watched that Bugs as old as 2005 are still open on Launchpad. Why?
[13:57] <jtaylor> most ubuntu packages have no dedicated maintainer, so often builds collect and are never closed even when solved
[13:58] <jtaylor> e.g. when they are fixed in debian seldom someone cares to close the duplciates in ubuntu
[14:12] <penguin42> you'd think we could train a bot for that
[14:14] <jtaylor> how would the bot associate ubuntu bugs with debian/upstream bugs?
[14:14] <jtaylor> most of them are not linked in by someone
[14:15] <kanha> I fixed a bug(LP :#818475) and applied it for sponsorship on  2011-10-27 but it has not been reviewed yet can anyone tell me what may be the possible reasons for delay..
[14:16] <jtaylor> UDS just ended
[14:17] <jtaylor> most people were busy before and during it
[14:17] <jtaylor> also ~1 week is no long delay
[14:18] <jtaylor> I'm also not sure this fix qualifies for an SRU, but it should be fixed for precise
[14:20] <kanha> I basically made this fix for oneiric and think it work fine!
[14:21] <kanha> what  i should do for a quick review?
[14:23] <jtaylor> be more patient
[15:37] <elgaton> Hi, could anyone here set the importance of bug #879109 and bug #884210 to High, bug #885661 and bug #885592 to Medium and bug #884135/#884132 to Wishlist? Thanks!
[15:37]  * penguin42 looks
[15:38] <Guest29594> elgaton: Bug 879109 on http://launchpad.net/bugs/879109 is private
[15:38] <Guest29594> elgaton: Bug 884210 on http://launchpad.net/bugs/884210 is private
[15:38] <Guest29594> elgaton: Bug 885661 on http://launchpad.net/bugs/885661 is private
[15:38] <Guest29594> elgaton: Bug 885592 on http://launchpad.net/bugs/885592 is private
[15:38] <Guest29594> elgaton: Bug 884135 on http://launchpad.net/bugs/884135 is private
[15:39] <elgaton> (The bugs are not private, it's just a bot bug).
[15:39] <penguin42> hmm no they aren't and why is our bot a guest
[15:40] <elgaton> penguin42: Don't know
[15:40] <zerwas> Hi guys. Is this the right channel to ask for some help on hunting down a bug?
[15:41] <elgaton> zerwas: Yes
[15:41] <zerwas> elgaton, Good, thanks
[15:42] <zerwas> This is what i want to triage: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/883592/+attachment/2578095/+files/sound-menu%20indicator%20bug.ogv
[15:42] <Guest29594> zerwas: Error: Bug #883592 is private.
[15:43] <zerwas> I already installed indicator-sound-dbgsym but it appears that indicator-sound-service isn't even crashing. It looks like the whole indicator area could be crashing. Now i don't know what i could do next
[15:45] <elgaton> zerwas: I'd install the debug symbols for the entire indicator area as well and try to get a backtrace, or run strace on the indicator area program.
[15:46] <zerwas> elgaton, is there a way to find out if anything is crashing at all? like a monitor that shows me when an application crashed/exited?
[15:47] <penguin42> elgaton: Why do you reckon 885592 is a medium?
[15:48] <elgaton> zerwas: I think (I'm not sure, correct me if I make a mistake) that the only ways to find out are 1) viewing if Apport is triggered, 2) checking standard output/standard error, or 3) run strace and see if there are any errors/signals catched.
[15:48] <zerwas> elgaton, Which package would "the entire indicator area" be? indicator-appmenu?
[15:48] <eapache> Could someone set bug #808421 to Wont-Fix as per the upstream maintainer's comment please?
[15:48] <zerwas> elgaton, Thanks, i'll have a look into this!
[15:48] <Guest29594> eapache: Bug 808421 on http://launchpad.net/bugs/808421 is private
[15:49] <elgaton> penguin42: I was undecided between "Wishlist" (request for an old Nautilus feature to be introduced again) and "Medium" (moderate impact on core application, as some users may not be able to find how to navigate the new system quickly).
[15:49] <eapache> no it's not
[15:49] <elgaton> eapache: it's an ubot bug
[15:49] <eapache> "This report is public"?
[15:49] <eapache> oh
[15:49] <eapache> k
[15:49] <penguin42> elgaton: It looks like it's related to a setting that's not there any more
[15:51] <elgaton> zerwas: Perhaps libindicator 3-6 (not sure). indicator-appmenu seems to be the widget that takes menus and puts them on the top bar.
[15:52] <elgaton> penguin42: So is it more appropriate to mark the bug as "Won't Fix" or as a "Wishlist" (for the old feature to be reintroduced)?
[15:52] <penguin42> elgaton: I've kept with your medium; if you used to have the option when you upgrade it shouldn't result in something broken
[15:53] <elgaton> zerwas: Or gnome-panel...
[15:53] <elgaton> penguin42: OK, thanks
[15:54] <elgaton> zerwas: You should try to determine the package by 1) running strace/getting a backtrace, 2) find the culprit library/binary and then 3) finding the package the file is contained in
[15:54] <elgaton> zerwas: That's the best way in this case
[15:55] <penguin42> elgaton: Have you considered applying to bug-control?
[15:56] <elgaton> elgaton: Not yet, I've only started triaging since some days, I think I need some more experience before applying
[15:56] <elgaton> penguin42: Not yet, I've only started triaging since some days, I think I need some more experience before applying
[15:56] <elgaton> (nick mistake -.-)
[15:57] <penguin42> elgaton: OK, keep going - your doing good
[15:57] <elgaton> penguin42: Thanks
[15:57] <zerwas> elgaton, apport didn't trigger anything. the strace output for sound-indicator does not look useful. Hm. gnome-panel does not crash.
[15:57] <penguin42> elgaton: OK, I think I've done all the ones you listed, just check them
[15:58] <elgaton> zerwas: could you please paste the strace log in a pastebin?
[16:00] <zerwas> elgaton, Sure, here you go: http://pastebin.com/raw.php?i=PUKdvbY8
[16:00] <penguin42> eapache: I've marked 808421 as a dupe of 758916
[16:03] <elgaton> zerwas: From what you've logged, seems that a client and a server process dialog via DBus and that one of the two is crashing. I'm not really sure since I'm not an expert in that area - maybe someone else here or in #ubuntu-desktop may help.
[16:04] <zerwas> elgaton, i see. Anyway, thank you very much for your help so far! ☻
[16:04] <elgaton> zerwas: Not a problem
[16:05] <zerwas> elgaton, One last question: Do you think i should add the strace output to the bug report?
[16:05] <elgaton> zerwas: Of course
[16:06] <elgaton> zerwas: specifying how you invoked strace
[16:06] <elgaton> zerwas: (e.g. to which processes you attached it)
[16:06] <zerwas> Okay
[16:12] <elgaton> penguin42: OK, just two or three other questions: 1) I forgot to ask if the importance of bug #882255 could be set to High, 2) is it right to leave these bugs in the "Confirmed" (and not "Triaged") state, or do developers just look at Triaged bugs and 3) could you please also set the status of bug #884135 to Triaged (according to <https://wiki.ubuntu.com/MozillaTeam/Bugs/TriagersHandbook>)?
[16:13] <Guest29594> elgaton: Bug 882255 on http://launchpad.net/bugs/882255 is private
[16:13] <Guest29594> elgaton: Bug 884135 on http://launchpad.net/bugs/884135 is private
[16:16] <penguin42> elgaton: On 882255 can you go to settings and give yourself a password again?
[16:17] <penguin42> elgaton: It's probably right to set to Triaged if it has all the info needed (although I'll admit I'm bad at remembering to do that)
[16:17] <elgaton> penguin42: Let me try. I'll need some minutes to create the VM again
[16:17] <penguin42> elgaton: If you can recover from it I say it's a medium, if you're stuck so you can't recover then I agree with the high
[17:03] <zerwas> elgaton, I've found out that unity-panel-service crashes, so i've created a backtrace. Am i missing any symbols here? https://launchpadlibrarian.net/84513839/gdb-unity-panel-service.txt
[17:05] <elgaton> zerwas: Yes (there are numerous "No symbol table info available." lines).
[17:06] <zerwas> good to know, i'll repeat the process with all dbgsym packages installed
[17:06] <elgaton> zerwas: Look at the first lines of your backtrace, the ones where it says "Reading symbols for...": the required symbols are listed there
[17:06] <zerwas> Ah, i see
[17:06] <elgaton> Hope you have a fast connection
[17:06] <zerwas> fortunately, yes
[17:11] <penguin42> zerwas: It depends on the developers; some of them are OK with a bt full; some of them will ask for it to be done with apport
[17:13] <zerwas> penguin42, but apport does not get triggered
[17:13] <penguin42> zerwas: Yeh it's off by default, see /etc/defaults/apport
[17:14] <zerwas> penguin42, no after i've enabled it, the crash does not trigger apport
[17:14] <penguin42> oh, ok
[17:14] <penguin42> zerwas: OK then a bt full is probably best - but with the debug packages; then you won't need the disassembly
[17:16] <zerwas> penguin42, done, this is what it looks like: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/883592/+attachment/2586494/+files/gdb-unity-panel-service-new.txt
[17:16] <zerwas> I hope it will be helpful
[17:16] <Guest29594> zerwas: Error: Bug #883592 is private.
[17:19] <penguin42> zerwas: You're missing the one for libido which is important since it's the one that called the function that died
[17:19] <zerwas> Hmpf. Thanks, didn't see that
[17:20] <zerwas> penguin42, but there are no dbg packages for libido3
[17:26] <elgaton> penguin42: Tested, sorry for the delay but I had to install Ubuntu twice as the installer seemed to have locked on the first attempt
[17:26] <penguin42> zerwas: There is a -dbgsym package in the ddebs repo
[17:26] <penguin42> elgaton: ANd what does it do - can you recover from the autologin?
[17:28] <elgaton> penguin42: After choosing to log in without a password it is only possible to change it with the passwd command from a terminal or by entering rescue mode (and using passwd). The UI does not allow it (it prompts for the current password but does not accept it), whether you choose "Unlock" at the top of the User Accounts window to unlock all settings or directly click on the password field.
[17:28] <zerwas> penguin42, where exactly? http://ddebs.ubuntu.com/pool/main/l/
[17:28] <penguin42> zerwas: Try /libi
[17:29] <penguin42> zerwas: Ah pool/main/i/ido/libido3-0.1-0-dbgsym_0.3.0-0ubuntu4_amd64.ddeb
[17:29] <penguin42> zerwas: Easier if you add the ddebs repo's
[17:29] <zerwas> penguin42, Strange! It's added and the package does not show up for me
[17:29] <penguin42> elgaton: OK, what was the bug number?
[17:30] <elgaton> penguin42: 882255
[17:30] <penguin42> ok
[17:30] <penguin42> hmm pleasently repetitive number
[17:31] <penguin42> elgaton: Done
[17:32] <elgaton> penguin42: Good observation, and thanks for all your help
[17:33] <penguin42> np
[17:41] <zerwas> penguin42, Thanks for your help
[17:41] <penguin42> no problem
[18:26] <ikt> how did the bugs filed against ubuntu drop nearly 150 bug reports?
[18:26] <elgaton> ikt: Maybe they expired
[18:26] <elgaton> ikt: or were duplicates of other bugs
[18:26] <ikt> iirc only incomplete bugs do that
[18:26] <ikt> https://bugs.launchpad.net/ubuntu/+bugs?assignee_option=any&field.assignee=&field.bug_commenter=&field.bug_reporter=&field.bug_supervisor=&field.component-empty-marker=1&field.has_cve.used=&field.has_no_package=on&field.has_no_package.used=&field.has_patch.used=&field.importance%3Alist=UNDECIDED&field.importance%3Alist=UNKNOWN&field.omit_dupes=on&field.omit_dupes.used=&field.searchtext=&field.status%3Alist=NEW&field.status_upstream-empty-marker=1&field.subs
[18:27] <ikt> long url ftl
[18:27] <ikt> this is new bugs against ubuntu
[18:27] <ikt> was sitting around 500, then there was a bug day which brought it down to 450 or so then it went back up to 550, now it's down to 340 :s
[18:29] <elgaton> Well, if you use this (the recommended link to get new bugs in the Ubuntu Wiki)
[18:29] <elgaton> https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&field.status%3Alist=New&field.importance%3Alist=Undecided&assignee_option=none&field.assignee=&field.owner=&field.component=1&field.component=2&field.component-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_no_package.used=&search=Search
[18:30] <elgaton> you get much more :P
[18:30] <ikt> no
[18:30] <ikt> that's new bugs
[18:30] <ikt> this is new bugs without a package
[18:31] <ikt> I'm sure it was just a bot that did it or something
[18:33] <elgaton> Don't know then - do you remember an old bug that you did not see anymore? I think you're right (maybe reports for EOL releases were closed).
[18:33] <elgaton> Let me see if some release reached end of life
[18:35] <ikt> ah true
[18:35] <elgaton> Nope
[18:35] <elgaton> The latest was Dapper Drake server on June 1, 2011
[18:35] <elgaton> (maybe the bot was run just now, but seems not probable...)
[18:38] <ikt> shouldn't have clicked that link
[18:38] <ikt> 22,000+ new bugs
[18:38] <ikt> makes me just depressed :(
[18:40] <elgaton> Me too, especially the fact that some of them have very low numbers
[18:40] <elgaton> meaning they have been left unfixed
[18:41] <elgaton> but always remember that Ubuntu has got billions of line of code (considering all software)
[18:42] <elgaton> and just about 700 members in the BugSquad team
[18:42] <elgaton> Triaging all bugs is a big but rewarding (and addicting) effort
[19:06] <ikt> elgaton: true, why i'm still here after all these years
[19:06] <ikt> strangely enough never asked to move into bug control
[19:07] <elgaton> ikt: Why not?
[19:07] <ikt> no idea, mainly just do basic bug triage so I guess I wouldn't get much out of being control anyway
[19:28] <njin> hggdh hello, can you please revert bug 811029 to confirmed and wishlist for me ? thanks
[19:28] <hggdh> njin: give me a sec
[19:28] <Guest29594> njin: Bug 811029 on http://launchpad.net/bugs/811029 is private
[19:29] <njin> ??? isn't private
[19:31] <hggdh> njin: don't worry, the bot was feeling alone for a while, and is now grumpy
[19:31] <hggdh> so, this is a bug for update-manager?
[19:32] <njin> hggdg , yes thanks
[19:32] <hggdh> njin: done
[19:32] <njin> great
[19:32]  * hggdh goes sleep for a while
[20:09] <bkerensa> darn I missed hggdh
[20:13] <penguin42> and there are LOTS of different PC hardware types with lots of weird bios setups