No, just file a new bug if it happens with the provided gnucash from the distribution. > this bug, my built GnuCash doesn't work? If yes, this bug is not just an > These messages are quite unclear to me, but doesn't it mean that, because of > gnc_main_window_setup_window: assertion failed: (filename)
FAILED TO LOAD MODULE CANBERRA GTK MODULE HOW TO
Because package can either contain "lib" or "lib64" I'm not sure how to do that. Last bit would be to have "rpmsrate-raw" ensure both rpm packages are on the installation media. I'm totally ok with someone figuring out a good solution and doing the work. For Mageia 5 the Recommends should avoid this message. > waste his/her time to explain that it is not the case. > it is the cause of the unrelated problem they have. (In reply to Henri de Solages from comment #30) These messages are quite unclear to me, but doesn't it mean that, because of this bug, my built GnuCash doesn't work? If yes, this bug is not just an "enhancement". Gnc.gui:ERROR./././src/gnome-utils/gnc-main-window.c:3604:gnc_main_window_setup_window: assertion failed: (filename) Gtk-Message: Failed to load module "canberra-gtk-module" The overwriting error message was: No such file or directory You must ensure an error is NULL before it's set. (process:4483): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory.
Moreover, since GnuCash in Mageia 4 is very buggy, I decided to compile the last one. Then someone else has to waste his/her time to explain that it is not the case. It means that this bug wastes thousand of people's time, leading them to think it is the cause of the unrelated problem they have. On the web, according to Google, there are 9880 pages including both this string and the word "Mageia". the sub-domains), including on 79 pages of. The string "Failed to load module 'canberra-gtk-module'" appears in 1230 pages within the site and its sub-sites (i.e. (And yes, I have several of the packages quoted in comment 13 installed on my system, but nevertheless do not get libcanberra-gtk0 installed simply as a dependency) $button->signal_connect (clicked => sub ) īut weird, I have a quite complex perl-Gtk application (which - necessarily - contains all the ingredients used in the small demo) and that runs perfectly even when the canberra module is not installed on my system: there are facettes of this problem which go beyond a missing require/suggest.
My $window = Gtk2::Window->new ('toplevel') The small demo from the Gtk3 manpage (converted back to Gtk2) fails with the message quoted in the bug description (Failed to load module "canberra-gtk-module), only runs if libcanberra-gtk0 is manually installed in addition to what has been installed at system generation - a nice example to put this problem into evidence.
0 kommentar(er)
