GNOME Bugzilla – Bug 729584
nautilus crashes while copying file to mtp-device via drag and drop
Last modified: 2015-11-24 11:06:37 UTC
Nautilus should not crash when mtp-device (nexus5) is unaviable after some time (after screenlock). Syslog: May 3 16:55:00 Arbeits-PC kernel: [ 9693.669563] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2 May 3 16:55:02 Arbeits-PC kernel: [ 9695.293974] nautilus[2203]: segfault at 0 ip 00007fa9b305f849 sp 00007fff48983750 error 4 in libgtk-3.so.0.1000.8[7fa9b2e7d000+4ff000] May 3 16:55:02 Arbeits-PC kernel: [ 9695.676146] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save.. May 3 16:55:02 Arbeits-PC kernel: [ 9695.676627] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0 May 3 16:55:04 Arbeits-PC kernel: [ 9697.682775] rtw_set_ps_mode(): Enter 802.11 power save mode... May 3 16:55:04 Arbeits-PC kernel: [ 9697.682780] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2 May 3 16:55:08 Arbeits-PC kernel: [ 9701.696141] rtw_set_ps_mode(): Busy Traffic , Leave 802.11 power save.. May 3 16:55:08 Arbeits-PC kernel: [ 9701.696256] rtl8192c_set_FwPwrMode_cmd(): Mode = 0, SmartPS = 0 May 3 16:55:10 Arbeits-PC kernel: [ 9703.702617] rtw_set_ps_mode(): Enter 802.11 power save mode... May 3 16:55:10 Arbeits-PC kernel: [ 9703.702622] rtl8192c_set_FwPwrMode_cmd(): Mode = 1, SmartPS = 2 May 3 16:55:16 Arbeits-PC kernel: [ 9709.837404] OnAction_back May 3 16:55:16 Arbeits-PC kernel: [ 9709.837413] OnAction_back, action=2 May 3 16:55:16 Arbeits-PC kernel: [ 9709.837414] OnAction_back(): DELBA: 0(0) May 3 16:55:23 Arbeits-PC kernel: [ 9716.401708] OnAction_back May 3 16:55:23 Arbeits-PC kernel: [ 9716.401712] OnAction_back, action=0 May 3 16:55:23 Arbeits-PC kernel: [ 9716.401714] issue_action_BA, category=3, action=1, status=0 May 3 14:13:48 Arbeits-PC whoopsie[1031]: online May 3 16:55:24 Arbeits-PC whoopsie[1031]: Parsing /var/crash/_usr_bin_nautilus.1000.crash. May 3 16:55:24 Arbeits-PC whoopsie[1031]: Uploading /var/crash/_usr_bin_nautilus.1000.crash. System: Ubuntu 14.10
Edit: typo, i mean Ubuntu 14.04
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I can confirm this bug for my MTP device (motorola g). I'm running unmodified Debian Wheezy. It happens when a file is dragged or copy/pasted into Nautilus showing the MTP device contents. That is, copying a file TO the MTP device crashes. Copying a file FROM the MTP device works fine. From my syslog: Jul 3 20:06:54 michael-wheezy kernel: [989460.457038] pool[12591]: segfault at 8 ip 00007f667c0d0260 sp 00007f6679099960 error 4 in libgvfsdaemon.so[7f667c0be000+24000] Jul 3 20:06:55 michael-wheezy kernel: [989460.596801] nautilus[12563]: segfault at 7fbc0000000a ip 00007fbc39971172 sp 00007fffd23848b0 error 4 in libc-2.13.so[7fbc398f6000+182000] Antonio, I tried to generate a stack trace. For this, I installed gvfs-dbg package and reproduced the crash. But it still only shows these two lines in syslog. The link you provided didn't help much. I would need clear instructions how to make a stack trace, so that I can provide it here.
Hi Michael. Indeed, that page may be confusing, so let me simplify the steps here: 1) Have the following 5 packages installed: libglib2.0-0-dbg gvfs-dbg libgtk-3-0-dbg nautilus-dbg gdb 2) In a Terminal, run this command (which will close all nautilus windows and quit): nautilus -q 3) Then, run this command: gdb nautilus 4) After gdb starts, you will see a "(gdb)" prompt in the terminal. Just enter this command: set pagination 0 5) After that, enter this command, which will launch nautilus inside gdb: run 6) Now that nautilus is running with gdb, make nautilus crash by copying a file to the MPT device, as you confirmed above. 7) After nautilus crashes, go back to the terminal window and enter this command: thread apply all bt 8) The output generated after this command is the stack trace. Just select it, right click and choose "Copy". 9) Paste the stack trace as a comment to this bug report. Thanks in advance! Feel free to come by our IRC channel #nautilus at irg.gnome.org or email me if have trouble getting the stack trace.
I managed to run Nautilus with gdb according to your instructions. However, in this window, I cannot access the MTP device, it is not listed. I only can see the MTP device by selecting "Browse files" from the Gnome Bluetooth menu, but that opens a different Nautilus window. Dragging a file into there, it did not segfault, but showed the message "Did not receive a reply". For the window opened in gdb, it also did not help browsing to the MTP path: obex://[41:40:D6:97:ED:8D]/PHONE_MEMORY/Pictures Nautilus thiks this is a local path /home/michael/obex...
(In reply to comment #5) > that opens a different Nautilus window. Dragging a file into there, it did not > segfault, but showed the message "Did not receive a reply". Weird. I don't know how to help with this. Maybe try again later after a reboot? > obex://[41:40:D6:97:ED:8D]/PHONE_MEMORY/Pictures So that's MTP over bluetooth? Are you able to try MTP over an USB cable? Does it make a difference?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!