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

Amarok 1.2.4 unstable with FC4

Tags: None
(comma "," separated)
Steinmb
Karma
0

Amarok 1.2.4 unstable with FC4

Wed Jul 13, 2005 12:22 am
Running:
amarok-1.2.4-6.fc4
amarok-visualisation-1.2.4-6.fc4
amarok-arts-1.2.4-6.fc4
amarok-akode-1.2.4-6.fc4

Have testet with xine and gstreamer engine, but it crashes with them both.
Removed all config from .kde that belongs to amarok.
I`m not able compile ver 1.3B2 cause to the blacklisting of gcc4.

Can anyone help me?

--
Stein Magne
Norway
steinmb
Karma
0

Re:Amarok 1.2.4 unstable with FC4

Wed Jul 13, 2005 12:24 am
A typical crash can look like this:
amarokapp
QObject::connect: Cannot connect Engine::Base::statusText( const QString& ) to (null)::shortMessage( const QString& )
QObject::connect: Cannot connect Engine::Base::infoMessage( const QString& ) to (null)::longMessage( const QString& )
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QColor::setRgb: RGB parameter(s) out of range
QColor::setRgb: RGB parameter(s) out of range
QColor::setRgb: RGB parameter(s) out of range
STARTUP
Very strange! got a DCOPReplyWait opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyDelayed opcode, but we were not waiting for a reply!
QWidget::setMinimumSize: The smallest allowed size is (0,0)
Caps negotiation succeeded with 44100 Hz @ 2 channels
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 7
Minor opcode: 0
Resource id: 0x3e008ef
terminate called after throwing an instance of \'std::bad_alloc\'
what(): St9bad_alloc
Segmentation fault
steinmb
Karma
0

Re:Amarok 1.2.4 unstable with FC4

Wed Jul 13, 2005 2:37 am
A typical crash can look like this:
amarokapp
QObject::connect: Cannot connect Engine::Base::statusText( const QString& ) to (null)::shortMessage( const QString& )
QObject::connect: Cannot connect Engine::Base::infoMessage( const QString& ) to (null)::longMessage( const QString& )
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
QColor::setRgb: RGB parameter(s) out of range
QColor::setRgb: RGB parameter(s) out of range
QColor::setRgb: RGB parameter(s) out of range
STARTUP
Very strange! got a DCOPReplyWait opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyDelayed opcode, but we were not waiting for a reply!
QWidget::setMinimumSize: The smallest allowed size is (0,0)
Caps negotiation succeeded with 44100 Hz @ 2 channels
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
X Error: BadWindow (invalid Window parameter) 3
Major opcode: 7
Minor opcode: 0
Resource id: 0x3e008ef
terminate called after throwing an instance of \'std::bad_alloc\'
what(): St9bad_alloc
Segmentation fault
Steinmb
Karma
0
Managed to compile 1.3 beta 2 now but same problem still.
compiled it with debug info on so i anyone could help out, we can make i work again.... ./configure --prefix=/home/steinmb/amarok_beta --enable-mysql --enable-debug=yes

Engines:
xine-lib-devel-1.0.1-2.2.fc4
xine-lib-1.0.1-2.2.fc4
xine-0.99.3-5.2.fc4
xine-skins-1.10-1.fcgstreamer-plugins-devel-0.8.8-6

gstreamer-monkeysaudio-0.8.0-1.2.fc4
gstreamer-tools-0.8.10-1
gstreamer-plugins-extra-audio-0.8.8-2.2.fc4
gstreamer-plugins-0.8.8-6
gstreamer-plugins-extra-video-0.8.8-2.2.fc4
gstreamer-plugins-extra-dvd-0.8.8-2.2.fc4
gstreamer-devel-0.8.10-1
gstreamer-0.8.10-1
gstreamer-ffmpeg-0.8.4.1-0.2.fc4

I`m getting this on startup:
amaroK: [Loader] Starting amarokapp..
amaroK: [Loader] Don\'t run gdb, valgrind, etc. against this binary! Use amarokapp.
QObject::connect: Cannot connect Engine::Base::statusText( const QString& ) to (null)::shortMessage( const QString& )
QObject::connect: Cannot connect Engine::Base::infoMessage( const QString& ) to (null)::longMessage( const QString& )
QLayout: Adding KToolBar/mainToolBar (child of QVBox/unnamed) to layout for PlaylistWindow/PlaylistWindow
[steinmb@stein bin]$ Very strange! got a DCOPReplyWait opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyDelayed opcode, but we were not waiting for a reply!
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
QObject::disconnect: Unexpected null parameter
QObject::connect: Cannot connect (null)::activePartChanged( KParts::Part * ) to KHTMLPart::slotActiveFrameChanged( KParts::Part * )
steinmb
Karma
0
Becoming a bad habit to answer my own posting :-)
Traced the crash i gdb and found it had problem with libtag. Removed a duplicate of libtag libaries :)

Reinstalled:
libtag
libtag-devel
tagid3
tagid3-devel

Recompiled 1.3 beta2 and are now enjoying a great program :-D Currently testing out the new mysql support.

--
Stein Magne
Norway
themaskedbear
Karma
0
Hi.

Thanks a lot for this thread.
I was having problems with some mp3 on differents versions of amarok and it allways finish by an amarok crash. I\'m using gentoo and for those who have enabled the \"debug\" flag (USE=debug emerge amarok) and have seen the error :

amarok: amaroK is crashing...
Very strange! got a DCOPReplyWait opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyDelayed opcode, but we were not waiting for a reply!

Try an \"emerge taglib\". And try to play a mp3 file with amarok :) It works fine for me now
Johnson
Karma
0

Re:Amarok 1.2.4 unstable with FC4

Thu Jan 19, 2006 7:06 pm
tried to re-emerge taglib and this solved the problem. Thanks a lot for the hint!
Mark Stosberg
Karma
0
Installing taglib fixed the same kind of problem for me, although I\'m using Mandriva 2006 and Amarok 1.3.8.

Thanks for the tip!

Mark


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]