Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 374883 - kde-misc/krusader-2.3.0_beta1: "start root mode krusader" not working as intended
Summary: kde-misc/krusader-2.3.0_beta1: "start root mode krusader" not working as inte...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: Normal minor (vote)
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-11 19:18 UTC by Alejandro Stankevicius
Modified: 2011-10-19 18:13 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Proposed patch (rootmode.patch,755 bytes, patch)
2011-07-11 19:21 UTC, Alejandro Stankevicius 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alejandro Stankevicius 2011-07-11 19:18:55 UTC 
In kde-misc/krusader-2.3.0_beta1, option "Start Root Mode Krusader" from "Tools" menu no longer works (although it does work when started from a root console or with sudo/kdesu).
Apparently, kdesu is being called with the wrong parameters. According to some fedora patch I've googled, kdesu arguement "-c" is missing.

Reproducible: Always

Steps to Reproduce:
1. Start Krusader as a normal user
2. Click option "Start Root Mode Krusader" from "Tools" menu
Actual Results:  
kdesu complains that it can't execute the desired command

Expected Results:  
krusader starting in root mode
Comment 1 Alejandro Stankevicius 2011-07-11 19:21:57 UTC 
Created attachment 279801 [details, diff]
Proposed patch

Proposed patch adapted from another one I googled while trying to solve this.
Comment 2 Andreas K. Hüttel archtester gentoo-dev 2011-10-17 19:44:37 UTC 
Is this fixed in krusader-2.4.0_beta1 ?
Comment 3 Alejandro Stankevicius 2011-10-19 18:13:15 UTC 
(In reply to comment #2)
> Is this fixed in krusader-2.4.0_beta1 ?

Yes, it is!

I think we can finally mark this bug as resolved, right?