No oo apps can start.

[Andrey Bondarenko]

shaman@shaman007:~$ oowriter2
no suitable windowing system found, exiting.
shaman@shaman007:~$

shaman@shaman007:~$ uname -a
Linux shaman007.homelinux.com 2.6.15-16-amd64-generic #1 SMP PREEMPT Mon Feb 20 16:35:03 UTC 2006 x86_64 GNU/Linux
shaman@shaman007:~$

Kde. Dapper Drake, up2dated.

[Andrey Bondarenko (abondarenko)]

Just want to add that I have composite effects on. Dia, gimp and other GTK apps works just fine.

[Bruce Cowan (bruce89-deactivatedaccount)]

I get the same thing, on AMD64 too
Linux DROOPY 2.6.15-16-amd64-k8 #1 SMP PREEMPT Mon Feb 20 16:52:39 UTC 2006 x86_64 GNU/Linux

[Andrey Bondarenko (abondarenko)]

By the way, COMPOSITE does not influense on this bug at all.

[Bruce Cowan (bruce89-deactivatedaccount)]

I reinstalled dapper, and all it's updates, and it still doesn't work.

[Tobi Vollebregt (tobivollebregt)]

I can confirm this too.

Linux ubuntu 2.6.15-16-amd64-k8 #1 SMP PREEMPT Mon Feb 20 16:52:39 UTC 2006 x86_64 GNU/Linux

[Floydius (lloydtaylor)]

Dapper Flight 4 x86-64. Ooffice2 runs fine before updating. after updating:

lloyd@floydius:~$ ooffice2
no suitable windowing system found, exiting.

this is true with or without nvidia binary driver installed, also with or without the new compiz stuff.

tried it as root as well, same result.

using 2.6.15-16-amd64-generic #1 SMP PREEMPT

[Rocco Stanzione (trappist)]

oowriter2 starts fine on my up-to-date dapper system.

[Floydius (lloydtaylor)]

Rocco, are you using amd64? from above posts, it appears all those having problems are dealing with amd64.

[Floydius (lloydtaylor)]

After looking further, it appears this is a duplicate of bug #32869

[jontxo (reincigarcia)]

the problem for me was the ia32-libs package. When I updated it from version 1.4ubuntu4 to 1.4ubuntu8 openoffice shows the message (when started from a terminal):
no suitable windowing system found, exiting.
this package cannot be downgraded so the only way to fix this is to reinstall the system

[gil-galad (espergreen)]

Same problem. Fully updated dapper.

[Rob Tirrell (r-tirrell)]

confirmed with fully updated amd64 dapper.

[John Moser (nigelenki)]

This is making it really hard to edit documents in 64-bit. I need to find the old ia32libs. I'll force remove current and install from the CD.

[Bruce Cowan (bruce89-deactivatedaccount)]

It worked yesterday, but now it says this in terminal :
/usr/lib/openoffice2/program/soffice: line 233: /usr/lib/openoffice2/program/soffice.bin: No such file or directory

[Bruce Cowan (bruce89-deactivatedaccount)]

Still doesn't work :
bruce@DROOPY:~$ ooffice -writer %F

(ooqstart:15064): Gdk-WARNING **: Error converting from UTF-8 to STRING: Could not open converter from 'UTF-8' to 'ISO-8859-1'

(ooqstart:15064): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported

(ooqstart:15064): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported

(ooqstart:15064): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported

(ooqstart:15064): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported
/usr/lib/openoffice/program/soffice: line 233: /usr/lib/openoffice/program/soffice.bin: No such file or directory

** (ooqstart:15064): WARNING **: Unknown error forking main binary / abnormal early exit ...

[Vincenzo Ampolo (vincenzo-ampolo)]

Same problem here (amd64 dapper up to date 6 March) and it's seems the same problem as bug #33448)

[Matthias Klose (doko)]

please could you install the following package and then retry to run OOo? the single applications now start with oocalc, oowriter, ... (without the trailing 2).

http://people.ubuntu.com/~doko/ia32-libs-openoffice.org_7_amd64.deb

[Bruce Cowan (bruce89-deactivatedaccount)]

It still dies :
bruce@DROOPY:~$ oowriter

(ooqstart:5905): Gdk-WARNING **: Error converting from UTF-8 to STRING: Could not open converter from 'UTF-8' to 'ISO-8859-1'

(ooqstart:5905): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported

(ooqstart:5905): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported

(ooqstart:5905): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported

(ooqstart:5905): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported

(soffice.bin:5918): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported

(soffice.bin:5918): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported
/usr/lib/openoffice/program/soffice: line 233: 5918 Segmentation fault "$sd_prog/$sd_binary" "$@"

** (ooqstart:5905): WARNING **: Unknown error forking main binary / abnormal early exit ...

[Adam Conrad (adconrad)]

The segv reported here should be solved by updating to the latest version of nvidia-glx (2.6.15.6-3) available at a mirror near you, by now. :)

[Bruce Cowan (bruce89-deactivatedaccount)]

It is fixed for me.

[Vincenzo Ampolo (vincenzo-ampolo)]

It works for me too with the newest nvidia-glx.

Thanks

[Matthias Klose (doko)]

fixed with recent nvidia-glx update

[Amaroq (coolsteve64)]

I have neither an nvidia or an ati card, that I know of. I have a crappy i810, so a video card driver can't be the problem for me.

I can confirm the "no suitable windowing system found, exiting." bug, and that I have managed to fix it somehow.

sudo aptitude reinstall alsaplayer-common apache-common evolution-data-server evolution-data-server-dbg evolution-dbg evolution-plugins gnucash gnusound gstreamer0.8-audiofile kdelibs-dbg kdelibs4-dev kdelibs4c2alibaudiofile-dev libc6 libc-dbg libc6-i686 libggi2 libgii0 libgnome-vfs-common libgnomepring2.2-0 libgnomevfs2-0 libgnomevfs2-0-dbg liblockfile-dev liblockfile1 liblockfile1-dev libvorbis-dev libvorbisfile-ruby1.6 libvorbisfile-ruby1.8 libvorbisfile3 libxine-main1 python2.4-kde3

I'm not sure which one of those fixed it. I simply tried a bunch of things that looked like it might work. If someone can try these out one by one and let the rest of us know which one fixes it, that would be great.

Of course, my problem probably stemmed from an accidental removal of all files containing the string "file.so" in their filenames from my system, and therefore fixing it for me may have been easier than it is for the rest of you. Used apt-file to obtain a list of packages containing the filename file.so and used that list as a basis of what to reinstall.