Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 69971

Summary: modemlights applet very broken in limbo
Product: [Retired] Red Hat Linux Reporter: Alex Yacoub <ayacoub>
Component: gnome-appletsAssignee: Mark McLoughlin <markmc>
Status: CLOSED CURRENTRELEASE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0CC: eitelman, lgoldma, martin, r.klein, tomg
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-12-20 12:53:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 67218, 79579, 100644    

Description Alex Yacoub 2002-07-27 03:59:29 UTC
The modemlights applet will not turn on ppp correctly.  The control button is
mapped to the commands "pppon" and "pppoff", which don't exist on redhat.  This
should instead be "/sbin/ifup ppp0" and "/sbin/ifdown ppp0"

When the ppp link is activated, the applet does not monitor correctly, such that
it doesn't show activity, nor does it let you turn off the link.

Comment 1 Havoc Pennington 2002-07-27 16:02:26 UTC
Filed at http://bugzilla.gnome.org/show_bug.cgi?id=89207

Comment 2 Bill Nottingham 2002-07-29 04:23:32 UTC
HP: we should just fix the ifup/ifdown stuff in a local patch; it's probably RH
specific anyway.

Comment 3 Havoc Pennington 2002-07-29 14:09:17 UTC
Yeah, we had a patch in 7.3 for that.

Comment 4 Havoc Pennington 2002-07-29 16:24:56 UTC
Marking the head of the priority queue with priority high

Comment 5 Havoc Pennington 2002-07-29 19:46:41 UTC
2.0.1-1 should contain a fix for the command

the applet presumably still doesn't work, though.

Comment 6 tom georgoulias 2002-08-07 23:01:05 UTC
After the latest round of updates, I noticed the pppon/pppoff commands were
switched to ifup ppp0 and ifdown ppp0.  The applet in its default config still
doesn't work for me, so I prepended "/etc/sysconfig/network-scripts/" to
ifup/ifdown and was able to dial and shut down the modem through the applet. 
Still doesn't give any status output or use any colors though, it just sits
there and looks the same the whole time.

[tomg@gemini sbin]$ rpm -q gnome-applets
gnome-applets-2.0.1-2

Comment 7 Havoc Pennington 2002-08-07 23:05:48 UTC
Need /sbin/ifup I guess.

Comment 8 tom georgoulias 2002-08-08 00:20:39 UTC
Yup, /sbin/ifup works too.  Still don't get any feedback from the applet after I
connect, and clicking on it to hang up doesn't work.  It just asks if I want to
connect, even though I'm already connected.

Comment 9 Havoc Pennington 2002-08-14 04:42:13 UTC
2.0.1-4 should fix the ifup/ifdown path stuff


Comment 10 Havoc Pennington 2002-08-26 06:21:30 UTC
*** Bug 72629 has been marked as a duplicate of this bug. ***

Comment 11 Havoc Pennington 2002-08-26 06:22:49 UTC
*** Bug 72628 has been marked as a duplicate of this bug. ***

Comment 12 Havoc Pennington 2002-08-26 06:23:26 UTC
applet /sbin path change got lost, still broken.

Comment 13 Havoc Pennington 2002-10-05 16:16:17 UTC
On mailing lists, someone said that the lights don't work because the lock file
is configured incorrectly; if changed to LCK..modem (with full path) then the 
lights and graphs work.



Comment 14 Havoc Pennington 2002-10-05 16:17:13 UTC
*** Bug 74527 has been marked as a duplicate of this bug. ***

Comment 15 Need Real Name 2002-10-11 12:42:49 UTC
I just installed RH 8.0. I am sorry for being so inept, but what is the correct 
path for the lock file. I can find no file on my system that contains the 
LCK...modem terms. I looked in /var/lock and I tried to locate anything about 
LCK or modem. Thanks

Comment 16 Steve Bangert 2002-10-15 04:47:24 UTC
Graphics and modem shutdown will work if modem lock file is set to correct path,
I'm using a USB modem so the path is "/var/lock/LCK..ttyACM0, this file
can _only_ be seen while the modem is connected. Hope this helps.

Comment 17 Need Real Name 2002-10-15 11:10:45 UTC
My thanks to sbangert. This was helpful. I also found some info 
at gnome.org. Easiest way to locate the correct path is to connect with the 
modem, open a terminal while connected and do $ ls /var/lock/LCK*. This will 
return the correct path.

Comment 18 Brent Fox 2002-10-16 19:49:41 UTC
Does the original problem seem to be fixed in 8.0 final?  I don't have a modem
in order to test it...

Comment 19 Need Real Name 2002-10-18 00:28:24 UTC
On a fresh 8.0 install, had to change connect command from "ifup ppp0" to
"/sbin/ifup ppp0", and similarly for disconnect command.  Also changed
lock file to "/var/lock/LCK..ttyS4" (which shows up when ppp connects
as per the previous comments) and device to "ttyS4".  Modem will
now connect and disconnect OK, but the graphs and lights don't work.  Only
the connect button changes from unlit to yellow, then sits there until
I disconnect.  The connect time updates, though.

Comment 20 Ronny Klein 2002-11-28 09:22:19 UTC
I had the same problem with isdn. The lights didn't show up. I tried xisdnload
and that gave me the right hint: /dev/isdninfo isn't world-readable. No idea if
there is a security problem with that; but I changed the permissions so that
other can read /dev/isdninfo: chmod o+r /dev/isdninfo. Now the modemlights are
blinking.

Comment 21 Havoc Pennington 2002-12-20 02:41:42 UTC
*** Bug 75262 has been marked as a duplicate of this bug. ***

Comment 22 Bill Nottingham 2003-02-11 04:54:55 UTC
/sbin readded in 2.2.0-2.

Comment 23 Bill Nottingham 2003-02-11 04:55:38 UTC
*** Bug 76403 has been marked as a duplicate of this bug. ***

Comment 24 Troy 2003-12-06 13:51:31 UTC
For people who now have linux but understand little to nothing about
the detail of working out problems such as this modem lights problem....

place your mouse pointer on your blue desktop screen and right click.
A window comes up that has, "New Terminal" as a selection....click on
it. A window comes up with a blinking curser....type in              
   find /var/lock/LCK*  and hit enter.

In my case  /var/lock/LCK..ttS0  is what the screen feed me back.
(that is S zero, not S Oh). Yours may be slightly diffrent. Make note
of exactly what it is.

Now right click on the modem light thing, select "prefrences" and
click the "advanced" tab. In that tab you will see "modem lock file"
followed by an area you can type in. In my case the area read
/var/lock/LCK..modem, which didn't work as there was no such file (we
looked for all /var/lock/LCK files when we ran find /var/lock/LCK* in
the terminal window.....and it wasn't listed). Change this to what was
listed....in my case it became /var/lock/LCK..ttS0.  This fixed my
modem problem 100%, and hopefully it will work for you too.


Comment 25 Troy 2003-12-06 14:20:40 UTC
I'm so sorry....tried to make it easy for anyone to fix the modem
lights problem and forgot one aspect (this is in addition to comment
#24 above). In addition to following comment #24, also do the following:

right click on your modemlights and select5 "prefrences". You will see
a connect and disconnect command. In the connect command type 
/sbin/ifup ppp0  (that is a zero not an oh)
In the disconnect command space type in
/sbin/ifdown ppp0

Now you will not only have your modem lights work, but in addition you
can connect and disconnect via clicking the left side of the modem
lights icon.....sorry for leaving this out above.

Comment 26 Mark McLoughlin 2004-12-20 12:53:56 UTC
Doesn't look like we've had reports of this since. Closing