thunar crashed with SIGSEGV in g_slice_free1()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thunar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I'm not sure if this is a duplicate of this bug: https:/
- What I just encountered was "Thunar crashed with SIGSEGV in g_slice_free1()"
- The bug in the link above is " Thunar crashed with SIGSEGV in g_slice_alloc()"
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: thunar 1.6.3-1ubuntu1
ProcVersionSign
Uname: Linux 3.11.0-2-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
Date: Mon Aug 19 20:28:37 2013
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2013-08-18 (1 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130818)
MarkForUpload: True
ProcCmdline: Thunar --daemon
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7fabb285112f: mov 0x8(%rax),%rcx
PC (0x7fabb285112f) ok
source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
?? () from /lib/x86_
?? () from /lib/x86_
g_slice_free1 () from /lib/x86_
g_type_
?? () from /usr/lib/
Title: thunar crashed with SIGSEGV in g_slice_free1()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1203296, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.