Hide Forgot
libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon comment: I clicked on a mounted file system in my bookmark list, then crashed crash_function: fast_validate executable: /usr/bin/Thunar kernel: 3.1.5-1.fc16.x86_64 pid: 1820 pwd: / reason: Process /usr/bin/Thunar was killed by signal 11 (SIGSEGV) time: Wed 14 Dec 2011 01:52:53 AM IRST uid: 1000 username: mazimi backtrace: Text file, 27481 bytes dso_list: Text file, 6873 bytes maps: Text file, 34070 bytes smolt_data: Text file, 2740 bytes environ: :SHELL=/bin/bash :DBUS_STARTER_ADDRESS=unix:abstract=/tmp/dbus-CBqDgZ98yC,guid=9ab1440912b104c47f52218700000023 :XDG_SESSION_COOKIE=06f7562994e6019dcbb7467600000010-1323802602.279553-1293624821 :XDG_RUNTIME_DIR=/run/user/mazimi :DISPLAY=:0 :DESKTOP_SESSION=xfce :WINDOWPATH=1 :PATH=/usr/local/bin:/usr/bin:/bin :GDMSESSION=xfce :XDG_VTNR=1 :USERNAME=mazimi :XDG_SESSION_ID=2 :DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-CBqDgZ98yC,guid=9ab1440912b104c47f52218700000023 :XDG_SEAT=seat0 :XAUTHORITY=/var/run/gdm/auth-for-mazimi-kyXA4K/database :USER=mazimi :DBUS_STARTER_BUS_TYPE=session :GNOME_KEYRING_PID=1196 :SHLVL=1 :PWD=/home/mazimi :GNOME_KEYRING_CONTROL=/tmp/keyring-Qhl5gl :LANG=en_US.UTF-8 :_=/usr/bin/dbus-launch :LOGNAME=mazimi :HOME=/home/mazimi event_log: :2011-12-14-01:53:53> Querying server settings :2011-12-14-01:53:55 Preparing an archive to upload :2011-12-14-01:53:58 Uploading 859956 bytes :2011-12-14-01:54:08 Uploading 83% :2011-12-14-01:54:09 Upload successful :2011-12-14-01:54:14 Retrace job started :2011-12-14-01:54:25 Analyzing crash data :2011-12-14-01:54:37 Analyzing crash data :2011-12-14-01:54:48 Analyzing crash data :2011-12-14-01:55:00 Analyzing crash data :2011-12-14-01:55:13 Initializing virtual root :2011-12-14-01:55:25 Initializing virtual root :2011-12-14-01:55:40 Initializing virtual root :2011-12-14-01:55:52 Initializing virtual root :2011-12-14-01:56:04 Initializing virtual root :2011-12-14-01:56:17 Initializing virtual root :2011-12-14-01:56:30 Initializing virtual root :2011-12-14-01:56:41 Initializing virtual root :2011-12-14-01:56:52 Initializing virtual root :2011-12-14-01:57:04 Initializing virtual root :2011-12-14-01:57:17 Initializing virtual root :2011-12-14-01:57:29 Initializing virtual root :2011-12-14-01:57:41 Initializing virtual root :2011-12-14-01:57:54 Initializing virtual root :2011-12-14-01:58:10 Initializing virtual root :2011-12-14-01:58:40 Initializing virtual root :2011-12-14-01:58:51 Initializing virtual root :2011-12-14-01:59:05 Initializing virtual root :2011-12-14-01:59:17 Initializing virtual root :2011-12-14-01:59:29 Initializing virtual root :2011-12-14-01:59:41 Initializing virtual root :2011-12-14-01:59:53 Initializing virtual root :2011-12-14-02:00:05 Initializing virtual root :2011-12-14-02:00:17 Initializing virtual root :2011-12-14-02:00:29 Initializing virtual root :2011-12-14-02:00:42 Initializing virtual root :2011-12-14-02:00:55 Initializing virtual root :2011-12-14-02:01:07 Cleaning up virtual root :2011-12-14-02:01:20 Retrace job finished successfully :2011-12-14-02:02:43> Smolt profile successfully saved var_log_messages: :Dec 14 01:52:53 localhost kernel: [12407.121573] Thunar[1820]: segfault at 0 ip 0000003978073cf8 sp 00007fff2c7b1180 error 4 in libglib-2.0.so.0.3000.1[3978000000+11e000] :Dec 14 01:52:54 localhost abrt[6774]: Saved core dump of pid 1820 (/usr/bin/Thunar) to /var/spool/abrt/ccpp-2011-12-14-01:52:53-1820 (32006144 bytes)
Created attachment 546425 [details] File: dso_list
Created attachment 546426 [details] File: smolt_data
Created attachment 546427 [details] File: maps
Created attachment 546428 [details] File: backtrace
Does this happen every time you click on that filesystem? What kind of mount is it?
(In reply to comment #5) > Does this happen every time you click on that filesystem? What kind of mount is > it? No This is the first time. This is NTFS mount.
Plugging in USB drive, mounting it. backtrace_rating: 4 Package: Thunar-1.3.0-4.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 555218 [details] File: backtrace
tried to mount a partition in thunar. Then it crashed suddenly. backtrace_rating: 4 Package: Thunar-1.3.0-6.fc17 OS Release: Fedora release 17 (Beefy Miracle)
Created attachment 565741 [details] File: backtrace
mounting in graphical frontend an ISO image backtrace_rating: 4 Package: Thunar-1.3.0-4.fc16 OS Release: Fedora release 16 (Verne)
Created attachment 577264 [details] File: backtrace
Copied 3 files to USB device Eject device from Thunar Told to wait 3 - 4 seconds later, Thunar crashed backtrace_rating: 4 Package: Thunar-1.3.0-6.fc17 OS Release: Fedora release 17 (Beefy Miracle)
open thunar backtrace_rating: 4 Package: Thunar-1.4.0-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.