Package Details: soulseekqt 20180130-6

Git Clone URL: (read-only)
Package Base: soulseekqt
Description: A desktop client for the Soulseek peer-to-peer file sharing network
Upstream URL:
Licenses: custom
Submitter: said
Maintainer: robertfoster
Last Packager: robertfoster
Votes: 61
Popularity: 0.257852
First Submitted: 2011-06-21 11:18
Last Updated: 2019-02-27 20:56

Latest Comments

1 2 3 4 5 Next › Last »

AlphaJack commented on 2019-05-21 09:43

I can't install the package bacause I'm getting this error:

==> Entering fakeroot environment...
==> Starting package()...
  -> Extraction...
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
Failed to connect to bus: Operation not permitted
Failed to connect to bus: Operation not permitted
==> ERROR: A failure occurred in package().
Error making: soulseekqt

What's to blame?

Gimmeapill commented on 2019-02-24 15:14

Ok, got it: not a reboot issue. Just that I don't have the fuse module loaded by default & it was not obvious why this was suddenly needed. Anyway: the squashfs method seems to work better, so far it's stable. Thanks for your work ;-)

kevku commented on 2019-02-23 17:24

you updated your kernel you need to reboot

Gimmeapill commented on 2019-02-21 18:44

The new package doesn't seem to work here (built in a chroot with extra-x86_64-build): "soulseekqt fuse: device not found, try 'modprobe fuse' first

Cannot mount AppImage, please check your FUSE setup. You might still be able to extract the contents of this AppImage if you run it with the --appimage-extract option. See for more information open dir error: No such file or directory"

robertfoster commented on 2019-02-21 00:57

@ezulo now the terminal spit out errors. I used another approach in packaging and it seems to accomodate the appimage runtime better. Also the freezes should be gone

ezulo commented on 2019-02-20 21:37

I'm having the same issue described by chrisco23. I'm on Arch using DWM with Xorg. It seems the issue is intermittent, it occurs consistently within a window of maybe a few hours, and then it'll work just fine some days I try it.

The freezes happen when files are right clicked or certain buttons are hovered over (for example, the button to close a search results panel). The only way I'm able to regain control of my system is by using a TTY, logging in and killing the process from there. For now I'm able to circumvent it and still get some use out of it by enabling the "double-click to download file" option.

Maybe this has something to do with Xorg? I'm not really sure where to begin. The terminal doesn't spit out any errors.

andrejr commented on 2019-02-12 14:06

The other soulseek client available on AUR, nicotine-plus-git, doesn't have the context-menu-freeze problem. It's totally usable, albeit a bit slower and with a clunkier interface.

ellul commented on 2019-01-02 21:46

I'm having a similar probelm to chrisco23 below except my system locks -infrequently - after I right click selected files in search results. I'm using an up to date Arch KDE. The latest file for download on the official site appears to be from 2016

robertfoster commented on 2018-09-04 11:44

@chrisco23 Hi,I can't reproduce this bad behaviour. And I can't do any sort of bug fixing because no code is available. I can try to suggest some test to do. you can try to:

change graphic session, between xorg and wayland

check for other processes

check for available new versions and notify here (there's no updated release page on the official site)

join the discussion group of official project. Nir is always available

chrisco23 commented on 2018-09-03 22:37

I've been using soulseekqt for years but in the last week or so it consistently locks up my machine within 30-60 seconds of running.

I'm running awesomewm on Arch Linux, 2 monitors if that matters somehow, 1 being a 40" tv.

The lockups are usually so severe that I actually have to cold-boot the machine, although just now I was able to minimize then expand and I saw the window frame with the soulseek logo, but the window was filled with my desktop background. I was able to run a terminal and kill the process, this time.

I had also just uninstalled and reinstalled, latest version. Arch is fully updated.

Any ideas?