=== luciano_ is now known as virusuy === luciano_ is now known as virusuy [05:52] Hey quick apport question to the chat, assuming apport enabled & appropriate debug symbols installed, will apport kick in if you have an X crash where your booted out to the login screen and then login again? [11:17] penalvch: if you have the time maybe you can have a look at bug 793075 [11:17] Laibsch: Bug 793075 on http://launchpad.net/bugs/793075 is private [11:18] there's been quite a few tickets with the same symptoms that had the files you were looking for [11:18] I hope that somebody who understands crash analysis has a chance to have a look at this stuff soon [11:25] If have this bug report where the reporter is not able to reproduce the problem anymore when I asked for more details. Should I close it as 'invalid'? [11:33] veger: what number? [11:37] oh I thought to keep it generic :) It is about bug 778543 [11:37] Launchpad bug 778543 in evolution (Ubuntu) "Evolution mostly (?!) fails to save sent email to IMAPs sent folder - the mail is saved in local folder instead (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/778543 [11:38] haha [11:39] I've had a similar problem myself [11:39] How did you solve this? [11:39] As I am still new, I keep tumbling into new situations... [11:40] oh, this is evolution [11:40] I've had a very similar problem in TB [11:40] let me read the comments [11:41] good I asked for bug number [11:41] Generally I'd say if the OP reports back "no longer a problem" then it's OK to close [11:42] but in this case it's just that there is no way to reliably reproduce the problem [11:42] true [11:42] this ticket needs to stay open [11:42] and probably even be reset from incomplete [11:42] the OP is giving you the information you requested [11:42] yes, indeed [11:43] you will find that quite many problems cannot be reliably reproduced [11:43] but the given information is not complete enough to pass on to a developer [11:43] one has to accept that for some tickets there is no progress [11:43] they should stay open for others to pile on and possibly give the necessary hint of how things can be reproduced [11:44] so, best to put it back to 'New'? [11:44] that's what I would do [11:44] your reasoning seems logical, so I'll go with it (and try to use it the next time) [11:44] thanks a lot [11:44] np [11:44] thank you for helping out [11:44] and asking questions before acting ;-) [11:44] not everybody does that [11:45] well I try to help not make a big mess [11:49] Laibsch: bug 791007 is kinda similar I suppose. Although this time the OP provided an (useless) backtrace. But the problem also went away magically. Would you use the same reasoning for this bug? [11:49] Launchpad bug 791007 in evolution (Ubuntu) "Evolution crashed after sending an email with a link (https) (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/791007 [11:56] Is it not possible to attach 2 upstream links to one LP bug report? For bug 39363 I would like to do this... [11:56] Launchpad bug 39363 in evolution (Ubuntu) (and 1 other project) "Arrow keys do not open and close threads (affects: 1) (heat: 2)" [Medium,New] https://launchpad.net/bugs/39363 [12:00] veger: not for the same upstream project, if the bug is tracked in a different upstream bug you can switch the link [12:00] well according to upstream the bug got fixed, but the LP users do not agree :) [12:01] so best is to change the upstream link to the new report? [12:02] let me read the bug again [12:06] veger: from what I understand the ubuntu bug is about making left/right work while the currently tracked bug is about adding shift+left/right, so I would say switch the links [12:07] yes that is true (or they changed the request a bit and implemented it their way) [12:07] I will change the link. Thank you for your time to help me [12:08] not really, the original post of the current upstream bug says: [12:08] 1. Shift Left/Right on message threads doesn't collapse/expand. Neither +/- [12:08] while the ubuntu report doesn't want shift [12:08] np, thanks for helping :) [12:09] veger: ask the guy from bug 791007 to install dbg packages where available and process related files in /var/crash with ubuntu-bug. [12:09] Launchpad bug 791007 in evolution (Ubuntu) "Evolution crashed after sending an email with a link (https) (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/791007 [12:09] the OP will need to activate apport -> have a look at /etc/default/apport [12:10] Laibsch: I could do that, but getting a backtrace from a non-crashed application is kinda useless I think [12:10] I thought it was crashing? [12:10] not anymore... :) [12:10] well, again [12:10] intermittent problem [12:10] you can enable apport once with 'sudo service apport start force_start=1' btw. [12:10] yes :) [12:11] just because it does not crash this time does not mean the bug report is invalid [12:11] give it some time [12:11] so best is to ask to turn on apport and 'hope' that a crash will happen again [12:11] it's not a race to close tickets [12:11] veger: exactly [12:11] hm, yeah, for such crashes rather enable apport [12:11] I'd keep the incomplete status on this one, though [12:11] right, keep incomplete, it'll expire anyway if he can't reproduce the bug [12:12] I know it is not a race, but after the OP replied to my question I though it to be polite to respons on that, but did not know how [12:12] and if he gets an apport crash file he'll open a new bug [12:13] when he does, I'd dupe the old ticket to the new one [12:13] leaving appropriate comments [12:13] thanks again for the help guys [12:14] no no, thank you for helping out [12:14] and asking questions [13:16] bug 374975 is marked 'Incomplete' I provided the requested information instead of the OP... Should I mark it New again or do we need to wait for the original OP? [13:16] Launchpad bug 374975 in evolution (Ubuntu) "Evolution incorrectly parses URLs (affects: 1) (heat: 9)" [Low,Incomplete] https://launchpad.net/bugs/374975 [14:30] Laibsch: Tried looking at bug 793075 LP says it doesn't exist... if it's not OOo or LO related it's probably outside my access level. [14:30] penalvch: Bug 793075 on http://launchpad.net/bugs/793075 is private [14:31] penalvch: I see. you're not allowed to look at private bugs? [14:31] Laibsch: I'm only asked to see private bugs for LO & OOo b/c that's my triage comfort zone. [14:31] let's wait for the retracing service and then I guess I can unmark it [14:32] 793075 is against openoffice.org [14:32] I just verified it once more [14:33] not sure where the problem is [14:33] Laibsch: Weird I cannot see it... At any rate, if it's a OOo crasher you can ask sweetshark if he has a few minutes to queue up the apport retracer [14:34] retracing service [14:34] what do you mean "queue up"? [14:34] I think apport retracing service will analyze the ticket automatically in a few hours at most [14:35] is the ability to see private bugs restricted to certain packages these days? [14:35] I think I can see all tickets, so I don't know [14:35] Laibsch: Well few hours is very optimistic :D I've had apport crasher bugs still in new status unretraced for weeks but they are very low probability occurrences and under very resource demanding environments. [14:36] Björn seems to asleep ATM [14:36] :D [14:36] I think sometimes the retracer gets stuck, and when it gets unstuck it tends not to be able to deal with things that got updated [14:36] Laibsch: I think he's in Germany so it's ~5PM their time. May be AFK [14:37] status said zzZZzz [14:37] I'll see if I can talk to him in IRC [14:37] thanks [17:03] some private bugs are really private -- only those originally subscribed can see them [17:03] for example, security bugs can only be seen by the security team [17:05] hggdh: yes === Tetsuo55_2 is now known as tetsuo55 === yofel_ is now known as yfel === yfel is now known as yofel