Bug 216708 - No play next file in playlist
Summary: No play next file in playlist
Status: RESOLVED DUPLICATE of bug 172550
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.2.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-29 19:24 UTC by Raul Malea
Modified: 2009-11-29 23:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Amarok debug log konsole command (779.34 KB, text/plain)
2009-11-29 20:06 UTC, Raul Malea
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Raul Malea 2009-11-29 19:24:34 UTC
Version:            (using KDE 4.3.3)
OS:                Linux
Installed from:    openSUSE RPMs

I using Kde 4.3.3 release 3 on opensuse 11.2. Amarok version is 2.2.1
I have more files in playlist. After play first file next file do not start. Also other file in curent playlist no not start. I restart amarok.
Also, next files start after more times (pauses is very long).
Comment 1 Raul Malea 2009-11-29 20:06:00 UTC
Created attachment 38691 [details]
Amarok debug log konsole command
Comment 2 Raul Malea 2009-11-29 20:07:44 UTC
Also, next files start after more times (pauses is very long aprox. 2-3
minutes!!!). After a paused long paused again!
I attached konsole messages and in attachment log of amarok --debug command.


Reproducible: Always

Steps to Reproduce:
1.Add more files (music) in amarok playlist.
2.Start first file in playlist. Music start.
3. After file is finish, next file in playlist do not start. File start after
more long times 2-3 minutes.



Amarok start in konsole. Konsole report:

Oscar@oscar:~> amarok
Object::connect: No such signal
Phonon::Gstreamer::MediaObject::availableSubtitlesChanged()
Object::connect: No such signal
Phonon::Gstreamer::MediaObject::availableAudioChannelsChanged()
Object::connect: No such signal
Phonon::Gstreamer::MediaObject::titleChanged(int)
Object::connect: No such signal
Phonon::Gstreamer::MediaObject::availableTitlesChanged(int)
Object::connect: No such signal
Phonon::Gstreamer::MediaObject::chapterChanged(int)
Object::connect: No such signal
Phonon::Gstreamer::MediaObject::availableChaptersChanged(int)
Object::connect: No such signal
Phonon::Gstreamer::MediaObject::angleChanged(int)
Object::connect: No such signal
Phonon::Gstreamer::MediaObject::availableAnglesChanged(int)
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
091129 20:29:44  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
QDBusObjectPath: invalid path ""
amarok: 
**********************************************************************************************
amarok:  ** AMAROK WAS STARTED IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING
INFORMATION, PLEASE USE: **
amarok:  ** amarok --debug                                                     
                     **
amarok: 
**********************************************************************************************
Oscar@oscar:~> QDir::exists: Empty or null file name
Oscar@oscar:~> Object::disconnect: Unexpected null parameter
Object::disconnect: Unexpected null parameter
Object::disconnect: Unexpected null parameter
QCoreApplication::postEvent: Unexpected null receiver
Comment 3 Myriam Schweingruber 2009-11-29 20:43:55 UTC

*** This bug has been marked as a duplicate of bug 172550 ***
Comment 4 Myriam Schweingruber 2009-11-29 20:44:36 UTC
You should use the phonon xine backend instead.
Comment 5 Raul Malea 2009-11-29 23:12:06 UTC
Gstreamer problem! Solution for this backend?
Comment 6 Myriam Schweingruber 2009-11-29 23:50:42 UTC
(In reply to comment #5)
> Gstreamer problem! Solution for this backend?

No, not that I know of, you really should use the xine backend.

*** This bug has been marked as a duplicate of bug 172550 ***