GNOME Bugzilla – Bug 150388
Crashed on file send
Last modified: 2009-02-25 14:39:31 UTC
Distribution: Gentoo Base System version 1.5.2 Package: gnome-bluetooth Severity: critical Version: GNOME2.6.2 0.5.1 Gnome-Distributor: Gentoo Linux Synopsis: Crashed on file send Bugzilla-Product: gnome-bluetooth Bugzilla-Component: obex Bugzilla-Version: 0.5.1 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: I sent a file from the phone to the computer. It asked if I accepted it and crashed Steps to reproduce the crash: 1. 2. 3. Expected Results: File transfer How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-obex-server' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". 0x0ee48360 in waitpid () from /lib/libpthread.so.0
+ Trace 49405
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-17 14:07 ------- Unknown version 0.5.1 in product gnome-bluetooth. Setting version to "0.5". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-bluetooth". Setting to default milestone for this product, '---' Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Fedora Core 2, Rawhide 0908.0 PPC [wmealing@ibook ~]$ rpm -qa | grep blue bluez-hcidump-1.10-1 bluez-utils-2.10-2 bluez-libs-2.10-2 bluez-pin-0.23-3 bluez-bluefw-1.0-5 gnome-bluetooth-0.5.1-3 gnome-bluetooth 0.5.1 Different backtrace, same problem. The file transfers correctly except gnome-obex-server crashes. Program received signal SIGTRAP, Trace/breakpoint trap.
+ Trace 50129
Thread 805547392 (LWP 7083)
I believe this has been fixed in CVS.
is the bug in gob2?
Well, it's in the code that uses gob, yeah. Here's the diff: % cvs diff -u -r1.2 fileactiondialog.gob Index: fileactiondialog.gob =================================================================== RCS file: /cvs/gnome/gnome-bluetooth/src/fileactiondialog.gob,v retrieving revision 1.2 diff -u -r1.2 fileactiondialog.gob --- fileactiondialog.gob 17 Jun 2004 20:42:55 -0000 1.2 +++ fileactiondialog.gob 8 Oct 2004 11:57:46 -0000 @@ -51,13 +51,16 @@ private const gchar *fname; private GdkPixbuf *icon = { gnomebt_icon (); } - destroywith gdk_pixbuf_unref; + destroywith g_object_unref; private GdkPixbuf *mimeicon = { NULL; } - destroywith gdk_pixbuf_unref; + destroywith g_object_unref; private GnomeVFSFileInfo *vfsinf = { NULL; } - destroywith gnome_vfs_file_info_unref; + destroy { + gnome_vfs_file_info_unref (vfsinf); + vfsinf = NULL; + }; private gchar *uri = { NULL; } destroywith g_free; @@ -114,6 +117,7 @@ gnome_vfs_mime_application_free (self->_priv->app); } +/* FIXME: make this DISCARD, not DELETE */ self->_priv->deletebutton = GTK_WIDGET (gtk_dialog_add_button ( GTK_DIALOG(self), GTK_STOCK_DELETE, GNOMEBT_FILEACTION_DELETE));
and the fixes in permissiondialog.gob ... thanks!
% cvs diff -u -r1.7 permissiondialog.gob Index: permissiondialog.gob =================================================================== RCS file: /cvs/gnome/gnome-bluetooth/src/permissiondialog.gob,v retrieving revision 1.7 retrieving revision 1.8 diff -u -r1.7 -r1.8 --- permissiondialog.gob 17 Jun 2004 20:42:55 -0000 1.7 +++ permissiondialog.gob 29 Jul 2004 17:13:39 -0000 1.8 @@ -43,7 +43,7 @@ private GtkWidget *rememberbutton; private GdkPixbuf *icon = { gnomebt_icon (); } - destroywith gdk_pixbuf_unref; + destroywith g_object_unref; private gboolean remember = FALSE;
*** Bug 158310 has been marked as a duplicate of this bug. ***
*** Bug 163266 has been marked as a duplicate of this bug. ***
Gday Edd, It is fixed in the upstream. Have it working fine as of Nov 2004. Fixed for my bug at least.
Yeah, I've just not dropped a new release with this fix in yet. I'll mark this bug fixed when I have done so.
Hopefully a release soon :) 2004-07-29 Frederic Crozat <fcrozat@mandrakesoft.com> * src/fileactiondialog.gob: * src/permissiondialog.gob: Fix crash when using gcc 3.4.