dolphin crashed with SIGSEGV in QLayout::activateRecursiveHelper()

Bug #336010 reported by Bernhard Nikola
2
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: kdebase

some sessions before i copied mass of files to different HDDs. In the beginning it runs with 50MBit/s, after 20000 file transfers it runs only with 1MBit/s. At the end it stops first. Now i do not open dolphin and it crashed ! --???

ProblemType: Crash
Architecture: i386
DistroRelease: /usr/bin/lsb_release:81: DeprecationWarning: the sets module is deprecated import sets Ubuntu 9.04
ExecutablePath: /usr/bin/dolphin
Package: dolphin 4:4.2.0-0ubuntu3
ProcAttrCurrent: unconfined
ProcCmdline: dolphin
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 LANGUAGE=
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdebase
StacktraceTop:
 QLayout::activateRecursiveHelper ()
 QLayout::activate () from /usr/lib/libQtGui.so.4
 QWidget::setVisible () from /usr/lib/libQtGui.so.4
 KWidgetJobTracker::Private::_k_slotShowProgressWidget ()
 KWidgetJobTracker::qt_metacall ()
Title: dolphin crashed with SIGSEGV in QLayout::activateRecursiveHelper()
Uname: Linux 2.6.28-8-generic i686
UserGroups:

Revision history for this message
Bernhard Nikola (bnikola) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:QLayout::activateRecursiveHelper ()
QLayout::activate () from /usr/lib/libQtGui.so.4
QWidget::setVisible () from /usr/lib/libQtGui.so.4
KWidgetJobTracker::Private::_k_slotShowProgressWidget (
KWidgetJobTracker::qt_metacall (this=0x9ec3a90,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in kdebase:
importance: Undecided → Medium
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Hi,
We were wondering if this is still an issue for you with the final version of Kubuntu 9.04.
Thanks in advance.

Changed in kdebase (Ubuntu):
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdebase (Ubuntu):
status: Incomplete → 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.