Bug 904829 - [abrt] Thunar-1.6.2-1.fc18: __pthread_mutex_lock: Process /usr/bin/thunar was killed by signal 11 (SIGSEGV)
Summary: [abrt] Thunar-1.6.2-1.fc18: __pthread_mutex_lock: Process /usr/bin/thunar was...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: Thunar
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1f551b24e68e32af3fcff80af3c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-27 19:12 UTC by Vincent
Modified: 2015-06-29 11:45 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 11:45:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (19.26 KB, text/plain)
2013-01-27 19:12 UTC, Vincent
no flags Details
File: cgroup (130 bytes, text/plain)
2013-01-27 19:12 UTC, Vincent
no flags Details
File: core_backtrace (1.58 KB, text/plain)
2013-01-27 19:12 UTC, Vincent
no flags Details
File: dso_list (9.91 KB, text/plain)
2013-01-27 19:12 UTC, Vincent
no flags Details
File: environ (1.59 KB, text/plain)
2013-01-27 19:12 UTC, Vincent
no flags Details
File: limits (1.29 KB, text/plain)
2013-01-27 19:12 UTC, Vincent
no flags Details
File: maps (46.48 KB, text/plain)
2013-01-27 19:12 UTC, Vincent
no flags Details
File: open_fds (1.09 KB, text/plain)
2013-01-27 19:12 UTC, Vincent
no flags Details
File: proc_pid_status (913 bytes, text/plain)
2013-01-27 19:12 UTC, Vincent
no flags Details
File: var_log_messages (300 bytes, text/plain)
2013-01-27 19:12 UTC, Vincent
no flags Details

Description Vincent 2013-01-27 19:12:31 UTC
Description of problem:
Just wanted to launch thunar with xfce4-places applet and got this crash.

Version-Release number of selected component:
Thunar-1.6.2-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/Thunar /home/vincent/Documents/informatique/Linux
crash_function: __pthread_mutex_lock
executable:     /usr/bin/thunar
kernel:         3.7.4-204.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 __pthread_mutex_lock at pthread_mutex_lock.c:50
 #1 g_mutex_lock at gthread-posix.c:210
 #2 thunar_thumbnailer_queue_async_reply at thunar-thumbnailer.c:617
 #3 thunar_thumbnailer_proxy_queue_async_callback at ../thunar/thunar-thumbnailer-proxy.h:44
 #4 complete_pending_call_and_unlock at dbus-connection.c:2314
 #11 gtk_main at gtkmain.c:1257

Comment 1 Vincent 2013-01-27 19:12:36 UTC
Created attachment 688569 [details]
File: backtrace

Comment 2 Vincent 2013-01-27 19:12:39 UTC
Created attachment 688570 [details]
File: cgroup

Comment 3 Vincent 2013-01-27 19:12:41 UTC
Created attachment 688571 [details]
File: core_backtrace

Comment 4 Vincent 2013-01-27 19:12:43 UTC
Created attachment 688572 [details]
File: dso_list

Comment 5 Vincent 2013-01-27 19:12:45 UTC
Created attachment 688573 [details]
File: environ

Comment 6 Vincent 2013-01-27 19:12:47 UTC
Created attachment 688574 [details]
File: limits

Comment 7 Vincent 2013-01-27 19:12:49 UTC
Created attachment 688575 [details]
File: maps

Comment 8 Vincent 2013-01-27 19:12:51 UTC
Created attachment 688576 [details]
File: open_fds

Comment 9 Vincent 2013-01-27 19:12:53 UTC
Created attachment 688577 [details]
File: proc_pid_status

Comment 10 Vincent 2013-01-27 19:12:55 UTC
Created attachment 688578 [details]
File: var_log_messages

Comment 11 Kevin Fenzi 2013-01-27 23:22:09 UTC
Does this happen everytime? 

Or it was a one time thing?

Comment 12 Vincent 2013-01-28 07:20:45 UTC
the crash happens sometimes, it can be at the first launch of Thunar in the session or later.
I will try launching Thunar with it's shortcut (or better with a terminal) than with the places applet.

Comment 13 markqbrunet 2013-03-19 20:11:43 UTC
trying to open a document (.doc) in libreoffice from nautilus (double click) - running yum upgrade at same time (libre office not in update list) - also thunderbird open.
probably trying to do too much at the same time...


backtrace_rating: 4
Package: Thunar-1.6.2-1.fc18
Architecture: i686
OS Release: Fedora release 18 (Spherical Cow)

Comment 14 Peter H. Jones 2013-09-30 22:07:08 UTC
Opening a folder on the desktop and sorting in chronological order

reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /bin/Thunar file:///home/jones/Desktop/tj
crash_function: __pthread_mutex_lock
executable:     /usr/bin/thunar
kernel:         3.10.12-100.fc18.x86_64
package:        Thunar-1.6.3-1.fc18
reason:         Process /usr/bin/thunar was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            3000

Comment 15 Fedora End Of Life 2013-12-21 15:19:55 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 16 Fedora End Of Life 2014-02-05 22:59:49 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 17 Miro Hrončok 2014-05-09 21:55:26 UTC
Happened again. No idea what was the trigger.

Comment 18 Fedora End Of Life 2015-05-29 08:52:27 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

Comment 19 Fedora End Of Life 2015-06-29 11:45:08 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.