Mageia forum

Good morning Mageians;

I am having this problem when running MCC or some other application in the console..it is not a problem actually but messages like this annoy me:

The message I am having is:

Gtk-Message: Failed to load module "canberra-gtk-module"

Should I install a package or should I just ignore it? My DE is KDE.

Thank you

From what i read, installing libcanberra-gtk3 would solve this.

isadora wrote:From what i read, installing libcanberra-gtk3 would solve this.

Shouldn't it be installed by default as being called by MCC?

Besides I have it installed! Or should I install the i586 version?! My installation is x86_64..

Yes you are right, it is installed by default.
Have lib64canberragtk3 installed.

Also started from CLI MCC, which gave following output:

Code: Select all

 "/usr/bin/drakmenustyle" is not executable [Menus] at /usr/sbin/drakconf.real line 820.
"/usr/sbin/drakbackup" is not executable [Backups] at /usr/sbin/drakconf.real line 820.
"/usr/sbin/drakvirt" is not executable [Virtualization] at /usr/sbin/drakconf.real line 820.
"/usr/sbin/tomoyo-gui" is not executable [Tomoyo Policy] at /usr/sbin/drakconf.real line 820.
"/usr/sbin/drakguard" is not executable [Parental Controls] at /usr/sbin/drakconf.real line 820.

So I have it installed and still got that error!!

installing lib64canberra-gtk0 solved the probleme for me.

thanks, but why though?

Apart from that, not every "error" message means that there's really a problem. I'd only investigate if there's a real problem.

doktor5000 wrote:Apart from that, not every "error" message means that there's really a problem. I'd only investigate if there's a real problem.

neither really an error nor really a problem to me, but nevertheless annoying. and if it can be solved by simply installing a package why i shouldn't do that?

This looks like a very old acquaintance gone to sleep. Maybe some voting for (which means against) this bug might trigger getting it fixed.

PS: Sorry, did not realize that voting has gone away - dont now how to signal that this bug really needs to be fixed.

juergen_harms wrote:Maybe some voting for (which means against) this bug might trigger getting it fixed.

PS: Sorry, did not realize that voting has gone away - dont now how to signal that this bug really needs to be fixed.

Well, you already commented on the relevant bug report. You might give it a push by asking about it on -dev mailing list ...