gnome-system-log crashed with SIGABRT

Bug #805480 reported by dino99
34
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-utils (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Oneiric i386

crashed several times in the same way:
- have gnome-utils-common 3.0.1-0ubuntu3 installed
- gnome-utils is removed (synaptic comment: "It can be safely removed from your system.")

As i've ran Dconf-editor to set logviewer with default entry [] (to clean it), then i've loaded new entries again, using: Files->open:
- select kern.log without trouble
-select syslog without issue
- then select auth.log, and the crash appear
but strangely the "auth.log" entry was added a few minutes later, so i wonder if the crash has happened because of a cron job updating this log.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-system-log 3.0.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.0-2.3-generic-pae 3.0.0-rc4
Uname: Linux 3.0-2-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
CrashCounter: 1
Date: Mon Jul 4 15:08:13 2011
ExecutablePath: /usr/bin/gnome-system-log
ProcCmdline: gnome-system-log
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-utils
Stacktrace:
 #0 0xb77e6424 in ?? ()
 No symbol table info available.
 #1 0x0846d000 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()
Title: gnome-system-log crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio avahi avahi-autoipd boinc cdrom couchdb crontab daemon debian-tor dialout disk fuse haldaemon klog kmem libuuid lpadmin mail messagebus mlocate mysql mythtv netdev ntp operator plugdev polkituser pulse root sambashare saned shadow ssh ssl-cert sudo syslog tty users utmp video voice www-data

Revision history for this message
dino99 (9d9) wrote :
dino99 (9d9)
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 0xb77e6424 in ?? ()
 No symbol table info available.
 #1 0x0846d000 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-utils (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libglapi-mesa-dbg: installed version 7.12.0~git20110701.4482eba9-0ubuntu0sarvatt2, latest version: 7.11~1-0ubuntu2
libdrm-intel1-dbg: installed version 2.4.26+git20110604.6dd804c5-0ubuntu0sarvatt, latest version: 2.4.25-2ubuntu2
libdrm-nouveau1a-dbg: installed version 2.4.26+git20110604.6dd804c5-0ubuntu0sarvatt, latest version: 2.4.25-2ubuntu2
libgbm1: installed version 7.12.0~git20110701.4482eba9-0ubuntu0sarvatt2, latest version: 7.11~1-0ubuntu2
libgl1-mesa-glx: installed version 7.12.0~git20110701.4482eba9-0ubuntu0sarvatt2, latest version: 7.11~1-0ubuntu2
libdrm2-dbg: installed version 2.4.26+git20110604.6dd804c5-0ubuntu0sarvatt, latest version: 2.4.25-2ubuntu2
libdrm-intel1: installed version 2.4.26+git20110604.6dd804c5-0ubuntu0sarvatt, latest version: 2.4.25-2ubuntu2
libegl1-mesa: installed version 7.12.0~git20110701.4482eba9-0ubuntu0sarvatt2, latest version: 7.11~1-0ubuntu2
libglapi-mesa: installed version 7.12.0~git20110701.4482eba9-0ubuntu0sarvatt2, latest version: 7.11~1-0ubuntu2
libegl1-mesa-dbg: installed version 7.12.0~git20110701.4482eba9-0ubuntu0sarvatt2, latest version: 7.11~1-0ubuntu2
libgl1-mesa-glx-dbg: installed version 7.12.0~git20110701.4482eba9-0ubuntu0sarvatt2, latest version: 7.11~1-0ubuntu2
libdrm-nouveau1a: installed version 2.4.26+git20110604.6dd804c5-0ubuntu0sarvatt, latest version: 2.4.25-2ubuntu2
libc6-dbg: installed version 2.13-8ubuntu2, latest version: 2.13-8ubuntu3
libgbm1-dbg: installed version 7.12.0~git20110701.4482eba9-0ubuntu0sarvatt2, latest version: 7.11~1-0ubuntu2
libdrm-radeon1-dbg: installed version 2.4.26+git20110604.6dd804c5-0ubuntu0sarvatt, latest version: 2.4.25-2ubuntu2
libdrm-radeon1: installed version 2.4.26+git20110604.6dd804c5-0ubuntu0sarvatt, latest version: 2.4.25-2ubuntu2
libdrm2: installed version 2.4.26+git20110604.6dd804c5-0ubuntu0sarvatt, latest version: 2.4.25-2ubuntu2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
Revision history for this message
Benjamin Kerensa (bkerensa) wrote :

Linked multiple duplicates of this bug and I also encountered in on Precise. Essentially the logviewer will crash if you try to open multiple logs or even happen to open certain ones.

Changed in gnome-utils (Ubuntu):
status: Invalid → Confirmed
dino99 (9d9)
Changed in gnome-utils (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
bojojo@orange.fr (bojojo-orange) wrote :

"[Bug 805480] Re: gnome-system-log crashed with SIGABRT"
dino99 doc

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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