Bug 69971
| Summary: | modemlights applet very broken in limbo | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Alex Yacoub <ayacoub> |
| Component: | gnome-applets | Assignee: | Mark McLoughlin <markmc> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike McLean <mikem> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | 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
HP: we should just fix the ifup/ifdown stuff in a local patch; it's probably RH specific anyway. Yeah, we had a patch in 7.3 for that. Marking the head of the priority queue with priority high 2.0.1-1 should contain a fix for the command the applet presumably still doesn't work, though. 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 Need /sbin/ifup I guess. 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. 2.0.1-4 should fix the ifup/ifdown path stuff *** Bug 72629 has been marked as a duplicate of this bug. *** *** Bug 72628 has been marked as a duplicate of this bug. *** applet /sbin path change got lost, still broken. 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. *** Bug 74527 has been marked as a duplicate of this bug. *** 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 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. 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. Does the original problem seem to be fixed in 8.0 final? I don't have a modem in order to test it... 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. 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. *** Bug 75262 has been marked as a duplicate of this bug. *** /sbin readded in 2.2.0-2. *** Bug 76403 has been marked as a duplicate of this bug. *** 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. 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. Doesn't look like we've had reports of this since. Closing |