FC3 system-config-network

[dishawjp]

Hi Again,

I thought I was all set, but I guess not. About the last thing I had to do was get my modem configured and everything would have been good. Here's my most current problem. Trying to run "system-config-network" from the command line gives the following:

Code: Select all

[root@eunix etc]# system-config-network
Traceback (most recent call last):
  File "/usr/sbin/system-config-network-gui", line 42, in ?
    locale.setlocale(locale.LC_ALL, "")
  File "/usr/lib/python2.3/locale.py", line 381, in setlocale
    return _setlocale(category, locale)
locale.Error: unsupported locale setting
[root@eunix etc]#


Which seems to indicate a "locale" error. Running the command "locale" gives teh following:

Code: Select all

[root@eunix etc]# locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
[root@eunix etc]#


Obviously some unhappiness there. How do I go about fixing my "locale" so that I can get my modem set up?

Jim

[Void Main]

Dammit Jim! (Star Trek reference, not that I know anything about Star Trek cause I don't) :) How do you do it? The only thing I can figure is that you are trying to break your system. :) I have actually found reference to something similar but not with a successful resolution:

https://listman.redhat.com/archives/fed ... 00049.html

Something else that is an interesting read if you have time:
http://www.linux.org/docs/ldp/howto/Uni ... WTO-3.html

Something I think might be related would be the contents of your /etc/sysconfig/i18n. Mine is:

Code: Select all

LANG="en_US.UTF-8"
SUPPORTED="en_US.UTF-8:en_US:en"
SYSFONT="latarcyrheb-sun16"


The output of my "locale" command is:

Code: Select all

LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=


The only thing I can think of is you have yours set up to something other than what I have and the locale you are using is broken. Of course that may be obvious. The "locale" files (executables and data in /usr/lib/locale) are part of glibc-common and upgrading it seems to have been when all of these problems started, as well as the previous ones you mentioned right? It would be interesting to see if you temporarily set your /etc/sysconfig/i18n file to match mine if the problems go away.

[dishawjp]

Voidmain,

Well, I tell you. I don't break it on purpose, but I do a heck of a job at it unintentionally. I have googled this fairly extensively and found some references, but few had resolutions and most were very specific to setting locale to Belorussian or customizing for multiple locales for different purposes. I wish I knew more about programming so I could understand some of this better. I did find one reference about using setlocale() and putting the arguments within the parentheses for each of the categories. But I am worried that if I do that wrong (very likely since I barely understand this) I may really hose something.

My i18n file does seem to be OK. Editing that would have been too simple a fix.

Code: Select all

[root@eunix sysconfig]# cat i18n
LANG="en_US.UTF-8"
SUPPORTED="en_US.UTF-8:en_US:en"
SYSFONT="latarcyrheb-sun16"
[root@eunix sysconfig]#


And if you look at the output from my "locale" command, it is identical to yours other than the error messages, but the actual 14 lines of settings are the same as yours. Maybe this is some sort of an error with glibc-common. Would I totally hose my system by doing an:

rpm -e glibc-common
apt-get install glibc-common

Or would apt likely depend on glibc-common. I suppose I could d'l the current version and "freshen" the install with rpm. I just hate to make things worse. I have everything else running, I even got totem to work! That foolish KDSKBENT error is gone. I'm pretty certain that if I replace my CD burner, that will work too. I'm soooo darn close....

I haven't read your URL's yet. I'm at work and should be spending some time working, but it's kind of slow here today and I hope to blow out early and spend some time on this later this afternoon. About all I really have to do is write up an "Executive Summary" (boss talk for explanation and justification) for a portion of my capital budget relating to residence hall renovations (heck it's only $3.2M over 5 years, next to nothing..) and then I can get out of here and do something important, like fixing (or totally hosing?) my Linux box.

I'm not certain when this problem began. Everything else was working perfectly, I was just getting around to reconfiguring everything and the last thing I had to do was my modem. That's when I found this issue. I guess the problem could lie in the system-config-network binary itself and not necessarily in glibc-common.

If you have any other thoughts, please pass them along. Oh, and if you ever need a perfectly good system hosed, let me know and I'll use it for a couple of days

Jim

[Ice9]

dishawjp wrote:

Would I totally hose my system by doing an:
rpm -e glibc-common
apt-get install glibc-common

you can actually do

Code: Select all

# apt-get install --reinstall glibc-common

and it will download the latest version and reinstall it.

[dishawjp]

Thanks Ice9!

I'll give that a try when I get home.

Jim

[dishawjp]

IT WORKED!!!!

Thanks Ice9 and Voidmain. I did the:

apt-get install --reinstall glibc-common and now system-config-network is working.

You folks are the best!

Now, I went and bought me a shiny new CD burner to replace the MSI unit I've been running and which FC3 doesn't seem to like. If that goes as well as this did, I'll be fully up and running in no time

Of course given my demonstarted luck/skills in Linux lately, I probably won't even be able to boot up once it's installed.

Jim

[dishawjp]

I should have known it wouldn't be that easy.

System-config-network is running. I selected to add an interface, a modem, and entered the ISP name and number, my username and password and all, went to activate the modem and got an error 2. It never found the modem. So I did a
ln -s /dev/modem /dev/ttyS0
and tried again. This time it found the modem, made dialing noises once, and exited on error 6.

Thinking I had a chance of fixing this without running back to you folks so soon, I did a "man pppd" and checked the exit status codes. All I found was: "The serial port could not be locked." Interesting, but not too helpful. I googled the error message and came up dry. I was running this as root, so it shouldn't be a permissions error. It did dial once before dying, so it *must* have been accessing the serial port and the modem.

<edit>
Moving on to minicom, seeing as I do need that for work and it is a related issue, I did the "minicom -s" pointed the serial device to /dev/modem (knowing that /dev/modem is linked to /dev/ttyS0 and that has worked in the past), saved my settings, but when I tried to run minicom (as root) I got the following, probably related message:

Code: Select all

[root@eunix ~]# minicom
Device /dev/modem lock failed: Operation not permitted.
[root@eunix ~]#


Maybe this will shed some light?
</edit>

Any thoughts?

Jim

[worker201]

I don't know jack, but that "operation not permitted" smells like a permissions problem. Who is the owner? What are the permissions set to?

[Void Main]

The messages would indicate that there is a lockfile for the device which indicates another program is using it. This could be a leftover lockfile if you know no other programs would be using the serial port at the moment. If this is the case you can delete the lockfile, probably found somewhere under the /var/lock directory. It would have the name of the device (modem, or ttyS0) associated with it. In the lock file(s) would be the process ID of the process that created the lock file. First look to see if that process is running. If it is not then remove the lock file(s) and try minicom again (or any other program needing to use the modem).

[dishawjp]

As usual, Voidmain was right on target. I'm using my modem right now to post this.

How do you know all this????? Not that I'm complaining, but you're amazing

More seriously, I bought a book today titled Troubleshooting Linux. If ever anyone has needed a book like that, it's me. I honestly do try to dig myself out of the holes I so frequently seem to bury myself in, but rarely seem to be able to do so without the help of this forum.

Anyway, I'll post more about the book it in The Lounge after I've had a chance to spend some time with it. Maybe someone here can recommend other good Linux troubleshooting references.

Jim

[Void Main]

Well Linux and UNIX have been my bread and butter for over 10 years now so most of this stuff comes really easy to me. I'm still learning just like everyone else though. I've noticed a few others around here picking up on things pretty well and have taught me a few things. I don't know what to recommend as far as books because I don't really have any books on Linux. Actually, I do have a couple of books that were given to me and signed by the authors but I really haven't read them. Those are a little out of date now anyway. Maybe you could start a new topic with that as the title so it catches people's eye and hopefully get them to make suggestions.

[worker201]

O'Reilly guides:
Using bash
Using csh and tcsh
vi Editor Pocket Reference

Those are the only books I have. Everything else I learn from Linux howtos:
http://www.tldp.org/HOWTO/HOWTO-INDEX/categories.html

[Tux]

O'Reilly's Safari service is pretty cool.