kdeinit4 crashed with SIGSEGV in QWidget::event()

Bug #427348 reported by Laurent Claessens
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kde4libs (Ubuntu)
New
Undecided
Unassigned

Bug Description

This crash happened when I was trying to split the windows of Konqueror in two parts (ctrl-shift-L).
Konqueror always crashes in that circumstance.

ProblemType: Crash
Architecture: i386
Date: Thu Sep 10 15:29:52 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/kdeinit4
Package: kdelibs-bin 4:4.3.1-0ubuntu2
ProcCmdline: kdeinit4:\ konqueror\ [kdeinit]\ --profile\ filemanagement
ProcCwd: /home/moky
ProcEnviron:
 PATH=(custom, user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.30-generic
SegvAnalysis:
 Segfault happened at: 0x752e0db: mov (%eax),%edx
 PC (0x0752e0db) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: kde4libs
StacktraceTop:
 ?? () from /usr/lib/libdolphinprivate.so.4
 ?? () from /usr/lib/libdolphinprivate.so.4
 QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
 QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4
 QAbstractScrollArea::viewportEvent(QEvent*) ()
Title: kdeinit4 crashed with SIGSEGV in QWidget::event()
Uname: Linux 2.6.31-10-generic i686
UserGroups:

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #424513, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-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.