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

Bug #838783 reported by El Pensador
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gnome-utils (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

The system log viewer crashes after the opening of three log files from File menu > Open

How to reproduce the bug:
1) Remove all the open logs from the side panel
2) Open two logs successively from File menu > Open...
3) Try to open a third log and the log viewer crashes

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-system-log 3.1.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
Uname: Linux 3.0.0-9-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Thu Sep 1 13:59:22 2011
ExecutablePath: /usr/bin/gnome-system-log
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110817)
ProcCmdline: gnome-system-log
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-utils
StacktraceTop:
 __kernel_vsyscall ()
 ?? ()
 ?? ()
Title: gnome-system-log crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: Upgraded to oneiric on 2011-08-25 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
El Pensador (el-pensador) wrote :
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-utils (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version has expired long time ago, and is no more supported

Changed in gnome-utils (Ubuntu):
status: Confirmed → Invalid
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.