You are not logged in.
Many thanks for the info. As I understand it, the only way to install KDE on Devuan at this time, is to do as I did? So the correct order would be: net install, edit the sources.list file for ascii, upgrade, and then do an apt-get install kde-standard?
No worries
I always use the latest MuseScore AppImage partially because I sometimes run into dependency issues, partially because MuseScore has a MIDI issue that has been dogging them for a long time, that they don't seem to be able to stamp out. Sometimes when playing a score, there is a lot of static/feedback noise that makes it unbearable to listen to what you have written, which kind of is the point of MIDI playback in the first place ![]()
BTW, I would like to advertise another posting of mine on the forum, that I am not getting any response on:
"Vanilla KDE Jessie Devuan system prompts for USB pen drives." I still haven't been able to figure that one out yet, and now I am testing a vanilla KDE Jessie Devuan install both on a laptop as well as on a home built tower computer, so it would be nice to get it sorted.
Nice to hear from you
You are doing a great job with MiyoLinux, as are all of the developers of other "spins", and much appreciated. I think that the plethora of spins is part of what makes the Devuan community vibrant and will hopefully draw new users to Devuan based systems.
I have experimented a bit with AppImages and found that all of the ones that I have tried, worked out of the box with a bog standard Devuan install, so I can confirm that everything necessary is in the official repos. A little tip, the AppImage that I have found so far with the largest amount of dependencies is the AppImage version of MuseScore musecore.org. I think the dependency issue is just a matter of not cutting into the bare metal, when doing a spin, or maybe including a disclaimer with a list of possible dependencies needed for running AppImages ![]()
All the best...
In general, I detect a certain amount of disdain these days for non-commercial Linux distributions. A narrowing of minds appears to be occurring within the sector of the Linux community that supports systemd. I dare to predict that the next major battle for hearts and minds will take place around a replacement for X11. Just search the KDE Neon for "i3" and you will discover that the Neon team originally excluded the possibility of switching DEs/WMs because the consensus was that most alternative WMs will not survive the switch to Wayland. While that may be true it doesn't preclude new WMs that can work with Wayland in the future!
I have been having an interesting exchange on http://discourse.appimage.org regarding AppImage dependencies. I have run into the problem that AppImages refuse to run on Devuan derivatives due to lacking dependencies. There are a fair amount and a bit of a bear to track down each one, so I thought that I would post a link to the exchange: https://discourse.appimage.org/t/musesc … 4bit/279/6 The final post provides a list of those dependencies that the host systems are expected to take care of.
The potential that I see for AppImage and Devuan is that I am reasonably confident that AppImages will never pull in systemd, unlike with snaps or flatpaks that very likely could draw systemd as a dependency in the sandboxed group of dependencies.
I hope this helps the Devuan team and anyone else interested in keeping a systemd free system.
Hi. I am new to Devuan (never used Debian) and have come across an irritating issue. I have a vanilla KDE Jessie Devuan system running on a laptop. Unlike other Devuan DEs, I get prompted for root (sudo) password each time that I want to mount a USB pen drive. As mentioned, this doesn't happen with the Devuan MATE or XFCE4 DEs and I am wondering - why?
$ ls -l /media | grep $USER
drwxr-x---+ 2 root root 4096 Jan 19 16:24 username$ getfacl /media/usernamegetfacl: Removing leading '/' from absolute path names# file: media/username# owner: root# group: rootuser::rwxuser:username:r-xgroup::---mask::r-xother::---Is this related with a KDE specific issue? How do I change this so I don't get prompted for a password all the time?
A two minute search found this:
Is Flatpak tied to systemd?
No. Versions of flatpak before 0.6.10 relied on systemd for cgroups setup, but this is no longer required.]
This I knew. While Flatpak isn't tied to systemd, that doesn't mean that it in principle couldn't be pulled in as a depend for the individual flatpak. I am unsure as how deep the depends for the individual flatpak are pulled in, when one can assume that many programs are coded to "take advantage of" systemd. Or am I misunderstanding something?
This brings up the issue of Flatpaks as an alternative to AppImages. Is it possible to use Flatpaks and ensure that systemd stays off my system?
$ ./MuseScore-2.1-x86_64.AppImage
/tmp/.mount_lNQqEe/bin/mscore-portable: error while loading shared libraries: libvorbisfile.so.3: cannot open shared object file: No such file or directory.
OK, so the reason is that it is lacking a bunch of dependencies like vorbis-tools, libsound files, pulse audio, etc. It looks like it probably best if I choose a less minimalist Devuan derivative. Anyway, thanks for your time.
OK, I tried Subsurface and it runs in place, but refuses to install to all users sudo ./Musescore 2.1 AppImage install. This seems to suggest that there is something with Musescore that refuses to work. I know that it has QT dependencies when it is installed as a .deb file. I will try to find an answer on their forum and post the reply here.
Devuan is fantastic. kudos to the team behind it!
Normally, running sudo ./Musescore 2.1 AppImage install (or whatever the file is called) will install a working version of the program on my system. I tried this with a Miyo i3 Jessie 64bit (Devuan based) system and while everything appears to have gone to the correct place, the program doesn't seem to work, no matter how I try to run it (menu, comman, clicking on the executable image (yes, I ran chmod +x on it). Don't AppImages work on Devuan or is there something with the way this program has been packaged that makes it incompatible with Devuan based systems (systemd dependence)?