Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
Dear,
I have upgraded today (may 21 2014), via public repository, my linux desktop spotify to version 0.9.10.17.g4129e1c9 and encountered a bug.
Whenever a new song starts playing or I resume playing after I paused the song, my system freezes. I have started the program from the terminal and the following messages appear:
08:52:37.582 E [watchdog.cpp:171 ] Deadlock detected (Thread: gui)
08:52:58.599 E [watchdog.cpp:191 ] The deadlock was a lie! (gui, 25017)
The first line appears moments (~3 seconds) after starting a new song. My system freezes until the moment the latter line appears.
I also see a popup of some kind for maybe 1-2 frames after my system unfreezes. Looks like it is a new feature of spotify trying to send a figure of the album art to the systems (ubuntu 12.04) notification centre that makes it freeze.
Release: 12.04
Kernel: 3.2.0-43-generic
Spotify: 0.9.10.17.g4129e1c9
Solved! Go to Solution.
It may have to do with the new feature to use system notifications.
Try starting Spotify like this from the terminal, and see if the freezing stops:
spotify --ui.track_notifications_enabled=false
I can't listen to music with spotify if after every song (3-4minutes) it freezes my computer for 20 seconds+. This is not acceptable, I expect a fix, or at least the acknlodgement of the bug with a workaround so I can use the program again. If not, well then you lost a long term (2+years) paying customer...
I am having a problem with the newest update too.. by not being able to start spotify.
spotify: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by spotify)
spotify: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/spotify/spotify-client/Data/libcef.so)
spotify: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /opt/spotify/spotify-client/Data/libcef.so)
Using debian wheezy 64-bit.
@hultberg wrote:
I am having a problem with the newest update too.. by not being able to start spotify.
spotify: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by spotify)
spotify: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/spotify/spotify-client/Data/libcef.so)
spotify: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /opt/spotify/spotify-client/Data/libcef.so)
Using debian wheezy 64-bit.
With Spotify 0.9.10.17.g4129e1c.78-1 on Debian stable/Wheezy amd64 with libc6 from testing/Jessie it runs fine. Though apt-pinning is not for everybody …
--
br,
kid
@kid wrote:
@hultberg wrote:
I am having a problem with the newest update too.. by not being able to start spotify.
spotify: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by spotify)
spotify: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by /opt/spotify/spotify-client/Data/libcef.so)
spotify: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.15' not found (required by /opt/spotify/spotify-client/Data/libcef.so)
Using debian wheezy 64-bit.
With Spotify 0.9.10.17.g4129e1c.78-1 on Debian stable/Wheezy amd64 with libc6 from testing/Jessie it runs fine. Though apt-pinning is not for everybody …
… but this might get you started.
Spotify deserves credit for making their software available on the Linux platform through package repositories, but I would be glad to have a build that eliminates the need for apt-pinning in Debian stable/Wheezy.
--
br,
kid
Thanks for link, tried this solution and it worked. I installed libc from jessie/testing. I did NOT update any other package than libc. (And related packages to the libc).
I have the exact same issue here (freezing on playback). As a premium customer I would appreciate a reply from spotify addressing the issue.
It may have to do with the new feature to use system notifications.
Try starting Spotify like this from the terminal, and see if the freezing stops:
spotify --ui.track_notifications_enabled=false
Thanks, that fixed it for me. Obviously I would like a fix from Spotify (so we still can have notifications), but for now this is great. Thank you olejon.
Great 🙂
If everyone with this problem reported som basic system information, it could maybe help the developers to identify what causes this. I have not encountered this bug on Xubuntu 12.04, Ubuntu GNOME 14.04 or Xubuntu 14.04 (all 64-bit, of course).
Can't test it at the moment (I downgraded) but I'm pretty sure it was the notifications so if that command stops it, great. Where did you get the information about that command?
@berendho wrote:
Can't test it at the moment (I downgraded) but I'm pretty sure it was the notifications so if that command stops it, great. Where did you get the information about that command?
It's in the first post in the official thread here for the new version 🙂
The bug was exactly as OP described and was fixed by disabling notifications. My details are:
OS: Ubuntu 12.10
Desktop: Gnome 3.6.1
Kernel: 3.5.0-49-generic
CPU Info:
hamish@hdev -> cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 30
model name : Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
stepping : 5
microcode : 0x3
cpu MHz : 1197.000
cache size : 8192 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm dtherm tpr_shadow vnmi flexpriority ept vpid
bogomips : 3997.18
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 30
model name : Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
stepping : 5
microcode : 0x3
cpu MHz : 1463.000
cache size : 8192 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 4
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm dtherm tpr_shadow vnmi flexpriority ept vpid
bogomips : 3997.18
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 30
model name : Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
stepping : 5
microcode : 0x3
cpu MHz : 1995.000
cache size : 8192 KB
physical id : 0
siblings : 4
core id : 2
cpu cores : 4
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm dtherm tpr_shadow vnmi flexpriority ept vpid
bogomips : 3997.18
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 30
model name : Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
stepping : 5
microcode : 0x3
cpu MHz : 1995.000
cache size : 8192 KB
physical id : 0
siblings : 4
core id : 3
cpu cores : 4
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 11
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 popcnt lahf_lm dtherm tpr_shadow vnmi flexpriority ept vpid
bogomips : 3997.18
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
I also had this (very annoying) bug, and it was fixed by:
spotify --ui.track_notifications_enabled=false
as suggested by olejon. Thanks!
My specs:
Debian 7.5
Intel(R) Core(TM) i7-3610QM CPU @ 2.30GHz
RAM 4GB
Same issues as all of you, running the follwoing fixes it however I am running gentoo.
spotify --ui.track_notifications_enabled=fals
distro gentoo
desktop awesome
kernel 3.12.20
cpu AMD Phenom(tm) II X6 1065T Processor
I had exactly the same issue with libc6 on debian wheezy and decided to go back to older version everything works for now so no need to update.
An update to help with the bug hunt:
I recently had to reinstall. I previously had Ubuntu 12.10 with Gnome 3.6 and had this bug (that was fixed by the disable notifications option). I reinstalled Ubuntu on the same hardware, now with 14.04 and Unity (stock install from Canonical website) and do not experience this bug
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…