danktankk

jdupes is outdated by almost a year now but says its up to date in nerd pack. Any chance this can be looked into?

i never could get this latest version to display the icons for dockers or VM's. I guess it doesn't really matter now as development for this is gone now anyway. Was a good run. Thanks

For me, the lockups were caused by running a cron backup job for single, selected appdata from userscripts. This interfered with the backup/restore appdata plugin in settings as they were trying to run at the same time. Once I changed the time to something else, it never locked up after that. I would turn off all cron jobs if you use any and see if that helps your issue.

Im having what is probably an easy fix, but I havent been successful yet. When I run: php artisan register:app appname I am getting the error: Could not open input file: artisan I have tried bashing into the container and using the console link as well. I have tried various folder locations from heimdall root and further in as well to run the command. Any help would be appreciated. I am sure I am missing something simple. Thanks! EDIT: Got it. Never mind...

I'm at about 40 days now in 6.9.2 It wasn't hardware for sure. Sent from my SM-G996U using Tapatalk

lol ok thanks for the update

thanks ill give that a try

If you are referring to the RAM speed, yes I did that a while back. Sent from my SM-G996U using Tapatalk

Thats definitely an option, but I think I will just remove the plugin. Thanks for the reply.

I have the same issue. My system is AMD and inexplicably freezes about every 3 days or so and requires a hard reset. No syslog errors... Nothing... No help either. It's not hardware for sure. Sent from my SM-G996U using Tapatalk

Simply ignoring this message isnt that easy when you have to look through your log files and see hundreds if not thousands of these messages. Its a lot to sort through. Is there a way to keep this out of the log files at least?

Awesome. Thank you!

Using this command I am able to stop the extremely annoying log entry: nvidia-smi --persistence-mode=1 Is there a way to make this command stick? It doesnt stay in this mode permanently after using it. Any help is appreciated. Thanks!

I still dont have this particular issue as the RAM is still humming along just fine @ 3200MHz without any issues. But it is an interesting topic for sure - Albeit nothing to do with what my problem is/was. Running for 3+ days fine without any issues still. I wont say its good until after a week or more though.

Maybe you should reread what you quoted me typing. I didnt say it was a secret. I didnt say it wasnt a "fact." What I said was that it was a limitation, which is exactly what it is. Im not sure there was any reason at all for your post.