thunar crashed with SIGSEGV in thunar_file_is_directory()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
thunar (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Thunar crashed after pressing the "up directory" button many times
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: thunar 1.6.3-1ubuntu5
ProcVersionSign
Uname: Linux 3.16.0-16-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Sep 22 09:25:03 2014
ExecutablePath: /usr/bin/thunar
InstallationDate: Installed on 2014-05-25 (119 days ago)
InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140524)
ProcCmdline: Thunar --sm-client-id 22e6ed30f-
ProcEnviron:
LANGUAGE=en_AU:en
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_AU.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f38455964c2 <thunar_
PC (0x7f38455964c2) ok
source "$0x2" ok
destination "0x20(%rdi)" (0x00000020) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
thunar_
thunar_
?? () from /lib/x86_
?? () from /lib/x86_
g_sequence_
Title: thunar crashed with SIGSEGV in thunar_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot 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 #1147349, 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.