Hi Philipp,
Am Sun, Jul 31, 2022 at 06:12:55PM +0200 schrieb Philipp Kern:
> > It existed - but if I remove it no such dir is create newly.
>
> And how about ~/.infinote-records and your homedir?
That dir existed in my homedir from former DebConfs when gobby worked.
If I rename it now and try gobby again it grashes as well. When trying
under strace I get:
...
openat(AT_FDCWD, "/home/tillea/.infinote/", O_RDONLY|O_NOFOLLOW) = -1 ENOENT
(No such file or directory)
openat(AT_FDCWD, "/home/tillea/.infinote/", O_RDONLY|O_NOFOLLOW) = -1 ENOENT
(No such file or directory)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7ffc14a99fe8} ---
+++ killed by SIGSEGV +++
I think I understand that issue now. I have copied the configuration of
my current box from a former laptop where I used a symlink
ln -s /home/andreas /home/tillea
since ages ago I was using user tillea. Currently I am
$ whoami
andreas
$ echo $HOME
/home/andreas
Since /home/tillea does not exist gobby can't create that dir.
OK, I think we found the reason - but IMHO gobby is buggy in two ways:
1. It should simply use $HOME to create the dirs it needs (and not some
"random" config which I would like to know to fix / remove it)
and more importantly
2. it should not crash SIGSEGV but rather print "can't create dir XY"
> FWIW, it does not crash for me on a new installation on bookworm.
I believe this now since I think I understood that issue (which I could
probably fix by the said symlink but I guess its better to find a real
solution.
Kind regards
Andreas.
--
http://fam-tille.de
