At the risk of polluting this forum with a useless post, I just wanted to say wholeheartedly that the upgrade process was almost flawless. I only had to do "apt install -f" once and there were just 2 /etc config file issues (due to my own edits of these files) which were easy to resolve.

A thousand times easier than my recent Debian upgrade which failed and resulted in me having to abort it and install from anew.

Well done Devuan people! This is how Linux upgrading should be!

I am seeing a crash in i965_dri.so while running FreeCAD Appimage. This is the command line output:

$ FreeCAD-asm3-Daily-Conda-Py3-Qt5-20220511-glibc2.12-x86_64.AppImage 
/tmp/.mount_FreeCAipF3cg
FreeCAD 0.20, Libs: 2022.511R26244 +4790 (Git)
Program received signal SIGSEGV, Segmentation fault.
#0  /lib/x86_64-linux-gnu/libc.so.6(+0x3bd60) [0x7f0646239d60]
#1  /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x14c7fa) [0x7f06374097fa]
#2  /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x1499ff) [0x7f06374069ff]
#3  /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x1e686e) [0x7f06374a386e]
#4  /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x1e6ffb) [0x7f06374a3ffb]
#5  /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x2206fc) [0x7f06374dd6fc]
#6  /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x2155ee) [0x7f06374d25ee]
#7  /usr/lib/x86_64-linux-gnu/dri/i965_dri.so(+0x47b8de) [0x7f06377388de]
#8  0x7f0648a12515 in NaviCubeShared::drawNaviCube(SoCamera*, bool, int, bool) from /tmp/.mount_FreeCAipF3cg/usr/bin/../lib/libFreeCADGui.so+0x15f5
#9  0x7f0648a12816 in NaviCubeImplementation::drawNaviCube(bool) from /tmp/.mount_FreeCAipF3cg/usr/bin/../lib/libFreeCADGui.so+0x46
#10  0x7f06489dc9b5 in Gui::View3DInventorViewer::renderScene() from /tmp/.mount_FreeCAipF3cg/usr/bin/../lib/libFreeCADGui.so+0x515
etc

Apparently this does not occur on normal Debian. Is there a way I can install the debug version of i965_dri.so to find out more about the crash?

Do any Devuan experts have any suggestions how to fix this or how I can investigate?

Many thanks.

I have the fuse module loaded and have installed "exfat-fuse exfat-utils" yet still have problems mounting an exfat USB drive.

What are my options to debug this? Thanks.

# lsmod | grep fuse
fuse                  147456  0
# mount  /dev/sdc /mnt/
mount: /mnt: unknown filesystem type 'exfat'.

I have success in setting the default application for many filetypes but not .slvs which is a solvespace file.

Here is some debugging investigation:

$ xdg-mime query filetype mysolvespacefile.slvs 
application/x-solvespace

$ xdg-mime query default application/x-solvespace
<blank>

$ kbuildsycoca5
kbuildsycoca5 running...
kf5.kservice.sycoca: Service type not found: "application/x-solvespace"

$ ktraderclient5 --mimetype application/x-solvespace
mimetype is : application/x-solvespace
kf5.kservice.services: KMimeTypeTrader: mimeType "application/x-solvespace" not found
got 0 offers.

Despite having an entry for solvespace in

~/.local/share/applications/mimeapps.list
~/.config/mimeapps.list 
~/.kde/share/config/mimeapps.list

KDE is unable to find the mimetype. I was following this thread to try to get an answer. Even strace did not seem to yield any useful info:

https://unix.stackexchange.com/question … ssociation

If anyone has seen this I'd be grateful to hear back. I am tempted to say it is a KDE bug.

As title, I've installed bash-completion and finding that it does not do autocomplete with git. e.g.

git chec***tab***

Then nothing. Same for

apt-get inst***tab***

I note that this is solved by doing

. /usr/share/bash-completion/completions/git

or

. /etc/bash_completion

but why is this not setup by default when you install the bash-completion package? Surely one of these scripts should automatically be run when opening bash?

According to https://www.gnu.org/savannah-checkouts/ … rtup-Files

"When Bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable."

I have no .bash_profile or .bash_login. I only have ,profile (and also .bashrc which *does* get parsed for different reasons) however I am finding that bash does not source this file when started.

Perhaps I should file this somewhere as a bug?
Cheers