After upgrading from Mageia 5, trying to run Amarok results in an immediate crash.
Created attachment 8286 [details]
KDE Crash handler log with backtrace
Fortunately, unlike with ksmserver when I first logged in, the file save dialog worked fine this time in the KDE Crash handler.
Side note, right-clicking an ogg file in Dolphin and choosing Open With > shows Amarok...twice.
Still valid with amarok-2.8.90-3.mga6 which is synced with Fedora including upstream bugfixes. I guess this is broken in Fedora too?
On my Cauldron VM at home, Amarok actually doesn't give a crash dialog when you try to run it. However, it either takes a really long time to start, or takes several attempts at starting it for it to actually run.
I'm not sure why it crashed at work and runs here.
Also, the Phonon settings needed to be fixed to prefer Default instead of pulse, otherwise Amarok wouldn't play any sound (even though Clementine was fine).
*** Bug 19327 has been marked as a duplicate of this bug. ***
Here in my cauldron system it doesn't crash and plays music fine. I haven't started amarok before today.
Does not affect everyone (only David could reproduce for now) so lowering priority by one step.
Please open new bug reports for the Phonon setting issue and also for the fact that opening the Phonon settings from Amarok seems to just loop forever.
*** Bug 20125 has been marked as a duplicate of this bug. ***
(In reply to Samuel Verschelde from comment #7)
> Does not affect everyone (only David could reproduce for now) so lowering
> priority by one step.
> Please open new bug reports for the Phonon setting issue and also for the
> fact that opening the Phonon settings from Amarok seems to just loop forever.
Ahh, it turns out I did already open a bug for that at Bug 19691.
This bug continues today.
Intel Core i7-2600K Sandy Bridge 3.4GHz
GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo
GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB
RTL8111/8168B PCI Express 1Gbit Ethernet
DRAM 16GB (4 x 4GB)
Mageia 6 64-bit, Nvidia driver
Backtrace looks similar to the vlc cache bug 17060. Try running as root:
/usr/lib64/vlc/vlc-cache-gen -f /usr/lib64/vlc/plugins/
See if that fixes it.
I think this is a bug with vlc.
On my main desktop, Amarok doesn't crash
I rarely run Amarok on my laptop, but it crashed with the same backtrace posted.
Running vlc-cache-gen segfaults, but Amarok is then able to start.
I think the backtrace shows that the crash happens when VLC is trying to load a plugin module.
(In reply to Curtis Hildebrand from comment #12)
> I think this is a bug with vlc.....
It wouldn't surprise me that this bug and the vlc bug:
the cause is the same or very related.
Today Amarok on M6, 64-bit, Plasma is running just fine on my nvidia
video editing platform. This is a change from just a few days ago.
What change(s) made this happen?
seems to be a dupplicate of bug 20020 as
/usr/lib64/vlc/vlc-cache-gen /usr/lib64/vlc/plugins/ fixes the issue
*** This bug has been marked as a duplicate of bug 20020 ***