<INFO> Domain name not defined for localhost?

[MikeHalloran]

..Remote machines couldn't contact localhost. Fill the doman name through Configuration/Interface menu. """

PC-LinuxOS running as CAELinux 2007.
Tried to start Salome_Meca; died lacking a configuration file.
Tried to start ASTK, got the message shown above.

Who put up the message, why, and where is the Configuration/Interface menu?

Thanks

 

[thedaver]

WHAT was that question?!!?!??

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/

 

[RhythmAce]

Sounds like an ASTK kinda question. I'm guessing that ASTK stands for Application Server ToolKit. If that is the case then it is saying you need to configure it before you can use the thing. At any rate, this is not a linux issue.

 

[MikeHalloran]

The above message came from last year's version of CAELinux, which I installed in a partition of its own on my work computer. I mess with it an night or when I have idle time at work. I swear I've run the CAE apps before, but the underlying PCLinuxOS was getting old, so I updated that, replacing a couple hundred packages. That's when the CAE stuff stopped working... if it ever really did. I haven't been able to spend as much time learning the CAE as I had intended, and my memory is getting fuzzy.

So I downloaded a newer version, which comes as a Live/Install DVD iso. Burned it under Linux, got a message that track 1 was messed up, ran it anyway. It seems to work, except for two things:

Run as a LiveDVD on the work computer, I have to run a 'CAE console' first and leave it open, to set up paths and such. Then I run Salome-Meca, or try to. It bombs out with an error message implying that some of the pieces are in the wrong part of a deep subtree. That's on the same computer as above, but without using the image on the hard drive.

Now, here's where it really gets weird. Run as a LiveDVD on my laptop, it all works, starts up Salome-Meca, imports a geometry file, displays it correctly, and so far as I can tell, works just fine... except that in front of everything, on every desktop, right in the middle, is a horizontal slider marked 'volume', that controls the sound system.

Now, here's where it gets really, really weird. The slider forces the sound to zero, all by itself. I use the mouse to move it to a high volume, and it goes back to zero, as if it's spring loaded. It also controls the volume control in the taskbar, forcing it to zero whenever I move it away, and it does the same to the master volume control in the mixer.

Now, here's where it gets really, really, really weird. When I close KSound, or whatever the taskbar volume control is named, it asks me if I really want to kill it. I say yes, and it dies, and then it comes right back up. I went looking for daemons, and shut down all I could find that had anything to do with sound, and it kept coming back. I.e. there's a daemon there that I can't kill.

I could do without the sound, if the big ol' volume slider in front were not so large that it covers up most of every error dialog. The volume slider is also immovable; not only can I not kill it, I can't slide it off to the side either. It doesn't have a title bar to grab.

Note that the exact same LiveDVD:
1. Works in my laptop, but brings up this zombie sound control that obscures the most important part of the screen.
2. In my work desktop, doesn't bring up the zombie sound control, but the CAE doesn't work.
PCLinuxOS appears to work okay on both.

I'm in the process of copying the DVD iso image to another computer and DVD burner that is known to reliably produce good DVDs, on the theory that this hidden in plain sight volume slider daemon is some kind of afterbirth of what would otherwise be a good DVD. I can't explain the divergent behavior on different computers.

Wish me luck.

 

[MikeHalloran]

Oh. I almost forgot. Thanks, Ace. The error message doesn't appear if I run the "CAE Console" before anything else. Of course that's not in the directions.

 

[MikeHalloran]

Burned a coaster, then another DVD, which is running like the first one did on the laptop.

After messing around with it a bit, I found the source of the zombie sound control; something called KMilo, listed in the Control Center's Service Manager as 'KDE special key notifier'. I wonder what that is supposed to do?