gnome-commander crashed with SIGSEGV in g_type_check_instance_cast()

Bug #946728 reported by Paul White
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNOME Commander
Expired
Medium
gnome-commander (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I was trying to copy a file to a shared Windows drive.

As the share was read only the copy failed and Gnome Commander crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-commander 1.2.8.15-2
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Sun Mar 4 23:44:49 2012
ExecutablePath: /usr/bin/gnome-commander
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120223.1)
ProcCmdline: gnome-commander
SegvAnalysis:
 Segfault happened at: 0xb70cc9fe <g_type_check_instance_cast+46>: mov (%edx),%eax
 PC (0xb70cc9fe) ok
 source "(%edx)" (0x00000021) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-commander
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: gnome-commander crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Paul White (paulw2u) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_cast (type_instance=0x21, iface_type=138013720) at /build/buildd/glib2.0-2.31.18/./gobject/gtype.c:3993
 get_parent_dir (f=0x8658b20) at gnome-cmd-file.cc:72
 gnome_cmd_file_get_uri (f=0x8658b20, name=0x0) at gnome-cmd-file.cc:460
 gnome_cmd_file_get_uri_str (f=0x8658b20, hide_options=GNOME_VFS_URI_HIDE_NONE) at gnome-cmd-file.cc:468
 gnome_cmd_dir_start_monitoring (dir=0x8658b20) at gnome-cmd-dir.cc:819

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 gnome-commander (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Paul White (paulw2u)
visibility: private → public
Changed in gnome-commander:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gnome-commander (Ubuntu):
status: New → Confirmed
Changed in gnome-commander:
importance: Critical → Medium
Changed in gnome-commander:
status: New → Expired
Revision history for this message
Paul White (paulw2u) wrote :

Marking my own bug as "Incomplete" as both Ubuntu and gnome-commander versions are obsolete and I can no longer test with a shared Windows drive. Anyone affected by this bug should create a new report of their own using currently supported version of Ubuntu and gnome-commander so that their logs are submitted for analysis.

Changed in gnome-commander (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Paul White (paulw2u) wrote :

Report did not expire due bug watch
See also comment #6
Marking "Invalid" to close

Changed in gnome-commander (Ubuntu):
status: Incomplete → 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.