Bug 41232 - on pppd die, reports no trace avail then displays trace
Summary: on pppd die, reports no trace avail then displays trace
Status: RESOLVED WORKSFORME
Alias: None
Product: kppp
Classification: Applications
Component: general (show other bugs)
Version: 2.0.3
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Harri Porten
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-04-18 14:33 UTC by Craig Ringer
Modified: 2008-02-15 03:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Craig Ringer 2002-04-18 14:32:38 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           kppp
Version:           2.0.3 (using KDE 2.2.2 )
Severity:          normal
Installed from:    Debian testing/unstable Packages
Compiler:          Not Specified
OS:                Linux
OS/Compiler notes: Not Specified

When pppd dies after execution for some reason kppp brings up the standard "pppd died unexpectedly" dialog. When one clicks on Details a dialog appears reporting that details are unavailable as pppd debugging is off. Click yes to turn on debugging and the trace appears anyway (though w/o LCP info etc even though this is in syslog).
What is unusual is that (1) "turning on debugging" seems to change nothing and (2) in this case "debug" is already in pppd's options as specified in kppp for the connection.

I'd expect kppp to either display a trace similar to that obtained by `grep ppp /var/log/syslog` when debug option is enabled.

If the pppd option "debug" is off I'd expect kppp to do what it does now : offer to turn it on. However it would then provide detailed information when debugging was on.

As things stand now the "debugging  disabled" warning seems to serve no purpose and is confusing.

Hope I'm not missing something obvious...


(Submitted via bugs.kde.org)
Comment 1 George Goldberg 2007-12-18 04:31:14 UTC
Is this bug still present in a recent version of KDE, such as 3.5.8 or KDE 4 RC2?
Comment 2 George Goldberg 2008-02-15 03:42:26 UTC
Closing due to no response. Please reopen if this bug can be reproduced with KDE >= 4.0.1