Ubuntu
pommed package

pommed crashed with SIGSEGV

Bug #147887 reported by Gar Bage on 2007-10-01

14

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	pommed (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: pommed

pommed crashed with SIGSEGV

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Oct 1 19:57:19 2007
Disassembly: 0xb7d9bfe6:
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/sbin/pommed
NonfreeKernelModules: nvidia ath_hal
Package: pommed 1.8~dfsg-2
PackageArchitecture: i386
ProcCmdline: /usr/sbin/pommed
ProcCwd: /
ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Signal: 11
SourcePackage: pommed
StacktraceTop:
?? () from /lib/ld-linux.so.2
?? ()
?? ()
?? ()
?? ()
Title: pommed crashed with SIGSEGV
Uname: Linux core2duo 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups:

Tags:

Revision history for this message

Gar Bage (garbage) wrote on 2007-10-01:

#1

CoreDump.gz Edit (65.9 KiB, application/x-gzip)
Dependencies.txt Edit (327 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (3.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (585 bytes, text/plain; charset="utf-8")
Registers.txt Edit (519 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (215 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (242 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2007-10-02: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (219 bytes, text/plain)

StacktraceTop:_start () from /lib/ld-linux.so.2
?? ()
?? ()
?? ()
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2007-10-02: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (246 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2007-10-02: Stack trace with source code

#4

StacktraceSource.txt Edit (220 bytes, text/plain)

Siegfried Gevatter (rainct) on 2007-12-06

Changed in pommed:
importance:	Undecided → Medium

Revision history for this message

Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote on 2008-01-17:

#5

Thank you for your bug report. Have you been able to reproduce this issue ?

Changed in pommed:
status:	New → Incomplete

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-02-18:

#6

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

Changed in pommed:
status:	Incomplete → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.