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.
wayland works for me on slackware plasma5/6 if i pull my nvidia graphics card.
wayland doesnt seem to be compatible with XFCE which i still find useful to me.
that aint breaking everything but it is a lot.
Well unfortunately NVIDIA is behind the 8-ball in terms of proper Wayland support - so I have to make a decision for my next system in terms of staying with NVIDIA whenever they get their shit together, or just jump over to AMD. As for XFCE at least they are now trying to start supporting Wayland - no word yet about MATE, and same with WM such as fluxbox/openbox, etc. AFAIK only SWAY will be the only working WM under Wayland; otherwise you will have to use GNOME or KDE for a DE.
Well unfortunately NVIDIA is behind the 8-ball in terms of proper Wayland support - so I have to make a decision for my next system in terms of staying with NVIDIA whenever they get their shit together, or just jump over to AMD. As for XFCE at least they are now trying to start supporting Wayland - no word yet about MATE, and same with WM such as fluxbox/openbox, etc. AFAIK only SWAY will be the only working WM under Wayland; otherwise you will have to use GNOME or KDE for a DE.
Ok, an extra two -- LXQT though still relies on Openbox , and I don't see anything in regards to wayland support yet. CDE has finally gone officially opensource and you got offshoots like NSCDE , but no wayland support , same with MWM, TWM, Windowmaker... Granted while more bleeding edge distros already plan to "drop" support for X11, that doesn't necessarily mean X11 isn't going to be available for said distro; but suffice to say X11 will start to become more and more broken as time goes by.
After today's update, elisa crashes immediately upon loading, and strawberry still crashes when playing a song with orc-0.4.35 installed. I reinstalled kirigami packages and drkonqi. Oh well, orc-0.4.34 it is for now.
Code:
bash-5.2$ elisa
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/Page.qml:328: Error: Cannot assign QObject* to PageRow_QMLTYPE_162*
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/Page.qml:328: Error: Cannot assign QObject* to PageRow_QMLTYPE_162*
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:265:13: QML SelectableLabel: Binding loop detected for property "implicitWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:265:13: QML SelectableLabel: Binding loop detected for property "implicitWidth"
org.kde.elisa.indexers.manager: Local file system indexer is inactive
org.kde.elisa.indexers.manager: Baloo indexer is unavailable
org.kde.elisa.indexers.manager: Baloo indexer is inactive
org.kde.elisa.baloo: Baloo indexer has been configured to be deactivated. Disabling Elisa support for using Baloo indexer.
org.kde.elisa.indexers.manager: Local file system indexer is active
org.kde.elisa.indexers.manager: MusicListenersManager::startAndroidIndexing
org.kde.elisa.indexers.manager: trigger init of local file indexer
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = elisa path = /usr/bin pid = 10680
KCrash: Arguments: /usr/bin/elisa
The X11 connection broke: I/O error (code 1)
XIO: fatal IO error 9 (Bad file descriptor) on X server ":0"
after 597 requests (597 known processed) with 0 events remaining.
The X11 connection broke (error 1). Did the X11 server die?
Unable to start Dr. Konqi
Mon Jan 29 19:17:30 UTC 2024
kde/digikam-8.2.0-x86_64-4.txz: Rebuilt.
Recompiled against ffmpeg-6.1.1.
kde/ffmpegthumbs-23.08.4-x86_64-2.txz: Rebuilt.
Recompiled against ffmpeg-6.1.1.
kde/k3b-23.08.4-x86_64-2.txz: Rebuilt.
Recompiled against ffmpeg-6.1.1.
kde/kfilemetadata-5.114.0-x86_64-2.txz: Rebuilt.
Recompiled against ffmpeg-6.1.1.
kde/kpipewire-5.27.10-x86_64-2.txz: Rebuilt.
Recompiled against ffmpeg-6.1.1.
Fri Feb 2 22:12:45 UTC 2024
kde/calligra-3.2.1-x86_64-36.txz: Rebuilt.
Recompiled against poppler-24.02.0.
kde/cantor-23.08.4-x86_64-2.txz: Rebuilt.
Recompiled against poppler-24.02.0.
kde/kfilemetadata-5.114.0-x86_64-3.txz: Rebuilt.
Recompiled against poppler-24.02.0.
kde/kile-2.9.93-x86_64-30.txz: Rebuilt.
Recompiled against poppler-24.02.0.
kde/kitinerary-23.08.4-x86_64-2.txz: Rebuilt.
Recompiled against poppler-24.02.0.
kde/krita-5.2.2-x86_64-3.txz: Rebuilt.
Recompiled against poppler-24.02.0.
kde/okular-23.08.4-x86_64-2.txz: Rebuilt.
Recompiled against poppler-24.02.0.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
