dolphin does not start as root
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dolphin (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Package: kubuntu-
step 1:
Starting dolphin from the menu fails - kdesu starts to accept password, but then Dolphin does not open.
three attempts to start dolphin from the command line:
step 2:
wolf@wolf-
kdesu: command not found
as per man file, this is because kdesu is not in the path
step 3:
wolf@wolf-
Executing Dolphin as root is not possible.
/usr/lib/
step 4:
wolf@wolf-
QInotifyFileSys
QFileSystemWatcher: failed to add paths: /home/wolf/
Bus::open: Can not get ibus-daemon's address.
IBusInputContex
Executing Dolphin as root is not possible.
Here I gave up, as the likely next steps are beyond my ability.
Other observations:
Since my system contains about a dozen partitions, I need to manually modify fstab and /media to define which partitions are mounted at start-up, and which are mounted only upon request. I do this by assigning unique labels to each partition, since UUID's are not human-readable. Since a label can be assigned to 17.10 only from another installation of 17.10 and not from an older installation such as e.g. 16.4, because of some code changes needed for e2label, I have also tried to directly copy the changes to fstab and /media from another installation. This copying action made the whole 17.10 unusable - the commandline is available, but the x-system needs starting manually, and there is also no network access.
wolf
Changed in dolphin (Ubuntu): | |
status: | New → Won't Fix |
Not sure if it was at the time, but this is not a bug. Dolphin no longer allows root access. You can see for yourself in the terminal:
$ sudo dolphin
Executing Dolphin with sudo is not possible due to unfixable security vulnerabilities.