[02:42] upper right where my time & name are on the top panel (ubuntu 11.04) all the icons are ok but the time display & name are very dim barley visable--any ideas on how to fix this--i have tried all the icon & themes and so far nothing is working [02:42] sorry wrong channel === chrisccoulson_ is now known as chr1sccoulson [10:47] bug 791007, as evolution crashed should I ask for a backtrace? [10:47] 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 [10:53] veger, yes [10:54] ok I will do that, thanks [10:57] and another question (still new here): bug 781851 got forwarded upstream. Overthere they provided a solution. What to do with the LP report? [10:57] Launchpad bug 781851 in evolution (Ubuntu) (and 1 other project) "allow to change keyboard shortcuts (affects: 2) (heat: 12)" [Wishlist,Triaged] https://launchpad.net/bugs/781851 [10:58] close it and mark it as 'Won't Fix'? [13:11] veger, let me look at it [13:16] veger, the bug is still real -- a documentation one now. I updated 781851 following https://wiki.ubuntu.com/Bugs/Description [13:57] hggdh: thanks, is it also required to change the Status of the bug? [14:01] Also, I am 'stuck' at bug 778543. Should I create an upsteam report? Request the reporter to update to 11.04 (to have the newest version of evolution)? [14:01] 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 [14:07] veger, no, the status is still triaged (until documentation is updated) [14:07] hggdh: I updated the gome FAQ. Or is there other documentation as well? [14:07] *gnome [14:08] veger, kudos for you! Thank you for doing this (also, please add a comment on the gnome bug about doing that) [14:08] ok, I'll leave a comment about the updated FAQ [14:09] veger, there is/was a Evo manual, but I do not know what is the current status. I _think_ it was last updated on 2.26 [14:11] the gnome/evo people set the status of the gnome rpeort to 'resolved notabug'. So I do not think they are planning to update this documentation... [14:12] How about my other question, on how to proceed with bug 778543, care to give a pointer? [14:12] 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 [14:14] veger: looking at his actual error message would be good [14:14] veger: I don't know if Evolution keeps a log file, that might be useful too (once scrubbed of sensitive information) [14:16] I do not see an evolution log file on my system. But asking the reporter about a more detailed error description is the way to go? [14:17] veger: I'd say so, from his description I'd even be inclined to think he has a buggy IMAP server (as opposed to buggy evolution) but looking at the actual error message might give you a clue [14:17] ok, thanks for helping out [14:19] veger: ah, evolution --debug=~/evo.log to generate a log file [14:19] oh, nice! I'll include this in my question for more info [14:32] veger: I just tested evolution --debug and I'm afraid it doesn't produce very useful logging :-/ [14:33] roadmr: just the regular terminal output? [14:33] veger: yep, there's apparently no output of server error messages (although admittedly my IMAP server is *not* erroring on me) [14:34] Hopefully the IMAP errors are also reported in the log, so the reporter is able to provide some useful info. Otherwise, it might be hard to find the problem I suppose [14:36] veger, roadmr: check http://projects.gnome.org/evolution/bugs.shtml [14:37] hggdh: thanks :) [14:37] I *think* it still applies -- you have to export some env variables to really get debug out [14:38] Adding CAMEL_DEBUG=all seems sensible to get info about the IMAP problem I suppose? [14:38] veger, roadmr: also you may want to be aware of http://mail.gnome.org/archives/gnome-bugsquad/2011-May/msg00000.html [14:39] veger, yes [14:39] hggdh: ah... so the reporter needs to update, before the problem can be accepted [14:40] veger, no... it actually means that we keep bugs for these versions, we cannot open them upstream anymore [14:41] hggdh: so we need to provide a patch to solve the problem instead of the gnome/evo develoeprs? [14:41] Unless the problem is still present in 2.32.2... ;) [14:43] aye [14:47] veger, (and also roadmr, of course ;-) BTW, thank you for helping on evo... I have been sort of slack on it; also, if you are going to keep on upstreaming to b.g.o, we can follow you and --when you are ready -- give you more access to b.g.o [14:48] hggdh: I'm just helping veger a bit, he's doing all the heavy lifting here [14:49] roadmr, heh. I know, but the offer still stands (if you still do not have the rights) [14:49] hggdh: thanks :) [14:50] hggdh: I'll try to continue working on some evo bugs frequently. I was/am still looking how to help out and since I use evolution it seems a nice project to help on :) BTW what is b.g.o ? :) [14:50] (and also try to get a 5-a-day streak :P ) [14:51] veger, b.g.o is shorthand for bugzilla.gnome.org [14:51] ah ok :) [14:52] If required, I'll also keep sending reports upstream. Although it is kinda hard to decide when to send one upstream... [14:55] veger, you will learn the ropes -- just keep on doing what you are doing now, asking when in doubt [14:56] every one of us started not knowing what do do ;-) [14:56] :) === bdmurray changed the topic of #ubuntu-bugs to: Ubuntu Bug Squad - next meeting 6/9/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 [15:23] I have another question: bug 777053 was wrongly blamed to evolution (according to the reported). What should I do now? :) [15:23] Launchpad bug 777053 in evolution (Ubuntu) "French spellcheck on Evolution doesn't recognize 1990 reformed spelling (affects: 1) (heat: 127)" [Undecided,New] https://launchpad.net/bugs/777053 [15:23] veger: do you know what's the actual affected package? [15:25] roadmr: the french language pack? (not 100% sure though) [15:25] veger: aspell-fr maybe [15:26] mdeslaur: I guess, as evolution is using aspell (dictionaries) for spelling checking [15:26] veger: looks like it, I installed aspell-fr, then aspell -a -l fr [15:27] So the package should be changed from evolution to aspell-fr? [15:27] veger: if I type "connaitre" the dictionary suggests "connaƮtre" which is apparently the old spelling [15:28] roadmr: aspell-fr somehow got outdated during the upgrade to natty? [15:28] *downgraded [15:28] veger: I'd change the package, yes - I may be wrong though, keep in mind I'm new to triaging :P [15:29] veger: it might also be worthwhile looking at existing bugs in aspell-fr, it might be a duplicate [15:29] roadmr: I am also new, so I'll take the blame... ;) [15:29] roadmr: good idea [15:29] veger, add a task for the translation team [15:29] (meaning leave the evo task also in) [15:30] hggdh: so I must not update the package to aspell-fr, but create a duplicate report for the aspell-fr package? [15:31] veger, not a duplicate report, still the same report, but with one more task [15:31] veger, see https://wiki.ubuntu.com/Translations/KnowledgeBase/ReportingBugs [15:31] hggdh: oh... I have seen that before yes [15:34] hggdh: is the aspell-fr package part of the aspell project? I cannot find an aspell-fr project when adding an additional project [15:35] Oh sorry, I misread. I need to add ubuntu-translations as the additional project [15:37] yes [15:37] done [15:39] hggdh: As I just passed on the problem to ubuntu-translations, should the status for evolution get changed into 'Triaged'? [15:51] veger, you can do it yourself [15:51] veger, er. Correction, someone from bugcontrol can do it [15:52] hggdh: yes I know I cannot change to Triaged :) But the idea was correct? [15:53] veger, yes, it was. I jsut marked it triaged/low [15:53] hggdh: thanks again :) [15:53] veger, no, *we* thank you :-) [15:54] well you (and the others here) have to be patient again and again with my questions, I really appriciate it [15:54] so, lets thank eachother... ;-) [16:08] :-) [16:13] heyo folks [16:15] cheers stlsaint [16:16] hggdh: back again for the 5th time in seek of mentor so i can move onto membership :D [16:16] i had mentor before but there was confusion with the bugs i was triaging [16:16] ol buddy drew [16:17] stlsaint, you can always ask here, any of us will help [16:18] hggdh: aye i usually triage bugs of teams i am apart of but i was told before that that really doesnt count and recently i was told that all bugs count as long as they are in lp [16:19] all bugs count, as long as they are Ubuntu bugs in LP [16:20] so, for example, triaging on bugzilla.gnome.org will count for triager access on b.g.o, but not LP [16:20] and triaging bug for other projects (not Ubuntu) on LP does not really count for Ubuntu bugcontrol [16:21] hggdh: what about ubuntu variants? (K)ubuntu, etc [16:22] they count (as long as they are official Ubuntu variants) [16:25] hggdh: good to know [16:25] hggdh: last question, is a mentor really required to gain membership? [16:25] stlsaint, but the variants may have their own bugs channel [16:26] stlsaint, no, it is not. It is your work on triaging bugs that count [16:27] cool thanks [16:34] stlsaint: to clarify, if the package in the yellow line has (ubuntu) after it, the bug counts for bug control [16:37] charlie-tca: ohai [16:37] charlie-tca: ok, i will keep that in mind [16:38] It might help. It took me a while to figure out that "evolution" is upstream, but "evolution (ubuntu) is an ubuntu bug [16:41] hrm, dont think i knew that [16:46] bug 790050 needs some love. I am sure once the right person looks at it it will be fixed/closed in about 30 seconds. [16:46] Launchpad bug 790050 in base-files (Ubuntu) "/etc/profile runs /etc/profile.d/*.sh twice (affects: 1) (heat: 8)" [Medium,Triaged] https://launchpad.net/bugs/790050 [16:46] stlsaint: That comes in a lot with other projects using launchpad [16:47] what is the process after Triaged? [16:47] I can swear I saw a flowchart for bugcontrol somewhere... [16:48] arand: that would be niffty [16:48] CarlFK: developer works the bug when they can [16:48] https://wiki.ubuntu.com/Bugs/WorkFlow is a bit incomplete... [16:49] charlie-tca: given it hasn't been assigned, I fear no developer is going to work on it [16:49] probably this? https://wiki.ubuntu.com/Bugs/HowToTriage/Charts [16:49] arand, ^ [16:49] CarlFK: I did tag that bug bitesize, since they have people specifically watching for that [16:50] It doesn't get assigned, sometimes ever, during the life a bug. It will get looked at, though. [16:50] CarlFK, there is no assignemnt until a maintainer starts working on it -- then this maintainer assign the bug to (her|him)self [16:50] omg why is the ubuntu wiki so slow... [16:50] i blame hggdh [16:50] pedro_, that goes without saying ;-) [16:50] pedro_: I will blame hggdh too then. [16:51] * hggdh is used to being blamed, being a consultant for long [16:51] charlie-tca, i do it for everything bad that happens :-) [16:51] pedro_: Yeah, noticed some timeout as well.. that's the one! [16:51] I didn't know I could ;-) [16:51] maybe we can update it [16:51] or put it somewhere is more visible :P [16:51] I thought they did update the wiki, to lower the timeouts and speed it up [16:51] it took me some time to find it [16:52] pedro_, BTW, I think I know why we get the errors on the KernelSRUResults -- the loadpages in there use grep, and I think we are exceeding the timeout [16:52] hggdh, ah that could be it, yes, i'm getting similar errors with the meetings page since it's use regexp [16:53] pedro_, I think I will try splitting the page on results per version, and link the version pages in the main [16:55] charlie-tca: thanks for tagging it. [16:56] Got to do what we can to get the developers/maintainers to look === deryck is now known as deryck[lunch] [17:13] what's the signal that you send to a program when it freezes, in order to make apport do a trace? [17:18] ali1234, on a graphical environment you can run 'apport-bugs -w' [17:18] er, apport-bug -w [17:19] and then select the window to be reported on [17:19] ok, thanks, will do that next time it happens [17:20] pedro_, well, here you go: https://wiki.ubuntu.com/QATeam/KernelSRUResults [17:20] YMMV [17:39] hggdh: -w is fantastic. now I don't need to figure out what package the 'power setting dialog' belongs to [17:40] CarlFK, it is -- and, most importantly, it was a patch straight from the community-at-large :-) [17:40] * CarlFK hugs community [17:40] Thats pretty neat. [17:42] hmm, I think it is not doing what is really needed... it picked "gnome-control-center" that sound OK for power settings? [17:42] yes, it does [17:42] yay. thanks [17:43] The reporter of bug 775492 is not able to reproduce it anymore. Should the status set to Invalid now? [17:43] Launchpad bug 775492 in evolution (Ubuntu) "No line break at quoted message when replying to an email (affects: 2) (heat: 14)" [Undecided,Incomplete] https://launchpad.net/bugs/775492 [17:46] hggdh: it was my patch :) === ttcudif is now known as micromix [18:08] abhinav-, indeed, sorry for not naming you as the author [18:09] hggdh: no need for sorry. people are appreciating the feature is worth it :) [18:10] veger, close INVALID, and state the OP can reopen at anytime if it reoccurs [18:10] abhinav-, :-) [18:10] next thing I am looking to add to apport is a screenshot feature: https://bugs.launchpad.net/apport/+bug/772336 :) [18:10] Launchpad bug 772336 in apport (Ubuntu) (and 1 other project) "Add feature to take screenshots of the buggy window (affects: 1) (heat: 98)" [Wishlist,Triaged] === deryck[lunch] is now known as deryck [18:16] abhinav-, go for it! Yes! [18:19] hggdh: :) yes. Already had a working implementation but with the changes brought in by the Gtk3 API, it seems difficult to do this directly in Python. I will be looking for some work around [18:59] hggdh: ok === yofel_ is now known as yofel [21:11] hggdh: i did apport-bug -w but i didn't get a backtrace from the frozen program? [21:14] ali1234, it should collect all necessary data, and propose to open a new bug -- the data should include a coredump [21:14] it did all that. the data does not include a coredump though [21:14] andol, now, the back-office retracer should eventually kick in and do the retrace [21:14] s/andol/and now/ # go figure this error... [21:14] bug 792549 [21:15] Launchpad bug 792549 in audacity (Ubuntu) "Audacity freezes when clicking on the audio timeline during playback (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/792549 [21:15] ali1234, yeah, no coredump... [21:16] i couldn't post a coredump even if i have one, i'm working on sensitive audio files [21:16] anyway i'm still looking at the frozen audacity, if you have any ideas [21:16] ali1234, OK. You can do it the hard way: you will need to have the (various) debug symbols installed, but you can 'gdb -p ' [21:17] and replace by the corresponding pid [21:17] ptrace: operation not permitted [21:17] ali1234, sorry, you will need to sudo [21:18] (ptrace is now a restricted operation) [21:18] ugh... it's got about a million threads [21:18] start simple... bt only (not thread apply all bt) [21:19] it's somewhere inside libportaudio [21:19] but -- given that it is frozen -- contention between the threads comes to mind [21:19] but i lack debug symbols [21:20] yeah... deadlocks :( [21:20] then no deal. You will need *at least* audacity ddeb, plust libportaudio (and a whole slew more) [21:22] one way to get the symbols, if you have good bandwidth: kill -12 audacity; this should kick apport in; go with it, but do no topen a bug. Instead, run 'apport-retrace -o /tmp/trash /var/crash/ [21:22] er. you also have to 'sudo' it [21:22] hmm i did that once before and it messed up my whole system :) [21:23] now i install ddebs manually [21:23] this will install *every* and *all* needed ddebs [21:23] yes last time it also installed a bunch of other weird stuff [21:23] ali1234, I do not see how it would mess up your system, it will only install ddbes [21:23] ddbes [21:23] dammit [21:23] hehehe [21:23] ddebs [21:23] well, ok, i'll do it [21:24] after the retrace is done, you can either rerun audacity and gdb into it, or apport-retrace -g on the crash file [21:25] kill -12 just ... killed it [21:25] apport did not kick in [21:25] apport service is running [21:26] nothing in /var/crash [21:26] apparently it's not deadlocked to the point where it can't shutdown cleanly? [21:30] * micahg thought it was kill -11 (i.e. SIGSEGV) that "called" apport [21:30] bah [21:31] try kill -11 (I am trying a sigsegv, usually guaranteed to kick apport) [21:31] IDK why I typed -12 [21:31] ok... next time :) [21:32] s/i.e./aka/ [21:35] For bugs from the same make and model, but with different components, whats the best way to state that in a bug? [21:36] Or is just doing an apport-bug with all the attachments good enough? [21:36] file a new bug and let the devs sort it out [21:37] okay-dokey [21:37] :) [21:37] just reference the other bug number in your comments [21:47] * hggdh does not know what would happen if micahg was not there monitoring ;-) [22:18] ok, kill -11 worked, apport-retrace -o says: ERROR: report file does not contain one of the required fields: CoreDump Package ExecutablePath [22:20] the file in /var/crash actually does contain a field marked CoreDump [22:22] it contains ExecutablePath as well, so idk what's up [22:24] ali1234, run /usr/share/apport/apport-gtk on your crash file. apport-gtk must do some initial processing for this crash to be usable [22:27] hggdh: ok, i don't want to submit it though, so i can cancel? [22:27] you should be able to, yes [22:28] yes, it's doing something now [22:28] lots of WARNING: ... not available or incompatible [22:29] i don't think it actually installed anything [22:29] wait, do i need to add the ddeb repository? [22:31] ali1234, yes, you do -- otherwise apt will not be able to find them [22:32] ok, still a few warnings but far less now [23:00] Hey, I just updated to Natty on my netbook, and the unity interface seems to be broken. When I log into an account I get only a black screen. [23:03] wait, nevermind. this is probably the wrong place. disregard