ksysguardd crashed with SIGABRT in __libc_message()

Bug #937359 reported by George on 2012-02-21
This bug affects 5 people
Affects Status Importance Assigned to Milestone
kde-workspace (Ubuntu)

Bug Description

Occurred while I was away.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: ksysguardd 4:4.8.0b-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Tue Feb 21 10:57:25 2012
ExecutablePath: /usr/bin/ksysguardd
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: ksysguardd
 PATH=(custom, no user)
Signal: 6
SourcePackage: kde-workspace
 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
 __fortify_fail () from /lib/x86_64-linux-gnu/libc.so.6
 __chk_fail () from /lib/x86_64-linux-gnu/libc.so.6
Title: ksysguardd crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-02-15 (5 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

George (gtaskeraus) wrote :
visibility: private → public

 __libc_message (do_abort=2, fmt=0x7f9b293e073c "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
 __GI___fortify_fail (msg=0x7f9b293e06d3 "buffer overflow detected") at fortify_fail.c:32
 __GI___chk_fail () at chk_fail.c:29
 _IO_str_chk_overflow (fp=<optimized out>, c=<optimized out>) at vsprintf_chk.c:35
 _IO_default_xsputn (f=0x7fffd7a9bb50, data=<optimized out>, n=15) at genops.c:485

Changed in kde-workspace (Ubuntu):
importance: Undecided → Medium
summary: - ksysguardd crashed with SIGABRT in raise()
+ ksysguardd crashed with SIGABRT in __libc_message()
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in kde-workspace (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers