If gnome-power-manager is run and libcanberra was compiled without gtk use flag, it crashes. Emerging libcanberra with gtk use flag fixes the problem. This dependancy should be enforced by ebuild. Reproducible: Always Steps to Reproduce: 1. Compile libcanberra without gtk use flag 2. Compile and run gnome-power-manager 3. It will now crash Actual Results: gnome-power-manager is allowed to be emerged without checking the gtk use flag of libcanberrra Expected Results: gnome-power-manager should not be allowed to compile until user compiles libcanberra with gtk flag gnome-power-manager 2.22.1 libcanberra 0.10 portage 2.2_rc14
I fail to see how 2.22 could use libcanberra since it releases started to appear after 2.22. Please provide emerge --info and readelf -d /usr/bin/gnome-power-manager (or maybe /usr/libexec/gnome-power-manager)
please get back to us.
Created attachment 172835 [details] output of emerge --info
Created attachment 172839 [details] output of readelf -d /usr/bin/gnome-power-manager
(In reply to comment #4) > Created an attachment (id=172839) [edit] > output of readelf -d /usr/bin/gnome-power-manager > this output might not be accurate. I took it afterwards on kde4. Interestingly, gnome-power-manager did not complain about libcanberra while I was on kde4. I wonder if I am missing something. On gnome it crashed saying that a library file was not found! I will try to reproduce the crash again and I'll post the new readelf output.
Ok so according to these info, g-p-m is actually not linking to libcanberra. Reading the code further, there is no call to libcanberra whatsoever in there. However it is using gstreamer to play some sounds but it's already dependending on that properly.
closing worksforme. Please reopen if you make it crash again with some strace or gdb backtrace attached. Thanks for reporting.
