Bug 19607 - Gtk-Message: Failed to load module "canberra-gtk-module" is seen in Terminal when starting Pidgin.
Summary: Gtk-Message: Failed to load module "canberra-gtk-module" is seen in Terminal ...
Status: RESOLVED DUPLICATE of bug 3536
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-17 00:10 CEST by Kristoffer Grundström
Modified: 2016-10-17 00:20 CEST (History)
2 users (show)

See Also:
Source RPM: pidgin
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Kristoffer Grundström 2016-10-17 00:10:37 CEST 
Description of problem: I just installed Mageia 6 (Cauldron) using the small network installation iso and I only choose to install Plasma5 as DE. As soon as I run Pidgin from Terminal I see Gtk-Message: Failed to load module "canberra-gtk-module". What does that error cause with the gui?

Version-Release number of selected component (if applicable): 2.11.0

How reproducible: Everytime.

Steps to Reproduce:
1. Install Mageia 6 (Cauldron) with the network installation iso.
2. Choose to install Plasma5 as the only DE.
3. Make sure you're updated once you're logged in.
4. Open a Terminal window and login as root.
5. Type urpmi pidgin --auto and press Enter/Return button.
6. Type exit and press Enter/Return button.
7. Now type pidgin and press Enter/Return button.
8. Voila! You'll get a GUI for Pidgin, but in the terminal you read Gtk-Message: Failed to load module "canberra-gtk-module".
Kristoffer Grundström 2016-10-17 00:10:46 CEST

CC: (none) => hamnisdude

Comment 1 Charles Edwards 2016-10-17 00:20:20 CEST 
This is a duplicate of bug # 3536

https://bugs.mageia.org/show_bug.cgi?id=3536

*** This bug has been marked as a duplicate of bug 3536 ***

Status: NEW => RESOLVED
CC: (none) => cae
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.