ark crashed with SIGSEGV in QSplitter::sizes()

Bug #456959 reported by hal2100 on 2009-10-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KDE Utilities
kdeutils (Ubuntu)

Bug Description

Binary package hint: kdeutils

I don't know what was happening

ProblemType: Crash
Architecture: i386
Date: Wed Oct 21 07:08:58 2009
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/ark
NonfreeKernelModules: nvidia
Package: ark 4:4.3.2-0ubuntu1
ProcCmdline: /usr/bin/ark -caption Ark /media/MAIN/1_Tools/Rainlendar/backups/Rainlendar2\ backup\
ProcVersionSignature: Ubuntu 2.6.31-12.41-386
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: kdeutils
 ?? ()
 QSplitter::sizes() const () from /usr/lib/
 CalendarView::writeSettings() ()
 ActionManager::writeSettings() ()
 ?? () from /usr/lib/kde4/
Title: ark crashed with SIGSEGV in QSplitter::sizes()
Uname: Linux 2.6.31-12-386 i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
 (xfce4-mixer-plugin:1951): libxfce4mixer-CRITICAL **: xfce_mixer_get_track: assertion `GST_IS_MIXER (card)' failed
 (polkit-gnome-authentication-agent-1:1973): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

hal2100 (hal-from-2001) wrote :

StacktraceTop:?? ()
QSplitter::sizes (this=0x9a1bbf8)
CalendarView::writeSettings (this=0x9738348)
ActionManager::writeSettings (this=0x9a996a8)
~KOrganizerPart (this=0x9737208)

Changed in kdeutils (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Download full text (4.9 KiB)

Application that crashed: ark
Version of the application: 2.13
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: Ark (ark), signal: Segmentation fault
[KCrash Handler]
#6 0x00000001 in ?? ()
#7 0x0149a112 in QSplitter::sizes (this=0x88c9810) at widgets/qsplitter.cpp:1606
#8 0x01c3eab8 in CalendarView::writeSettings() () from /usr/lib/
#9 0x01cbf7ee in ActionManager::writeSettings() () from /usr/lib/
#10 0x0817cedf in ?? () from /usr/lib/kde4/
#11 0x005e2e2e in KParts::Part::slotWidgetDestroyed (this=0x88ca500) at ../../kparts/part.cpp:354
#12 0x005e2f4b in KParts::Part::qt_metacall (this=0x88ca500, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfe143c8) at ./part.moc:76
#13 0x005e2fba in KParts::ReadOnlyPart::qt_metacall (this=0x88ca500, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfe143c8) at ./part.moc:154
#14 0x0817d40a in ?? () from /usr/lib/kde4/
#15 0x004ad263 in QMetaObject::activate (sender=0x88ca0c8, from_signal_index=0, to_signal_index=1, argv=0xbfe143c8) at kernel/qobject.cpp:3113
#16 0x004ad6d8 in QMetaObject::activate (sender=0x88ca0c8, m=0x5841a8, from_local_signal_index=0, to_local_signal_index=1, argv=0xbfe143c8) at kernel/qobject.cpp:3207
#17 0x004ad76b in QObject::destroyed (this=0x88ca0c8, _t1=0x88ca0c8) at .moc/release-shared/moc_qobject.cpp:143
#18 0x004ae536 in ~QObject (this=0x88ca0c8, __in_chrg=<value optimized out>) at kernel/qobject.cpp:757
#19 0x0107debf in ~QWidget (this=0x88ca0c8, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1380
#20 0x004a646f in QObjectPrivate::deleteChildren (this=0x88bb0e0) at kernel/qobject.cpp:1847
#21 0x0107d85b in ~QWidget (this=0x8884828, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1367
#22 0x01431961 in ~QFrame (this=0x8884828, __in_chrg=<value optimized out>) at widgets/qframe.cpp:243
#23 0x00916301 in ~KHBox (this=0x8884828, __in_chrg=<value optimized out>) at ../../kdeui/widgets/khbox.cpp:51
#24 0x0096e795 in ~KVBox (this=0x8884828, __in_chrg=<value optimized out>) at ../../kdeui/widgets/kvbox.cpp:29
#25 0x004a646f in QObjectPrivate::deleteChildren (this=0x88bd4b8) at kernel/qobject.cpp:1847
#26 0x0107d85b in ~QWidget (this=0xbfe146c8, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1367
#27 0x01519184 in ~QDialog (this=0xbfe146c8, __in_chrg=<value optimized out>) at dialogs/qdialog.cpp:298
#28 0x007ae4c4 in ~KDialog (this=0xbfe146c8, __in_chrg=<value optimized out>) at ../../kdeui/dialogs/kdialog.cpp:197
#29 0x0650bc4e in ?? () from /usr/lib/kde4/
#30 0x0650cbb4 in ?? () from /usr/lib/kde4/
#31 0x065056bb in ?? () from /usr/lib/kde4/
#32 0x064fe28b in ?? () from /usr/lib/kde4/
#33 0x004a5f0b in QMetaCallEvent::placeMetaCall (this=0x85856a8, object=0x8343f30) at kernel/qobject.cpp:477
#34 0x004a75fe in QObject::event (this=0x8343f30, e=0x85856a8) at kernel/qobject.cpp:1111
#35 0x0102cf54 in QApplicationPrivate::notify_helper (this=0x829d8f8, receiver=0x8343f30, e=0x85856a8) at kernel/qapplication.cpp:4056
#36 0x0103467...


More information is needed. Please install the debug packages for Ark (or kdeutils), and tell us what you were doing and what you were previewing when this crash happened.

I can successfully reproduced the crash as describe below:

1) in Firefox export Google Agenda
2) save as <email address hidden> file
3) in Dolphin click to open the zip archive
3) in Ark click on bigey@<email address hidden> VCS/ICS calendar file to open it
4) KOrganizer open the file (it seems to be KOrganizer but not sure?)
5) click the Close button
6) then Ark crashes


Download full text (8.3 KiB)

Reassigning to KOrganizer, as it looks like it's its fault.

More details: this crash happens when KOrganizer's view is set to 'To-do' list, so the calendar view is disabled.

More detailed backtrace:

Application: Ark (ark), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5217960 (LWP 8031))]

Thread 2 (Thread 0xb2ee4b70 (LWP 8033)):
#0 0xb76e3424 in __kernel_vsyscall ()
#1 0xb5ad89b1 in select () from /lib/
#2 0xb5e0dfcf in QProcessManager::run (this=0xb5f4a710) at /home/kubo/kde4/src/qt-copy/src/corelib/io/qprocess_unix.cpp:245
#3 0xb5d31d3e in QThreadPrivate::start (arg=0xb5f4a710) at /home/kubo/kde4/src/qt-copy/src/corelib/thread/qthread_unix.cpp:244
#4 0xb5c978ac in start_thread () from /lib/
#5 0xb5adfa9e in clone () from /lib/

Thread 1 (Thread 0xb5217960 (LWP 8031)):
[KCrash Handler]
#6 0x03000020 in ?? ()
#7 0xb60f3e23 in QWidget::ensurePolished (this=0x97ea828) at /home/kubo/kde4/src/qt-copy/src/gui/kernel/qwidget.cpp:9295
#8 0xb6558882 in QSplitter::sizes (this=0x97ea828) at /home/kubo/kde4/src/qt-copy/src/gui/widgets/qsplitter.cpp:1627
#9 0xb221d9da in CalendarView::writeSettings (this=0x97e9b20) at /home/kubo/kde4/src/kdepim/korganizer/calendarview.cpp:487
#10 0xb2286984 in ActionManager::writeSettings (this=0x98c0210) at /home/kubo/kde4/src/kdepim/korganizer/actionmanager.cpp:731
#11 0xb24ba3df in ~KOrganizerPart (this=0x97e93b8, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /home/kubo/kde4/src/kdepim/korganizer/korganizer_part.cpp:103
#12 0xb75cd5cc in KParts::Part::slotWidgetDestroyed (this=0x97e93b8) at /home/kubo/kde4/src/kdelibs/kparts/part.cpp:354
#13 0xb75cd67b in KParts::Part::qt_metacall (this=0x97e93b8, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfe0de28) at /home/kubo/kde4/src/build/kdelibs/kparts/part.moc:82
#14 0xb75cd6ca in KParts::ReadOnlyPart::qt_metacall (this=0x97e93b8, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfe0de28) at /home/kubo/kde4/src/build/kdelibs/kparts/part.moc:166
#15 0xb24ba13a in KOrganizerPart::qt_metacall (this=0x97e93b8, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfe0de28) at /home/kubo/kde4/src/build/kdepim/korganizer/korganizer_part.moc:75
#16 0xb5e37d0a in QMetaObject::metacall (object=0x97e93b8, cl=QMetaObject::InvokeMetaMethod, idx=6, argv=0xbfe0de28) at /home/kubo/kde4/src/qt-copy/src/corelib/kernel/qmetaobject.cpp:237
#17 0xb5e462eb in QMetaObject::activate (sender=0x94106d8, m=0xb5f42790, local_signal_index=0, argv=0xbfe0de28) at /home/kubo/kde4/src/qt-copy/src/corelib/kernel/qobject.cpp:3274
#18 0xb5e46783 in QObject::destroyed (this=0x94106d8, _t1=0x94106d8) at .moc/release-shared/moc_qobject.cpp:149
#19 0xb5e48f3a in ~QObject (this=0x94106d8, __in_chrg=<value optimized out>) at /home/kubo/kde4/src/qt-copy/src/corelib/kernel/qobject.cpp:869 ...


Created attachment 38309
Valgrind when calendar view is off.

Created attachment 38310
Valgrind log for the crash that happens when calendar view is on.

If calendar view is on, a different crash happens: the preview window cannot be loaded and core is dumped. DrKonqi doesn't show up, but I'm able to get this Valgrind log.

Confirmed in trunk.

visibility: private → public
Jonathan Thomas (echidnaman) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at:
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.


Changed in kdeutils (Ubuntu):
status: New → Invalid
Changed in kdeutils:
status: Unknown → Confirmed

Created attachment 43544
New crash information added by DrKonqi

Crash happend when closing Kontact. The backtrace is very similar to the one reported, therefore I think it's the same bug.

Changed in kdeutils:
importance: Unknown → High

Can anyone reproduce in 4.6 ?

I tried to reproduce it with KOrganizer set to both calendar and todo modes. Ark did not crash when I closed its previewer in either mode. It did crash when I closed Ark itself, but I'm getting an incomplete backtrace. This is kdepim and kdepim-runtime from the master branch.

It'd be nice if someone else using either the 4.6 or master branches could try to reproduce the crash too.

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.

Changed in kdeutils:
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.