Version-Release number of selected component: Thunar-1.6.3-2.fc20 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.11.1-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:550 #1 magazine_chain_prepare_fields at gslice.c:623 #2 magazine_cache_push_magazine at gslice.c:697 #3 thread_memory_magazine2_unload at gslice.c:815 #4 g_slice_free1 at gslice.c:1106 #5 g_type_free_instance at gtype.c:1938 #6 gtk_container_destroy at gtkcontainer.c:1073 #11 gtk_object_dispose at gtkobject.c:421 #13 gtk_toolbar_forall at gtktoolbar.c:2529 #14 gtk_container_destroy at gtkcontainer.c:1073
Created attachment 805095 [details] File: backtrace
Created attachment 805097 [details] File: cgroup
Created attachment 805098 [details] File: core_backtrace
Created attachment 805100 [details] File: dso_list
Created attachment 805102 [details] File: environ
Created attachment 805103 [details] File: exploitable
Created attachment 805104 [details] File: limits
Created attachment 805105 [details] File: maps
Created attachment 805106 [details] File: open_fds
Created attachment 805107 [details] File: proc_pid_status
Created attachment 805108 [details] File: var_log_messages
Just installed rpmfusion free and non-free, saved a screenshot to an ext3-formatted usb-drive. Using Thunar to unmount the usb-drive, then closing Thunar. reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.11.1-300.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: Process /usr/bin/thunar was killed by signal 11 (SIGSEGV) runlevel: unknown type: CCpp uid: 1000
I worked with flash (unmounted and closed file manager). I don't know about reproducing. reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.11.3-301.fc20.i686 package: Thunar-1.6.3-2.fc20 reason: Process /usr/bin/thunar was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Close Thunar reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.11.8-300.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: Process /usr/bin/thunar was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
exiting thunar with ctrl-w, then it crashed. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/Thunar crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.11.8-300.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: Process /usr/bin/thunar was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Just used x11vnc reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: thunar crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.12.5-302.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I had the problem doing something similar to what Ray did in comment 11 reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/Thunar file:///home/biafra crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.12.5-302.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
There is a volume (/dev/loop0), I clicked on it, it asked me for root password, I closed that window. The "in progress" icon was still shown by the volume. I closed Thunar.
Yesterday I copied some (lots of, various folders in parallel batches) files to two different removable drives (flash drive and android sdcard via reader, both FAT32 I guess), unmounted both (using Eject button) and left all the ~5 windows overnight. In the morning first thing I touched in Thunar was a window that previously had removable drive opened and was just in the state after ejecting the drive and auto-switching to $HOME. I only turned off hidden files (C-H) and hit C-W to close it, when Thunar crashed.
I also have this problem. I unmounted a device, then closed the window (ctrl+w) and the ABRT alert appeared.
Still being reported in very random cases.
It happened with FUSE SSH to me.
Another user experienced a similar problem: Not a clue - sorry. I didn't particularly notice Thunar closing - probably thought I'd done it by accident until the bug reporting tool put its hand up. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.13.9-200.fc20.i686+PAE package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Here is how it happened here: 1) Unmounted a cryptsetup encrypted volume (by right-clicking it in thunar and selecting "Unmount Volume") 2) Closed thunar immediately (maybe, not sure, before the actual umounting or "cryptsetup close" finished running).
Another user experienced a similar problem: Unmount a usb stick or a phone which was connected in MTP Mode. I had this problem occur several times reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.14.5-200.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I had just finished copying and deleting some files from a USB stick, after I had ejected the stick this bug occurred. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: thunar crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.14.5-200.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I clicked the unmount button on USB stick with NTFS file system. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/Thunar crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.14.7-200.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Deleting files off a 16gig micro-sd card. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.14.7-200.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I was just browsing various forlder unsing Thunar and then I unmounted my usb flash drive. The message was shown right after the (succesful) umount and eject. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.14.8-200.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Is this bug also filed in the upstream bugtracker already?
I think that yes -at least according to Automatic Bug Report Tool. (In reply to hannes from comment #30) > Is this bug also filed in the upstream bugtracker already?
Also, I would like to mention that it happened again. I observed that in both instances, the problem took place just right after a "Umount & Eject" command. If I remember correctly, using Umount only is not a problem -this appears when it is used in conjunction with Eject. Of course, I might be wrong and I hope that the technical report might and will help.
Another user experienced a similar problem: Same as before. Trying to unmount a volume, and it crashed. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: thunar crash_function: magazine_chain_pop_head executable: /usr/bin/thunar kernel: 3.14.8-200.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
(In reply to hannes from comment #30) > Is this bug also filed in the upstream bugtracker already? Not sure. It might be https://bugzilla.xfce.org/show_bug.cgi?id=10341 but it's not clear. I've filed a new one: https://bugzilla.xfce.org/show_bug.cgi?id=10979
Edit ==> Pref ==> Advanced Uncheck "Enable Volume Management" Press okay. Try mounting or unmounting a usb drive.
As requested, I just tried mounting and unmounting a 2BG USB 2.0 memory stick. This stick has its default formatting and is empty. Mounting and unmounting it worked without crashing regardless of whether Volume Management was enabled or disabled - I tried both.
(In reply to Martin Gregorie from comment #36) > As requested, I just tried mounting and unmounting a 2BG USB 2.0 memory > stick. This stick has its default formatting and is empty. Mounting and > unmounting it worked without crashing regardless of whether Volume > Management was enabled or disabled - I tried both. If I may, please, try to do it again by performing more complex procedures, like e.g., copying files to/from that usb, browsing within its folders, etc. and then try to umount and eject it... I tend to believe that the problem is in "eject".
OK, I dragged a set of files in a directory onto the same memory stick that I used last time, dragged them back to mt hard drive, opened files on the memory stick the with Firefox and gedit. No crashes. Mount, file manipulations and unmount tried with Volume Management both enabled asnd disabled. Unmount/eject done from Thunar 1.6.3 by clicking on the triangle+bar symbol on the right of the memory stick's Device symbol. Did pretty much the same (dragged files onto the USB disk, opened a file, deleted it) with a USB hard drive and both Volume Management enabled and disabled. Unmount/eject done the same as for the memory stick. Worked OK - no crashes. Mounted a camera, used Thunar to cut an image from the camers and paste it into my normal user, unmounted camera. Worked OK - no crashes. Tried with Volume Management enabled and disabled. One oddity: I always used to be able to mount/unmount USB devices as a normal user without getting password prompts, but since the last yum upgrade, which I did last Friday, I can't mount or unmount a USB device without getting prompted for the root password. I didn't change anything that could cause this behavior and can't find any obvious way of disabling it from Thunar preferences or from the XFCE4 Settings or Administration menus - in fact Applications Menu|Administration|Users and Groups has stopped working entirely: doesn't even prompt for the root password. Bug raised.
(In reply to Martin Gregorie from comment #38) > OK, I dragged a set of files in a directory onto the same memory stick that > I used last time, dragged them back to mt hard drive, opened files on the > memory stick the with Firefox and gedit. No crashes. Mount, file > manipulations and unmount tried with Volume Management both enabled asnd > disabled. > > Unmount/eject done from Thunar 1.6.3 by clicking on the triangle+bar symbol > on the right of the memory stick's Device symbol. > > Did pretty much the same (dragged files onto the USB disk, opened a file, > deleted it) with a USB hard drive and both Volume Management enabled and > disabled. Unmount/eject done the same as for the memory stick. Worked OK - > no crashes. > > Mounted a camera, used Thunar to cut an image from the camers and paste it > into my normal user, unmounted camera. Worked OK - no crashes. Tried with > Volume Management enabled and disabled. > > One oddity: I always used to be able to mount/unmount USB devices as a > normal user without getting password prompts, but since the last yum > upgrade, which I did last Friday, I can't mount or unmount a USB device > without getting prompted for the root password. I didn't change anything > that could cause this behavior and can't find any obvious way of disabling > it from Thunar preferences or from the XFCE4 Settings or Administration > menus - in fact Applications Menu|Administration|Users and Groups has > stopped working entirely: doesn't even prompt for the root password. Bug > raised. Well that's weird! Many here (including myself) have problems with umount/eject -except you. On the other hand, I did the same upgrade without any problem. It seems that the can of worms has opened!
(In reply to Martin Gregorie from comment #38) > OK, I dragged a set of files in a directory onto the same memory stick that > I used last time, dragged them back to mt hard drive, opened files on the > memory stick the with Firefox and gedit. No crashes. Mount, file > manipulations and unmount tried with Volume Management both enabled asnd > disabled. > > Unmount/eject done from Thunar 1.6.3 by clicking on the triangle+bar symbol > on the right of the memory stick's Device symbol. > > Did pretty much the same (dragged files onto the USB disk, opened a file, > deleted it) with a USB hard drive and both Volume Management enabled and > disabled. Unmount/eject done the same as for the memory stick. Worked OK - > no crashes. > > Mounted a camera, used Thunar to cut an image from the camers and paste it > into my normal user, unmounted camera. Worked OK - no crashes. Tried with > Volume Management enabled and disabled. > > One oddity: I always used to be able to mount/unmount USB devices as a > normal user without getting password prompts, but since the last yum > upgrade, which I did last Friday, I can't mount or unmount a USB device > without getting prompted for the root password. I didn't change anything > that could cause this behavior and can't find any obvious way of disabling > it from Thunar preferences or from the XFCE4 Settings or Administration > menus - in fact Applications Menu|Administration|Users and Groups has > stopped working entirely: doesn't even prompt for the root password. Bug > raised. Was the USB hard drive encrypted? All my disks are encrypted.
No, the USB hard drive is not encrypted. I do have an encrypted partition on /dev/sda but no data on that was used in these tests.
Hi all, apparently it's not a problem in thunar, but one in gtk. Please see the upstream bug report. [1] Is there a way to backport it? Should the component be changed to gtk? Thanks a lot! [1] https://bugzilla.gnome.org/show_bug.cgi?id=723366
Note that this is a gtk2 isssue, not gtk3. Many of the gnome folks are traveling right now, I was going to ask them about backporting this to gtk2 later this week.
(In reply to Kevin Fenzi from comment #43) > Note that this is a gtk2 isssue, not gtk3. > > Many of the gnome folks are traveling right now, I was going to ask them > about backporting this to gtk2 later this week. thanks.
gtk2-2.24.24-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/gtk2-2.24.24-2.fc20
Package gtk2-2.24.24-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gtk2-2.24.24-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-9777/gtk2-2.24.24-2.fc20 then log in and leave karma (feedback).
gtk2-2.24.24-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.