Bug 75855

Summary:	AmaroK exits when the analyzer is clicked multiple times
Product:	[Applications] amarok	Reporter:	Axel <axelotto>
Component:	general	Assignee:	Mark Kretschmann <kretschmann>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version First Reported In:	0.9-beta1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Axel 2004-02-22 19:14:25 UTC

Version:           0.9-beta1 (using KDE KDE 3.2.0)
Installed from:    SuSE RPMs
OS:          Linux

Click the analyzer a few times.
The analyzer change mode the first time. Then it exits.

Comment 1 Max Howell 2004-02-23 01:29:04 UTC

Sounds like amarok is crashing. Can you tell us what is reported when you run amarok from a Konsole? Thanks.

Comment 2 Axel 2004-02-23 23:50:44 UTC

Here is the whole output:

axel@NL04-129-197:~> amarok
QMetaObject::findSignal:KFileDetailView: Conflict with QListView::doubleClicked(QListViewItem*,const QPoint&,int)
QMetaObject::findSignal:KFileDetailView: Conflict with QListView::doubleClicked(QListViewItem*,const QPoint&,int)
mcop warning: user defined signal handler found for SIG_PIPE, overriding
axel@NL04-129-197:~> TagLib: ID3v2.4 no longer supports the frame type TSIZ.  It will be discarded from the tag.
Unable to resolve GL/GLX symbols - please check your GL library installation.

axel@NL04-129-197:~>

Comment 3 Max Howell 2004-02-23 23:57:14 UTC

Seems that your Qt installation is in someway mucked up. I recommend fixing your Qt, or more easy, re-compiling amaroK without OpenGL support. Do to this compile with:

./configure --without-opengl

and then make as usual. This should solve your problems. I hope you try it so we can confirm this is the problem. Many thanks :-)

Comment 4 Mark Kretschmann 2004-02-24 09:05:15 UTC

As a side note, I wonder where this stuff comes from, and what it means:

> QMetaObject::findSignal:KFileDetailView: Conflict with
> QListView::doubleClicked(QListViewItem*,const QPoint&,int)

(this is not directly related to the poster's bug report.)

Comment 5 Max Howell 2004-02-24 16:00:31 UTC

That signal conflict is somewhere in the FileBrowser (or so I have been thinking).

Comment 6 Mark Kretschmann 2004-03-01 05:43:45 UTC

Seems to be caused by a hosed OpenGL setup on the poster's system. Since no additional comments followed, I'm closing it.

Comment 7 Anil Kumar Sharma 2005-07-08 08:37:10 UTC

This is happening again with me on fedora core 4.
I installed amarok via rpm's all for fc4 
amarok
amarok-akode
amarok-arts
amarok-visualizations
What I need to submit more to u.