FS#32927 - [gconf] causes banshee to crash
Attached to Project:
Arch Linux
Opened by Luciano Ruete (luchano) - Saturday, 01 December 2012, 21:02 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 13 March 2013, 13:57 GMT
Opened by Luciano Ruete (luchano) - Saturday, 01 December 2012, 21:02 GMT
Last edited by Jan de Groot (JGC) - Wednesday, 13 March 2013, 13:57 GMT
|
Details
Description:
gconf is causing banshee (and maybe other applications) to crash. As reported in this issue[0] just applying this patch[1] solves the problem. [0] https://bugs.archlinux.org/task/32390 [1] https://bazaar.launchpad.net/~timo-jyrinki/gconf/ubuntu.support-s-to-as-migrations/view/head:/debian/patches/call-dbus_g_thread_init.patch Additional info: * package version(s) local/gconf 3.2.5-3 * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Jan de Groot (JGC)
Wednesday, 13 March 2013, 13:57 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in gconf-sharp.
Why fixing it there and not in gconf itself:
- the proposed patch is incorrect, will cause side effects for apps that call any dbus function before calling into gconf
- Mono applications will not call into dbus directly anyways because they use native dbus-sharp, so fixing it there is safe
Wednesday, 13 March 2013, 13:57 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in gconf-sharp.
Why fixing it there and not in gconf itself:
- the proposed patch is incorrect, will cause side effects for apps that call any dbus function before calling into gconf
- Mono applications will not call into dbus directly anyways because they use native dbus-sharp, so fixing it there is safe
https://bugzilla.gnome.org/show_bug.cgi?id=683830
My guess is that this will get fixed in gconf some day, but I don't know if that's before or after Banshee has moved to gsettings.
The patch is a one-liner that can be easly reverted and seems to be stable enough as opossed to the un-patched version.
That said, I understand I'm not a maintainer and maybe this arguments are not strong enough to include the inappropriated (but working) fix.
See https://bugzilla.gnome.org/show_bug.cgi?id=662358