This forum has been archived. All content is frozen. Please use KDE Discuss instead.

amaroK 1.0-beta4 kills KDE

Tags: None
(comma "," separated)
Joe Innes
Karma
0

amaroK 1.0-beta4 kills KDE

Wed Feb 02, 2005 7:10 am
Whenever I start up amaroK after having upgraded to the latest release, my KDE dies, but not spectacularly; it looks like it has been told to logout. I\'ve tried to direct the std output to a file to see where it goes wrong, but when I get back into KDE, the file is empty.

I had only just got beta3 working properly as well ;o)

Any help would be greatly appreciated.

Mandrake 10.1

Joe
Flextron
Karma
0

Re:amaroK 1.0-beta4 kills KDE

Thu Feb 03, 2005 3:18 am
I can cofirm this. Amarok kills X server (In my case it\'s since beta3)

No output is available. SuSE 9.1 X.org
User avatar
Max Howell
Alumni
Posts
195
Karma
0

Re:amaroK 1.0-beta4 kills KDE

Thu Feb 03, 2005 8:04 am
Well without any output or anything, there\'s not much I can suggest. For one it is a flaw in your XServer, there\'s no way amaroK should be able to kill it just be using it.

I reckon it\'s openGL related. Rebuild ./configure --without-opengl opengl seems to be the cause of many issues like these.
PeteD
Karma
0

Re:amaroK 1.0-beta4 kills KDE

Thu Feb 03, 2005 9:14 pm
Just had the same thing. Beta4 linked from http://www.gkmweb.com/amarok only happened when a playlist had finished the last track. Screen went black and I got a kde login screen and now I can\'t restart amarok (no other instances of it running). I can\'t remember if I\'ve let a playlist finish before :( Only other thing i\'ve done today is update Foxytunes http://www.iosart.com/foxytunes/firefox/ to the latest version.

Anyone else who is having this problem using the latest (1.1) Foxytunes?
Flextron
Karma
0

Re:amaroK 1.0-beta4 kills KDE

Thu Feb 03, 2005 11:07 pm
PeteD wrote:
Only other thing i\'ve done today is update Foxytunes http://www.iosart.com/foxytunes/firefox/ to the latest version.

Anyone else who is having this problem using the latest (1.1) Foxytunes?

Ops!, I forgot to say that I also use foxytunes and gnome-settings-daemon. If I don\'t use Firefox and don\'t run gnome-settings-daemon, I can\'t reproduce the problem. I will try with Firefox but without using gnome-settings-daemon and see what happens.

PD: ¿Maybe the changes in the dcop interface affected foxytunes? As I said in my previous post, beta3 seems to be quite stable.
Joe Innes
Karma
0

Re:amaroK 1.0-beta4 kills KDE

Mon Feb 14, 2005 5:13 am
Thanks to the people who helped- however in the meantime, I switched to SuSE, and now, it works just fine :laugh: Thanks guys!

Joe
PeteD
Karma
0

Re:amaroK 1.0-beta4 kills KDE

Mon Feb 14, 2005 6:10 pm
@Joe Did you use foxytunes at all when it was dropping out of KDE?

I contacted the foxytunes author and he\'s looking into it because it only seems to happen for me with the latest foxytunes,
Iosart
Karma
0

Re:amaroK 1.0-beta4 kills KDE

Tue Feb 15, 2005 6:40 am
PeteD wrote:
@Joe Did you use foxytunes at all when it was dropping out of KDE?

I contacted the foxytunes author and he\'s looking into it because it only seems to happen for me with the latest foxytunes,

Hi,

I\'m the FoxyTunes author.

The only thing that has changed in the new version of FoxyTunes is that I added a call to \'artist()\' to get the name of the current track artist.
This is exactly the place where the problem seems to happen. Sending this command to Amarok seems to crash both the DCOP client and later the whole KDE/X Server.

I\'m not able to reproduce the problem on FC2. Most of the reports seem to be coming from Mandrake 10.1 users.

Amarok developers - any ideas what this can be?
User avatar
Max Howell
Alumni
Posts
195
Karma
0

Re:amaroK 1.0-beta4 kills KDE

Tue Feb 15, 2005 10:57 am
That\'s absolutely amazing! The artist function is really nothing special. Here\'s a section of the code:

[code:1]
QString DcopPlayerHandler::nowPlaying()
{
return EngineController::instance()->bundle().prettyTitle();
}

QString DcopPlayerHandler::artist()
{
return EngineController::instance()->bundle().artist();
}

QString DcopPlayerHandler::title()
{
return EngineController::instance()->bundle().title();
}

QString DcopPlayerHandler::track()
{
return EngineController::instance()->bundle().track();
}
[/code:1]

So you see, it does nothing out of the ordinary. The artist() function for the bundle() just returns a QString, it is a simple inline const function:

[code:1]
QString artist() const { return m_artist; }
[/code:1]

So I can\'t understand how it could have such disasterous consequences...
Pavel Benisek
Karma
0

Re:amaroK 1.0-beta4 kills KDE

Fri Feb 25, 2005 3:39 am
i am using Gentoo Linux and have same problems :( Sometimes it kills KDE and Xorq. I tried it under I hope for updade ASAP, becouse I really love this player :)

cat ~/.xsession-errors
[code:1]
kdecore (KAction): WARNING: KAction::insertKAccel( kaccel = 0x820e6a8 ): KAccel object already contains an action name \"del\"
QWidget::«»setMinimumSize: The smallest allowed size is (0,0)
QWidget::«»setMinimumSize: The smallest allowed size is (0,0)
QWidget::«»setMinimumSize: The smallest allowed size is (0,0)
No running windows found
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
QPixmap: Cannot create a QPixmap when no GUI is being used
*** loading the extensions datasource
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: PKCS7_content_free
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_conf
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_noconf
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: PKCS7_content_free
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_conf
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_noconf
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: PKCS7_content_free
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_conf
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_noconf
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x800020
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x800020
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x800020
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 20
Minor opcode: 0
Resource id: 0x800020
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: PKCS7_content_free
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_conf
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_noconf
kopete: WARNING: [static QString KopeteMessage::decodeString(const QCString&, const QTextCodec*, bool*)] Unable to decode string using provided codec(s), taking best guesses!
kopete: WARNING: [static QString KopeteMessage::decodeString(const QCString&, const QTextCodec*, bool*)] Unable to decode string using provided codec(s), taking best guesses!
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: PKCS7_content_free
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_conf
kdecore (KLibLoader): WARNING: KLibrary: /usr/lib/libcrypto.so.0.9.7: undefined symbol: OpenSSL_add_all_algorithms_noconf
QGArray::find: Index 0 out of range
[/code:1]
amaroklover
Karma
0

Re:amaroK 1.0-beta4 kills KDE

Tue Mar 08, 2005 6:54 am
hi,
same problem here with debian sarge and amarok 1.1.1. Im also using foxytunes. Sometimes it crashes even when i\'m starting amarok and 100% when the playlist reaches the end. :blink:


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], rockscient