![bookworm 1.12 2 bookworm 1.12 2](http://heavenlyforest112.weebly.com/uploads/1/2/3/9/123918556/542201004.jpg)
![bookworm 1.12 2 bookworm 1.12 2](http://2.bp.blogspot.com/-knYCjvj5Suk/VSfflWDn1pI/AAAAAAAAOOM/EizxflUp1nQ/s1600/2.jpg)
UID PID PPID C STIME TTY TIME ~ $ ps -fc įehler: unbekannter benutzerdefinierter Formatbezeichner »m.«įür weitere Informationen siehe ~ $ ps -fc įehler: unbekannter benutzerdefinierter Formatbezeichner »m.«įür weitere Informationen siehe ~ ~ $ flatpak list -appĬom./i386/stable system,currentĬom./i386/stable ~ $īabylon. fixing it let me wait for confirmation.Ĭode: Select all ~ $ ps -fC If it shows not you as UID but root, as I do suspect it does given your original problem, I can for now tell you that this is not how things should be.īefore I go and try and find out more wrt. Get the names from flatpak list -app or from just ps -ef while its running. It does here, and so do my other flatpaks (Steam, P圜harm Community, KeePassXC). Linux is choice! Yeah, it's also a mountain of rubbish.Īnyways: what does ps -fC tell you? The first column should indicate your regular user. Even though it sounds wildly suspicious I can as such not definitively tell you there's something wrong at your end: although flatpaks should just run as your user certainly they are, to some extent, sandboxed and your window title display might just be some daft MATE thing as far as this Cinnamon user knows. One of the generic issues of the Linux desktop: I see you are using MATE but I am using Cinnamon. Note that Mint 18.x is Ubuntu 16.04-based.Īnd if still not, I'd tell bookworm to go take a hike. sudo swapon -a after its done doing either. Bookworm will either behave, crash or complain. There's a possibility that bookworm in fact behaves if you tell it in advance that it has little memory to work with: sudo swapoff -a to limit your memory size to your actual RAM. Still, yes, 32-bit may be the issue in the direct sense of bookworm using bad algorithms coupled with the limited amount of memory you are going to have on that sysem of your large epub collection causing bookworm to balloon internal data structures to the point of swapping: if on every iteration through an algorithm the system needs to write out and back in the data on which it operates certainly this can make it take insane amounts of time. As to why bookworm crapped out in the first place I cannot test I use (64-bit and) Calibre, and not its reader in fact I read only on an actual ebook reader. If you want to restore, chmod 644 ~/.dmrc (adds reading rights for members of your group as well as others will not matter in practice). It'll be fine as is, but mine's user-owned and the regular 644. Your chmod of ~/.dmrc does not make a lot of sense and seems unrelated. Code: Select all sudo find ~/ ! -user $(whoami) -print0 | xargs -0 sudo chown $(whoami):