kppp menu entry should launch as root by default

Bug #53879 reported by Alexandros Papadopoulos
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdenetwork (Ubuntu)
Fix Released
Medium
Harald Sitter

Bug Description

Binary package hint: kdebase

When kppp is installed, both as a standalone application and as found in kubuntu, it is launched with the standard user rights.

As a result, it cannot complete basic tasks like tuning the routing table on connection/disconnection, updating the DNS resolver records etc.

kppp should be launched as root by default, asking for the user's password, otherwise it is not apparent to the new user why kppp can't work properly (no "permission denied" messages)

Revision history for this message
p3net (admin-p3net) wrote :

Hello Mr. Papadopoulos,

It has been quite some time since a response, and I would like to know if you are still experiencing this issue or if it has resolved itself in more recent versions of the affected software so that we may adequately route this bug.

Changed in kdebase:
assignee: nobody → admin-p3net
status: Unconfirmed → Needs Info
Revision history for this message
mlaverdiere (mlaverdiere) wrote :

Well, in my case, on Kubuntu Feisty with KDE 3.5.7, I found that I can't start Kppp just by clicking on it in the menu. It will refuse to start ant won't give any explanation or error message. This is clearly not a user friendly behavior for such a basic function...

I guess that following this bug report, the Kppp binary has been set to start as root only, but the entry menu has not been modified accordingly. To start Kppp, i have to issue the command "sudo kppp" in a terminal...

I think the Kppp entry meny should be set up like the Wireless assistant app. entry, i.e. to launch directly from the menu, as root, provinding that the user password is entered. To do this, you just have to modify the Kppp entry menu by selecting "executable as another user". Then, the user will be able to launch Kppp as root, by entering his password.

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

On Intrepid, kppp starts, but doesn't ask for a root password, so I assume some of its functionality doesn't work.

Changed in kdebase:
assignee: admin-p3net → nobody
importance: Undecided → Medium
status: Incomplete → Confirmed
Changed in kdenetwork:
assignee: nobody → apachelogger
status: Confirmed → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package kdenetwork - 4:4.1.2-0ubuntu2

---------------
kdenetwork (4:4.1.2-0ubuntu2) intrepid; urgency=low

  * Add kubuntu_01_suid_kppp.diff to launch kppp with kdesudo (LP: #53879)
  * kubuntu_02_kppp_add_boud_rates.diff adds 4800 and 1200 boud rates
    (LP: #77254)

 -- Harald Sitter <email address hidden> Sat, 11 Oct 2008 23:12:31 +0200

Changed in kdenetwork:
status: In Progress → Fix Released
Revision history for this message
speedyx (speedyx) wrote :

Problem: I admin a multiuser kubuntu installation. If I want other users to use kppp to access the internet dialup I must include them in the admin group.
I think it was a better behaviour if users included in dialout group or dip group can use kppp, even if they are not in the admin group.
What do you think?

Revision history for this message
Sam H (samjh) wrote :

Hi,

I have changed the status of this bug to "Confirmed", due to this thread on ubuntuforums.org:
http://ubuntuforums.org/showthread.php?t=1311845

The bug has been tested by me and the result is the same as the OP of the ubuntuforums.org thread linked above.

Changed in kdenetwork (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Works fine here.

Revision history for this message
Harald Sitter (apachelogger) wrote :

That is because GNOME is stupid... or maybe because freedesktop.org is stupid and did not include a way to launch an app as root in their desktop entry spec. From a KDE POV a special entry can be added to ensure KDE always launches the executable with kdesu/kdesudo. Since that is common practise within KDE and since fd.o failed to provide a standard the only solution is to make GNOME comply with that KDE way of archiving rootness since Ubuntu would have to patch in special desktop files for gksudo and whatnot whenever there is one using that KDE entry for sudo ... which is unmaintanable.

Changed in kdenetwork (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.