[05:34] <duanedesign> 14
[05:37] <greg-g> 12
[10:30] <ssam> please could someone renew my ubuntu-bugcontrol membership. my launchpad page is https://launchpad.net/~samtygier
[10:49] <korrawit> Hello. I've found this https://bugs.launchpad.net/bugs/617264 is already fixed in 3.3.2 (from upstream comment and my test)
[10:50] <korrawit> But bug status of "libreoffice (ubuntu)" is just triaged.
[10:50] <korrawit> Can I set the status to "fix released"?
[10:55] <trinikrono> korrawit: normally i see the launchpad janitor does that :)
[10:55] <trinikrono> once it has the upstream tracker like you do
[11:01] <korrawit> trinikrono: Thanks! but I think the janitor missed this bug, maybe because there's no changelog mentioning this bug ...
[11:02] <trinikrono> korrawit: is it fixed in oneiric?
[11:04] <korrawit> trinikrono: maybe yes, (I didn't test yet) because oneiric have version 3.4.2
[11:04] <trinikrono> well i think we should test it in oneiric first
[11:05] <trinikrono> since they said it is fixed in 3.4?
[11:05] <korrawit> trinikrono: from upstream, they said it will be in 3.4 and 3.3.2
[11:06] <korrawit> trinikrono: natty currently already have 3.3.3 ...
[11:06] <trinikrono> korrawit: is it working in natty?
[11:09] <korrawit> trinikrono: sorry, but I don't have natty to test, I just looking at https://launchpad.net/df-libreoffice/+packages
[11:09] <trinikrono> korrawit: i was looking at the changelog here http://changelogs.ubuntu.com/changelogs/pool/main/libr/libreoffice/libreoffice_3.4.2-2ubuntu3/changelog
[11:09] <korrawit> trinikrono: FYI, I only tested 3.3.2 in maverick and it works fine
[11:12] <korrawit> trinikrono: and that changelog doesn't mention lp#617264
[11:12] <trinikrono> well i am looking and i have not seen it as yet
[11:14] <trinikrono> korrawit: you see in the upstream tracker how it is linked to another bug report
[11:14] <trinikrono> this one https://bugs.freedesktop.org/show_bug.cgi?id=31939
[11:15] <korrawit> trinikrono: yep
[11:18] <korrawit> trinikrono: excuse me, but what exactly the problems here? we need some tests, right?
[11:19] <trinikrono> i am just trying to find where in the changelog this is fixed
[11:19] <trinikrono> i believe if you say it is fix release we need to know where
[11:26] <trinikrono> korrawit: well this bug only affects people in lucid come back right?
[11:27] <korrawit> trinikrono: what it means by "lucid come back"?
[11:27] <trinikrono> i mean lucid and karmic etc
[11:30] <trinikrono> i think the safest thing you can do is to put a comment on the bug report, since it already has someone from bug control (penalvch) working on it, say how you tested it in maverick and it works
[11:30] <trinikrono> korrawit: what do you think
[11:30] <trinikrono> i see it also has a bug in open office also
[11:32] <korrawit> trinikrono: Aha! I found the changelog, it's in the mailing list http://nabble.documentfoundation.org/LibreOffice-3-3-2-Release-Candidate-1-available-tp2663041p2663041.html
[11:33] <korrawit> trinikrono: it mentions freedesktop bug 31939
[11:34] <korrawit> trinikrono: for your question "lucid and karmic etc", I don't have that ubuntu release to test
[11:34] <trinikrono> penalvch: ping :D
[11:35] <korrawit> trinikrono: but I conclude that if they have libreoffice >= 3.3.2 or >= 3.4 it should be fine
[11:41] <trinikrono> korrawit: you see i dont believe once a bug is already triaged if we should change the status to something else
[11:41] <trinikrono> i would of asked penalvch first
[11:46] <korrawit> trinikrono: OK, but I'll be back in an hour. Thanks very much :D
[13:15] <korrawit> trinikrono: I've just commented on it, but refresh to see penalvch beats me to it. Anyway, thanks again!
[13:16] <trinikrono> roger
[15:13] <hggdh> trinikrono: you were looking for me, right?
[15:22]  * hggdh goes walking the dogs
[19:24] <bullgard4> To produce backtraces during a LIbreOffice crash is it enough to install additionally the package  libreoffice-dbg?
[20:21] <hggdh> bullgard4: probably not. You will also need the run-time auxiliary libraries, at least
[20:21] <hggdh> bullgard4: probably easier to have apport write  a crash, and then use apport-retrace to get the stacktrace/run gdb
[20:26] <bullgard4> hggdh: "to have apport write a crash" --  I do not understand you well. I thought that apport is a passive tool which photographs a state of the computer after an error has occured. Can you elaborate.
[20:27] <hggdh> bullgard4: if apport is active (seel /etc/default/apport), then when a crash happens, apport saves data to /var/crash/<whatever>
[20:28] <bullgard4> Ah!
[20:28] <hggdh> and proposes to process the crash and upload it to LP
[20:28] <hggdh> so... you use it, up to it asking to open a bug. At this point you cancel apport, and run apport-retrace
[20:29] <hggdh> apport is not so much a passive tool as a reactive tool (for crashes)
[20:30] <bullgard4> How can I find out what the run-time auxiliary libraries are for LibreOffice?
[20:30] <hggdh> well... you can run 'apt-cache rdepends <libreoffice package name>'
[20:30] <hggdh> get some pencils and a lot of paper
[20:31] <bullgard4> hggdh: Thank you very much for your ample help.
[20:31] <hggdh> yw