Bug 287239 - Clementine was misbehaving, so I rebooted and I got this crash
Summary: Clementine was misbehaving, so I rebooted and I got this crash
Status: RESOLVED DUPLICATE of bug 258916
Alias: None
Product: policykit-kde-agent-1
Classification: Plasma
Component: polkit-kde-authentication-agent-1 (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Jaroslav Reznik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-22 10:34 UTC by Sal Colon
Modified: 2011-11-24 13:03 UTC (History)
0 users

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 Sal Colon 2011-11-22 10:34:03 UTC
Application: polkit-kde-authentication-agent-1 (0.99.0)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-13-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:I was making changes to my mp3 collection using Mp3diags, all the while Clementine was playing music in the background. Clementine began misbehaving, which I won't go into here. I chose to restart the laptop(HP HDX 16) and I got this crash.

-- Backtrace:
Application: PolicyKit1-KDE (polkit-kde-authentication-agent-1), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fdcae99e840 (LWP 2122))]

Thread 4 (Thread 0x7fdc9e82c700 (LWP 2131)):
#0  0x00007fdca8e03034 in __pthread_mutex_lock (mutex=0x20338c8) at pthread_mutex_lock.c:61
#1  0x00007fdcaa057fcc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fdcaa058792 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fdca9b3e516 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007fdcaa07d2b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fdca8e00efc in start_thread (arg=0x7fdc9e82c700) at pthread_create.c:304
#6  0x00007fdcabea489d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7fdc9d7ef700 (LWP 2805)):
#0  0x00007fdcabe7051d in nanosleep () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007fdcaa0806d2 in g_usleep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fdcaa053cfc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fdcaa07d2b6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fdca8e00efc in start_thread (arg=0x7fdc9d7ef700) at pthread_create.c:304
#5  0x00007fdcabea489d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#6  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fdc96fbf700 (LWP 2806)):
#0  0x00007fdcabe98773 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007fdcaa057f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fdcaa058429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fdcad2dff3e in QEventDispatcherGlib::processEvents (this=0x212df90, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007fdcad2b3cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fdcad2b3ef7 in QEventLoop::exec (this=0x7fdc96fbed10, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007fdcad1cb27f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007fdcad296cbf in QInotifyFileSystemWatcherEngine::run (this=0x211c200) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fdcad1cdd05 in QThreadPrivate::start (arg=0x211c200) at thread/qthread_unix.cpp:331
#9  0x00007fdca8e00efc in start_thread (arg=0x7fdc96fbf700) at pthread_create.c:304
#10 0x00007fdcabea489d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fdcae99e840 (LWP 2122)):
[KCrash Handler]
#6  0x00007fdca9df4f40 in g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#7  0x00007fdca9dd38cd in g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#8  0x00007fdca96648da in ?? () from /usr/lib/libpolkit-agent-1.so.0
#9  0x00007fdca9dd39f0 in g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007fdcadd35d44 in PolkitQt1::Agent::Session::~Session() () from /usr/lib/libpolkit-qt-agent-1.so.1
#11 0x00007fdcadd35d89 in PolkitQt1::Agent::Session::~Session() () from /usr/lib/libpolkit-qt-agent-1.so.1
#12 0x00007fdcad2cba88 in QObject::event (this=0x2130cb0, e=<optimized out>) at kernel/qobject.cpp:1200
#13 0x00007fdcac665424 in notify_helper (e=0x2066710, receiver=0x2130cb0, this=0x1e4ce40) at kernel/qapplication.cpp:4486
#14 QApplicationPrivate::notify_helper (this=0x1e4ce40, receiver=0x2130cb0, e=0x2066710) at kernel/qapplication.cpp:4458
#15 0x00007fdcac66a291 in QApplication::notify (this=0x7fff8aa3f470, receiver=0x2130cb0, e=0x2066710) at kernel/qapplication.cpp:4365
#16 0x00007fdcae387126 in KApplication::notify (this=0x7fff8aa3f470, receiver=0x2130cb0, event=0x2066710) at ../../kdeui/kernel/kapplication.cpp:311
#17 0x00007fdcad2b4afc in QCoreApplication::notifyInternal (this=0x7fff8aa3f470, receiver=0x2130cb0, event=0x2066710) at kernel/qcoreapplication.cpp:787
#18 0x00007fdcad2b851f in sendEvent (event=0x2066710, receiver=0x2130cb0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=52, data=0x1e265f0) at kernel/qcoreapplication.cpp:1428
#20 0x00007fdcad2b87c4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1071
#21 0x000000000040847e in ?? ()
#22 0x00007fdcabde430d in __libc_start_main (main=0x4081f0, argc=1, ubp_av=0x7fff8aa3f6b8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff8aa3f6a8) at libc-start.c:226
#23 0x00000000004084e5 in _start ()

This bug may be a duplicate of or related to bug 258916.

Possible duplicates by query: bug 286586, bug 286407, bug 286339, bug 286214, bug 285946.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-11-24 13:03:02 UTC

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