gnome-system-log crashed with SIGABRT in raise()

Bug #937419 reported by bcbc
0
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-utils (Ubuntu)
New
Undecided
Unassigned

Bug Description

Opened up kern.log.1 in Log file viewer. Then opened up kern.log. Crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-system-log 3.2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
CheckboxSubmission: dd7f729683fa7fd3f2e256ba311e86cb
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Mon Feb 20 20:48:10 2012
ExecutablePath: /usr/bin/gnome-system-log
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20111006)
ProcCmdline: gnome-system-log
Signal: 6
SourcePackage: gnome-utils
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? ()
Title: gnome-system-log crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
bcbc (bcbc) wrote :
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 #818516, 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.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-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.