Bug 377530 - partitionmanager Crashes on Run without administrative privileges from Unprivileged User Session
Summary: partitionmanager Crashes on Run without administrative privileges from Unpriv...
Status: RESOLVED DUPLICATE of bug 375394
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (show other bugs)
Version: 3.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-12 19:03 UTC by 13hurdw
Modified: 2017-03-12 19:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
backtrace (5.89 KB, text/plain)
2017-03-12 19:03 UTC, 13hurdw 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description 13hurdw 2017-03-12 19:03:46 UTC 
Created attachment 104523 [details]
backtrace

3.0.1-0neon+16.04+build3 amd64
KDE neon LTS User Edition 5.8

To reproduce:
Launch partitionmanager from Application Launcher or Terminal in an unprivileged user session.
Click "Ignore" or "Cancel" on KDE su window.
Click "Run without administrative privileges".

Expected:
Partition manager still opens in limited mode without ability to apply operations.

Actual:
KDE Partition Manager Closed Unexpectedly (see backtrace)

The following output if running from terminal:
org.kde.kdesu: Daemon not safe (not sgid), not using it.

Loaded backend plugin:  "pmlibpartedbackendplugin"
"Using backend plugin: pmlibpartedbackendplugin (1)"
"Scanning devices..."
QSocketNotifier: Invalid socket 6 and type 'Read', disabling...
The X11 connection broke (error 1). Did the X11 server die?
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = partitionmanager path = /usr/bin pid = 4798
KCrash: Arguments: /usr/bin/partitionmanager --dontsu 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1001/kdeinit5__0
Comment 1 Andrius Štikonas 2017-03-12 19:07:06 UTC 

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