gnome-commander crashed with SIGSEGV in g_type_create_instance()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-commander (Ubuntu) |
Triaged
|
High
|
Unassigned |
Bug Description
gnome commander crashes every time when I directly connect to a remote server
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-commander 1.2.8.14-1build1
ProcVersionSign
Uname: Linux 3.2.0-4-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Date: Mon Dec 12 09:40:55 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: gnome-commander
ProcEnviron:
PATH=(custom, no user)
LANG=sv_SE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x80be8c4: mov 0x1c(%ebx),%edx
PC (0x080be8c4) ok
source "0x1c(%ebx)" (0x0000001c) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-commander
StacktraceTop:
?? ()
g_type_
?? () from /usr/lib/
g_object_newv () from /usr/lib/
g_object_new () from /usr/lib/
Title: gnome-commander crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to precise on 2011-11-23 (18 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
tags: | added: saucy |
Changed in gnome-commander (Ubuntu): | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
Status changed to 'Confirmed' because the bug affects multiple users.