Version: 3.2.2 (using KDE KDE 3.2.2) Installed from: Debian testing/unstable Packages OS: Linux Using the KPPP from 3.2.2, if I try to set the modem device to be /dev/ttyS4, I get the error "Unable to create modem lock file". If I uncheck "use lock file", and try again, I get "Unable to open modem". This is very strange behaviour, because if I create a symlink from /dev/ttyS4 to /dev/modem, KPPP works, so the problem clearly isn't with permissions (KPPP is being run SUID root). Why then does KPPP not work when I set the modem device to /dev/ttyS4 directly? Is it because it's not one of the pre-defined modem devices? In that case, there seems to be a bug in KPPP. (BTW, ttyS4 should be pre-defined, since 2.6 kernels use ttyS4 as the first PCI hardware modem). Also, when changing the modem device, if you type in a custom device (like ttyS4), and then click on OK, the change isn't remembered. You have to type in you change, and then hit Enter, for the change to stick. (Hitting Enter isn't required if you choose one of the pre-defined modem devices using the selector itself - only when typing in a custom device). Thanks, Christopher Martin

I've added the missing devices to the list of hardcoded values. The custom device feature appearantly doesn't work yet (disabled for KDE 3.2.3) and needs more work. There's already a wishlist report I think. For now please use symlinks to /dev/modem.