Thunar crashed with SIGSEGV in thunarx_menu_provider_get_file_actions()

Bug #951344 reported by mrDoctorWho
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
thunar (Ubuntu)
New
Undecided
Unassigned

Bug Description

What i do:
1) By another program make dir "some_dir", make dir "some_dir2" in "some_dir" and make dir "some_dir3" in "some_dir2".
2) Then i removed it by Thunar
3) Then reperat item #1.
*** Thunar think that it's file, but it's a dir.
4) then i open context menu and Thunar crash
Sorry for my English.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: thunar 1.2.3-3ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Sat Mar 10 13:17:15 2012
ExecutablePath: /usr/bin/Thunar
InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Beta i386 (20120228)
ProcCmdline: Thunar --daemon
ProcEnviron:
 LANGUAGE=ru:en
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb252bafd: repz cmpsb %es:(%edi),%ds:(%esi)
 PC (0xb252bafd) ok
 source "%es:(%edi)" (0xb252f56e) ok
 destination "%ds:(%esi)" (0x0000007b) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/thunarx-2/thunar-uca.so
 ?? () from /usr/lib/i386-linux-gnu/thunarx-2/thunar-uca.so
 thunarx_menu_provider_get_file_actions () from /usr/lib/i386-linux-gnu/libthunarx-2.so.0
 ?? ()
 ?? ()
Title: Thunar crashed with SIGSEGV in thunarx_menu_provider_get_file_actions()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
mrDoctorWho (mrdoctorwho) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #852410, 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.

tags: removed: need-i386-retrace
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.