Hide Forgot
Description of problem: libnotifymm shouldn't link or require gtkmm2. At the very least, make it >= gtkmm2. GTK3 Applications that try to use libnotifymm-devel will end up trying to link against both GKT2 and GTK3, and that isn't allowed. There is some weird discrepancy between libnotifymm and libnotifymm-devel, where the -devel requires gtk, but the normal package doesn't. Here is the output of pkg-config (notice linking against gtkmm-2.4) #pkg-config --libs libnotifymm-1.0 -pthread -lnotifymm-1.0 -lgtkmm-2.4 -lnotify -latkmm-1.6 -lgdkmm-2.4 -lgiomm-2.4 -lpangomm-1.4 -lgtk-x11-2.0 -lglibmm-2.4 -lcairomm-1.0 -lsigc-2.0 -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lpangocairo-1.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 But let's look what is actually required in the .so (notice the lack of gtkmm): ldd /usr/lib64/libnotifymm-1.0.so linux-vdso.so.1 => (0x00007fff315ff000) libglibmm-2.4.so.1 => /usr/lib64/libglibmm-2.4.so.1 (0x00007f120aeb1000) libsigc-2.0.so.0 => /usr/lib64/libsigc-2.0.so.0 (0x00007f120acac000) libnotify.so.4 => /usr/lib64/libnotify.so.4 (0x00007f120aaa3000) libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007f120a854000) libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f120a534000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f120a22c000) libc.so.6 => /lib64/libc.so.6 (0x00007f1209e77000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f1209c62000) libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007f1209a5c000) libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x00007f1209858000) librt.so.1 => /lib64/librt.so.1 (0x00007f1209650000) libm.so.6 => /lib64/libm.so.6 (0x00007f12093cb000) libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007f12091a9000) libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x00007f1208e69000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f1208c4c000) libffi.so.5 => /usr/lib64/libffi.so.5 (0x00007f1208a44000) /lib64/ld-linux-x86-64.so.2 (0x00007f120b342000) libdl.so.2 => /lib64/libdl.so.2 (0x00007f120883f000) libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x00007f1208618000) libz.so.1 => /lib64/libz.so.1 (0x00007f1208401000) libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f12081e1000) libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f1207fc5000) Version-Release number of selected component (if applicable): 0.6.1
Upstream libnotifymm requires both gtkmm24 and libnotify 0.6.x, while i was working on fixing this upstream, someone did push a stupid patch that makes it work with libnotify 0.7 but without removing now useless API. Due to Gdk::PixBuf dependency which is not available in a separate library , a fixed up libnotifymm will either requires gtkmm24 or gtkmm30. Nobody should use this bizarre package for new developments with gtkmm30 toolkit
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.