As usual (and indeed correctly by the ubuntu policy), the bug is being closed as "fix released" when there is in fact no fix for the stable distribution against which the bug was originally reported. And as usual this is extremely confusing. If one reports a bug against a package that is in distribution version foo which still has not reached end of life, he expects the bug to be cosidered closed when a fix is available for foo, not for something else. Unfortunately 'fix release' gives no clue at all about whether the bug fix will be released to the distribution against which it was reported or if the bug will in fact be considered 'invalid'/'not worth fixing' for it. Can someone knowledgeable be so kind to hint at whether this bug will likely be fixed for quantal or not?
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1075928 Title: Please, silence IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed Status in “libcanberra” package in Ubuntu: Fix Released Bug description: On Kubuntu 12.10, whenever a gtk application is opened from the konsole, the terminal gets flooded with Gdk-CRITICAL **: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed which makes the konsole almost impossible to use after a gtk application has been backgrounded. The only way to start gtk apps from the konsole (or a terminal) keeping the konsole usable is to start them redirecting stderr to /dev/null, which should not be the case. This message turns a probably innocuous bug in gtk apps into a severe annoyance also to the konsole. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1075928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
