[Bug 275297] New: Smb4K asks for superuser auth in forked terminal instead of via kdesu, cannot enter password; cannot mount shares, program currently unusable
JR
zorael at gmail.com
Thu Jun 9 17:24:18 BST 2011
https://bugs.kde.org/show_bug.cgi?id=275297
Summary: Smb4K asks for superuser auth in forked terminal
instead of via kdesu, cannot enter password; cannot
mount shares, program currently unusable
Product: unknown
Version: unspecified
Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: NOR
Component: general
AssignedTo: unassigned-bugs at kde.org
ReportedBy: zorael at gmail.com
Version: unspecified (using KDE 4.6.3)
OS: Linux
Kubuntu 11.04, running KDE 4.6.3 from kubuntu ppas. Smb4K package version is
0.10.9-1. I could not find a Smb4K product to file this bug against.
I have set up Smb4K to ask me for superuser privileges whenever I mount a
share, but everytime I try it seems to use the terminal sudo instead of the
graphical kdesu. Since Smb4K forks and runs in the background, the terminal
doesn't have focus so no password can be entered. As a result, the program
cannot complete its main function. :<
Error details output in Smb4K proper;
Sorry, try again.
Sorry, try again.
Sorry, try again.
sudo: 3 incorrect password attempts
Terminal output;
$ smb4k
$ [sudo] password for zorael:
[sudo] password for zorael:
[sudo] password for zorael:
[sudo] password for zorael:
[sudo] password for zorael:
[sudo] password for zorael:
$ <waiting for new input>
Reproducible: Always
Steps to Reproduce:
1. Start Smb4K
2. Configure Smb4K -> Super User section, tick Use super user privileges to
mount and unmount shares
3. Hit OK
4. Double-click an available share in your local network
Actual Results:
5. Error message thrown with details as above
6. Share does not get mounted due to insufficient privileges
Expected Results:
5. kdesu spawns and asks for superuser authentication
6. Share gets mounted upon successful password input
The Kubuntu team renames the kdesu binary to kdesudo (likely since Canonical
wants *sudo homogenity), but I have a kdesu symlink in /usr/local/bin, so that
file should be available to Smb4K via PATH.
(As for severity, the fields description page[1] suggests bugs that cause major
loss of function should be tagged Major, whereas the dropdown menu in the bug
report form suggests that tag should be used for bugs that causes data loss.)
[1]: https://bugs.kde.org/page.cgi?id=fields.html#bug_severity
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list