(*** This bug was imported into bugs.kde.org ***) Package: kppp Version: KDE 3.0.0 Severity: normal Installed from: Compiled From Sources Compiler: gcc-2.96-0.48mdk OS: Linux OS/Compiler notes: default from Mandrake 8.0 Essentially even though I unckecked the "disconnect on X-server shutdown" option if X goes down or I chose to exit I loose my ppp connection. This was not the case when using kde 2.2.2. I installed kde 3 clean and started with an empty .kde/ directory. (Submitted via bugs.kde.org)
FreeBSD 4.8 RC KDE 3.1 Installed from ports This problem occurs in FreeBSD also. Unchecking the "disconnect on X-server shutdown" does not prevent Kppp from being disconnected when closing the KDE X session.
Gentoo Linux KDE 3.1.0 Installed from portage unchecking "disconnect on X-server shutdown" does not prevent kppp from being disconnected when X session ends.
Just guessing... It think that the problem is that when a KDE session is logged out, every application running on the session, including KPPP, receives the QUIT signal. I think that the problem would be solved if there where an option "Do not disconnect on Quit". That way, while the option is checked, if KPPP quits (manually or by logging out) the connection would remain. That feature would require to add the option "Quit" besides to "Disconnect" in the connection window and in the menu popped up while right-clicking on the docked icon. Such a feature, in conjunction with feature requested in report 37236, would be very handy. That would allow to log out a session and then log in (with possibly a different session) and still monitoring with KPPP the same internet connection. I hope the ideas will be helpfull Cheers. Jos
I'd like to second José's proposal. upon starting KPPP when a PPP session is active, the disconnect and quit buttons should be available. (even if pppd not started by KPPP) cheers, Rob
*** Bug 42326 has been marked as a duplicate of this bug. ***
Replaced lordvader@eisa.net.au with pwnell@iafrica.com due to bounces by reporter
Is this bug still present in a recent version of KDE, such as 3.5.8 or KDE 4 RC2?
Closing due to no response by reporters. Please reopen if this bug still exists in a recent version of KDE, such as 4.0.0 or 3.5.8.