Apache OpenOffice (AOO) Bugzilla – Issue 122436
oxygen-gtk not supported under KDE
Last modified: 2014-02-25 13:45:32 UTC
Using AOO 3.4.1 on Mageia 3, also had similar issues on OpenSuse. When I start AOO it doesn't use the oxygen-gtk as it should, but instead uses a corrupted Motif-like theme. Launching AOO from the terminal produces the following message: (soffice:5913): Gtk-WARNING **: /opt/openoffice.org3/program/../basis-link/ure-link/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so) (soffice:5913): Gtk-WARNING **: /opt/openoffice.org3/program/../basis-link/ure-link/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so) Fontconfig warning: "/opt/openoffice.org/basis3.4/share/fonts/truetype/fc_local.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected [ed@localhost ~]$ soffice (soffice:8011): Gtk-WARNING **: /opt/openoffice.org3/program/../basis-link/ure-link/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so) (soffice:8011): Gtk-WARNING **: /opt/openoffice.org3/program/../basis-link/ure-link/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /usr/lib/gtk-2.0/2.10.0/engines/liboxygen-gtk.so) Fontconfig warning: "/opt/openoffice.org/basis3.4/share/fonts/truetype/fc_local.conf", line 33: Having multiple <family> in <alias> isn't supported and may not work as expected
After backing it up, remove /opt/openoffice.org/ure/lib/libstdc++.so.6
The fix works, but this is still a bug that needs to be fixed from the developers' end so that it doesn't happen in the first place. Until this is properly fixed, is there any chance of documenting the workaround somewhere obvious? I didn't find it anywhere on openoffice.org, or anywhere else with any of the search terms I tried.
(In reply to Ed from comment #2) > The fix works, but this is still a bug that needs to be fixed from the > developers' end so that it doesn't happen in the first place. This is fixed on the version I compiled for older linux distros: http://people.apache.org/~arielch/packages/r1372282-glibc-2.5/ > Until this is properly fixed, is there any chance of documenting the > workaround somewhere obvious? I didn't find it anywhere on openoffice.org, > or anywhere else with any of the search terms I tried. I guess it could be documented on http://www.openoffice.org/development/releases/3.4.1.html#AOO3.4.1ReleaseNotes-KnownIssues