Version: 1.2-beta3 (using KDE KDE 3.3.2) Installed from: SuSE RPMs Compiler: updated for KDE3.3.2 for SUSE9.1 OS: Linux I using xbindkeys to control amarok. with old versions 1.1.1 for instance was possible to control it through multimedia keybords keys But for the Version 1.2 Beta 2 and 1.2 Beta3 seems not possible to call amarok with "amarok -p". It crahses with full CPU usage (KDM could not be killed). But if I call him with "amarok %U" and then let it play from the pop up menu from the systry icon, it works. Thank you for looking for the solution My system again SUSE9.1 Professional, KDE3.3.2
by the way the followiing commands are working: amarok -r amarok -s amarok -f amarok --pause
Can you update to beta4 or current cvs and see if this still occurs?
Hallo, thank you for the feedback. unfortunately, the behavior is still happened: Try to start amarok Beta4 with the command line "amarok -p" and KDE freeze under 100% CPU charge. I will start amarok only with one command to open it and start to play. Even the command "play at start" under "Play settings" (Wiedergabe Einrichtung - I have the German version) doesn't help. Please try to kill this bug and offer amarok a playable setting like xmms has. Best regards, Juan_Lutz Greg Meyer wrote: >------- You are receiving this mail because: ------- >You reported the bug, or are watching the reporter. > >http://bugs.kde.org/show_bug.cgi?id=96867 > > > > >------- Additional Comments From greg gkmweb com 2005-02-02 06:36 ------- >Can you update to beta4 or current cvs and see if this still occurs? > > >
Please specify engine.
amarok1.2-beta4-4-i586 SUSE9.1, KDE3.3.2, Gnome2.6 If tese are not the wanted information, please clarify which engine are you looking for. Best regards Juan_lutz Max Howell wrote: >------- You are receiving this mail because: ------- >You reported the bug, or are watching the reporter. > >http://bugs.kde.org/show_bug.cgi?id=96867 > > > > >------- Additional Comments From max.howell methylblue com 2005-02-10 20:55 ------- >Please specify engine. > > >
audio-engine, look in the config-dialog.
OK ! The audio engine I am using is aRts. SuSE9.1, KDE3.3.2, Gnome 2.6 I have also the following engines installed: xine: but amarok crash when I select it. I am using xine for all other DVD and video multimedia files: Kaffeine, Kplayer, Xine without problem, even by playing MS formats. Gstreamer: It seems to be OK under my SuSE9.1 system. But I missing the output-plugin ossink, that is present in other PC I have with SuSE9.2. Under SuSE9.1, Kde3.3.2 and Gnome 2.6 (even the installed some gestreamer files seems to be missing this one). Amarok don't chrash it but no sound come out. If you call with the command "amarok -p" under SuSE9.2, amarok open it saying "list finished" and don't play you must select the play command once more. aRts is work fine, but under SuSE9.1 the behavior is described in my bug 96867 if you call first time amarok with "amarok -p" Regards, Juan_lutz Max Howell wrote: >------- You are receiving this mail because: ------- >You reported the bug, or are watching the reporter. > >http://bugs.kde.org/show_bug.cgi?id=96867 > > > > >------- Additional Comments From max.howell methylblue com 2005-02-11 18:14 ------- >audio-engine, look in the config-dialog. > > >
So can I just verify. The crash only occurs with aRts-engine?
The crash described in Bug 96867 occurs under aRts engine, yes. By the other ones (xine, gstreamer) amarok doesn't work properly. Max Howell wrote: >------- You are receiving this mail because: ------- >You reported the bug, or are watching the reporter. > >http://bugs.kde.org/show_bug.cgi?id=96867 > > > > >------- Additional Comments From max.howell methylblue com 2005-02-12 19:18 ------- >So can I just verify. The crash only occurs with aRts-engine? > > >
So, how's this issue with 1.2.3?
Closing for lack of feedback. Juan Ehrenhaus, please, if you want to help, get a newer version, and reopen the bug if necessary.
Hi, sorry for the dealy sending you an answer. I am using the Version 1.2.3, compile in a SUSE9.1 with KDE 3.3.2 Unfortunately, I still cann't open amarok using for instance F2 and the command "amarok -p" as in the past (Version 1.1.1) was. It should be a very good issue to activate it again. Best reagrds, Juan Ehrenhaus.
Thanks for showing up, and notice that as the reporter you could have reopened the bug yourself (you just need to login before). Anyway, this bug is very strange. If amaroK is crashing, please, try to get us a backtrace, or at least the debug information it outputs to console.
Can you update to 1.3 final and see if this is still happening?
Take a look at the amarok FORUM-HELP, please. I have other problems with the amarok 1.3. For the moment I have downgrade to the Version 1.2.4 as I explained there. As soon as I get an operable 1.3 Version I will follow up this issue. Feedback then. THX you for your follow up. best reagrds, Juan Ehrenhaus
Closing, I can't reproduce this.