Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install 64-bit Mageia-6-sta2 (Plasma) on UEFI/GPT HP 450-G2 Probook 2. Start kompozer 3. kompozer segfaults 4. Install lib64canberra-gtk0 (gtk3_0 version already installed) 5. start kompozer again 3. kompozer no-ops (see attached trace)
Created attachment 8898 [details] strace of kompozer no-op Result of 'strace kompozer' no-op
CC: (none) => wilcal.int
Assigning to all packagers collectively, since there is no registered maintainer for this package.
CC: (none) => marja11Assignee: bugsquad => pkg-bugsSummary: kompozer does not start => kompozer does not start (segfaults)
Just to make it clear, the canberra lib actually has nothing to do with this, and even if you don't install that, it's just a warning that you can safely ignore. It is annoying though :o).
OK - but ignoring it doesn't seem to get kompozer to start!
On my nVidia desktop with latest Mageia-6-sta2 fully updated, I still get the 'canberra' error, but then kompozer does start. Same error message with the same Mageia-6-sta2 .iso on laptop, except that kompozer does NOT then start...
Just done fresh Plasma install of the 30/6 64-bit Mageia-6 on UEFI GPT HP Probook laptop. Kompozer fails to start: "Gtk-Message: Failed to load canberra-gtk-module" Looking in Bug 15176 I saw that installing lib64canberra-gtk0 might fix it, but after installing that I now see: '(kompozer-bin:22345) Gtk-WARNING: **: Unable to locate theme engine in module-path: "adwaita" ' So Kompozer unusable here... Is there really no fix?
I have seen this in the past but lately for me Kompozer has been working just fine in Plasma.
Mystery solved! After deleting old ~/.kompozer.net directory, although Kompozer still flashes up: "Gtk-Message: Failed to load canberra-gtk-module" it does then start... So the remaining mystery is only: Why does it report: "Gtk-Message: Failed to load canberra-gtk-module" ?
Marking as WFM as it works for you. The warning can be safely ignored, as David said in comment 3. Many applications throw this warning.
Resolution: (none) => WORKSFORMEStatus: NEW => RESOLVED