lomanager issue [solved]

[pinoc]

do you have xterminal installed?
plese enter in a konsole:

Code: [Select]

xterm -u8 -font 7x13bold -fg darkslategray -bg white You should get a white xterm window.
Yes?

Oh, which version of lomanager have you installed, the latest is the lomanager0.2-2 rpm from PASS. Any 0.1 version can not work. Another option is to run lomanager on the PC where it works, then save the rpms, copy them over, and install them. That will get you LO installed but still does not solve why lomanager does not work on that PC...

[craesz]

Yes I have xterm
output:

Code: [Select]

Warning: couldn't find charset data for locale en_US; using ISO 8859-1.
[chris@localhost ~]$


lomanager is at 0.2-2pclos2011. This is very bizarre. At this point, I am thinking of reinstalling.... I absolutely have to have LO on this machine. Sort of makes it worthless when I need to get work done from a production standpoint. Just so you know, I went, after your last post of modification of the script and downloaded straight from their servers the installation x86 packages. I moved everything to a single directory just like your script does and utilized rpm. Still no go. Is it possible that I have something wrong with the rpm program?? How would I debug it to find out?

[pinoc]

Hi craesz,

hmm, if you can't install a rpm then there is definitely something wrong. The output in your last post about the charset not found for en_US is strange. Looks like an incomplete/interrupted addlocale run when localizing the system? Can you run addlocale and rest to en_US, then reboot, and see if you still get that error when running the xterm command? If not, try to install the rpms or run lomanager again to see what happens. Or maybe you have a partially updated system due to the repo problems right now? Reinstall is of course an option, only takes 5 minutes; lomanager should run without problems on a fresh reinstall, it only pulls in rpms from LO, so you don't even need our repos, just an Internet connection / or the set of LO-rpms.
good luck,
-p.

[craesz]

I'm in the middle of reinstalling.... at the office now.... headed home soon to finish the reinstall. Thanks for all you help so far. I'll let you know if the reinstall fixed the problem.

[craesz]

Reinstall solved the issue. Thanks to OP for his scripts... will PM him later for delivery of his favorite beverage  [saved me a lot of time]. System is now up and functional with all prior installed programs.

I do not believe the issue was lomanager at this point.... probably some borked portion of my prior install?? Regardless, I am working now. Sorry pinoc for all the trouble.

[pinoc]

Hi craesz,
good to hear it works now. Could you mark this thread as solved then?
regards,
-p.

[craesz]

I don't mind marking it solved.... sort of strange though since I reinstalled rather than found the solution don't you think?

[pinoc]

lomanager worked on a fully updated system on your other PC as well as on a fresh installed system. It did not work earlier on a system where, for whatever reason (incomplete update or partial sync of server, etc), you could no longer install a rpm-package but this is another problem which is independent of the lomanager-script. For the sake of learning it might have been interesting to figure out the reason why you couldn't install a rpm but that could have taken a very long time as well. You needed a working system now, so the reinstall was the safest and fastest option to get you up and running => solved
let's be pragmatic 
regards,
-p.

[craesz]

works for me