The command line is a wonderful thing. Try this link.
It is also possible the GUI failed if the correct tool was not installed i.e. bzip2 for .bz2 files.
Yes, xarchiver works fine.
But, of course, you must install bzip2, xz, zip, unzip, p7zip to be able to extract these archives.
Go to Edit -> Preferences -> Advanced -> Archiver integration
And you can select the one that you want…
Yeah, like screenFetch. Which installs /usr/bin/screenfetch. It bugs me that the package name / executable don’t match case. I know that’s not void’s fault, but void is one of the few to ignore that.
not directed at cr6 specifically but i highly recommend wifish for anyone using a laptop or switching wifi networks often, but without the use of a gui tool. it’s in the main repo and maintained by a community member.
make sure to edit the wifish script once installed to point at your wireless interface if it’s not already.
Separate -devel packages… oh hell no
I was given a challenge, to install void for someone but it had to be able to run Plasma on it.
Little that I know about it, I only use openbox a little of LXDE, I did an installation of all the KDE and Plasma crap I could find in the repository. Then I tried to see how to get it started. Then I gave up as I know little about it. I can’t seem to find an easy explanation on the forum, or whether plasma actually works now.
Can you run plasma without a DM? If not, is lightdm the ongoing proffered DM? They might need a DM if they want to be switching from one account to another.
I had no idea that KDE runs on top of openbox and Void has a KDE-ob script to configure it. So I may be close to understanding how to. Start ob-kde and then start plasma? If it works make all this autostart?
KDE Plasma can use different window managers like openbox, but by default it uses kwin, using a DM you can select which window manager to use.
First install the kde5 metapackage. If you don’t need a DM just run xinit /usr/bin/startkde
(To use openbox instead of kwin use xinit /usr/bin/openbox-kde-session)
(Or by using an environment variable export KDEWM=/usr/bin/openbox-session && xinit /usr/bin/startkde)
export KDEWM=/usr/bin/openbox-session && xinit /usr/bin/startkde
If you do use a DM (Any DM should work), start KDE by selecting Plasma
(To use openbox instead of kwin select KDE/Openbox)
I need to get round to expanding the wiki page on KDE to explain all this as well.
Thank you. I am not on that machine now, I may get to it sometime tomorrow and I will try where I left it at. I may be missing some kde part.
Tangent --> if you only have one de installed, openbox for example, would xinit alone start it? Or is it some etc/…rc file where the default DE is set?
Yes, a line in your ~/.xinitrc file:
And run xinit
Note: I usually run startx instead of xinit , I don’t know precisely why.
Thanks a ton
You have cleared out much of confusion, both of you.
I confuse the startx and xinit and between the 5 systems I am running each has a different setup from all others. I need to review it all and make it more uniform.
My preference is what I have with void now, no DM, just openbox starting with xinit with no root rights necessary. But this is for me. I hate looking at my ~/ and it being more complex than /etc
With other systems I had to do much more work to simplify it to this point.
I’m currently using openbox in Void and devuan with the same setup.
Using startx runs a script that does a little more. It also (at least it did, haven’t checked in awhile), requires hostname -f (FQDN) to be working, otherwise, it hangs for awhile. If startx hangs but xinit starts X immediately, that’s usually the issue and can be fixed by putting the localhost name in /etc/hosts.
The ArchLinux wiki has a script to run multiple desktops. I made up my own lame one that I’m embarrassed to share, but it works for me.