After a strace session, I see this :
brk(0x55fa07e7f000) = 0x55fa07e7f000
brk(0x55fa07ea0000) = 0x55fa07ea0000
brk(0x55fa07ec2000) = 0x55fa07ec2000
futex(0x7fd578933c40, FUTEX_WAKE_PRIVATE, 1) = 1
access("/usr/lib/vice/C64/kernal", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/lib/vice/DRIVES/kernal", R_OK) = -1 ENOENT (No such file or
directory)
access("/usr/lib/vice/PRINTER/kernal", R_OK) = -1 ENOENT (No such file or
directory)
access("/usr/bin/C64/kernal", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/bin/DRIVES/kernal", R_OK) = -1 ENOENT (No such file or directory)
access("/usr/bin/PRINTER/kernal", R_OK) = -1 ENOENT (No such file or directory)
access("/home/stefan/.config/vice/C64/kernal", R_OK) = -1 ENOENT (No such file
or directory)
access("/home/stefan/.config/vice/DRIVES/kernal", R_OK) = -1 ENOENT (No such
file or directory)
access("/home/stefan/.config/vice/PRINTER/kernal", R_OK) = -1 ENOENT (No such
file or directory)
getcwd("/home/stefan", 3968) = 13
openat(AT_FDCWD, "/home/stefan/kernal", O_RDONLY) = -1 ENOENT (No such
file or directory)
So it looks like vice doesn't go to the ~/.vice directory. However, on the
documentation page here :
http://vice-emu.sourceforge.net/vice_4.html#SEC26
It is said :
The place where they will be searched for depends on the value of the
Directory resource, which is a colon (:)-separated search path list, like the
UNIX PATH environment variable. The default value is
PREFIX/lib/vice/EMU:$HOME/.vice/EMU:BOOTPATH/EMU
Notice that $HOME/.config/vice/EMU is not shown...
So dunno if it's a bug with vice or debian but well, not clear to me.
When I move the files under the .config directory, vice starts as expected.
stF
