Comment 18 for bug 127944

Revision history for this message
Heiko Sieger (heiko-actcom) wrote : Re: [gutsy]Open Office applications don't start

Well, I just tried the workaround mentioned here:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/128211

Installed with:
$ sudo dpkg -i libgtk2.0-0_2.10.11-0ubuntu3_i386.deb

dpkg - warning: downgrading libgtk2.0-0 from 2.11.6-1ubuntu1 to 2.10.11-0ubuntu3
.
(Reading database ... 123015 files and directories currently installed.)
Preparing to replace libgtk2.0-0 2.11.6-1ubuntu1 (using libgtk2.0-0_2.10.11-0ubuntu3_i386.deb) ...
Unpacking replacement libgtk2.0-0 ...
dpkg: warning - unable to delete old directory `/etc/gtk-2.0': Directory not empty
Setting up libgtk2.0-0 (2.10.11-0ubuntu3) ...

I started ooffice -writer from the terminal and it starts OK, but I got the following errors on the terminal screen:

$ ooffice -writer
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 148
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 168
  Major opcode: 148
  Minor opcode: 3
  Resource id: 0x0
Failed to open device

(process:23641): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.13.7/gobject/gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function

(process:23641): Gdk-CRITICAL **: gdk_screen_get_font_options: assertion `GDK_IS_SCREEN (screen)' failed

(process:23641): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.13.7/gobject/gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function

(process:23641): Gdk-CRITICAL **: gdk_screen_get_font_options: assertion `GDK_IS_SCREEN (screen)' failed
$
(process:23641): GLib-GObject-CRITICAL **: /build/buildd/glib2.0-2.13.7/gobject/gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function

(process:23641): Gdk-CRITICAL **: gdk_screen_get_font_options: assertion `GDK_IS_SCREEN (screen)' failed

Looks the same as before, but Openoffice DID start. I just checked the spreadsheet and it works too. Yet, the error message remains. Hope it gives someone with more insight a little clue.