maximus crashed with SIGSEGV

Bug #408486 reported by Matt Zimmerman
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maximus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: maximus

Fresh install of UNR Karmic 20090802. I opened a URL from gnome-terminal, which caused firefox to open. I didn't want it, because I had firefox-3.5 open already, so I closed it. I noticed the crash report soon after that.

ProblemType: Crash
Architecture: i386
Date: Mon Aug 3 17:50:25 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/maximus
NonfreeKernelModules: wl
Package: maximus 0.4.8-0ubuntu3
ProcCmdline: maximus
ProcCwd: /home/mdz
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-4.23-generic
SegvAnalysis:
 Segfault happened at: 0x804c01b <g_slist_free@plt+6359>: orl $0x2,(%esi)
 PC (0x0804c01b) ok
 source "$0x2" ok
 destination "(%esi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: maximus
Stacktrace:
 #0 0x0804c01b in ?? ()
 #1 0x094c4440 in ?? ()
 #2 0x040000c9 in ?? ()
 #3 0x0000014a in ?? ()
 #4 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Tags: ubuntu-unr
Title: maximus crashed with SIGSEGV
Uname: Linux 2.6.31-4-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

visibility: private → public
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.