Summary: | Amarok crashes on startup | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Landon R. Brainard <landon> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bugzilla, landon |
Priority: | NOR | Keywords: | drkonqi |
Version: | 2.8.0 | ||
Target Milestone: | 2.9 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Landon R. Brainard
2014-04-06 01:28:05 UTC
Created attachment 85971 [details]
New crash information added by DrKonqi
amarok (2.8.0) on KDE Platform 4.12.3 using Qt 4.8.5
I uninstalled amarok along with removing the data files and nothing changed. I don't know what's causing this.
-- Backtrace (Reduced):
#6 xcb_glx_query_server_string_string_length (R=R@entry=0x0) at glx.c:2448
#7 0x0000003302a427d5 in __glXQueryServerString (dpy=dpy@entry=0x1bdd7e0, opcode=<optimized out>, screen=screen@entry=0, name=name@entry=2) at glx_query.c:55
#8 0x0000003302a1d2ce in AllocAndFetchScreenConfigs (priv=0x2cbfd50, dpy=0x1bdd7e0) at glxext.c:764
#9 __glXInitialize (dpy=dpy@entry=0x1bdd7e0) at glxext.c:881
#10 0x0000003302a19a3b in GetGLXPrivScreenConfig (dpy=dpy@entry=0x1bdd7e0, scrn=scrn@entry=0, ppriv=ppriv@entry=0x7fffe8b75730, ppsc=ppsc@entry=0x7fffe8b75738) at glxcmds.c:174
The problem is your OpenGL not working with the visualizer. Two possiblities: use the phonon-backend-vlc instead or disable the visualizer in the $HOME/.kde/share/config/amarok_homerc file. FWIW: this is already fixed for a later release. *** This bug has been marked as a duplicate of bug 327150 *** (In reply to comment #2) > The problem is your OpenGL not working with the visualizer. Two > possiblities: use the phonon-backend-vlc instead or disable the visualizer > in the $HOME/.kde/share/config/amarok_homerc file. > > FWIW: this is already fixed for a later release. > > *** This bug has been marked as a duplicate of bug 327150 *** and which line in said file are we to tinker with? - It's not obvious to dumb old me. isn't that self-explaining? Look for the word "analyzer", should be in the plugins list at the very start of the file. |