Works fine here.
--
kppp menu entry should launch as root by default
https://bugs.launchpad.net/bugs/53879
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdenetwork in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
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)
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
** Changed in: kdenetwork (Ubuntu)
Assignee: (unassigned) = Harald Sitter (apachelogger)
Status: Confirmed = In Progress
--
kppp menu entry should launch as root by default
https://bugs.launchpad.net/bugs/53879
You received this bug notification because you are a member of Ubuntu
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)
On Intrepid, kppp starts, but doesn't ask for a root password, so I
assume some of its functionality doesn't work.
** Changed in: kdenetwork (Ubuntu)
Sourcepackagename: kdebase = kdenetwork
Importance: Undecided = Medium
Assignee: p3net (admin-p3net) = (unassigned)
Status:
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
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 (Ubuntu)
