dolphin crashed with SIGSEGV in KTimeZone::~KTimeZone()

Bug #447580 reported by positron
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

?

ProblemType: Crash
Architecture: i386
Date: Fri Oct 9 23:12:28 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/dolphin
NonfreeKernelModules: nvidia
Package: dolphin 4:4.3.2-0ubuntu1
ProcCmdline: /usr/bin/dolphin -icon system-file-manager -caption Dolphin /home/username
ProcEnviron:
 LANGUAGE=es_ES:es:en_GB:en
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x7936e4c <_ZN9KTimeZoneD1Ev+44>: call *0x4(%edx)
 PC (0x07936e4c) ok
 source "*0x4(%edx)" ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: kdebase
StacktraceTop:
 KTimeZone::~KTimeZone() () from /usr/lib/libkdecore.so.5
 KDateTime::~KDateTime() () from /usr/lib/libkdecore.so.5
 KFileItem::~KFileItem() () from /usr/lib/libkio.so.5
 _start ()
Title: dolphin crashed with SIGSEGV in KTimeZone::~KTimeZone()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev root sambashare

Revision history for this message
positron (serlucli) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:~KTimeZone (this=0x991582c)
~KDateTime (this=0x2)
~KFileItem (this=0x9a218f8)
QList<KFileItem>::free (this=0x919cecc, data=0x94e96d0)
InformationPanel::setSelection (this=0x919ce80,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
affects: ubuntu → kdebase (Ubuntu)
Changed in kdebase (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Is this crash reproducible?

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 requested 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.