ksplashx crashed with SIGABRT in raise()

Bug #796816 reported by sam tygier
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase-workspace (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: kdebase-workspace

on the kubuntu live cd in testdrive/qemu-kvm

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: kdebase-workspace-bin 4:4.6.3-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
Uname: Linux 2.6.39-3-generic x86_64
Architecture: amd64
Date: Mon Jun 13 20:23:41 2011
ExecutablePath: /usr/bin/ksplashx
LiveMediaBuild: Kubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110610)
ProcCmdline: ksplashx Default --pid
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: kdebase-workspace
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
 free () from /lib/x86_64-linux-gnu/libc.so.6
Title: ksplashx 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
sam tygier (samtygier) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=2, fmt=0x7f5d55dc5678 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 malloc_printerr (av=<value optimized out>, p=0x1fa2280) at malloc.c:6283
 _int_free (av=<value optimized out>, p=0x1fa2280) at malloc.c:4795

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in kdebase-workspace (Ubuntu):
importance: Undecided → Medium
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.