SigHunter @ SigHunter @feddit.de

Posts

0

Comments

39

Joined

2 yr. ago

thanks for the insight!

I'm running latest version of normal owncloud in a docker container. Is there any advantage in using infinite scale oc? Not sure what the difference actually is

Ctrl + R is bash history search

Nostalgia for those 80s and 90s kids who grew up with norton commander ;-)

Ages 0-99

Transition takes time

Kpatience for the win!

Nice, cant wait to have this

can you work around this by copy/pasting maybe all 25 characters at once or maybe each segment at a time?

• alternative: install somewhere else (windows pc or VM) and copy the install dir contents and registry
• alternative 2: get the steam version, I just tried it with proton experimental and it seems to work fine.

edit: steam lets me choose the base game, war chiefs or asian dynasties, AD and WC work without a problem but the base game asks for a key and I can also just input 4 characters instead of 5. but I'd always play with all expansions

I think your panel freezing is https://bugs.kde.org/show_bug.cgi?id=469016 and I got rid of it by disabling window previews

Simple Keyboard

I'd imagine there aren't many people in the world who could even attempt to clean up such code. since I don't use such old hardware and I think such old hardware for the most part does not use kernels >= 6.5, I concur with this removal

Not sure if one of those is native but they run like native: Played a lot of transport fever, soldat 2, some csgo and northgard via steam recently and it's like on windows

Gentoo is fun

Kscreenlocker because it came as default and I made it look identical to sddm

well, you can't keep every weird american racist issue in mind, there are too many

    
# systemd-analyze time

Startup finished in 39.050s (firmware) + 6.680s (loader) + 993ms (kernel) + 3.519s (initrd) + 22.326s (userspace) = 1min 12.570s 
graphical.target reached after 21.680s in userspace.

  

for me, most time is used until the bootloader shows up, because I had to disable "fast boot" in bios because it made some problems on rebooting. pressing enter in grub could speed up 5 seconds more ;-) gentoo, systemd, 2x2tb nvme, 32 gb ram, 4 hdds. could be faster, but it mostly doesn't matter because I power on the system every morning but don't use it right away

edit: on my server, which is not UEFI, therefore has no "firmware" part:

    
# systemd-analyze time
Startup finished in 1.814s (kernel) + 47.640s (initrd) + 36.602s (userspace) = 1min 26.057s 
graphical.target reached after 36.602s in userspace.


  

and on my laptop, which boots fast AF

    
# systemd-analyze time
Startup finished in 4.242s (firmware) + 14.631s (loader) + 1.737s (kernel) + 3.210s (initrd) + 5.136s (userspace) = 28.959s 
graphical.target reached after 4.936s in userspace.



  

I use both on gentoo for some obscure or proprietary stuff that is not packaged in portage, like filebot, authy desktop, discord, steam and foobar2000 (including wine in 1 bundle to avoid dependencies and switching all portage packages to 32bit abi). It works well and opens me up to loads of stuff. It's freedom in some way.

Snap or flatpak makes no difference to me, they're just different backends for kde discover

this "takeover" is imho a good thing. the greeter/login manager is an essential part of a desktop experience and I was sad that sddm was so left behind until now