SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,018
Rep:
ELISA (music player) crashes - looks like a bug
Just tested this after I updated Slackware-current-64-bit today (12-13-2020).
Plasma5 - 5.20.4
Elisa music player crashes when browsing more complicated file system tree:
This is happening in host and in VM client.
I have music folder set on second HDD (SSD Samsung) Ext4 fs
I created symlink directly to the Music folder and Elisa recognizes folder and plays music without a hiccups, but when I try to browse folders going to another disk. Elisa crashes.
[KCrash Handler]
#4 0x00007f22d933bb50 in QQmlIncubatorPrivate::incubate(QQmlInstantiationInterrupt&) () at /usr/lib64/libQt5Qml.so.5
#5 0x00007f22d933c142 in QQmlIncubationController::incubateFor(int) () at /usr/lib64/libQt5Qml.so.5
#6 0x00007f22d9f184d0 in () at /usr/lib64/libQt5Quick.so.5
#7 0x00007f22d8ce386f in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#8 0x00007f22da4d726f in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#9 0x00007f22d8cb934a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#10 0x00007f22d8d0c6d3 in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#11 0x00007f22d8d0cea4 in () at /usr/lib64/libQt5Core.so.5
#12 0x00007f22d813ea5d in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#13 0x00007f22d813ecb0 in () at /usr/lib64/libglib-2.0.so.0
#14 0x00007f22d813ed3f in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#15 0x00007f22d8d0d1ff in QEventDispatcherGlib:rocessEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#16 0x00007f22d8cb7e8b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#17 0x00007f22d8cbfaac in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#18 0x00000000004051be in ()
#19 0x00007f22d8509e6b in __libc_start_main () at /lib64/libc.so.6
#20 0x000000000040558a in ()
[Inferior 1 (process 3115) detached]
JuK and audacious work fine, no problems with folder browsking
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,018
Original Poster
Rep:
Quote:
Originally Posted by frankbell
I've never used Elisa, but you can check the bug reports here and file one of your own if it seems warranted.
than you for suggestion.
I never used Elisa either. The problem came up after last upgrade (run first in VM). I test apps if they work before moving to upgrade Slackware host and I noticed Elisa issues.
Tried to reproduce here. Deleted old library location. Created symlink to my music archive folder on another drive in $HOME/Music/CDs -> /data2/music, rescanned after adding $HOME/Music to Elisa. Plays ok and I can browse the directory tree just fine from within Elisa.
Elisa is on /dev/nvme0n1p2
$HOME is on /dev/nvme0n1p3
music library is on /dev/sdd1
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,018
Original Poster
Rep:
Quote:
Originally Posted by kingbeowulf
Tried to reproduce here. Deleted old library location. Created symlink to my music archive folder on another drive in $HOME/Music/CDs -> /data2/music, rescanned after adding $HOME/Music to Elisa. Plays ok and I can browse the directory tree just fine from within Elisa.
Elisa is on /dev/nvme0n1p2
$HOME is on /dev/nvme0n1p3
music library is on /dev/sdd1
thing is broken:
I have folder
/vbox
in root directory
Elisa does not see it. Only standard folders in root are visible. So that is a bug.
Then the next questions are:
1. does your user have permissions to access /vbox?
2. is /vbox mounted? I assume this is a host share from within Virtualbox?
Some upstream devs can get pretty cranky if you are not careful in your bug reports.
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,018
Original Poster
Rep:
Quote:
Originally Posted by kingbeowulf
Then the next questions are:
1. does your user have permissions to access /vbox?
2. is /vbox mounted? I assume this is a host share from within Virtualbox?
Some upstream devs can get pretty cranky if you are not careful in your bug reports.
As I mentioned in my first post: JuK and audacius do not have these problems.
So, yes all VM clients have full access to the /vbox.
Also, not having access does not mean that folder is invisible as is the case of Elisa.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.