Ping? What happened to this bug? My fault for not following up on
2.0.1; marking 2.0.2, which'll be tracked better.

What's the status here Havoc? I'm not sure as to what modemlights
should be doing by default.

It may well be something that can't be gotten right for all
distributions by default, at least not without configure script
hackery. I am not much of an expert on this...

An issue in 2.2? If so it needs looking at soon-ish. Marking TARGET 2.2.2.

The two issues are:

* Wrong connect commands
* No auto-detection of modem lock file

I'm not sure but I think that most distros use
/sbin/ifup - maybe debian doesnt though, I'll 
try and find out.

As for the lock file - well someone needs to work out how
to autodetect which device the modems is and use the corresponding
lock file.

Dudes, maintainers: Can someone either

a) Fix this applet, or
b) Make an executive decision to drop it at some point?

This bug isn't getting enough love for something that is apparently
entirely broken.

This bug is not a bad as it seems. We've been shipping this applet for
years with the same behavior. The problem is that each distribution
has different methods for doing ppp, so it wouldn't be that easy to
fix, thus it's probably up to the distributions to set the defaults
accordingly.

Thus I don't see any reason to drop the applet now. Untill there
becomes a nice gnome ppp dialer with an applet of it's own, I think we
should keep shipping modemlights (I use it myself all the time).

I've asked gnome-love to try and love this applet. Ideally we should be able to
get some integration with gnome-system-tools at some point, I'm led to believe
it will be supporting ppp in the not too distant future.

My dreams came true. The applet was rewritten to do everything via
gnome-system-tools.

This bug is by definition no longer an issue.