thunar crashed with SIGSEGV in __GI___pthread_mutex_lock()

Bug #1215294 reported by INIZAN yannick
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

thunar freeze after directory deleting

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: thunar 1.6.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-3.7-generic 3.11.0-rc6
Uname: Linux 3.11.0-3-generic x86_64
ApportVersion: 2.12.1-0ubuntu2
Architecture: amd64
Date: Thu Aug 22 08:45:30 2013
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2013-08-20 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130723.2)
MarkForUpload: True
ProcCmdline: Thunar --sm-client-id 2b494cf2e-63a1-42a5-920d-d7f972a9fc3b --daemon
ProcEnviron:
 LANGUAGE=fr_FR
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fab057ecf74 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7fab057ecf74) ok
 source "0x10(%rdi)" (0x0000000f) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
Stacktrace:
 #0 __GI___pthread_mutex_lock (mutex=0x0, mutex@entry=<error reading variable: Cannot access memory at address 0x7fff6348a0b8>) at pthread_mutex_lock.c:50
         __PRETTY_FUNCTION__ = "__pthread_mutex_lock"
         type = 4294967295
 Cannot access memory at address 0x7fff6348a0b8
StacktraceTop: __GI___pthread_mutex_lock (mutex=0x0, mutex@entry=<error reading variable: Cannot access memory at address 0x7fff6348a0b8>) at pthread_mutex_lock.c:50
Title: thunar crashed with SIGSEGV in __GI___pthread_mutex_lock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip fax floppy fuse lpadmin nopasswdlogin plugdev sambashare sudo tape video

Revision history for this message
INIZAN yannick (inizan-yannick) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 __GI___pthread_mutex_lock (mutex=0x0, mutex@entry=<error reading variable: Cannot access memory at address 0x7fff6348a0b8>) at pthread_mutex_lock.c:50
         __PRETTY_FUNCTION__ = "__pthread_mutex_lock"
         type = 4294967295
 Cannot access memory at address 0x7fff6348a0b8
StacktraceSource:
 #0 __GI___pthread_mutex_lock (mutex=0x0, mutex@entry=<error reading variable: Cannot access memory at address 0x7fff6348a0b8>) at pthread_mutex_lock.c:50
   [Error: pthread_mutex_lock.c was not found in source tree]
StacktraceTop: __GI___pthread_mutex_lock (mutex=0x0, mutex@entry=<error reading variable: Cannot access memory at address 0x7fff6348a0b8>) at pthread_mutex_lock.c:50

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in thunar (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in thunar (Ubuntu):
status: New → Confirmed
Revision history for this message
Sean Davis (bluesabre) wrote :

Seems likely to be a one-off crash. Closing this issue out.

Changed in thunar (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.