Version: 2.2 (using KDE 4.3.1)
Installed from: Unspecified Linux
I'm using Amarok 2.2 on Archlinux 64bit and since first RC available in Arch I'm experiencing the same little bug.
The OSD does not appear when track change automaticaly at the end of a song, the only moment it appears is when I manualy change the track or change the volume.
This wasn't the case with Amarok 2.1
Please ask if you need more information.
This works fine for me in 2.2 (installed from tarball) on Kubuntu 9.04, KDE 4.3.1, might be a packaging issue?
Hum could be... I'm posting a bug on the Archlinux bugtracker too.
But this would be realy weird, I don't think they modify Amarok before compiling it. Is there any specific options (with ./configure for example) related to OSD when compiling Amarok?
I can confirm, using debian packages.
I can confirm this is not a packaging problem, this problem does not appears on a computer's friend using the distro as me (64bit too).
I don't know what's special with my configuration, I've a nvidia card but so do he...
You might be using different Phonon backends?
I'm using the xine backend, I always had problem with the gstreamer backend. Even right now I cannot get a sound from Amarok with the gstreamer backend even if the it work when I test sound in the system settings.
I'll ask my friend to know what backend he is using.
Actually I can reproduce this now. Seems to be a regression.
I think this commit may have caused the regression:
Author: Seb Ruiz <email@example.com>
Date: Sun Jun 21 01:03:08 2009 +0000
The OSD no longer subscribes to metadata changes. This fixes showing the
osd when a track finishes (because finishedPlaying updates stats which
notifies observers). It also fixes annoying problems of showing the osd
when metadata changes (eg, editing a title) or the scanner updates a
svn path=/trunk/extragear/multimedia/amarok/; revision=984541
Author: Mark Kretschmann <firstname.lastname@example.org>
Date: Sat Oct 10 16:08:36 2009 +0200
Regression fix: OSD was not shown on automatic track change.
*** Bug 210431 has been marked as a duplicate of this bug. ***