Summary: | crash when selecting an analyser using openGL hardware acceleration using the nvidia drivers 1.0.6111 | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | aurelien grosdidier <agrosdidier> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 1.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
aurelien grosdidier
2004-09-29 09:39:31 UTC
This is almost certainly a Qt issue for you. Try another application that uses GL and is based on Qt. I think perhaps KStars does. Please write back soon! KStars works fine if it's slow. I also checked out http://boson.eu.org/, which is supposed to use Qt and OpenGL, and it works fine and fast. The previous version of amarok i used (1.0.x) worked perfectly. Glad to see someone else is interested in solving this bug :) I had the same problem running on trident CyberBladeXP card. Just try to remove line beggining with 'Current Analyzer=' from ~/.kde/share/config/amarokrc. It worked for me. Editing ~/.kde/share/config/amarokrc works, meaning that amarok can be launched without crashing, but choosing an openGL analyzers still lead to a crash. So for me it's just a workaround, and not a solution. :( that's true - it is only workaround, but still may be usable for people that want to see Amarok working (at all). Before upgrading kde 3.2.3 to 3.3 everything worked fine. My computer runs Mandrake 10.0 Official ("commercial" version) and kde 3.3 from thac rpm repository. All we do is use QGLWidget. I can't see how this can be anything but a Qt issue. Still please provide a backtrace so we can be sure: % gdb amarokapp (gdb) run <make amarok crash> (gdb)bt Then paste the backtrace here, thanks. (gdb) bt No stack. :( ? I don't think KStars uses GL widgets actually. Could you try this little applet out, it's tiny and easy to compile: http://kde-apps.org/content/show.php?content=10583 I'm certain that uses QGlWidget. Thanks. Right, kcube is not working, meaning that the applet remains empty... i guess there is a progress here :) The question now is : why was amarok 1.0.x working and not this release ? arhh, right now I have fully working amarok 1.1 and I'm unable to recreate crash. As I remember all I've done was updating kde 3.3 rpms from thac repository. Sorry, no gdb output, but the good side is that bug is gone for good:) seems like the problem is solved using the binary rpms of kde 3.3.1 for fedora2 @ ftp://ftp.kde.org/pub/kde/stable/3.3.1/RedHat/Fedora2/i386/ :) woups, this bug is now resolved :) |