If you attempt to start any GTK2 app the following will be output to stdout: Gtk-Message: Failed to load module "pk-gtk-module"
Over the course of several Fedora releases there has been a back[1] and forth[2] shift on dependencies on PackageKit-gtk{3}-module. Fedora 17 has removed PackageKit-gtk-module so now there is no easy work around.
The problem stems from /usr/lib{64}/gnome-settings-daemon-3.0/gtk-modules/pk-gtk-module.desktop declaring pk-gtk-module a loadable GTK module.
Could the PackageKit-gtk3-module package be updated to not have GTK2 apps looking for a non-existant module?
[1] https://bugzilla.redhat.com/show_bug.cgi?id=476066 [2] https://bugzilla.redhat.com/show_bug.cgi?id=643129
Michael Cronenworth wrote:
Sorry, meant to paste this bug: https://bugzilla.redhat.com/show_bug.cgi?id=747449
Michael Cronenworth wrote:
Could the PackageKit-gtk3-module package be updated to not have GTK2 apps looking for a non-existant module?
One idea would be to rename the PackageKit-gtk3-module module from libpk-gtk-module.so to libpk-gtk3-module.so. Would this be acceptable?
P.S. Instead of ignoring this issue and hoping anyone who talks about it goes away --- can we please take the 30 seconds required to fix this? I'll write up patches if that would get the ball rolling. Every Linux distribution has a bug report open for this message. Unfortunately they, too, are shoving it under the rug.
On Fri, 2012-06-01 at 11:49 -0500, Michael Cronenworth wrote:
Michael Cronenworth wrote:
Could the PackageKit-gtk3-module package be updated to not have GTK2 apps looking for a non-existant module?
One idea would be to rename the PackageKit-gtk3-module module from libpk-gtk-module.so to libpk-gtk3-module.so. Would this be acceptable?
That wouldn't make the warning go away. GTK+ 2 and 3 share the same xsetting that tells them what modules to look for. In hindsight, that was not the smartest idea. But it is just a harmless message, and I don't really want to start maintaining whitelists of 3rd party modules inside gtk...
On 06/01/2012 06:20 PM, Matthias Clasen wrote:
That wouldn't make the warning go away. GTK+ 2 and 3 share the same xsetting that tells them what modules to look for. In hindsight, that was not the smartest idea. But it is just a harmless message, and I don't really want to start maintaining whitelists of 3rd party modules inside gtk...
Could we have a stub gtk2 module? If you don't want to spend time on it I'll be glad to do something about it. To me, it is an ugly message that makes Linux look like the amateur hobby OS that some ignorant people call it.
On Sat, 2012-06-02 at 11:49 -0500, Michael Cronenworth wrote:
On 06/01/2012 06:20 PM, Matthias Clasen wrote:
That wouldn't make the warning go away. GTK+ 2 and 3 share the same xsetting that tells them what modules to look for. In hindsight, that was not the smartest idea. But it is just a harmless message, and I don't really want to start maintaining whitelists of 3rd party modules inside gtk...
Could we have a stub gtk2 module? If you don't want to spend time on it I'll be glad to do something about it. To me, it is an ugly message that makes Linux look like the amateur hobby OS that some ignorant people call it.
The easiest would probably be to just bring the old gtk2 module back - I honsestly don't know why Richard decided to purge it...
desktop@lists.stg.fedoraproject.org
-
Matthias Clasen -
Michael Cronenworth