Bug 371646 - powerdevil crashed when power cord detatched
Summary: powerdevil crashed when power cord detatched
Status: RESOLVED DUPLICATE of bug 371507
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.8.2
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Development Mailing List
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-10-25 04:54 UTC by JamesMOConnell
Modified: 2016-10-26 00:42 UTC (History)
1 user (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 JamesMOConnell 2016-10-25 04:54:16 UTC
Application: org_kde_powerdevil ()

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.8.4-1-ARCH x86_64
Distribution: "Arch Linux"

-- Information about the crash:
- What I was doing when the application crashed: unplugging the laptop, moving from ac to battery power; then powerdevil crashed

-- Backtrace:
Application: org_kde_powerdevil (org_kde_powerdevil), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7febd8cb4840 (LWP 1068))]

Thread 3 (Thread 0x7febc35ca700 (LWP 1074)):
#0  0x00007febd143cdd4 in g_mutex_unlock () at /usr/lib/libglib-2.0.so.0
#1  0x00007febd13f6c7c in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0
#2  0x00007febd13f76ab in  () at /usr/lib/libglib-2.0.so.0
#3  0x00007febd13f789c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#4  0x00007febd750672b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#5  0x00007febd74b023a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#6  0x00007febd72d30f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5
#7  0x00007febd7917e55 in  () at /usr/lib/libQt5DBus.so.5
#8  0x00007febd72d7d78 in  () at /usr/lib/libQt5Core.so.5
#9  0x00007febd25a6454 in start_thread () at /usr/lib/libpthread.so.0
#10 0x00007febd6bed7df in clone () at /usr/lib/libc.so.6

Thread 2 (Thread 0x7febc45fc700 (LWP 1073)):
#0  0x00007febd6be448d in poll () at /usr/lib/libc.so.6
#1  0x00007febd47aa8e0 in  () at /usr/lib/libxcb.so.1
#2  0x00007febd47ac679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1
#3  0x00007febc5f13449 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x00007febd72d7d78 in  () at /usr/lib/libQt5Core.so.5
#5  0x00007febd25a6454 in start_thread () at /usr/lib/libpthread.so.0
#6  0x00007febd6bed7df in clone () at /usr/lib/libc.so.6

Thread 1 (Thread 0x7febd8cb4840 (LWP 1068)):
[KCrash Handler]
#6  0x00007febb001bb94 in  () at /usr/lib/libQtGui.so.4
#7  0x00007febd8bb74fa in call_init.part () at /lib64/ld-linux-x86-64.so.2
#8  0x00007febd8bb760b in _dl_init () at /lib64/ld-linux-x86-64.so.2
#9  0x00007febd8bbbb38 in dl_open_worker () at /lib64/ld-linux-x86-64.so.2
#10 0x00007febd8bb73a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#11 0x00007febd8bbb2d9 in _dl_open () at /lib64/ld-linux-x86-64.so.2
#12 0x00007febd16c0ee9 in  () at /usr/lib/libdl.so.2
#13 0x00007febd8bb73a4 in _dl_catch_error () at /lib64/ld-linux-x86-64.so.2
#14 0x00007febd16c1521 in  () at /usr/lib/libdl.so.2
#15 0x00007febd16c0f82 in dlopen () at /usr/lib/libdl.so.2
#16 0x00007febc0cebbb0 in  () at /usr/lib/libvlccore.so.8
#17 0x00007febc0ccfebb in  () at /usr/lib/libvlccore.so.8
#18 0x00007febc0cd01e8 in  () at /usr/lib/libvlccore.so.8
#19 0x00007febc0cd0144 in  () at /usr/lib/libvlccore.so.8
#20 0x00007febc0cd06c4 in  () at /usr/lib/libvlccore.so.8
#21 0x00007febc0cd0cca in  () at /usr/lib/libvlccore.so.8
#22 0x00007febc0c56eb1 in libvlc_InternalInit () at /usr/lib/libvlccore.so.8
#23 0x00007febc0a27cee in libvlc_new () at /usr/lib/libvlc.so.5
#24 0x00007febc0f882c8 in  () at /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so
#25 0x00007febc0f5d586 in  () at /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so
#26 0x00007febc0f8c195 in qt_plugin_instance () at /usr/lib/qt5/plugins/phonon4qt5_backend/phonon_vlc.so
#27 0x00007febd749acdb in QPluginLoader::instance() () at /usr/lib/libQt5Core.so.5
#28 0x00007febd048d180 in  () at /usr/lib/libphonon4qt5.so.4
#29 0x00007febd048fada in  () at /usr/lib/libphonon4qt5.so.4
#30 0x00007febd0490179 in  () at /usr/lib/libphonon4qt5.so.4
#31 0x00007febd0490aa4 in Phonon::Factory::backend(bool) () at /usr/lib/libphonon4qt5.so.4
#32 0x00007febd0491339 in  () at /usr/lib/libphonon4qt5.so.4
#33 0x00007febd0485031 in  () at /usr/lib/libphonon4qt5.so.4
#34 0x00007febd552e7e0 in  () at /usr/lib/libKF5Notifications.so.5
#35 0x00007febd550d1c0 in  () at /usr/lib/libKF5Notifications.so.5
#36 0x00007febd5509490 in KNotification::sendEvent() () at /usr/lib/libKF5Notifications.so.5
#37 0x00007febd74de4b9 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#38 0x00007febd74b1c7a in QCoreApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#39 0x00007febd74b1de0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#40 0x00007febd74b456d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#41 0x00007febd7506303 in  () at /usr/lib/libQt5Core.so.5
#42 0x00007febd13f7587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#43 0x00007febd13f77f0 in  () at /usr/lib/libglib-2.0.so.0
#44 0x00007febd13f789c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#45 0x00007febd750670f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#46 0x00007febd74b023a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#47 0x00007febd74b873c in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#48 0x0000000000404dbd in  ()
#49 0x00007febd6b25291 in __libc_start_main () at /usr/lib/libc.so.6
#50 0x0000000000404e2a in _start ()

Reported using DrKonqi
Comment 1 jason.ritenour 2016-10-25 22:37:37 UTC
I have observed this same behavior on qt5-base 5.7.0-3, and powerdevil 5.8.2-1 on Arch.  At first, I thought it was just randomly crashing, but have since correlated it with the adapter being unplugged.
Comment 2 Christoph Feck 2016-10-26 00:42:49 UTC

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