You are not logged in.
Claiming "elitism" is the argument used for wishing to infiltrate and subvert software. Being a "gatekeeper" is all that one has to ensure that a project never gets watered down with normies or other bad actors -- those who have nothing better to do than cry about "racism", "transphobia", or "bigotry" in an ill attempt to get rid of talented programmers, and a "CoC" will be written to prove "morality".
The Linux Foundation is pimped by corporations (including Microsoft and Google), so they have a huge influence on Linux. Systemd's creator even works for Microsoft now. As well, Debian proper is living on borrowed time. Instead of focusing on giving the users what they want (a system that "just works"), they chose to suck up to politics, which already drove away a few maintainers worth their salt. One of them is now happily a part of the Arch staff, where he ironically feels more accepted in.
Ultimately, Linus Torvalds sold out to the hurt feelings crowd, likely as blackmail from the women in his family. Meanwhile, Theo de Raadt of OpenBSD refuses to be a pushover, and anyone whining about politics on their mailing list gets the boot.
If you don't like a distro, just don't use it. Find the one that works best for your use cases, but don't distrohop. Devuan itself is just a tool for those who want Systemd removed from an Aptitude-based distro, and it does a good job at making all the services compatible with traditional inits. Everything else falls on the user to customize it the way that they like it.
In my case, I always base my installs on Refracta, which is a well-done Devuan respin by the same guy you're butthurt over. No one distro out of the box is for everyone. That's just the reality of FLOSS. You are more than welcome to stick to Debian or another distro... In fact, you could go above and beyond by doing us all a favor: go back to Windows 10/11/whatever and stay there. Their support team at least will get a paycheck for babysitting you.
I can see that my feedback fell on deaf ears. All clicking on [*quote] does is add a [*quote][*/quote] string to my post (asterisks are there because FluxBB apparently fails to parse things dynamically), which proves what I'm saying about having to highlight a post to add it to a reply. All this move does is punish good users for the actions of a relatively few bad ones. Why is this so difficult to understand?
And, how does that actually encourage people to stick around, especially when there have been MULTIPLE ad hominem attacks coming straight from the administrators' mouths themselves? If I knew there was going to be so much hostility and bitterness coming from people in positions of power, I wouldn't have even bothered opening an account here, and simply sought support elsewhere.
This is not the first time that anyone has left this forum (I can recall at least several of them, some with serious potential to give back to Devuan, being ran off because of this nonsense), and it will certainly not be the last time. For all the bitching some of the individuals give about people "not putting in the effort", you ensure your fate by treating them like second-class citizens. If you want the project to fizzle out of existence, then keep showing zero regard for the users' feelings. I was hoping Devuan would've been different from all of this, but I guess I was wrong.
As much as I dislike the act of distrohopping, maybe I'll just suck it up and change my repositories to Debian's and accept that Systemd, Wayland, and UsrMerge are inevitable. In fact, as long as Elogind and Eudev are pulled in, Systemd will always win.
What happened to the quote button? I'm not seeing it anymore. Did you actually remove it? If so... Why?
I understand not lazily quoting an entire post to address a specific point (but hardly a "waste of bytes", as has been claimed -- you ought to just disable avatars and signatures, since those are every bit as unnecessary and can be "distracting"), but this just inconveniences responsible users who want to respond to a specific point of a previous post, but don't want to have to also highlight portions of a post to quote.
That just discourages communication in a support community, if anything. Abusive or careless users will still highlight entire posts and use the quote tags as they like, so you might as well just disable quote tags, too.
I don't think this was a good move.
Because if you use a DE or WM that's not at all reliant on any part of Wayland, then you can continue to use X11 for however long it still exists. Knowing that i3 will never adopt Wayland is an example of this, so you can stay on it and not worry about the powers that be ordering you to remove it because it uses "insecure" X11. Something like OpenMATE as an example means that there will at least be some efforts to keep X11 chugging along for a while.
But, as I mentioned in closing in my previous post, software as we know it will never be the same again.
You can also edit your repositories via Synaptic Package Manager (sudo apt install synaptic) by going to Settings, and then Repositories. The rest of it is pretty straight-forward: just check and uncheck what you prefer, and add the extra lines as needed (check in Section(s)).
I will simply direct the focus to this thread on OpenMATE. It's a fork of MATE 1.4, so originally released back in 2012.
I think if people focused their efforts on that project, we'd be one step closer towards preserving traditional display servers for Unix-like OSes.
Forget about other distros and DEs. There's no getting off this train that's bound to crash. Enjoy it while it lasts.
I checked in aptitiude, and installing XFCE4 on my system would require downloading 500 MB of new files. It depends on PulseAudio and a whole bunch of other things I don't have installed.
That's because xfce4 itself is a metapackage, so of course it's going to install everything under the sun.
You'd want a "minimal" Xfce install with the following command (feel free to adjust to your own liking with more or less packages):
sudo apt install xfce4-terminal xfce4-session xfce4-settings xfwm4 xfdesktop4 xfce4-panel xfce4-power-manager thunar --no-install-recommends
In fact, you could do away with xfwm4 and just use something like openbox, i3wm, or fvwm in its place. Hell, even just keep xfce4-panel and use feh or xwallpaper for setting your desktop wallpaper without the need for xfdesktop4. thunar is recommended for full functionality, but you could swap it out for rox-filer or spacefm (not the icky GTK3 build, of course) and still use those for a "desktop" UI.
The point is that Xfce is what you make of it, and it can work for various use cases.
In my experience, Ventoy has been a smooth experience. All I had to do was format the USB thumb drive with the program, and then copy and paste individual ISOs onto its path. Once that's done, I just do a safe removal prompt and wait a short while until Thunar says it's OK to physically unplug the device (yes, it does seem to take longer for EXT4 partitions, but it's not that big of a deal if you do this ahead of time). I then test it by rebooting and seeing the menu with the ISOs available. I have had minor troubles on UEFI-only systems, but I just have to select the UEFI option on the system boot menu (just before the Ventoy USB thumb drive boots).
It's strange to me that despite its rising popularity, no GNU/Linux distro has ever packaged it for their official repositories. The official binaries from the maintainer work, and I'm not too worried about making sure I have the latest version, provided that what I use already works. It has definitely eliminated any further need for other live USB programs. If and when I ever produce my own Devuan derivative, it WILL include a Ventoy launcher of some sort. Amazing piece of software!
Wake me up when Wayland is "ready" for production use... It's never going to overtake Xorg, no matter what the shills say.
I made a personal list of GTK2-supported programs for Chimaera and Daedalus. Sadly, some approaches might require turning your system into a FrankenDevuan, but it can be worked with.
I purposely keep GTK2 programs such as Leafpad (text editor), Pale Moon (Web browser), Pidgin (IRC), LazPaint (image editor), VeraCrypt 1.24 (file encryption), etc. installed.
I shall soon replace FileZilla (FTP client) with gFTP and Thunderbird (e-mail client) with Claws Mail (Chimaera version is still on GTK2). It might be possible to use Xfce 4.12 on Chimaera or Daedalus, but you have to be very specific with Apt pinning to prevent updating to the newer and shinier 4.16 or 4.18 builds.
LXDE is still the only GTK2 DE available on the latest stable release, so that can be utilized.
Openbox can replace Xfce's WM and replicate much of its functionality with config changes. For compositing, Picom could be used.
The GTK2 build of SpaceFM can also be installed to replace Thunar, Caja, and other file managers, but you must understand that it is a dead project with over two hundred bugs (last official commit was in early 2018, with no further signs of life from the maintainer). Moreover, it will be removed from Devuan as of Excalibur when it goes stable in two years (the latest build for Ceres only ships GTK3 now).
Your best bet is to replace what you can with GTK2 or even Qt (using Qt5ct to skin its programs to look more GTK2-esque).
Otherwise, just go back to any of the first three Devuan releases (Jessie, Ascii, and/or Beowulf). The unfortunate thing is the lack of official support for the first two already, and Beowulf will be archived soon.
Finally, with all of this out of the way, it would have been great if MATE or Xfce forked GTK2 ten years ago. It's too late now. All the more reasons to hate GNOME developers for their lack of respect for the end user. They are by far one of the most incompetent disgraces to the open-source community.
not sure, what i expected in the 1st place, from a nazi friendly environment
Wait... What?
If I can gauge the political talks on here over the years, I would say there's a lot more clamoring support for Antifa/BLM, mask and vaccine mandates, and anti-capitalism/pro-socialism. In fact, it's very common to refer to a user as "they/them", which means the individual probably believes in the "gender" fallacy. If these folks are "Nazis" to you, then I'm your worst nightmare.
Anyway, you are not helping your situation by getting defensive here. Others have tried to explain to you that everything you've described is fairly normal and not any evidence for concern. You're also not doing it right by using ClamAV, which is for finding Windows viruses (not so much GNU/Linux or even another Unix/Unix-like OS). In all reality, if you are that paranoid about security, you should probably start looking into using OpenBSD, as it is a much smaller attack target compared to GNU/Linux or macOS (and these two are less of a risk compared to Windows).
Yes to all of the above. Devuan is 1:1 with Debian except in instances where Systemd would be invoked or a package would be too problematic to fork. The maintained list can be located here.
#/etc/apt/sources.list
deb http://deb.devuan.org/merged/ daedalus-backports main contrib non-free non-free-firmware
You should ideally use an Invidious instance. It works well on Firefox- and Chromium-based browsers.
You can also browse YouTube through the command line by installing ytfzf.
What I like to do with my personal YouTube channel subscriptions is add their RSS feeds to Newsboat and pipe them through Mpv. Saves me the trouble of having to use that bloated Web site.
For best results, you are better off just using AMD or Intel GPUs.
You need to add Chimaera to your sources list:
deb http://deb.devuan.org/merged/ chimaera main contrib non-free
Refresh:
sudo apt update
Afterwards:
sudo apt install libopenexr25 libtiff5
Note that if you don't install the daemonless "build" of Logind from the official repositories, this will cripple Polkit (e.g. Pkexec) and restrict your Xfce's session management (you'd only be able to log out). As well, NetworkManager will have to be replaced with Connman. All your KDE packages will be gone.
First thing is to install dummy-logind (prevents most of the packages from being removed), consolekit, seatd, libck-connector0, libpolkit-gobject-consolekit-1-0, udevil (for user-level drive mounting without authentication, with devmon as the daemon you have to execute), and lxqt-sudo (for authentication).
Afterwards, you'll have to look for your packages' binary files that call upon Pkexec to some extent (e.g. Synaptic, Gufw, Timeshift, GSmartControl, GParted) and replace them all with LXQt's version. It's also a good idea to adjust your Polkit rules in /usr/share/polkit-1/.
If you start your Xfce session with Startx, then change your Xinit configuration file used to exec startxfce4 --with-ck-launch.
The packages you might be looking for are package-update-indicator and gnome-package-updater.
Install those and launch package-update-indicator (should appear on your panel and set to start automatically on your next session). You can choose how often to refresh the updates and the command to run when there is an update. The default command is gpk-update-viewer, but you could still use Synaptic instead with synaptic-pkexec --dist-upgrade-mode.
First, which Devuan version are you using? If it's Chimaera (stable), then I'd avoid mixing and matching different repositories for the best chances at stability. Some of those packages (libssl1.0.0 in particular) are either no longer installable (deprecated) or not available in your main repository. If you were using Daedalus (testing) or Ceres (unstable), you might be able to get away with installing specific DEBs from other branches.
Have you tried to install from the official DEB file (2.18)? Using Ceres (unstable), GDebi tells me that "all dependencies are satisfiable".
What is nvtop, and why should you use it? It's programmed to look and behave like the popular htop, but instead of tracking the actively running processes on your CPU and RAM, it focuses on your GPU by displaying a plot, fan percentage, power consumption, frequency usage (both GPU and VRAM), and temperature. And, just like htop, nvtop correctly shows which processes are GPU-bound, and how much they are requiring from it. You can configure it with F2 to how you want it to display and save the configuration with F12. If you don't need the plot, run it as nvtop --no-plot, but check its manual with man nvtop for other usage instructions.
You can check its official repository over at GitHub.
Like the issue of firmware-amd-graphics (solution provided), some packages from Devuan Ceres are pretty old. The current version is at 1.2.2-1, while the latest upstream version is at 2.0-2. It also curiously only picks up Nvidia GPUs, while AMD GPUs are now supported. Keep in mind that nvtop only supports newer GPU hardware (i.e. not older than five years), so if you got an HD 6450 laying around, you're shit out of luck.
Before compiling, make sure you got the required dependencies (we'll assume a build for both AMD and Nvidia GPUs):
apt install cmake git libdrm-dev libncurses-dev libncurses5-dev libncursesw5-dev
With those dependencies installed, it's time to get on with the process:
git clone https://github.com/Syllo/nvtop.git
mkdir -p nvtop/build && cd nvtop/build
cmake .. -DNVIDIA_SUPPORT=ON -DAMDGPU_SUPPORT=ON
make
sudo make install
Even some packages from Devuan Ceres are quite old, namely the likes of firmware-amd-graphics still using binaries from last year (August 2021). Downloading the latest snapshot and copying the binaries from the amdgpu, r128, and radeon folders to /lib/firmware/ folders (overwrite the existing files) should do the trick. This will not remove firmware-amd-graphics, but add to the existing files.
As of the date of this post, we'll download linux-firmware-20220815 as the latest snapshot, extract it, and copy the folders to their respective directories:
wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/snapshot/linux-firmware-20220815.tar.gz
tar -xf linux-firmware-20220815.tar.gz && cd linux-firmware-20220815
sudo cp amdgpu /lib/firmware/
sudo cp r128 /lib/firmware/
sudo cp radeon /lib/firmware/
Reboot your system afterwards for the changes to take full effect.
Let's face it, some systems aren't good enough to run higan (which is technically bsnes), and zsnes is too old and too shitty for a conventional Super Nintendo or Super Famicom emulator. Plus, retroarch isn't for everyone. That's why I'd recommend installing snes9x as a standalone emulator, since it Just Werks™️ and doesn't require much to get it running.
The quickest and easiest way to do this is to download and install the lone DEB file from Bearoso's personal repository. Make sure all dependencies are met prior to installation.
wget https://sites.google.com/site/bearoso/snes9x/snes9x_1.60-1_amd64.deb && dpkg -i snes9x_1.60-1_amd64.deb
Now, keep in mind that as of the date of this post, the latest stable build of snes9x is currently at 1.61, and there are some changes since then. If you're upgrading, make a backup of your snes9x.conf file and check the second method below for replacing the binary.
You'll need to get certain packages installed:
apt install build-essential cmake git glslang-dev libgtk2.0-dev libgtk-3-dev libminizip-dev libsdl2-2.0-0 libsdl2-dev meson portaudio19-dev
Clone the git repository, build, and install (feel free to change --prefix=/usr/ to --prefix=/usr/local, if preferred):
cd ~/snes9x/
git clone https://github.com/snes9xgit/snes9x.git
cd snes9x/
git submodule update --init shaders/SPIRV-Cross
cd gtk
meson build --prefix=/usr/ --buildtype=release --strip
cd build
ninja
sudo ninja install
If all went well, your snes9x should be ready to go, and with your backed up snes9x.conf file, apply your changes to the new file.
Another method is to use the nightly builds and choose either snes9x-gtk or snes9x-x11 platforms, and then just move the executable binary to /usr/bin/ or /usr/bin/local/, and then launch it as snes9x.
Have you got it shared as an deb file so people with Debian and Debian distros can use it too ???
The following DEBs are available for manual installation:
https://www.gnuinos.org/amixer-gtk/amixer-gtk_0.1_amd64.deb
https://www.gnuinos.org/amixer-gtk/amixer-gtk_0.1_i386.deb
Quick installation commands (one for amd64 and the other for i386:
wget https://www.gnuinos.org/amixer-gtk/amixer-gtk_0.1_amd64.deb && sudo dpkg -i amixer-gtk_0.1_amd64.deb
wget https://www.gnuinos.org/amixer-gtk/amixer-gtk_0.1_i386.deb && sudo dpkg -i amixer-gtk_0.1_i386.deb
These instructions are copied from LinuxReviews.
corectrl is a graphical system monitor for your graphics card that can assist in optimizing GPU fan curves, frequency, and voltage in order to improve performance quality. You can also monitor usage metrics to see which processes are demanding more power from your GPU. It's a handy tool for gamers, streamers, video creators, musicians, and even developers (particularly if software is more GPU-bound). It can also handle your CPU frequency scaling and governors, but the draw of corectrl is for GPU optimization.
Before proceeding, keep in mind that this program WILL interfere with fancontrol from lm-sensors. Make sure that this is something you are absolutely sure of (i.e. you have experience fixing stuff by yourself), as corectrl will take immediate effect once launched. In following along with this tutorial, you agree to not hold anyone but yourself liable for any potential damages caused.
The official repository is hosted at GitLab, where you can view the source code and report issues.
As Debian doesn't provide a DEB file for this tool, your only choices are to either compile it from source or add Ernst Sjöstrand's PPA.
You must first install the following packages:
apt install botan2-devel qca-qt5-devel qt5-qtcharts-devel
The process for building is as follows:
git clone https://gitlab.com/corectrl/corectrl.git
cd corectrl
mkdir build;cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr -Wno-dev ..
make -j$(nproc)
sudo make install
If you leave the -DCMAKE_INSTALL_PREFIX=/usr part unchanged, the binary will be installed to /usr/bin/, instead of /usr/local/, which is more preferable because it relies on a daemon called corectrl-helper, and is started as root via dbus. We can learn how to make it work with PolicyKit (polkitd) rules and start up automatically later on in the tutorial.
You will need the package libbotan-2-12, which is available from Ubuntu's repositories (should install just fine). Click here to download the package dependency.
Otherwise, you can run the following commands:
wget http://mirrors.kernel.org/ubuntu/pool/universe/b/botan/libbotan-2-12_2.12.1-2build1_amd64.deb && sudo dpkg -i libbotan-2-12_2.12.1-2build1_amd64.deb
To add the PPA to your repository list, open your /etc/apt/sources.list file and add the following (no need to change the focal codename, unless it won't install):
deb http://ppa.launchpad.net/ernstp/mesarc/ubuntu focal main
As root, run apt update. It's likely you'll have an unverified key issue, so run these commands:
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys B78C97EF9B2235DD && mv /etc/apt/trusted.gpg /etc/apt/trusted.gpg.d/corectrl.gpg
If apt update works, then run apt install corectrl. It should install with all dependencies met.
Keep the following information in mind:
Although Debian and Devuan documentation strongly recommend against using outside repositories (particularly PPAs and anything outside of a Debian-specific build), I can confirm that this method works without any issues while using the unstable branches of Debian or Devuan. It's possible that this might also work for Bookworm or Daedalus (the current testing branches as of the date of this post), but I haven't tested installing it on them yet. My instructions are for Sid and Ceres users.
With the installation process done, the following is completely optional, but highly recommended:
Create or edit the file in /etc/polkit-1/localauthority/50-local.d/90-corectrl.pkla:
[User permissions]
Identity=unix-group:*
Action=org.corectrl.*
ResultActive=yes
If you have an older PolicyKit version (0.106 and older -- check with pkaction --version), create a file in /etc/polkit-1/rules.d/90-corectrl.rules and add the following lines of code:
polkit.addRule(function(action, subject) {
if ((action.id == "org.corectrl.helper.init" ||
action.id == "org.corectrl.helperkiller.init") &&
subject.local == true &&
subject.active == true &&
subject.isInGroup("*")) {
return polkit.Result.YES;
}
});
Afterwards, you'll need to create a desktop launcher:
cp /usr/share/applications/org.corectrl.corectrl.desktop ~/.config/autostart/org.corectrl.corectrl.desktop
Change StartupNotify=true to StartupNotify=false.
Save the file and reboot your system. Once you log into your graphical session, corectrl will launch automatically.
For AMD GPU users (like myself), you'll probably want to unlock the kernel parameters of the amdgpu kernel module by going into your /etc/default/grub file and inserting this line into GRUB_CMDLINE_LINUX:
amdgpu.ppfeaturemask=0xffffffff
It should look like this:
GRUB_CMDLINE_LINUX="amdgpu.ppfeaturemask=0xffffffff"
Save the file and run update-grub, and then reboot your system. You'll be able to increase the maximum watts of your AMD GPU and adjust both voltage and frequency. Leaving them by default is generally recommended, unless you know exactly what you're doing and won't ruin your hardware.
Once again, this is all done at your own risk, as I'm not liable for any problems that could arise. Please keep this in mind, should you do this.
All feedback is welcomed.
What Camtaf said. It's a small project that's run by a few volunteers, so I don't understand the need to escalate things, when there are some workarounds for this. Manually installing the updated DEB file worked for me.
Be like our friend MiyoLinux and offer to help out.
The creator of doas explains their reasons here:
I've been listening to some of Ted Unangst's talks. He's very thorough about his approach to improving code.
Anyway, I've been playing around with doas and actively considering installing OpenBSD on the side. I like the more minimalist, no-hands-held environment.