The system still freezes after it's been on for a couple of days.
Sometimes only 1 day.
I leave it on, then in the morning I come in, and it's locked up.
I have started a logging system so that when I find it's dead in the morning, I can check the logs to find out the resource usage of things.
Hopefully this will help the devs resolve this issue that has been a plague since early on.
If anyone already knows a resolution to this bug, please let me know so that I can get it resolved. I'm tired of having to re-do the work that gets lost if files get corrupted or not saved properly, and also browsing information from things I'm doing.
Sincerely,
Drew.
Mine is weird.
I have a cron running in the background.
This allows me to find out what happens while I'm not here to see the PC stop and lock.
It locked again over the weekend.
I can't get to a terminal/console/shell/prompt or whatever you want to call it.
Others can ALT+F2 and get a shell, some can't. And I can't.
I've attached the log file for running processes and memory usage at the time of me arriving here to find it locked up. So it's not completely locked up, things still are running. But it s3eems all input devices may have stopped or been disabled.
This happens every time I leave the PC for a day or so.
Hope someone can help.
It doesn't have the issue if I'm on the pc during the day since upgrade to 3.2 , only if I leave it for a day, (more than 12 hours)
Doesn't matter.
USB or not, it doesn't respond to input.
Is your issue after a wake from suspend? Desktop freezes on me on one machine if it is left asleep for too long. I figure its related to bios or what vms were running when it went to sleep. I also find its less of a problem on kde then on xfce. In my case it also seems to happen more often if i wake machine up from power button rather then a keyboard press.
Short answer: no.
Long answer:
It isn't from waking, it never goes to sleep, only blanks the screen itself.
I changed to XFCE because it was happenning overnight on KDE. XFCE takes a lot longer to happen.
Since mine never sleeps, and is always working (I am a programmer), all I normally do is move the mouse and it comes back to life from the lock screen.
But this PC locking up is odd. It never happpenned in version. or 3.0 that I can remember. Nope, it did happen once when Qubes Manager absorbed all the RAM. Since that 1 leak was fixed, it didn't happen in 3.0. And that didn't matter if I used KDE or XFCE.
I wish they would go back to the older GUI instead of this new wanky one.
Well, it just happened again.
While I was using it.
I'll attach the log fine. But as far as I can tell, it's because Qubes uses SystemD. And when that runs out of RAM to use, it locks up. and since everything runs as SystemD, just like Windows, everything locks up, instead of 1 process.
How do I install another O/S as Dom0? (it is Linux)
How do I install another O/S as integrated guests? (it is Linux)
Help please?
Addn: I forgot to mention, this time, nothing kept running in the background, EVERYTHING was frozen. Not even the logging kept going.
A bit late to the party? What party is this? I started this thread.
I don't want to suspend/restore. My PC never suspends.
> I'm generally not one to rationalize a bug by saying "well, just don't do
> that," or "don't use that feature"; but the whole suspend/restore thing
> does seem to add a layer of complexity to the whole security mess, with a
> lot of CPU/BIOS/motherboard dependencies and such.
Okay, I see that you are going to keep going on about the suspend/restore that I don't use and that isn't the issue here, so I'll stop reading your post here, and let you re-read my posts so that you can then re-post with your thoughts and all on the actual topic, not the complete reverse of what I have/use/want/do that is the actual issue. :}
about keeping it unconnected you have to make sure all wakes are off in the bios. and then the really paranoids are worried about big brother in cahoots with hardware manufacturers when it don't matter even if your pc is off lol.