Bug 302097 - Crash reporting assistant was invoked when a KDE PIM Address Book contact entry received as an attachment to an e-mail message was added to the KDE PIM address book.
Summary: Crash reporting assistant was invoked when a KDE PIM Address Book contact ent...
Status: RESOLVED DUPLICATE of bug 290742
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: 4
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-18 03:50 UTC by K. A. Sayeed
Modified: 2012-06-18 05:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description K. A. Sayeed 2012-06-18 03:50:29 UTC
Application: kmix (4)
KDE Platform Version: 4.8.2 (4.8.2)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-24-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:

1. The user received a KDE PIM  Address Book contact entry as an attachment to an e-mail message.

2. While in the Kmail application, the user then added this entry to KDE PIM address book by clicking the mouse on the "Add this contact to the address book" hot button at the bottom of the contact entry.

-- Backtrace:
Application: KMix (kmix), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdc17c39780 (LWP 1958))]

Thread 3 (Thread 0x7fdbf7c02700 (LWP 1990)):
#0  0x00007fdc0de7205d in __pthread_mutex_unlock_usercnt (mutex=<optimized out>, decr=<optimized out>) at pthread_mutex_unlock.c:52
#1  __pthread_mutex_unlock (mutex=0x7fdbf0000a60) at pthread_mutex_unlock.c:290
#2  0x00007fdc0d343591 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fdc0d307713 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fdc0d307f1b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fdc0d308124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007fdc14282426 in QEventDispatcherGlib::processEvents (this=0x7fdbf00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#7  0x00007fdc14251c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#8  0x00007fdc14251ed7 in QEventLoop::exec (this=0x7fdbf7c01dd0, flags=...) at kernel/qeventloop.cpp:204
#9  0x00007fdc14150fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#10 0x00007fdc142319ff in QInotifyFileSystemWatcherEngine::run (this=0x181c760) at io/qfilesystemwatcher_inotify.cpp:248
#11 0x00007fdc14153fcb in QThreadPrivate::start (arg=0x181c760) at thread/qthread_unix.cpp:298
#12 0x00007fdc0de6ee9a in start_thread (arg=0x7fdbf7c02700) at pthread_create.c:308
#13 0x00007fdc175074bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#14 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fdbf71f5700 (LWP 1993)):
#0  0x00007fdc0d343591 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007fdc0d307a2d in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fdc0d307f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fdc0d308124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fdc14282426 in QEventDispatcherGlib::processEvents (this=0x7fdbe40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#5  0x00007fdc14251c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007fdc14251ed7 in QEventLoop::exec (this=0x7fdbf71f4dd0, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007fdc14150fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#8  0x00007fdc142319ff in QInotifyFileSystemWatcherEngine::run (this=0x188ac30) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007fdc14153fcb in QThreadPrivate::start (arg=0x188ac30) at thread/qthread_unix.cpp:298
#10 0x00007fdc0de6ee9a in start_thread (arg=0x7fdbf71f5700) at pthread_create.c:308
#11 0x00007fdc175074bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fdc17c39780 (LWP 1958)):
[KCrash Handler]
#6  0x0000000001c11cb0 in ?? ()
#7  0x00007fdc17827e26 in MDWSlider::update (this=0x1c50260) at ../../kmix/gui/mdwslider.cpp:1001
#8  0x00007fdc1782364b in ViewDockAreaPopup::refreshVolumeLevels (this=<optimized out>) at ../../kmix/gui/viewdockareapopup.cpp:168
#9  0x00007fdc14267281 in QMetaObject::activate (sender=0x1b97890, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#10 0x00007fdc14267281 in QMetaObject::activate (sender=0x1bcc610, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#11 0x00007fdc177fcb0c in Mixer_Backend::readSetFromHW (this=0x1bcc610) at ../../kmix/backends/mixer_backend.cpp:155
#12 0x00007fdc1780cdf5 in sink_cb (c=<optimized out>, i=<optimized out>, eol=<optimized out>) at ../../kmix/backends/mixer_pulse.cpp:191
#13 0x00007fdc15be4944 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#14 0x00007fdc0d826693 in ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so
#15 0x00007fdc0d826a03 in pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so
#16 0x00007fdc15bdabdd in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0
#17 0x00007fdc0d82b2a9 in ?? () from /usr/lib/x86_64-linux-gnu/libpulsecommon-1.1.so
#18 0x00007fdc159c8ab3 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0
#19 0x00007fdc0d307c9a in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fdc0d308060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fdc0d308124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fdc142823bf in QEventDispatcherGlib::processEvents (this=0x1794ad0, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#23 0x00007fdc14f6cd5e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007fdc14251c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#25 0x00007fdc14251ed7 in QEventLoop::exec (this=0x7fff81679370, flags=...) at kernel/qeventloop.cpp:204
#26 0x00007fdc14256f67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#27 0x00007fdc178143e2 in kdemain (argc=3, argv=0x7fff816798f8) at ../../kmix/apps/main.cpp:76
#28 0x00007fdc1743676d in __libc_start_main (main=0x400630 <main(int, char**)>, argc=3, ubp_av=0x7fff816798f8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff816798e8) at libc-start.c:226
#29 0x0000000000400661 in _start ()

Possible duplicates by query: bug 302021, bug 301304, bug 301221, bug 300867, bug 300839.

Reported using DrKonqi
Comment 1 K. A. Sayeed 2012-06-18 03:59:49 UTC
1. KDE PIM seems to move one step forward, then one step backward, then one step to the left, and then one step to the right. This cycle seems to be repeated over and over again in succeeding versions of the PIM.

2. Consequently, KDE PIM has NOT advanced in features, reliability, stability, usability from the KDE PIM version 4.3.2.

3. It appears that there is no continuity in terms of improving upon the previous version as new versions are introduced. The entire development seems to be quite erratic in terms of usability.
Comment 2 Jekyll Wu 2012-06-18 05:02:36 UTC
This crash (fixed in KDE SC 4.8.3) is within kmix. Nothing to do with KDE PIM.

*** This bug has been marked as a duplicate of bug 290742 ***