Clementine: Playback Issues on PPC

[h45rd]

Hi,

Having issues with Clementine 1.3.1 on an iMac G5 iSight running Debian sid for PowerPC.

uname -a
Linux imac5g 4.14.0-3-powerpc64 1 SMP Debian 4.14.13-1 (2018-01-14) ppc64 GNU/Linux

clementine --version
Clementine 1.3.1

Can't for the life of me seem to get playback to work.
Trying to play any file format only yields Internal data stream error. in the GUI and WARN unknown QTimeLine::start: already running on the shell (with Clementine running in verbose mode).

Already cycled through all possible output devices to rule out any misconfiguration. No dice.
Running gstreamer manually on the same files, with or without GUI and/or custom sink works fine.
All other players (vlc, mplayer) work as well.

Any advice on how to debug this further?
Any way to get Clementine to be a bit more verbose?

[scotte]

I can't help, but can tell you it's nothing unique to PowerPC - the same thing happens on x86_64 Ubuntu Bionic with the version in the bionic repo (1.3.1+git276-g3485bbe43+dfsg-1.1build1). Likewise, --verbose provides no additional information and all other media players work just fine.

[UPDATE: Started working again for me - I changed audio output device in the settings from 'default' and that fixed it. Dunno why it stopped working for me - it was, then it wasn't, and just finally tried to dig through why. shrug Anyway, maybe it helps you, maybe it doesn't. :-) ]

[pignouf305]

I can't help, but can tell you it's nothing unique to PowerPC - the same thing happens on x86_64 Ubuntu Bionic with the version in the bionic repo (1.3.1+git276-g3485bbe43+dfsg-1.1build1). Likewise, --verbose provides no additional information and all other media players work just fine.

[UPDATE: Started working again for me - I changed audio output device in the settings from 'default' and that fixed it. Dunno why it stopped working for me - it was, then it wasn't, and just finally tried to dig through why. _shrug_ Anyway, maybe it helps you, maybe it doesn't. :-) ]

@scotte Thank you very much for your update, I had exactly the same error after changing the audio output, and changing it back fixed the problem !