Re: [qubes-users] System still freezes, still no resolution.
On Wednesday, September 28, 2016 at 10:58:57 PM UTC-4, raah...@gmail.com wrote: > saves energy, keeps pc cool, clears ram, keeps it unconnected when idle, > saves boot time. 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. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f20e8450-b07c-47b2-acf1-a10237a212b9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
saves energy, keeps pc cool, clears ram, keeps it unconnected when idle, saves boot time. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6562a0b0-4fc7-4a5e-95de-6111ada0e9b6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
On Wed, 28 Sep 2016 02:20:35 -, johnyju...@sigaint.org wrote: > A bit late to the party (as they say) in this discussion, but why is > it so important to suspend/restore in the first place? [...] > For a laptop on the go, okay, I can see the argument. But I don't > think most Qubes users are on laptops, given the hardware > requirements. (Very much moreso with 4.0. :P) Correct me if I'm > wrong. Yes, it's for laptops. Using laptop at home and in the office, and commuting every day, makes suspend/restore very useful feature. Hibernate would be even better, but it's not supported by Qubes. Qubes on laptops are not rare, according to published HCLs. And Qubes-compatible laptop doesn't have to be expensive - e.g. used Thinkpad T520 with i5-2520M for $200 and 16 GB RAM for $110 is really affordable. And I hope it will also run Qubes 4.0, since it supports SLAT/EPT (well, according to specs). -- yaqu -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20160928132829.28AF2101528%40mail2.openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
On Wednesday, 28 September 2016 12:20:47 UTC+10, johny...@sigaint.org wrote: > A bit late to the party (as they say) in this discussion, but why is it so > important to suspend/restore in the first place? 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. :} > It's never worked well for me, from the days of the first laptop that > promised to suspend/restore, up until my last Macbook. :) Maybe I've > just lost one too many sessions from a failed suspend/restore, that I've > been turned off of the feature. Or maybe I just don't leave the house > enough. > > I like to leverage all the hardware/software features I can, but > suspend/restore never seemed worth the trouble in most cases. > > Suspend/restore doesn't quite reach the 26x increase in complexity I > perceived in the Wifi vs. Ethernet comparison, but it's probably at least > 2x or 3x the complexity and dependency upon a variety of processor/mobo > features. > > For a laptop on the go, okay, I can see the argument. But I don't think > most Qubes users are on laptops, given the hardware requirements. (Very > much moreso with 4.0. :P) Correct me if I'm wrong. > > Why do you need to suspend? > > A good, strong, password for your user account, making sure you have > physical security (or at least awareness if it's been breached), and/or > shutting down when you need to, works fine for me. (At last I hope, lol.) > > It would be nice to see "xl save" and "xl restore" (which basically > hibernate a VM) smoothly integrated into Qubes, so the VM Manager > supported it, or at least was aware of it. Which would reduce the need > for a true hardware suspend/restore (if you can restore a VM fully after a > full reboot). > > But if you need to keep your current state, why not just keep the machine > on? (And securely locked/monitored?) I'm hardly flush with cash, but the > electricity cost of keeping a PC on 24/7 isn't exactly breaking the bank. > > And the alternative of shutting it down (and taking the disks with me) > when I leave, isn't terribly inconvenient, w.r.t. the risks, either. > > Apologies if I completely missed the point, as I so often do. And maybe > I'm wrong and most Qubes users are running around with high powered, > compatible laptops. > > I'm just looking to find out the motivations for such a feature that > brings additional complexity. > > Cheers > > JJ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8675ffcb-ee52-4269-8e71-a8a62e68e6ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
> On Wednesday, 28 September 2016 03:54:10 UTC+10, raah...@gmail.com wrote: >> 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. > > 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 ystemD. 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. A bit late to the party (as they say) in this discussion, but why is it so important to suspend/restore in the first place? 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. It's never worked well for me, from the days of the first laptop that promised to suspend/restore, up until my last Macbook. :) Maybe I've just lost one too many sessions from a failed suspend/restore, that I've been turned off of the feature. Or maybe I just don't leave the house enough. I like to leverage all the hardware/software features I can, but suspend/restore never seemed worth the trouble in most cases. Suspend/restore doesn't quite reach the 26x increase in complexity I perceived in the Wifi vs. Ethernet comparison, but it's probably at least 2x or 3x the complexity and dependency upon a variety of processor/mobo features. For a laptop on the go, okay, I can see the argument. But I don't think most Qubes users are on laptops, given the hardware requirements. (Very much moreso with 4.0. :P) Correct me if I'm wrong. Why do you need to suspend? A good, strong, password for your user account, making sure you have physical security (or at least awareness if it's been breached), and/or shutting down when you need to, works fine for me. (At last I hope, lol.) It would be nice to see "xl save" and "xl restore" (which basically hibernate a VM) smoothly integrated into Qubes, so the VM Manager supported it, or at least was aware of it. Which would reduce the need for a true hardware suspend/restore (if you can restore a VM fully after a full reboot). But if you need to keep your current state, why not just keep the machine on? (And securely locked/monitored?) I'm hardly flush with cash, but the electricity cost of keeping a PC on 24/7 isn't exactly breaking the bank. And the alternative of shutting it down (and taking the disks with me) when I leave, isn't terribly inconvenient, w.r.t. the risks, either. Apologies if I completely missed the point, as I so often do. And maybe I'm wrong and most Qubes users are running around with high powered, compatible laptops. I'm just looking to find out the motivations for such a feature that brings additional complexity. Cheers JJ -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/674a707e5014ac6d0121137f1d9616bb.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
On Wednesday, 28 September 2016 11:28:45 UTC+10, Drew White wrote: > On Wednesday, 28 September 2016 03:54:10 UTC+10, raah...@gmail.com wrote: > > 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. > > 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 > ystemD. 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. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8bd05fb7-5e45-4e07-9bf0-5b3b5b886bcf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
On Wednesday, 28 September 2016 03:54:10 UTC+10, raah...@gmail.com wrote:
> 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.
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
ystemD. 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?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/5d91201a-81a1-4214-88e7-95f4b36156ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
==
Wed Sep 28 10:55:01 AEST 2016
--
Filesystem Size Used Avail Use% Mounted on
devtmpfs2.0G 0 2.0G 0% /dev
tmpfs 2.0G 1.2M 2.0G 1% /dev/shm
tmpfs 2.0G 1.6M 2.0G 1% /run
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
/dev/sda324G 3.0G 20G 14% /
tmpfs 2.0G 20K 2.0G 1% /tmp
xenstore2.0G 168K 2.0G 1% /var/lib/xenstored
/dev/sda1 485M 114M 346M 25% /boot
/dev/sda2 211G 170G 31G 85% /var/lib/qubes
tmpfs 393M 0 393M 0% /run/user/{user-id}
tmpfs 393M 8.0K 393M 1% /run/user/{user-id}
/dev/sdb1 1.4T 1.4T 24G 99% /run/media/{user}/{driveid}
--
top - 10:55:01 up 29 min, 2 users, load average: 0.15, 0.11, 0.09
Tasks: 319 total, 2 running, 317 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.3 us, 0.5 sy, 0.0 ni, 98.5 id, 0.3 wa, 0.0 hi, 0.0 si, 0.4 st
KiB Mem : 4021248 total,29992 free, 647188 used, 3344068 buff/cache
KiB Swap:0 total,0 free,0 used. 3272200 avail Mem
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
1375 root 20 0 1208156 138944 16488 S 0.0 3.5 0:40.26
/usr/sbin/libvirtd
2429 root 20 0 471568 119596 46572 S 0.0 3.0 1:15.27 /usr/bin/X
-background none :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp
vt1 -novtswitch
2551 {user}20 0 1064608 110784 58184 S 0.0 2.8 0:25.71
/usr/bin/python2 /usr/bin/qubes-manager -session
22e377861-de6d-4a80-bcbb-bca633662d3a_1473145497_828268
2547 {user}20 0 725028 68748 37600 S 0.0 1.7 0:02.11 xfdesktop
--display :0.0 --sm-client-id 20f7090c4-72bd-4a35-835a-cef95d8d23a7
2543 {user}20 0 514208 36048 20136 S 0.0 0.9 0:01.34 xfce4-panel
--display :0.0 --sm-client-id 29b506d82-70ff-48be-8d61-f796aa02cdc8
2542 {user}20 0 334292 33680 17268 S 0.0 0.8 0:06.25 xfwm4
--display :0.0 --sm-client-id 20396542a-441a-4b46-b663-130920bb
6923 {user}20 0 445460 32996 18288 S 0.0 0.8 0:00.22
/usr/bin/python /usr/lib/qubes/icon-receiver
2687 {user}20 0 445192 32840 18352 S 0.0 0.8 0:00.20
/usr/bin/python /usr/lib/qubes/icon-receiver
2711 {user}20 0 445192 32648 18164 S 0.0 0.8 0:00.17
/usr/bin/python /usr/lib/qubes/icon-receiver
1523 root 20 0 583180 31364 18204 S 0.0 0.8 0:00.56
/usr/bin/python2 /usr/lib/qubes/qmemman_daemon.py
2534 {user}20 0 479428 27896 13400 S 0.0 0.7 0:00.64
xfce4-session
3533 {user}20 0 559228 26944 21204 S 0.0 0.7 0:33.49
/usr/bin/Thunar file:///run/media/{user}/Drew1_5
2557 {user}20 0 488024 24140 19360 S 0.0 0.6 0:00.18
xfce4-power-manager --restart --sm-client-id
2d75b6a48-8608-4e8e-a374-d28b1677ed75
2729 {user}20 0 524880 21396 17600 S 0.0 0.5 0:01.24
/usr/bin/xfce4-terminal
2576 {user}20 0 712960 21216 17804 S 0.0 0.5 0:00.08
/usr/lib64/xfce4/panel/wrapper-1.0 /usr/lib64/xfce4/panel/plugins/libmixer.so
13 18874411 mixer Audio Mixer Adjust volume levels
2593 {user}20 0 463612 20388 17640 S 0.0 0.5 0:00.21
/usr/lib64/xfce4/notifyd/xfce4-notifyd
2595 {user}20 0 474064 19536 16768 S 0.0 0.5 0:00.34
/usr/lib64/xfce4/panel/wrapper-1.0 /usr/lib64/xfce4/panel/plugins/libfsguard.so
8 18874418 fsguard Free Space Checker Monitor free disk space
2599 {user}20 0 459648 18588 16292 S 0.0 0.5 0:06.85
/usr/lib64/
Re: [qubes-users] System still freezes, still no resolution.
On Wednesday, 28 September 2016 03:54:10 UTC+10, raah...@gmail.com wrote: > 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. 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? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ba8e5b49-1540-4e93-9342-c98c09e25c5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
On Wednesday, 28 September 2016 03:54:10 UTC+10, raah...@gmail.com wrote: > 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. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2e08aed4-1cc5-4d98-ab7e-2c1c14200cf1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
On Monday, September 26, 2016 at 4:00:38 AM UTC-4, Drew White wrote: > On Monday, 26 September 2016 15:31:19 UTC+10, Foppe de Haan wrote: > > usb input devices? if so, can you attach a ps/2 mouse/keyboard and does > > that do anything? also, maybe have a look at bios settings related to > > (sleep/wake from) usb? > > 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. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cb164323-fabb-44d8-8942-5d156f7136c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
On Monday, 26 September 2016 15:31:19 UTC+10, Foppe de Haan wrote: > usb input devices? if so, can you attach a ps/2 mouse/keyboard and does that > do anything? also, maybe have a look at bios settings related to (sleep/wake > from) usb? Doesn't matter. USB or not, it doesn't respond to input. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9f403973-8673-4783-bcd6-17625dbcc5ef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
On Monday, September 26, 2016 at 2:45:44 AM UTC+2, Drew White wrote: > On Friday, 23 September 2016 18:05:39 UTC+10, Simon wrote: > > Hello Drew, > > > > > 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. > > > > I share your frustration. Which computer are you using? Are your > > applications > > still running in the background (ie. only the graphical interface is > > frozen) > > or is it a complete system freeze? > > > > On my side I'm running Qubes on a Lenovo Thinkpad T500 and I just wrote > > a > > similar request as yours just a few days ago: > > > > https://groups.google.com/forum/#!topic/qubes-users/O4UO9CjO4TM > > > > On my side the graphical display is frozen, and with KDE I managed to > > workaround the issue by setting KWin to use XRender instead of OpenGL as > > compositing engine. After that the system became rock-solid and I never > > encountered such freeze anymore for months, while it happened about once > > a > > week until that. > > > > The sad thing is that Qubes has now switched to XFCE, the freezes came > > back > > and I do not know any equivalent setting on XFCE. I recently tried to > > completely disable compositing and am now crossing my fingers. > > > > Regards, > > Simon. > > 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. usb input devices? if so, can you attach a ps/2 mouse/keyboard and does that do anything? also, maybe have a look at bios settings related to (sleep/wake from) usb? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7e83656a-75be-4798-abc5-352f010115e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] System still freezes, still no resolution.
On Friday, 23 September 2016 18:05:39 UTC+10, Simon wrote: > Hello Drew, > > > 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. > > I share your frustration. Which computer are you using? Are your > applications > still running in the background (ie. only the graphical interface is > frozen) > or is it a complete system freeze? > > On my side I'm running Qubes on a Lenovo Thinkpad T500 and I just wrote > a > similar request as yours just a few days ago: > > https://groups.google.com/forum/#!topic/qubes-users/O4UO9CjO4TM > > On my side the graphical display is frozen, and with KDE I managed to > workaround the issue by setting KWin to use XRender instead of OpenGL as > compositing engine. After that the system became rock-solid and I never > encountered such freeze anymore for months, while it happened about once > a > week until that. > > The sad thing is that Qubes has now switched to XFCE, the freezes came > back > and I do not know any equivalent setting on XFCE. I recently tried to > completely disable compositing and am now crossing my fingers. > > Regards, > Simon. 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) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/e7e03868-aa8e-4c97-a870-60e31c087b0a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. == Mon Sep 26 10:10:01 AEST 2016 -- Filesystem Size Used Avail Use% Mounted on devtmpfs2.0G 0 2.0G 0% /dev tmpfs 2.0G 8.1M 2.0G 1% /dev/shm tmpfs 2.0G 1.7M 2.0G 1% /run tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup /dev/sda324G 2.9G 20G 13% / tmpfs 2.0G 16K 2.0G 1% /tmp xenstore2.0G 256K 2.0G 1% /var/lib/xenstored /dev/sda1 485M 114M 346M 25% /boot /dev/sda2 211G 143G 58G 72% /var/lib/qubes tmpfs 393M 0 393M 0% /run/user/992 tmpfs 393M 8.0K 393M 1% /run/user/1000 -- top - 10:10:01 up 2 days, 18:41, 3 users, load average: 0.00, 0.00, 0.00 Tasks: 370 total, 1 running, 369 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.1 us, 0.1 sy, 0.0 ni, 99.7 id, 0.0 wa, 0.0 hi, 0.0 si, 0.1 st KiB Mem : 4021248 total,43140 free, 817852 used, 3160256 buff/cache KiB Swap:0 total,0 free,0 used. 3086124 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2546 %uname20 0 1066044 203512 55316 S 0.0 5.1 61:26.53 /usr/bin/python2 /usr/bin/qubes-manager -session 22e377861-de6d-4a80-bcbb-bca633662d3a_1473145497_828268 2415 root 20 0 503664 08 46156 S 0.0 2.8 20:37.22 /usr/bin/X -background none :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch 515 root 20 0 160628 101244 100876 S 0.0 2.5 0:24.84 /usr/lib/systemd/systemd-journald 1362 root 20 0 1194384 91964 16456 S 0.0 2.3 121:32.11 /usr/sbin/libvirtd 2533 %uname20 0 723912 69496 37820 S 0.0 1.7 0:13.11 xfdesktop --display :0.0 --sm-client-id 20f7090c4-72bd-4a35-835a-cef95d8d23a7 2529 %uname20 0 512576 36528 20284 S 0.0 0.9 0:07.31 xfce4-panel --display :0.0 --sm-client-id 29b506d82-70ff-48be-8d61-f796aa02cdc8 2528 %uname20 0 498660 36412 19876 S 0.0 0.9 3:33.63 xfwm4 --display :0.0 --sm-client-id 20396542a-441a-4b46-b663-130920bb 4418 %uname20 0 445452 33208 18504 S 0.0 0.8 0:00.75 /usr/bin/python /usr/lib/qubes/icon-receiver 4825 %uname20 0 445452 33176 18476 S 0.0 0.8 0:00.25 /usr/bin/python /usr/lib/qubes/icon-receiver 3393 %uname20 0 445452 33140 18436 S 0.0 0.8 0:00.31 /usr/bin/python /usr/lib/qubes/icon-receiver 2663
Re: [qubes-users] System still freezes, still no resolution.
Hello Drew, 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. I share your frustration. Which computer are you using? Are your applications still running in the background (ie. only the graphical interface is frozen) or is it a complete system freeze? On my side I'm running Qubes on a Lenovo Thinkpad T500 and I just wrote a similar request as yours just a few days ago: https://groups.google.com/forum/#!topic/qubes-users/O4UO9CjO4TM On my side the graphical display is frozen, and with KDE I managed to workaround the issue by setting KWin to use XRender instead of OpenGL as compositing engine. After that the system became rock-solid and I never encountered such freeze anymore for months, while it happened about once a week until that. The sad thing is that Qubes has now switched to XFCE, the freezes came back and I do not know any equivalent setting on XFCE. I recently tried to completely disable compositing and am now crossing my fingers. Regards, Simon. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cbcb5184437ac80fb4bead50c187364c%40whitewinterwolf.com. For more options, visit https://groups.google.com/d/optout.
