Open LooOOooM opened 9 months ago
Why as root? No idea if it's related, but Tomahawk should run fine in user context
Wayland shouldnt matter too much as it should be handled by Qt Platform Abstraction
Hi dscmidt - Thanks for your fast reply. This is exactly what i want to do run the program as user - not as root , but then the error comes -- I just recompiled it as user, however it makes no difference. I did the first compilation as root as I want this program finnaly not end up in my home rather then in for example in /opt /or /usr/local . However it makes anyway no difference if I compile it as user or root , as long as I chown -R the whole directory to user or root
Hi Folks, I am running on a fresh installed Fedora 38. I was able to compile and installed correctly Tomahawk as root, using the Fedora howto from you. If I execute tomahawk as root all is fine, however if I execute as user it is not, resulting in the following message not matter of ownerships:
[me@host build]$ ./tomahawk QSocketNotifier: Can only be used with threads started with QThread qt.qpa.qgnomeplatform.theme: The desktop style for QtQuick Controls 2 applications is not available on the system (qqc2-desktop-style). The application may look broken. KDSingleApplicationGuard: Could neither create nor attach to shared memory segment. QSharedMemomry::create() failed: QSharedMemoryPrivate::initKey: unable to set key on lockQSharedMemomry::attach() failed: QSharedMemoryPrivate::initKey: unable to set key on lock
0:11:58 [0]: DownloadManager::DownloadManager() Initializing DownloadManager. 0:11:58 [0]: virtual DownloadManager::~DownloadManager() Shutting down DownloadManager. 0:11:58 [1]: void DownloadManager::storeJobs(const QList<QSharedPointer >&)
any idears? I fear it has to do with "wayland"