Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#36919 - [amarok] segfault upon start

Attached to Project: Arch Linux
Opened by George (gh403) - Friday, 13 September 2013, 19:11 GMT
Last edited by Andrea Scarpino (BaSh) - Tuesday, 14 October 2014, 16:42 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Ronald van Haren (pressh)
Andrea Scarpino (BaSh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
When launching Amarok, it immediately segfaults without getting as far as displaying the main window. I've tried deleting all the Amarok-related config files in .kde4/.

Additional info:
* package version: amarok-2.8.0-1
* KDE-generated backtrace attached

Steps to reproduce:
- Install Amarok
- Launch Amarok
   amarok-20130913-140438.kcrash... (15.2 KiB)
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Tuesday, 14 October 2014, 16:42 GMT
Reason for closing:  No response
Comment by George (gh403) - Friday, 13 September 2013, 19:12 GMT
Note that disabling desktop effects allows Amarok to launch.
Comment by Mark Kretschmann (mark_kretschmann) - Saturday, 14 September 2013, 07:23 GMT
It's an issue with your Intel graphics driver. If you disable the analyzer visualization applet, it will also work with compositing.

That said, I would rather see this issue solved for all users (I'm an Amarok developer).
Comment by Jan de Groot (JGC) - Saturday, 14 September 2013, 09:25 GMT
Mark, any upstream bug known for this? Probably a bug in mesa, as 965-dri is in the backtrace.
Comment by Mark Kretschmann (mark_kretschmann) - Saturday, 14 September 2013, 09:36 GMT
I don't know of any, but I'm not very familiar with such issues either. The odd thing is, Amarok is only doing fairly simple drawing operations. No shaders, and nothing advanced. The crash happens with a plain drawPixmap() call, so that's pretty much the most basic operation there is. I wonder how compositing or anything else with OpenGL works for the user at all.
Comment by Mark Kretschmann (mark_kretschmann) - Monday, 28 October 2013, 20:42 GMT
We have a patch to work around this issue. The fix will also be featured in Amarok 2.8.1. If you require it earlier, please let me know.
Comment by Andrea Scarpino (BaSh) - Monday, 28 October 2013, 21:02 GMT
Sure, link it so we can apply it.
Comment by Gerardo Exequiel Pozzi (djgera) - Wednesday, 12 February 2014, 02:54 GMT
  • Field changed: Status (Assigned → Waiting on Response)
  • Field changed: Category (Packages: Extra → Upstream Bugs)
status?

Loading...