Weird behaviours ... programs just dies

[svarreby]

I have just performed a clean install of SuSE 9.1. Everything is updated.

When I start some software (OpenOffice 1.1.1, Thunderbird 0.8) they starts loading and then suddenly dies.

I have looked thru the log files but I can't find any references to either these programs nor their errors.

Does this indicate some "major" flaw in my system?

Would the best way be to uninstall them and then re-install them again?

[rbrimhall]

try running them from the command line to see if any errors are produced...

[svarreby]

This is what I found.

This one is for BitTorrent:

Traceback (most recent call last):
File "usr/bin/btdownloadgui.py", line 13, in ?
from wxPython.wx import *
ImportError: No module named wxPython.wx

I have searched (thru YAST) but the weird thing is ... I can't even find this (wxPython-2.???) package?!?!?


This one is for Thunderbird:
linux:/ # usr/bin/thunderbird
DISPLAY empty or unusable
DISPLAY=:0.0
linux:/ #

... and at last, this is from the OpenOffice Writer:
linux:/ # OOo-writer
Installing default (en) configuration...
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

cannot connect to X server
Error: The default configuration was not created.
Error: Try again or try to run "OOo-wrapper --skip-check"
linux:/ #


Any clues?

[JohnT]

Try this...sometimes it works..its fast anyway. As root.... Close everything on the desktop. Delete everything in your /tmp directory, empty your trashbin following that action then reboot. Run your apps from the console again. Your possibly missing some development packages that weren't installed.

[rbrimhall]

some distros don't let you run graphical apps as root... are you running these as a user or as root?

connection to ":0.0" refused by server... I've seen this when trying to run graphical apps as su - instead of just a normal su...

[svarreby]

Thanks for your replies :-)

I am issuing these commands both as root and as a user.

This is how it looks when I try to kick start OOOwriter:

danne@linux:~> OOo-writer
Starting /opt/OpenOffice.org/program/swriter...
sh: line 1: crash_report: command not found
Segmentation fault

The splash screen is visible, the program starts, just to die ...

[gehidore]

Originally posted by JohnT
...then reboot...
we dont need no stinking reboot :p

[pickarooney]

Which window managers (KDE, Gnome, Fluxbox etc.) have you installed and which ones have you tried running with?

What happens when you type this?
echo $DISPLAY

[svarreby]

I'm running KDE 3.2.

Here's the result:

danne@linux:~> echo $DISPLAY
:0.0


Well, I for one can't make something out of that :-) ... but
I'm sure you can!

[Icarus]

The bittorrent error tells me you don't have wxPython installed
I've always had problems with the btdownloadgui.py until I started using Gentoo and it installed to correct pieces.

The OO is pretty vauge, could be a simular problem...I don't think that OO uses Python, but it is not finding something it needs. I personally would find out what is on line 1 of /opt/OpenOffice.org/program/swriter as it's just a Bourne Shell Script, and very short...

As for the display, try running this first

xhost +localhost

then run the app again

[techwise]

sounds just like a post in a windows forum would. I think it is the fault of distros like SuSE attempting to be a windows replacement befor it is ready.

I would bet that the reason it is not working is because one of the SuSE updates broke it. In practice, the only things that shuld be updated are issues related to security and to add features you need. If something otherwise works then dont update it.

These distros like SuSE and Mandrake will often publish "fixes" or updates that simply do not work.

Mike

[stevewabc]

Yes this was a problem with suse update but run it again now the problem has been fixed :( :eek: good luck

[svarreby]

Thank you guys for all your input!
I appreciate it very much :-)

When I installed SuSE I thought I would "cut down" on every unnessecary package. In my effort I must have been too thorough :-)

To solve this I reinstalled the whole lot. Now everything works "right-out-of-the-box".

... and again, thanks! (and to you too SuSE :-)