2012/03/20/#ubuntu-bugs.txt

=== JanC_ is now known as JanC
=== bladernr_afk is now known as bladernr_
[11:43] <hggdh> good morning
=== greyback is now known as greyback|lunch
=== chrisccoulson_ is now known as chrisccoulson
=== bladernr_ is now known as bladernr_afk
=== greyback|lunch is now known as greyback
[12:49] <UrB> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/950413 - anyone with similar bluetooth chip care to confirm whether this is hardware related or just my computer acting up
[12:49] <ubot2`> Launchpad bug 950413 in bluez "Bluetooth connections stalling" [Undecided,New]
=== bladernr_afk is now known as bladernr_
[14:21] <bcurtiswx> good morning
=== bulldog98_ is now known as bulldog98
[15:25] <shnatsel> Hello! I'm here because of bug 122637
[15:25] <ubot2`> Launchpad bug 122637 in notification-daemon "notification-daemon crashed with signal 5 in g_logv()" [Medium,Won't fix] https://launchpad.net/bugs/122637
[15:26] <shnatsel> The bug is marked "won't fix" with a note to reopen the bug if more info can be provided
[15:26] <shnatsel> I've added GDB and Valgrind logs, also I run into this crash almost every time
[15:27] <shnatsel> I think the bug should be reopened, but it looks like commoners can't change status from "Won't fix" to anything else
[15:28] <shnatsel> so could anybody with the right permissions please reopen the bug?
[15:49] <greyback> shnatsel: the gdb isn't very useful I'm afraid. Can you capture it again, and then run "bt" to get the back-trace
[15:49] <shnatsel> greyback: ok, will do
[15:49] <hggdh> shnatsel: also, it would be better to open a new bug. This one most probably has nothing more to do -- really old release levels
[15:50] <shnatsel> hggdh: Apport redirects all crash reports to that bug
[15:50] <hggdh> shnatsel: and yes, indeed Won't Fix is a terminal status. Changes from Won't Fix (or Fix Released) need special permissions.
[15:50] <hggdh> shnatsel: oh. We will fix it
[15:51] <shnatsel> hggdh: well, not "all", but reports about this crash go to that bug
[15:52] <hggdh> enough to matter, anyway. Apport should not do that, not for that bug
[15:55] <bdmurray> there is a bugpattern for that bug which could be removed
[16:07] <shnatsel> I've installed debugging symbols for glib and gtk, got a backtrace from gdb and attached it to that bug
[16:15] <shnatsel> anything else I can do to get this fixed?
[16:19] <hggdh> shnatsel: open a NEW bug, please. This one is gone
[16:22] <shnatsel> hggdh: can I do it using apport now?
[16:38] <hggdh> shnatsel: I am updating the pattern, please wait a bit
[16:39] <shnatsel> hggdh: thanks, and no problem, I'll wait
[16:40] <hggdh> bdmurray: can you review https://code.launchpad.net/~hggdh2/apport/ubuntu-bugpatterns-122637/+merge/98452
[16:40] <hggdh> ?
[16:42] <bdmurray> hggdh: of course
[16:42] <cyphermox> om26er: so, news? :)
[16:43] <bdmurray> hggdh: the merge into branch is wrong
[16:44] <bdmurray> its showing lp:apport and it should be lp:~ubuntu-control/apport/ubuntu-bugpatterns
[16:44] <om26er> cyphermox, its complext ;-) but the summary is my internet is broke (dead phone line) and I am using a really slow connection just for IRC so did not get around to test it
[16:44] <hggdh> dammit
[16:44] <cyphermox> om26er: np. in any case I ran this by upstream and there was indeed a leak there in upstream code
[16:44] <hggdh> correcting
[17:07] <hggdh> bdmurray: done, can you review https://code.launchpad.net/~hggdh2/apport/bug122637/+merge/98459?
[18:27] <hggdh> shnatsel: you should now be able to open a new bug via apport
[18:28] <shnatsel> hggdh: thanks! will do
=== yofel_ is now known as yofel
[19:50] <shnatsel> hggdh: reported the bug as 960556 (private until retraced), thanks a lot for your help!
[19:51] <hggdh> shnatsel: you are welcome.
[19:51] <hggdh> bug 960556
[19:52] <shnatsel> it's private, visible only to apport retracing service
[19:52] <hggdh> and to me ;-)
[19:53] <hggdh> shnatsel: there is already an update, apport is asking you to update your system and try again
[19:53] <shnatsel> hggdh: ah, thanks, will do
[21:48] <shnatsel> hggdh: re-reported the bug as bug 960642
[22:04] <shnatsel> hggdh: oh good, now it's been marked as duplicate of somebody else's private report :D
=== jbicha is now known as Guest22703
[22:36] <bkerensa> bdmurray: Someone found a bug that the current ISO's for 11.10 will not burn because they exceed the capacity of a CD
[22:36] <bkerensa> https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/960630
[22:36] <ubot2`> Launchpad bug 960630 in brasero "Cannot burn Ubuntu Installation CD" [Undecided,Confirmed]
[22:36] <bkerensa> I just was able to reproduce this with both i386 and amd64 both easily exceeding the capacity of a CD
[22:41] <bkerensa> Can someone mark Bug #960489 as Wishlist
[22:41] <ubot2`> Launchpad bug 960489 in calibre "Update to latest version for Sony Reader support" [Undecided,New] https://launchpad.net/bugs/960489
[22:43] <micahg> bkerensa: that's not wishlist, it's incomplete as the bug was filed with the oneiric package version in mind, we already have the proper version in precise, might be a convert to backports bug if it's a possible to backport, checking
[22:44] <bkerensa> micahg: oversight on my part :P
[22:44] <micahg> we can probably backport that
[22:44] <bkerensa> sorry about that
[22:44] <micahg> so, I'd just move the bug to oneiric-backports
[22:44] <micahg> it's a project
[22:44] <bkerensa> ok