Description of problem:
Amarok goes into a loop at startup, issuing this message over and over:
QNativeImage: Unable to attach to shared memory segment.
It's still responsive to mouse clicks and all - just spending most of a CPU repeatedly issuing the message.
Traceback with gdb shows it's here:
#0 0x00007ff84d6df343 in __GI___poll (fds=<optimized out>, nfds=<optimized out>,
timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x0000003198408ba2 in ?? () from /usr/lib64/libxcb.so.1
#2 0x000000319840a16f in xcb_wait_for_reply () from /usr/lib64/libxcb.so.1
#3 0x0000003198045e7d in _XReply (dpy=0x24c0750, rep=0x7ffff61bd2d0, extra=0, discard=1)
#4 0x00000031980414f3 in XSync (dpy=0x24c0750, discard=0) at Sync.c:44
#5 0x00007ff84e5910cd in ?? () from /usr/lib64/libQtGui.so.4
#6 0x00007ff84e59de0f in QApplication::x11ProcessEvent(_XEvent*) ()
#7 0x00007ff84e5c5a3c in ?? () from /usr/lib64/libQtGui.so.4
#8 0x00007ff849aa3bcd in g_main_dispatch (context=0x2366a70) at gmain.c:2441
#9 g_main_context_dispatch (context=0x2366a70) at gmain.c:3011
#10 0x00007ff849aa43c8 in g_main_context_iterate (context=0x2366a70, block=<optimized out>,
dispatch=1, self=<optimized out>) at gmain.c:3089
#11 0x00007ff849aa459c in g_main_context_iteration (context=0x2366a70, may_block=1)
#12 0x00007ff84db5377f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#13 0x00007ff84e5c572e in ?? () from /usr/lib64/libQtGui.so.4
#14 0x00007ff84db23bd2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
#15 0x00007ff84db23e27 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
#16 0x00007ff84db28825 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#17 0x000000000040916e in ?? ()
#18 0x00007ff84d61962d in __libc_start_main (main=0x402230, argc=1, ubp_av=0x7ffff61c0758,
init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=
0x7ffff61c0748) at libc-start.c:226
#19 0x000000000040bd3d in _start ()
This set of RPMs is OK:
These (and more recent) are broken:
Although the traceback implicates Qt, it seems to be an amarok issue, I tested against all Qt4 and kdelibs releases in rawhide since July 1, and they all work with 2.4.1-3 but fail against 188.8.131.52.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.
(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)
More information and reason for this action is here:
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 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 change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.