Bug 400633

Summary:	Kstart crashes trying to start powerdevil
Product:	[Plasma] kstart	Reporter:	Matej Mrenica <matejm98mthw>
Component:	general	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	kde, matejm98mthw
Priority:	NOR	Keywords:	wayland
Version:	5.14.2
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Matej Mrenica 2018-11-03 17:29:16 UTC

STEPS TO REPRODUCE
1. Make sure powerdevil is not running, like after a crash
2. run in konsole 'kstart5 /usr/lib/org_kde_powerdevil'

OBSERVED RESULT
Kstart5 crashes 
Starting powerdevil without kstart5 works.
Is powerdevil supposed to start like this - with kstart5?
This bug might be caused by powerdevil and not by kstart5

EXPECTED RESULT
Kstart5 starts powerdevil

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.14.2
KDE Frameworks Version: 5.51
Qt Version: 5.12-beta3

ADDITIONAL INFORMATION
Wayland

Log: (altough there isn't much to see)

Application: KStart (kstart5), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f344adb5800 (LWP 8523))]

Thread 2 (Thread 0x7f3446744700 (LWP 8524)):
#0  0x00007f344f0abc21 in poll () from /usr/lib/libc.so.6
#1  0x00007f344dc26ee0 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007f344dc26fce in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007f344f5de604 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4  0x00007f344f5875fc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5  0x00007f344f3cb5c9 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x00007f344ee83ba6 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x00007f344f3cc9cc in ?? () from /usr/lib/libQt5Core.so.5
#8  0x00007f344e667a9d in start_thread () from /usr/lib/libpthread.so.0
#9  0x00007f344f0b6b23 in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f344adb5800 (LWP 8523)):
[KCrash Handler]
#6  0x00007f344ee520ce in xcb_send_request_with_fds64 () from /usr/lib/libxcb.so.1
#7  0x00007f344ee5266a in xcb_send_request () from /usr/lib/libxcb.so.1
#8  0x00007f344ee58da5 in xcb_intern_atom () from /usr/lib/libxcb.so.1
#9  0x00007f3450108032 in ?? () from /usr/lib/libKF5WindowSystem.so.5
#10 0x00007f345010c9d7 in ?? () from /usr/lib/libKF5WindowSystem.so.5
#11 0x00007f345010e952 in NETRootInfo::NETRootInfo(xcb_connection_t*, QFlags<NET::Property>, QFlags<NET::Property2>, int, bool) () from /usr/lib/libKF5WindowSystem.so.5
#12 0x00005623e2247ed2 in ?? ()
#13 0x00005623e2246541 in ?? ()
#14 0x00007f344efdf223 in __libc_start_main () from /usr/lib/libc.so.6
#15 0x00005623e2246ace in _start ()
[Inferior 1 (process 8523) detached]

Comment 1 Kai Uwe Broulik 2018-11-12 16:25:46 UTC

Doesn't crash here, but running this application manually isn't a workflow we support, that's why it's in libexec and not /usr/bin, after all.

Comment 2 Matej Mrenica 2018-11-12 16:56:42 UTC

(In reply to Kai Uwe Broulik from comment #1)
> Doesn't crash here, but running this application manually isn't a workflow
> we support, that's why it's in libexec and not /usr/bin, after all.

I know people normally dont start powerdevil manually, I tried it only because powerdevil crashed so I wanted to start it somehow and then I noticed this.