View previous topic :: View next topic |
Author |
Message |
radgeRayden n00b
Joined: 13 Feb 2019 Posts: 6 Location: Brazil
|
Posted: Sun Feb 17, 2019 8:37 pm Post subject: Spotify crashing X |
|
|
I just installed spotify and I can play a song for a while but then it crashes the X server. This has happened multiple times.
This is what I could find in `/var/log`, more specifically kern.log:
Code: |
Feb 17 12:41:56 sakamoto kernel: [57439.435232] perf: interrupt took too long (6816 > 6766), lowering kernel.perf_event_max_sample_rate to 29000
Feb 17 15:10:17 sakamoto kernel: [66340.894577] traps: spotify[5417] general protection ip:1176b83 sp:7fff7adfa3a8 error:0 in spotify[108d000+103b000]
Feb 17 15:15:17 sakamoto kernel: [66640.208360] Core Thread[5950]: segfault at 48 ip 00000000020ad7e7 sp 00007f9da73f9040 error 6 in spotify[108d000+103b000]
|
anyone else experiencing this? I installed spotify with libnotify, pulseaudio and systray. |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9677 Location: almost Mile High in the USA
|
Posted: Mon Feb 18, 2019 6:07 pm Post subject: |
|
|
Crashes in an X client shouldn't cause the server to go down, unless the X server was set up to die when that client dies...
Might want to also try upgrading your X server if there is any updates to see if someone else has fixed the problem already.
Also should check if your hardware is in good shape. Clean out fans if it's an old machine, ensure PSU is working, memory test, etc. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
radgeRayden n00b
Joined: 13 Feb 2019 Posts: 6 Location: Brazil
|
Posted: Mon Feb 18, 2019 7:12 pm Post subject: |
|
|
My hunch is that it's DBUS related, as it seems to happen during a song transition. I was also poking with a CLI spotify client (sends dbus messages for play, status query etc). Would that explain the X crash? It's my understanding that DBUS runs at a lower level. Either way I've cleaned my fans recently, the hardware is not exactly in shape but I would expect something like a kernel panic if it was hw failure. Things like watching youtube go smoothly. |
|
Back to top |
|
|
r7l Tux's lil' helper
Joined: 16 Feb 2019 Posts: 89
|
Posted: Mon Feb 18, 2019 7:17 pm Post subject: |
|
|
I have a problem with Spotify as well. It's not crashing X but it's crashing itself. It loads up fine but once i want to start playing any song it just crashes with segmentation fault. I've tried the Debug Mode and this is the output:
Code: | 19:14:41.045 I [dns.cpp:60 ] Resolved i.scdn.co to 151.101.120.246
19:14:41.096 I [dns.cpp:60 ] Resolved i.scdn.co to 151.101.120.246
19:14:41.136 I [dns.cpp:60 ] Resolved i.scdn.co to 151.101.120.246
19:14:41.182 I [dns.cpp:60 ] Resolved i.scdn.co to 151.101.120.246
19:14:43.885 I [storage_system_impl.cpp:720 ] Deleted 1 files from storage. Time spent: 0 ms. (files that was scheduled for delayed wipe)
19:14:43.885 I [storage_system_impl.cpp:726 ] 1 in pl4 realm
19:14:43.885 I [offline_manager_impl.cpp:2853 ] Storage has been cleaned
19:14:47.994 I [audio_session.cpp:234 ] Creating track player for track (playback_id 0122bae54383a8072247a627cad37969)
19:14:47.994 I [audio_session.cpp:235 ] track_uri: spotify:track:7iC8b4n0dUKEHv3Eg0ijD8
19:14:47.994 I [audio_session.cpp:236 ] speed: 1.000000
19:14:47.994 I [audio_session.cpp:237 ] normalization: track
19:14:47.994 I [audio_session.cpp:238 ] stream_type: default
19:14:47.994 I [audio_session.cpp:239 ] urgency: now
19:14:47.994 I [audio_session.cpp:240 ] track_select_flag: 0
|
Running Spotify 1.1.0 without pulseaudio but with systray and libnotify flags. It was running fine with the versions before. |
|
Back to top |
|
|
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3595
|
Posted: Tue Feb 19, 2019 1:53 am Post subject: |
|
|
Indeed, spotify crashes here to.
Setting Menu doesn't work. there are editable in ~/.config/spotify.
Unfortunately, I can't get firefox to work as a client, which is a pity as it would probably save memory since firefox is almost always open.
BTW, do you get ads in current version? I don't.
Thks 4 ur attention.
Last edited by CaptainBlood on Tue Feb 19, 2019 9:32 am; edited 1 time in total |
|
Back to top |
|
|
eccerr0r Watchman
Joined: 01 Jul 2004 Posts: 9677 Location: almost Mile High in the USA
|
Posted: Tue Feb 19, 2019 4:02 am Post subject: |
|
|
Dbus is irrelevant, other than the X server may listen to it for some events, it should not cause it to crash unless there's a bug in the X server -- not spotify.
And no, not all hardware failures would result in kernel panics. Things like segmentation faults to user programs is common. _________________ Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching? |
|
Back to top |
|
|
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3595
|
Posted: Tue Feb 19, 2019 9:36 am Post subject: |
|
|
I agree, it very unlikely to be dbus related.
Moreover, my ISP internet box currently reboots every hour or so, a situation where spotify does'nt seem to be resiliant when playing.
So it crashes, whereas playing youtube video in firefox resumes as soon as internet is back.
Does anyone gets adverts with current version?
Thks 4 ur attention, interest & support. |
|
Back to top |
|
|
r7l Tux's lil' helper
Joined: 16 Feb 2019 Posts: 89
|
Posted: Tue Feb 19, 2019 1:08 pm Post subject: |
|
|
I've figured that there is a different error message when running Spotify from command line without debugging option:
Code: | /opt/spotify/spotify-client/spotify: /usr/lib64/libcurl.so.4: no version information available (required by /opt/spotify/spotify-client/spotify)
/opt/spotify/spotify-client/spotify: /usr/lib64/libcurl.so.4: no version information available (required by /opt/spotify/spotify-client/spotify)
/proc/self/exe: /usr/lib64/libcurl.so.4: no version information available (required by /proc/self/exe)
Segmentation fault
|
This seems to have a history with Spotify as a Google search suggests. Any idea how to fix this? I've tried to rebuild Curl but that does not work. I am running Curl with ipv6 and ssl flags. |
|
Back to top |
|
|
kristaholle36 n00b
Joined: 27 Feb 2019 Posts: 2
|
Posted: Fri Mar 29, 2019 7:20 am Post subject: |
|
|
Try Vpn once. let's see if it work. |
|
Back to top |
|
|
r7l Tux's lil' helper
Joined: 16 Feb 2019 Posts: 89
|
Posted: Fri Mar 29, 2019 8:48 pm Post subject: |
|
|
kristaholle36 wrote: | Try Vpn once. let's see if it work. |
That's not the issue. I can connect fine using the web browser. |
|
Back to top |
|
|
Juippisi Developer
Joined: 30 Sep 2005 Posts: 723 Location: /home
|
Posted: Sat Mar 30, 2019 6:33 am Post subject: |
|
|
r7l wrote: |
Code: | /opt/spotify/spotify-client/spotify: /usr/lib64/libcurl.so.4: no version information available (required by /opt/spotify/spotify-client/spotify)
/opt/spotify/spotify-client/spotify: /usr/lib64/libcurl.so.4: no version information available (required by /opt/spotify/spotify-client/spotify)
/proc/self/exe: /usr/lib64/libcurl.so.4: no version information available (required by /proc/self/exe)
Segmentation fault
|
|
I believe these has always been there, even in working versions.
Did you try downgrading? Does ldd show something different? Do you use some LTO+graphite optimizations (it's known to break openssl)?
Also try running it with some external debugger, like gdb or strace or valgrind, to get more info about the segmentation fault. |
|
Back to top |
|
|
r7l Tux's lil' helper
Joined: 16 Feb 2019 Posts: 89
|
|
Back to top |
|
|
|