ksplashx assert failure: double free or corruption

Bug #443975 reported by Robert Moerland
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-bin

After upgrading jaunty to karmic alpha 6, after I logon with kdm, the hard disk starts doing something but after a while I get dropped back to kdm again. kdm.log shows that apparently ksplashx crashed due to a double free or corruption. I first blamed the display driver, but after installing xubuntu-desktop, I can post this bug information from the troubled machine without problems (logged in with gdm).

ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** ksplashx: double free or corruption (out): 0x08413ad8 ***
Date: Wed Sep 30 23:18:47 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ksplashx
Package: kdebase-workspace-bin 4:4.3.1-0ubuntu14
ProcCmdline: ksplashx Default
ProcEnviron:
 PATH=(custom, no user)
 SHELL=/bin/sh
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
Signal: 6
SourcePackage: kdebase-workspace
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: ksplashx assert failure: *** glibc detected *** ksplashx: double free or corruption (out): 0x08413ad8 ***
Uname: Linux 2.6.31-11-generic i686
UserGroups:

Revision history for this message
Robert Moerland (veel-mail) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
__libc_message (do_abort=2,
malloc_printerr (action=<value optimized out>,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in kdebase-workspace (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Robert Moerland (veel-mail) wrote :

I've noticed that this bug report is marked as a duplicate, and I'm by no means an expert on the subject, but still I'd like to mention that I did not have this problem with 9.04, what the 'original' bug report is about.

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.