thunar crashed with SIGSEGV and with connection like mtp with the smartphone android

Bug #1294408 reported by federico soffientini
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

after the connection of my smartphone android like mtp with the computer I can't see the files inside the telephone and thunar go in block

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: thunar 1.6.3-1ubuntu4
ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6
Uname: Linux 3.13.0-17-generic i686
ApportVersion: 2.13.3-0ubuntu1
Architecture: i386
CurrentDesktop: XFCE
Date: Tue Mar 18 20:14:26 2014
ExecutablePath: /usr/bin/thunar
ProcCmdline: Thunar --sm-client-id 20b73a651-9889-482b-bb19-a0e961dc8e53 --daemon
ProcEnviron:
 LANGUAGE=it:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6be1a5b: movl $0x0,0x4(%eax)
 PC (0xb6be1a5b) ok
 source "$0x0" ok
 destination "0x4(%eax)" (0x00000004) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: thunar
Stacktrace:
 #0 0xb6be1a5b in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 No symbol table info available.
 Cannot access memory at address 0xbfc391cc
StacktraceTop: ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
federico soffientini (federsax) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0xb6be1a5b in magazine_cache_trim (allocator=0xb6c8ab60 <allocator>, stamp=<error reading variable: Cannot access memory at address 0xbfc3918c>, ix=<error reading variable: Cannot access memory at address 0xbfc39198>) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:653
   [Error: /build/buildd/glib2.0-2.39.91/./glib/gslice.c was not found in source tree]
 #1 magazine_cache_push_magazine (ix=<error reading variable: Cannot access memory at address 0xbfc39198>, ix@entry=<error reading variable: Cannot access memory at address 0xbfc391cc>, magazine_chunks=<optimized out>, count=<error reading variable: Cannot access memory at address 0xbfc391d0>) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:710
   [Error: /build/buildd/glib2.0-2.39.91/./glib/gslice.c was not found in source tree]
StacktraceTop:
 magazine_cache_trim (allocator=0xb6c8ab60 <allocator>, stamp=<error reading variable: Cannot access memory at address 0xbfc3918c>, ix=<error reading variable: Cannot access memory at address 0xbfc39198>) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:653
 magazine_cache_push_magazine (ix=<error reading variable: Cannot access memory at address 0xbfc39198>, ix@entry=<error reading variable: Cannot access memory at address 0xbfc391cc>, magazine_chunks=<optimized out>, count=<error reading variable: Cannot access memory at address 0xbfc391d0>) at /build/buildd/glib2.0-2.39.91/./glib/gslice.c:710

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in thunar (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
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: New → 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.