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.
Worth noting for those of us not using sbopkg to build the deps: the slackbuild and associated files for menu-cache need to be gotten from the SBO git server since there's a patch there needed for it to build.
Worth noting for those of us not using sbopkg to build the deps: the slackbuild and associated files for menu-cache need to be gotten from the SBO git server since there's a patch there needed for it to build.
Note: I did not want to mess around with my .xinitrc and other files.
Sbo packages installed without hurdles and lxqt built ok, though the dreaded appeared when I tried startxlxqt:
"$ startlxqt
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Noticed there are only 4 files in ~/.config/lxqt/
lxqt.conf power.conf session.conf windowmanagers.conf
copied some settings from the files in /usr/share/lxqt/
added to lxqt.conf icon_theme=oxygen
added to session.conf window_manager=openbox
added to windowmanagers.conf (I'm not sure if I had to ¯\_(ツ)_/¯ but did anyway) openbox/Name=Openbox
Killed xfce and next chose lxqt via xwmconfig.
It started but with no panel.
Killed lxqt and back to xfce
There are now more files visible in ~/.config/lxqt/
globalkeyshortcuts.conf lxqt-powermanagement.conf lxqt-runner.conf lxqt.conf notifications.conf panel.conf power.conf session.conf windowmanagers.conf
Added settings to the panel.conf file from /usr/share/lxqt/panel.conf plugins=mainmenu,desktopswitch,quicklaunch,taskbar,tray,statusnotifier,mount,volume,worldclock,showd esktop
Back to xwmconfig, selected lxqt and once again startx.
And now I have a panel with mainmenu, etc.
From then on, settings were easy to find, enabled dual monitors, etc.
Note: I did not want to mess around with my .xinitrc and other files.
Sbo packages installed without hurdles and lxqt built ok, though the dreaded appeared when I tried startxlxqt:
"$ startlxqt
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Noticed there are only 4 files in ~/.config/lxqt/
lxqt.conf power.conf session.conf windowmanagers.conf
copied some settings from the files in /usr/share/lxqt/
added to lxqt.conf icon_theme=oxygen
added to session.conf window_manager=openbox
added to windowmanagers.conf (I'm not sure if I had to ¯\_(ツ)_/¯ but did anyway) openbox/Name=Openbox
Killed xfce and next chose lxqt via xwmconfig.
It started but with no panel.
Killed lxqt and back to xfce
There are now more files visible in ~/.config/lxqt/
globalkeyshortcuts.conf lxqt-powermanagement.conf lxqt-runner.conf lxqt.conf notifications.conf panel.conf power.conf session.conf windowmanagers.conf
Added settings to the panel.conf file from /usr/share/lxqt/panel.conf plugins=mainmenu,desktopswitch,quicklaunch,taskbar,tray,statusnotifier,mount,volume,worldclock,showd esktop
Back to xwmconfig, selected lxqt and once again startx.
And now I have a panel with mainmenu, etc.
From then on, settings were easy to find, enabled dual monitors, etc.
It's alive! ( ͡° ͜ʖ ͡°)
Absolutely, I recommend to copy all system-wide configurationfiles to $HOME/.config/lxqt.
By the way, I add lxmenu-data to build-deps.sh,required for libfm.
Nice.
removepkg should work ok.
Tried it with 'removepkg --warn Kvantum' and no dramas observed.
Btw, did a test install of Devuan Chimaera on an old HP Elitebook yesterday.
It had lxqt as in option next to xfce, etc when selecting the gui.
Tried it and it just worked. With the panel, firefox, nm-applet all showing up and no crashing.
Methinks lxqt will become a viable alternative to xfce.
It starts with a panel, but both the background and text color are both black, with no widgets set up for it. And the desktop background is black.
So: it starts with an empty panel that is indistinguishable from the desktop background. After beating my head against the wall for an embarrassing number of minutes, I figured out that I could right click on where the panel was supposed to be and configure it to become useful and right click on the desktop to change its configuration.
I suppose that's one way to avoid the pitfall of users complaining about being shoehorned into a default setup? :rofl:
Distribution: slackware, slackware from scratch, LFS, slackware [arm], linux Mint...
Posts: 1,491
Rep:
I tried to build today the whole packages but I'm stuck with these errors:
-------------
libfm-qt-1.0.0/src/xdndworkaround.h
-- The C compiler identification is GNU 11.2.0
-- The CXX compiler identification is GNU 11.2.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Checking for module 'glib-2.0'
-- Found glib-2.0, version 2.70.1
-- Checking for module 'gio-unix-2.0'
-- Found gio-unix-2.0, version 2.70.1
-- Found GLIB: /usr/include/glib-2.0;/usr/lib64/glib-2.0/include (found suitable version "2.70.1", minimum required is "2.50.0")
-- Checking for module 'libmenu-cache'
-- No package 'libmenu-cache' found
CMake Error at /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
Could NOT find MenuCache (missing: MENUCACHE_LIBRARIES
MENUCACHE_INCLUDE_DIR MENUCACHE_INCLUDE_DIRS) (Required is at least version
"1.1.0")
Call Stack (most recent call first):
/usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake/lxqt-build-tools/find-modules/FindMenuCache.cmake:84 (find_package_handle_standard_args)
CMakeLists.txt:40 (find_package)
-- Configuring incomplete, errors occurred!
See also "/tmp/snuk/libfm-qt-1.0.0/build/CMakeFiles/CMakeOutput.log".
---------------------
I'm on slackware64 current.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.