Summary: | Amarok crashes at launch after latest update | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | fishears <f1she4rs> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | blumberg.christian, carlos.escobedo.olivares, davi87, diego.ml, djdunn.safety, jam, jherrera_93, jhnnslschnr, kaleemsagard, mae.lippert, marcos.brito.carvalho, matej, mirvana-dmitry, mr.soup12, nalakahewapathirana, pacific1996, popmysoul, rdieter, skystarfoxwolf, thomas.bettler, xms-00 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 2.8.0 | ||
Target Milestone: | 2.9 | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/amarok/d2fef6cb1a0293a000edbf87fd566574b6e8ae51 | Version Fixed In: | 2.8.1 |
Attachments: |
amarok-crash.log
Amarok debug output New crash information added by DrKonqi |
Description
fishears
2013-08-17 13:13:35 UTC
Can you please start Amarok from console as: amarok --nofork (suprisingly, without the --debug flag) to see any possible X errors that may be printed? Done. Here's the output: bash-4.2$ amarok --nofork QCoreApplication::postEvent: Unexpected null receiver QCoreApplication::postEvent: Unexpected null receiver QCoreApplication::postEvent: Unexpected null receiver loaded the Generic plugin QWidget::insertAction: Attempt to insert null action X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 7 (X_ReparentWindow) Resource id: 0x6e00111 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 7 (X_ReparentWindow) Resource id: 0x6e00111 X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 7 (X_ReparentWindow) Resource id: 0x6e00111 X Error: RenderBadPicture (invalid Picture parameter) 141 Extension: 138 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x9e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 10 (X_UnmapWindow) Resource id: 0x6e00094 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 (X_ReparentWindow) Resource id: 0x6e00094 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x6e00094 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 4 (X_DestroyWindow) Resource id: 0x6e00094 X Error: RenderBadPicture (invalid Picture parameter) 141 Extension: 138 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x6e00094 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 10 (X_UnmapWindow) Resource id: 0x6e00096 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 (X_ReparentWindow) Resource id: 0x6e00096 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x6e00096 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 4 (X_DestroyWindow) Resource id: 0x6e00096 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 10 (X_UnmapWindow) Resource id: 0x6e00098 X Error: RenderBadPicture (invalid Picture parameter) 141 Extension: 138 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x6e00098 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 10 (X_UnmapWindow) Resource id: 0x6e00098 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 (X_ReparentWindow) Resource id: 0x6e00098 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 7 (X_ReparentWindow) Resource id: 0x6e0009b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 (X_GetProperty) Resource id: 0x6e00098 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 4 (X_DestroyWindow) Resource id: 0x6e00098 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 12 (X_ConfigureWindow) Resource id: 0x6e0009b Could not parse stylesheet of widget 0x235fd30 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 12 (X_ConfigureWindow) Resource id: 0x6e0009b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 12 (X_ConfigureWindow) Resource id: 0x6e0009b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 12 (X_ConfigureWindow) Resource id: 0x6e0009b X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension: 152 (Uknown extension) Minor opcode: 3 (Unknown request) Resource id: 0x6e0009b X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension: 152 (Uknown extension) Minor opcode: 12 (Unknown request) Resource id: 0x6e0009b X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Extension: 152 (Uknown extension) Minor opcode: 7 (Unknown request) Resource id: 0x6e0009b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 8 (X_MapWindow) Resource id: 0x6e0009b ********************************************************************************************** ** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: ** ** amarok --debug ** ********************************************************************************************** KCrash: Application 'amarok' crashing... KCrash: Attempting to start /usr/libexec/kde4/drkonqi from kdeinit sock_file=/home/jb/.kde/socket-localhost.localdomain/kdeinit4__0 [1]+ Stopped amarok --nofork Setting status correctly. Hmm, this is definitely not the EGL bug unless I'm wrong. I still suspect something with OpenGL/analyzers. Markey? Definitely an OpenGL rendering issue, but not in our software. It must be somewhere higher upstream. Does OpenGL work fine for you with other Qt applications? *** Bug 323824 has been marked as a duplicate of this bug. *** Same behaviour here with amarok-2.7 and amarok-2.8 on gentoo after updating to kdelibs-4.11 et al: Crash Message X Error: BadMatch (invalid parameter attributes) 8 Major opcode: 1 (X_CreateWindow) Resource id: 0x9a0005f X Error: BadWindow (invalid Window parameter) 3 Major opcode: 3 (X_GetWindowAttributes) Resource id: 0x9a00061 KCrash: Application 'amarok' crashing... Created attachment 81896 [details]
amarok-crash.log
Created attachment 81903 [details]
Amarok debug output
Think I have the same issue after upgrades. After starting Amarok would go into system tray, but when I click on it, it will crash.
amarok --version
Qt: 4.8.4
KDE Development Platform: 4.11.00
Amarok: 2.8.0
Attached log files ->
amarok_debug.log with --debug flag
Output with --nofork flag
amarok --nofork
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
[0x1182c78] main services discovery error: no suitable services discovery module
WARNING: Phonon::createPath: Cannot connect Phonon::MediaObject ( no objectName ) to Phonon::AudioDataOutput ( no objectName ).
Object::connect: No such signal Phonon::VLC::MediaObject::angleChanged(int) in ../../phonon/mediacontroller.cpp:64
Object::connect: No such signal Phonon::VLC::MediaObject::availableAnglesChanged(int) in ../../phonon/mediacontroller.cpp:65
QWidget::insertAction: Attempt to insert null action
**********************************************************************************************
** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: **
** amarok --debug **
**********************************************************************************************
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 7 (X_ReparentWindow)
Resource id: 0x4600169
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 7 (X_ReparentWindow)
Resource id: 0x4600169
X Error: BadMatch (invalid parameter attributes) 8
Major opcode: 7 (X_ReparentWindow)
Resource id: 0x4600169
X Error: RenderBadPicture (invalid Picture parameter) 143
Extension: 139 (RENDER)
Minor opcode: 7 (RenderFreePicture)
Resource id: 0x83
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 10 (X_UnmapWindow)
Resource id: 0x460005d
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 7 (X_ReparentWindow)
Resource id: 0x460005d
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x460005d
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 4 (X_DestroyWindow)
Resource id: 0x460005d
X Error: RenderBadPicture (invalid Picture parameter) 143
Extension: 139 (RENDER)
Minor opcode: 7 (RenderFreePicture)
Resource id: 0x460005d
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 10 (X_UnmapWindow)
Resource id: 0x460005f
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 7 (X_ReparentWindow)
Resource id: 0x460005f
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x460005f
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 4 (X_DestroyWindow)
Resource id: 0x460005f
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 10 (X_UnmapWindow)
Resource id: 0x4600061
X Error: RenderBadPicture (invalid Picture parameter) 143
Extension: 139 (RENDER)
Minor opcode: 7 (RenderFreePicture)
Resource id: 0x4600061
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 10 (X_UnmapWindow)
Resource id: 0x4600061
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 7 (X_ReparentWindow)
Resource id: 0x4600061
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 7 (X_ReparentWindow)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20 (X_GetProperty)
Resource id: 0x4600061
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 4 (X_DestroyWindow)
Resource id: 0x4600061
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
"/org/freedesktop/UDisks2/drives/HUAWEI_SD_Storage_HUAWEI_SD_Storage_0_3a0" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/hp_______CDDVDW_TS_L633N_R3186GBSB86695" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/HUAWEI_Mass_Storage_HUAWEI_Mass_Storage_0_3a0" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/SAMSUNG_HM501II_S24QJ9FB900813" : property "Drive" does not exist
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
Could not parse stylesheet of widget 0x15759e0
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 12 (X_ConfigureWindow)
Resource id: 0x4600064
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Extension: 153 (Uknown extension)
Minor opcode: 3 (Unknown request)
Resource id: 0x4600064
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Extension: 153 (Uknown extension)
Minor opcode: 12 (Unknown request)
Resource id: 0x4600064
X Error: BadDrawable (invalid Pixmap or Window parameter) 9
Extension: 153 (Uknown extension)
Minor opcode: 7 (Unknown request)
Resource id: 0x4600064
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 8 (X_MapWindow)
Resource id: 0x4600064
KCrash: Application 'amarok' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/nalaka/.kde/socket-ngsspot/kdeinit4__0
(In reply to comment #8) > Created attachment 81896 [details] > amarok-crash.log Thomas: please always paste backtraces in the comment, else those are not searchable. FWIW: your backtrace is quite different from the ones in this report, please file a separate bug for that, this is clearly not the same crash. To all others commenting on this report: please state the distribution you are using, the Qt version and KDE version, and whether you can use OpenGL in other Qt applications. Qt = 4.8.5 KDE = 4.10.5 OpenGL is working in other QT apps Hi Myriam, My operating system is "Ubuntu 13.04" Qt: 4.8.4 KDE Development Platform: 4.11.00 Amarok: 2.8.0 As I can remember this started to happen when I updated Amarok to 2.8. Amarok icon appears in system tray but when I click on it, it will crash. I'm going to install debug symbols required to build a proper automated bug report. But please guide us on this and I'm willing to provide information. (This is the first time I'm using bugtracking system) Thanks :) Created attachment 81980 [details]
New crash information added by DrKonqi
amarok (2.8.0) on KDE Platform 4.11.00 using Qt 4.8.4
- What I was doing when the application crashed:
After starting amarok from menu, it goes to systray. I clicked on systray icon and it crashed.
-- Backtrace (Reduced):
#6 0x00007fc58814a86d in get_stencil_miptree (irb=0x26c3f40) at brw_misc_state.c:325
#7 brw_workaround_depthstencil_alignment (brw=brw@entry=0x2416020) at brw_misc_state.c:341
#8 0x00007fc58811a320 in brw_try_draw_prims (max_index=3, min_index=0, ib=0x0, nr_prims=1, prim=0x7fffa62e5050, arrays=0x2452470, ctx=0x2416020) at brw_draw.c:442
#9 brw_draw_prims (ctx=0x2416020, prim=0x7fffa62e5050, nr_prims=1, ib=0x0, index_bounds_valid=<optimized out>, min_index=0, max_index=3, tfb_vertcount=0x0) at brw_draw.c:587
#10 0x00007fc57eb89954 in vbo_draw_arrays (ctx=0x2416020, mode=6, start=0, count=4, numInstances=1, baseInstance=<optimized out>) at ../../../../../src/mesa/vbo/vbo_exec_array.c:619
Thank you for the feedback. Apparently something is wrong with your OpenGL driver. Disabling the analyzer applet in $HOME/.kde/share/config/amarok_homerc is a possible workaround for now. Disabling analyzer allows me to launch Amarok successfully. Does that mean this is not an Amarok bug? (In reply to comment #15) > Disabling analyzer allows me to launch Amarok successfully. Does that mean > this is not an Amarok bug? Indeed, the problem is the OpenGL driver. I for example run Amarok on an Intel graphics card without these problems. It should be reported to your distribution. Thank you for your help resolving this. Hi Myriam Thanks a lot for the guidance. Disabling analyzer worked for me too. Disabling analyzer worked for me too. In addition, the analyzer work when activate it once the app is opened, but at restart it amarok crash again. @Christian: That's interesting. Thanks for the information. *** Bug 325797 has been marked as a duplicate of this bug. *** *** Bug 325845 has been marked as a duplicate of this bug. *** *** Bug 325894 has been marked as a duplicate of this bug. *** Git commit f4a3f4fcf59cc0c592bd6d703542cb162a19721c by Mark Kretschmann. Committed on 19/07/2013 at 08:37. Pushed by markey into branch 'master'. Rewrite Block Analyzer to use pure OpenGL instead of QGLPaintEngine2. This rewrite should fix a number of issues that users had, especially with Intel drivers. The issues, including crashes, are all due to driver bugs, but essentially they were triggered by Qt using some uncommon features for texture drawing (stencil operations, etc). This commit should be backported to 2.8.1. CCMAIL: amarok-devel@kde.org BACKPORT M +1 -0 ChangeLog M +12 -22 src/context/applets/analyzer/AnalyzerBase.cpp M +3 -19 src/context/applets/analyzer/AnalyzerBase.h M +1 -1 src/context/applets/analyzer/BallsAnalyzer.cpp M +1 -1 src/context/applets/analyzer/BallsAnalyzer.h M +82 -23 src/context/applets/analyzer/BlockAnalyzer.cpp M +9 -10 src/context/applets/analyzer/BlockAnalyzer.h M +1 -1 src/context/applets/analyzer/DiscoAnalyzer.cpp M +1 -1 src/context/applets/analyzer/DiscoAnalyzer.h http://commits.kde.org/amarok/f4a3f4fcf59cc0c592bd6d703542cb162a19721c Git commit d2fef6cb1a0293a000edbf87fd566574b6e8ae51 by Mark Kretschmann. Committed on 19/10/2013 at 14:48. Pushed by markey into branch 'master'. Fix rendering glitch introduced with commit f4a3f4f. BACKPORT M +22 -25 src/context/applets/analyzer/BlockAnalyzer.cpp M +26 -5 src/context/applets/analyzer/BlockAnalyzer.h http://commits.kde.org/amarok/d2fef6cb1a0293a000edbf87fd566574b6e8ae51 *** Bug 326443 has been marked as a duplicate of this bug. *** *** Bug 329841 has been marked as a duplicate of this bug. *** *** Bug 331669 has been marked as a duplicate of this bug. *** *** Bug 331669 has been marked as a duplicate of this bug. *** *** Bug 333417 has been marked as a duplicate of this bug. *** Setting status correctly. Git commit 351d723d4373f861c4943d06bb7c59ca1fe8495a by Vedant Agarwala, on behalf of Mark Kretschmann. Committed on 19/07/2013 at 08:37. Pushed by vedanta into branch 'tagguessing'. Rewrite Block Analyzer to use pure OpenGL instead of QGLPaintEngine2. This rewrite should fix a number of issues that users had, especially with Intel drivers. The issues, including crashes, are all due to driver bugs, but essentially they were triggered by Qt using some uncommon features for texture drawing (stencil operations, etc). This commit should be backported to 2.8.1. CCMAIL: amarok-devel@kde.org BACKPORT M +1 -0 ChangeLog M +12 -22 src/context/applets/analyzer/AnalyzerBase.cpp M +3 -19 src/context/applets/analyzer/AnalyzerBase.h M +1 -1 src/context/applets/analyzer/BallsAnalyzer.cpp M +1 -1 src/context/applets/analyzer/BallsAnalyzer.h M +82 -23 src/context/applets/analyzer/BlockAnalyzer.cpp M +9 -10 src/context/applets/analyzer/BlockAnalyzer.h M +1 -1 src/context/applets/analyzer/DiscoAnalyzer.cpp M +1 -1 src/context/applets/analyzer/DiscoAnalyzer.h http://commits.kde.org/amarok/351d723d4373f861c4943d06bb7c59ca1fe8495a Git commit 793e7c2c400326bd32102357c77ef5e1c51edfa5 by Vedant Agarwala, on behalf of Mark Kretschmann. Committed on 19/10/2013 at 14:48. Pushed by vedanta into branch 'tagguessing'. Fix rendering glitch introduced with commit f4a3f4f. BACKPORT M +22 -25 src/context/applets/analyzer/BlockAnalyzer.cpp M +26 -5 src/context/applets/analyzer/BlockAnalyzer.h http://commits.kde.org/amarok/793e7c2c400326bd32102357c77ef5e1c51edfa5 *** Bug 335541 has been marked as a duplicate of this bug. *** *** Bug 335620 has been marked as a duplicate of this bug. *** *** Bug 336809 has been marked as a duplicate of this bug. *** *** Bug 343334 has been marked as a duplicate of this bug. *** *** Bug 344131 has been marked as a duplicate of this bug. *** *** Bug 344378 has been marked as a duplicate of this bug. *** *** Bug 348819 has been marked as a duplicate of this bug. *** *** Bug 350430 has been marked as a duplicate of this bug. *** |