keditbookmarks crashed with SIGSEGV

Bug #355592 reported by Shura
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: kdebase

I was trying to manage my bookmarks (moving a folder to another place).

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/keditbookmarks
NonfreeKernelModules: nvidia
Package: konqueror 4:4.2.2-0ubuntu1
ProcCmdline: /usr/bin/keditbookmarks --customcaption konqueror --dbusObjectName konqueror /home/username/.kde/share/apps/konqueror/bookmarks.xml
ProcEnviron:
 LANGUAGE=fr_FR:fr:en_GB:en
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: kdebase
StacktraceTop:
 ?? () from /usr/lib/libQtXml.so.4
 ?? () from /usr/lib/libQtXml.so.4
 ?? () from /usr/lib/libQtXml.so.4
 ?? () from /usr/lib/libQtXml.so.4
 ?? () from /usr/lib/libQtXml.so.4
Title: keditbookmarks crashed with SIGSEGV
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

StacktraceTop:QDomElementPrivate::save (this=0x8aa1e00, s=@0xbfbb9390,
QDomNodePrivate::save (this=0x8aa1da8, s=@0xbfbb9390,
QDomElementPrivate::save (this=0x8aa1da8, s=@0xbfbb9390,
QDomNodePrivate::save (this=0x8a08d18, s=@0xbfbb9390,
QDomElementPrivate::save (this=0x8a08d18, s=@0xbfbb9390,

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

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugs.kde.org/show_bug.cgi?id=190625

visibility: private → public
Changed in kdebase (Ubuntu):
importance: Medium → Low
status: New → Triaged
Revision history for this message
Stilor (stilor) wrote :

This is probably a duplicate of bug #353806. They have different bugs in KDE database; they should be declared as duplicates too.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

The backtrace would indicate that these are separate crashes. this is however a duplicate of bug 280727, which should be fixed in KDE 4.3.2.

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.