abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: /usr/libexec/gvfsd-obexftp --spawner :1.10 /org/gtk/gvfs/exec_spaw/6 component: gvfs crash_function: pthread_cond_signal@@GLIBC_2.3.2 executable: /usr/libexec/gvfsd-obexftp kernel: 2.6.34.7-63.fc13.i686 package: gvfs-obexftp-1.6.2-1.fc13 rating: 4 reason: Process /usr/libexec/gvfsd-obexftp was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1292054305 uid: 502 How to reproduce ----- 1. tried to browse files on remote cellphone via bluetooth 2. 3.
Created attachment 468122 [details] File: backtrace
Package: gvfs-obexftp-1.6.2-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. With a Motorola V3XX 2. Enable Bluetooth 3. gnome-bluetooth ... Set up new device ... enable it ... bind to it 4. An icon appears on your GNOME desktop 5. dclick on the icon to explode that into a nautilus file browser See the crash Comment ----- This segfault wasn't reproducible the second time that I tried to associate with this device. i.e. it worked the 2nd time, didn't segfault and brought up a nautilus obex ftp on the device. The original owner of this device had significant amounts of trouble working with it; an experience that I'm repeating here. Larger backstory ... I have two of these devices at hand, one works flawlessly and exhibits a wonderful GNOME bluetooth user experience and one had "issues" to the extent that, while bluetooth association works, bringing up nautilus causes segfaults and browsing the "pictures" directory on the phone is impossible. Folder contents could not be displayed Couldn't parse the incoming data I will document that issue in a separate report. This report is exclusively about the segfault in gvfsd-obexftp as shown. The units are: W's V3XX is unproblematic C's V3XX has issues. What I did here to exhibit the crash. 1. associate to W's V3XX, mount it in gvfs, browse its filesystem, extract some pictures, dismount 2. associate with C's V3XX, attempt to mount it. The point of this is to highlight that it isn't some Motorola V3XX device-specific problem so much as the data on the device somehow. I have one V3XX (W's V3XX) that works fine under GNOME bluetooth and one that does not (C's V3XX). The difference between the two is that one unit has minimal customization and minimal data loading (W's V3XX is used by an adult); the other one is massively customized and has lots of internal data, pictures, music (C's V3XX is used by a teenager). Here is what ~/.xsession-errors saw $ ls -lsh ~/.xsession-errors 63M -rw-------. 1 wbaker wbaker 63M Jan 1 21:38 /home/wbaker/.xsession-errors It's a 60MB file and is considered "a binary file" by most utilities due to all the chatter from evince and other utilities. I will highlight only the relevant part. bash -c 'cat -ve .xsession-errors | tail -n 10000 > dot.xsession-errors.safe ; gedit dot.xsession-errors.safe' ... cut & past ... with annotations ** (bluetooth-wizard:2439): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ ** (bluetooth-applet:22498): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ ** (bluetooth-wizard:2439): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ ** Message: has_config_widget 00:21:36:1B:26:B2 DialupNetworking$ ** Message: has_config_widget 00:21:36:1B:26:B2 OBEXObjectPush$ ** Message: has_config_widget 00:21:36:1B:26:B2 OBEXFileTransfer$ ** Message: has_config_widget 00:21:36:1B:26:B2 AudioSource$ ** Message: has_config_widget 00:21:36:1B:26:B2 A/V_RemoteControlTarget$ ** Message: has_config_widget 00:21:36:1B:26:B2 Headset_-_AG$ ** Message: has_config_widget 00:21:36:1B:26:B2 HandsfreeAudioGateway$ ** Message: has_config_widget 00:21:36:1B:26:B2 DialupNetworking$ ** Message: has_config_widget 00:21:36:1B:26:B2 OBEXObjectPush$ ** Message: has_config_widget 00:21:36:1B:26:B2 OBEXFileTransfer$ ** Message: has_config_widget 00:21:36:1B:26:B2 AudioSource$ ** Message: has_config_widget 00:21:36:1B:26:B2 A/V_RemoteControlTarget$ ** Message: has_config_widget 00:21:36:1B:26:B2 Headset_-_AG$ ** Message: has_config_widget 00:21:36:1B:26:B2 HandsfreeAudioGateway$ ** Message: Default Bluetooth adapter is powered$ <--- here ends Step 1 wherein I associated with W's V3XX and it was a happy experience <--- here begins Step 2 wherein I associated with C's V3XX and it segfaulted. Failed to mount OBEX volume: Connection to the device lost** Message: adding killswitch idx 0 state 1$ ** Message: killswitch 0 is 1$ ** Message: killswitches state 1$ ** (bluetooth-properties:3027): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ ** (bluetooth-properties:3027): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ $ (gnome-help:3061): Gtk-CRITICAL **: gtk_tool_button_new: assertion `icon_widget == NULL || GTK_IS_MISC (icon_widget)' failed$ $ (gnome-help:3061): GLib-GObject-WARNING **: invalid (NULL) pointer instance$ $ (gnome-help:3061): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed$ $ (gnome-help:3061): Gtk-CRITICAL **: gtk_toolbar_insert: assertion `GTK_IS_TOOL_ITEM (item)' failed$ $ (gnome-help:3061): Gtk-CRITICAL **: gtk_tool_button_new: assertion `icon_widget == NULL || GTK_IS_MISC (icon_widget)' failed$ $ (gnome-help:3061): GLib-GObject-WARNING **: invalid (NULL) pointer instance$ $ (gnome-help:3061): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed$ $ (gnome-help:3061): Gtk-CRITICAL **: gtk_toolbar_insert: assertion `GTK_IS_TOOL_ITEM (item)' failed$ OMF category 'GNOME|Office' not recognised, ignoring.$ Failed to mount OBEX volume: Service search failed (Software caused connection abort)** Message: RFKILL event: idx 0 type 2 op 1 soft 0 hard 0$ $ ** Message: removing killswitch idx 0$ ** Message: RFKILL event: idx 0 type 2 op 1 soft 0 hard 0$ $ ** Message: removing killswitch idx 0$ ** Message: RFKILL event: idx 1 type 2 op 0 soft 0 hard 0$ $ ** Message: RFKILL event: idx 1 type 2 op 0 soft 0 hard 0$ $ ** Message: adding killswitch idx 1 state 1$ ** Message: adding killswitch idx 1 state 1$ ** Message: killswitch 1 is 1$ ** Message: killswitch 1 is 1$ ** Message: killswitches state 1$ ** Message: killswitches state 1$ ** Message: RFKILL event: idx 1 type 2 op 2 soft 0 hard 0$ $ ** Message: killswitch 1 is 1$ ** Message: killswitches state 1$ ** Message: RFKILL event: idx 1 type 2 op 2 soft 0 hard 0$ $ ** Message: killswitch 1 is 1$ ** Message: killswitches state 1$ ** (bluetooth-properties:3027): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ ** (bluetooth-applet:22498): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ ** (bluetooth-properties:3027): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ ** (bluetooth-applet:22498): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ Failed to mount OBEX volume: Service search failed (Host is down)$ ** (evince:9292): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:8832): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:9588): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:9523): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:9543): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:7696): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:9207): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:9588): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:9207): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:7696): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:9292): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:9523): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:9543): WARNING **: Error setting file metadata: No such file or directory$ $ ** (evince:8832): WARNING **: Error setting file metadata: No such file or directory$ Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x201fc04 (/ on Clara); these messages lack timestamps and therefore suck.$ ** Message: adding killswitch idx 1 state 1$ ** Message: killswitch 1 is 1$ ** Message: killswitches state 1$ ** (bluetooth-properties:3306): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ ** (bluetooth-properties:3306): DEBUG: Unhandled UUID 0000111b-0000-1000-8000-00805f9b34fb (0x111b)$ For this interval, /var/log/messages contains: Jan 1 21:17:29 suffragette bluetoothd[1867]: Discovery session 0x10d7d50 with :1.13276 activated Jan 1 21:17:46 suffragette bluetoothd[1867]: Stopping discovery Jan 1 21:17:47 suffragette bluetoothd[1867]: link_key_request (sba=00:1B:DC:0F:5D:C8, dba=00:21:36:1B:26:B2) Jan 1 21:17:47 suffragette bluetoothd[1867]: pin_code_request (sba=00:1B:DC:0F:5D:C8, dba=00:21:36:1B:26:B2) Jan 1 21:18:03 suffragette bluetoothd[1867]: link_key_notify (sba=00:1B:DC:0F:5D:C8, dba=00:21:36:1B:26:B2, type=0) Jan 1 21:18:03 suffragette bluetoothd[1867]: probe failed with driver input-headset for device /org/bluez/1856/hci0/dev_00_21_36_1B_26_B2 Jan 1 21:18:04 suffragette bluetoothd[1867]: Stopping discovery Jan 1 21:19:19 suffragette obex-data-server: sdp_extract_seqtype: Unexpected end of packet Jan 1 21:19:19 suffragette bluetoothd[1867]: link_key_request (sba=00:1B:DC:0F:5D:C8, dba=00:1F:7E:30:20:A0) Jan 1 21:19:23 suffragette obex-data-server: sdp_extract_seqtype: Unexpected end of packet Jan 1 21:19:23 suffragette bluetoothd[1867]: link_key_request (sba=00:1B:DC:0F:5D:C8, dba=00:21:36:1B:26:B2) Jan 1 21:19:27 suffragette kernel: gvfsd-obexftp[2463]: segfault at 6f6e657c ip 0033389d sp bf8ff66c error 4 in libpthread-2.12.1.so[329000+17000] Jan 1 21:19:28 suffragette abrt[2473]: saved core dump of pid 2463 (/usr/libexec/gvfsd-obexftp) to /var/spool/abrt/ccpp-1293945568-2463.new/coredump (11218944 bytes) Jan 1 21:19:28 suffragette abrtd: Directory 'ccpp-1293945568-2463' creation detected Jan 1 21:19:29 suffragette abrtd: New crash /var/spool/abrt/ccpp-1293945568-2463, processing Jan 1 21:19:29 suffragette abrtd: RunApp('/var/spool/abrt/ccpp-1293945568-2463','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .') Jan 1 21:19:30 suffragette abrtd: Getting crash infos... Jan 1 21:22:43 suffragette abrtd: Creating report... Jan 1 21:31:50 suffragette kernel: usb 1-1.2: USB disconnect, address 6 Jan 1 21:31:50 suffragette kernel: btusb_intr_complete: hci0 urb f1f5c600 failed to resubmit (19) Jan 1 21:31:50 suffragette kernel: btusb_bulk_complete: hci0 urb f4dfe780 failed to resubmit (19) Jan 1 21:31:50 suffragette kernel: btusb_bulk_complete: hci0 urb f2c1dc00 failed to resubmit (19) Jan 1 21:31:50 suffragette kernel: btusb_send_frame: hci0 urb d9128d80 submission failed Jan 1 21:31:50 suffragette bluetoothd[1867]: hci_open_dev(0): No such device (19) Jan 1 21:31:50 suffragette bluetoothd[1867]: hci_open_dev(0): No such device (19) Jan 1 21:31:50 suffragette bluetoothd[1867]: HCI dev 0 down Jan 1 21:31:50 suffragette bluetoothd[1867]: Adapter /org/bluez/1856/hci0 has been disabled Jan 1 21:31:50 suffragette bluetoothd[1867]: Stopping security manager 0 Jan 1 21:31:50 suffragette bluetoothd[1867]: HCI dev 0 unregistered Jan 1 21:31:50 suffragette bluetoothd[1867]: Unregister path: /org/bluez/1856/hci0 Jan 1 21:31:50 suffragette NetworkManager[1391]: <info> BT device 00:1F:7E:30:20:A0 removed Jan 1 21:31:50 suffragette NetworkManager[1391]: <info> BT device 00:21:36:1B:26:B2 removed Jan 1 21:31:50 suffragette dbus: [system] Rejected send message, 2 matched rules; type="error", sender=":1.161" (uid=500 pid=22498 comm="bluetooth-applet) interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply=0 destination=":1.17" (uid=0 pid=1856 comm="/usr/sbin/bluetoothd)) Jan 1 21:31:51 suffragette kernel: usb 1-1.2: new full speed USB device using ehci_hcd and address 12 Jan 1 21:31:51 suffragette kernel: usb 1-1.2: New USB device found, idVendor=0a12, idProduct=0001 Jan 1 21:31:51 suffragette kernel: usb 1-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Jan 1 21:31:51 suffragette bluetoothd[1867]: HCI dev 0 registered Jan 1 21:31:51 suffragette bluetoothd[1867]: HCI dev 0 up Jan 1 21:31:51 suffragette bluetoothd[1867]: Starting security manager 0 Jan 1 21:31:51 suffragette bluetoothd[1867]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Jan 1 21:31:51 suffragette bluetoothd[1867]: probe failed with driver input-headset for device /org/bluez/1856/hci0/dev_00_1F_7E_30_20_A0 Jan 1 21:31:51 suffragette bluetoothd[1867]: probe failed with driver input-headset for device /org/bluez/1856/hci0/dev_00_21_36_1B_26_B2 Jan 1 21:31:51 suffragette bluetoothd[1867]: Adapter /org/bluez/1856/hci0 has been enabled Jan 1 21:33:02 suffragette obex-data-server: sdp_extract_seqtype: Unexpected end of packet Jan 1 21:33:02 suffragette bluetoothd[1867]: link_key_request (sba=00:1B:DC:0F:5D:C8, dba=00:1F:7E:30:20:A0) Jan 1 21:36:16 suffragette obex-data-server: sdp_extract_seqtype: Unexpected end of packet Jan 1 21:36:17 suffragette bluetoothd[1867]: link_key_request (sba=00:1B:DC:0F:5D:C8, dba=00:21:36:1B:26:B2)
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.