Firefox/Thunderbird problem with missing symbol in libstartup-notification-1-0

First, I am not quite sure whether this truly belongs in this sub-forum or if I should rather post it in Applications. I do use Tumbleweed X86_64 with 12.1 as a base, but neither Firefox/Thunderbird nor libstartup-notification-1-0 are part of the Tumbleweed repository but come both from the normal update-openSUSE-current instead.

Anyways, my problem:

Thunderbird & Firefox do not start when called via krunner, kmenu or shortcuts, they however do start when invoked from konsole, without additional output…This behaviour persists with both Thunderbird/Firefox versions from the update-openSUSE-current and the current beta from the mozilla/beta-repository

So…onwards to the problem, I know what the problem is, but the solution escapes me, apart from compiling libstartup-notification-1-0 myself, which I would rather like to avoid


Linux rmk2 3.2.1-3-desktop #1 SMP PREEMPT Fri Jan 13 10:38:45 UTC 2012 (2eca2bf) x86_64 x86_64 x86_64 GNU/Linux
sh-4.2$ thunderbird -v
 Thunderbird 10.0

sh-4.2$ firefox -v
Mozilla Firefox 10.0
sh-4.2$ cat .xsession-errors | tail -3
(Parent is Solid::Backends::UDisks::UDisksDevice(0xb1a560), parent's thread is QThread(0x615970), current thread is ThreadWeaver::Thread(0x9ac000)
/usr/lib64/firefox/firefox-bin: symbol lookup error: /usr/lib64/ undefined symbol: xcb_aux_get_screen
/usr/lib64/thunderbird/thunderbird-bin: symbol lookup error: /usr/lib64/ undefined symbol: xcb_aux_get_screen
sh-4.2$ ldd -r /usr/lib64/firefox/firefox-bin =>  (0x00007fffea8b7000) => /lib64/ (0x00007f46a6cb5000) => /usr/lib64/ (0x00007f46a69ab000) => /lib64/ (0x00007f46a678e000) => /lib64/ (0x00007f46a63ff000)
        /lib64/ (0x00007f46a6eb9000) => /lib64/ (0x00007f46a61a8000) => /lib64/ (0x00007f46a5f92000)
sh-4.2$ ldd -r /usr/lib64/thunderbird/thunderbird-bin =>  (0x00007fff669cf000) => /lib64/ (0x00007f893fea6000) => /usr/lib64/ (0x00007f893fca3000) => /usr/lib64/ (0x00007f893fa63000) => /usr/lib64/ (0x00007f893f836000) => /usr/lib64/ (0x00007f893f4fc000) => /usr/lib64/ (0x00007f893f2d6000) => /usr/lib64/ (0x00007f893f0d2000) => /usr/lib64/ (0x00007f893eecd000) => /usr/lib64/ (0x00007f893ec8f000) => /lib64/ (0x00007f893ea8b000) => /usr/lib64/ (0x00007f893e863000) => /lib64/ (0x00007f893e61e000) => /usr/lib64/ (0x00007f893e3ce000) => /usr/lib64/ (0x00007f893e1c9000) => /lib64/ (0x00007f893dfc1000) => /usr/lib64/ (0x00007f893dcc9000) => /usr/lib64/ (0x00007f893d9bf000) => /lib64/ (0x00007f893d768000) => /lib64/ (0x00007f893d552000) => /lib64/ (0x00007f893d1c3000)
        /lib64/ (0x00007f89400c3000) => /lib64/ (0x00007f893cfab000) => /usr/lib64/ (0x00007f893cc67000) => /usr/lib64/ (0x00007f893ca5f000) => /lib64/ (0x00007f893c821000) => /usr/lib64/ (0x00007f893c61d000) => /lib64/ (0x00007f893c3ff000) => /lib64/ (0x00007f893c1e8000)
sh-4.2$ ldd -r /usr/lib64/
undefined symbol: xcb_aux_get_screen    (/usr/lib64/ =>  (0x00007fff679ed000) => /usr/lib64/ (0x00007fc93b183000) => /usr/lib64/ (0x00007fc93af81000) => /usr/lib64/ (0x00007fc93ad63000) => /lib64/ (0x00007fc93a9d4000) => /usr/lib64/ (0x00007fc93a7d0000)
        /lib64/ (0x00007fc93b5b8000)

So Firefox (and for that matter, Thunderbird) tell me that libstartup-notification-1-0 lacks the symbol xcb_aux_get_screen, and ldd seems to agree

Any ideas or suggestions on how to fix this?

I have the same problem here (on i586 though) - also using Tumbleweed but additionally the X11:XOrg, KDF and some more repositories and thought that the upgraded XOrg might be causing it.
DO you also have X11:XOrg enabled?

Mhm…as a matter of fact, I do. The question would then be which end breaks it, X11 or libstartup-notification-1-0 (which is not part of X11). Let’s see if someone else chimes in or if we are the two lucky people with a (different…) constellation that breaks (the same…) things :wink:
X11:XOrg could be the problem

Oh, lovely! The temporary workaround with “export LD_PRELOAD=/usr/lib64/” into /etc/profile.local worked.

Now, on Factory it apparently was resolved by a repository-side rebuild. I think X11: XOrg for 12.1 needs the same…

But this at least solves the problem temporarily until the underlying cause is fixed! Thanks! :slight_smile: