[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#9501: kppp hangs when accessing modem
From:       Harri Porten <harri () trolltech ! com>
Date:       2000-09-03 22:04:45
[Download RAW message or body]

Marc Mertens wrote:
> 
> Harri Porten wrote:
> 
> > Message type 2 should be used for the creating a lock file. Could you
> > please test if the problem goes away if you uncheck the "Use Lock File"
> > option in the Device setup section ?
> >
> > Harri.
> 
> Hello , I have tried as you suggested but alas not to any avail , I still
> get
> a hang of the program on the 'Looking for the modem' message. The
> debug output is in this case also a little different and is included in this
> message
> 
> kppp: The user doesn't want a lockfile.
> kppp: sendRequest: trying to send msg type 1
> unable to send file descriptors: Bad file descriptor
> kppp: sendRequest: sent message
> kppp: timeout()
> 
> I have noticed also a strange thing in that when I moved back KDE 1 with the
> 
> old kppp , It had exactly the same hang , if I rebooted my computer the old

Really weird.

> system worked as before (as this mail proves). If I tried to reproduce this
> (using kppp of KDE 2 beta4 followed by kppp of the latest KDE 1) I could not
> 
> get a hang in the old kppp.
> 
> Maybe I could try to compile kppp with the -g flag and debug it If you tell
> me
> on which line and in which source the program starts the 'Looking for the
> modem'.

The "Looking for the modem" place isn't that important. It's the GUI
process hanging while waiting for an answer from the suid root child
process. The child process tried to send the file descriptor of the lock
file or modem back to the parent and fails (see "Bad file descriptor").
The GUI keeps on waiting for an answer ...

Could you please send me a few more lines of debug *before* the error
message ? Maybe we can see something there.

Thanks,

Harri.

[prev in list] [next in list] [prev in thread] [next in thread]