on a fully updated f14:
$ system-config-boot /usr/bin/python: symbol lookup error: /usr/lib/gtk-2.0/modules/libatk-bridge.so: undefined symbol: g_module_make_resident
also, $ gnome-sudoku python: symbol lookup error: /usr/lib/gtk-2.0/modules/libatk-bridge.so: undefined symbol: g_module_make_resident
is this a known issue?
On Tue, 2010-08-31 at 09:59 +0300, cornel panceac wrote:
on a fully updated f14:
$ system-config-boot /usr/bin/python: symbol lookup error: /usr/lib/gtk-2.0/modules/libatk-bridge.so: undefined symbol: g_module_make_resident
also, $ gnome-sudoku python: symbol lookup error: /usr/lib/gtk-2.0/modules/libatk-bridge.so: undefined symbol: g_module_make_resident
is this a known issue?
I don't know.
It looks similar to bug 626852, perhaps something similar is going on? https://bugzilla.redhat.com/show_bug.cgi?id=626852
I think it's worth filing this in bugzilla, against whatever package provides that file: rpm -qf /usr/lib/gtk-2.0/modules/libatk-bridge.so
Hope this is helpful Dave
On Tue, 2010-08-31 at 13:42 -0400, David Malcolm wrote:
On Tue, 2010-08-31 at 09:59 +0300, cornel panceac wrote:
on a fully updated f14:
$ system-config-boot /usr/bin/python: symbol lookup error: /usr/lib/gtk-2.0/modules/libatk-bridge.so: undefined symbol: g_module_make_resident
also, $ gnome-sudoku python: symbol lookup error: /usr/lib/gtk-2.0/modules/libatk-bridge.so: undefined symbol: g_module_make_resident
is this a known issue?
I don't know.
It looks similar to bug 626852, perhaps something similar is going on? https://bugzilla.redhat.com/show_bug.cgi?id=626852
I think it's worth filing this in bugzilla, against whatever package provides that file: rpm -qf /usr/lib/gtk-2.0/modules/libatk-bridge.so
Please check for updates first. There is already an update that fixes this. No need to file more bugs.
2010/8/31 Matthias Clasen mclasen@redhat.com
Please check for updates first. There is already an update that fixes this. No need to file more bugs.
i'll check tomorrow, at work.
2010/8/31 cornel panceac cpanceac@gmail.com
2010/8/31 Matthias Clasen mclasen@redhat.com
Please check for updates first. There is already an update that fixes this. No need to file more bugs.
i'll check tomorrow, at work.
after all the updates, the bug is still there, and i believe it's the same bug as
after all the updates, the bug is still there, and i believe it's the same bug as
anyway, as joachim backes kindly suggested,
yum downgrade at-spi2-atk
fixed the problem, for now.