[qubes-users] Re: HCL - Lenovo Thinkpad E15
Update: Everything seems to work now! The system suspends and recovers correctly. The cursor lag has disappeared. Another problem of slow, choppy video and no audio has also disappeared. The system has been working correctly for about 2 months now. I suppose one of the updates resolved the problems. I have not tried hibernate yet as I don't use it. I will probably try it at some time and will report. In the future I will install the latest version and use both drives on this laptop. Many thanks to the Qubes people for a great system! I will donate! On Wednesday, July 8, 2020 at 10:52:11 PM UTC Pmonf wrote: > I recently installed Qubes 4.0.3 on a new Thinkpad E15 Intel i-5-10210U > with 16GB ram with a 512SSD and a 1T drive. The installation was on the > SSD. I had two failures on installation (wiping the pesky windoze) both > times while entering the user password. Error was "unexpected error". I did > not report it and selected "quit". I then decided to try installing LM 19.2 > and then see if Qubes would install over that. It worked! Qubes is the only > os installed and it is on the 512SSD. > > Everything seems to work so far, except: > >1. The apparently common problem of not resuming after suspend, and >having to button off to shut down. I have not tried hibernate yet. >2. The touchpad and mouse cursor does not move smoothly across the >screen. It hops. It was necessary to select a larger windows scheme in >order to have a bigger target for the cursor's inprecise movements. Not >sure if this may be a memory problem or how to fix it. If anyone knows I >would like to hear it. > > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/96ea28b1-3262-4449-abcc-660e5ff46331n%40googlegroups.com.
Re: [qubes-users] SLS update Fail
On Mon, Feb 22, 2021 at 01:52:32PM -0800, Alexander Reseneder wrote: > Hello qubes-users, > > can someone tell me maybe what i have configured wrong or what i have to do > to fix that update failure? > > [image: fedora_sls_update_fail.png] > > Greetings > Alex > I cant see that - can you at least provide a clue as to what the failure is? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20210224155202.GC5777%40thirdeyesecurity.org.
Re: [qubes-users] trouble with apt-get on dabian
Steve Coleman: I installed the stock Debian-10 rpm yesterday and it also fails to update using the default proxy. The whonix templates based on Debian work because they are using a different update vm. I really don't have a clue how all the Fedora templates work using the exact same default update proxy while the Debian ones do not. I have not made any deliberate custom modifications to any of the update settings, but something obviously changed. My suspicion is on the receiving side proxy configuration in sys-firewall but I don't know how to debug that. With the TERM setting being complained about I am wondering how this proxy is being launched without a full set of environment variables. This error text is in red, as coming through the pipe, so its on the other side, not in the template itself. The update pipe is not a terminal afaik so I don't know why the proxy would be complaining it doesn't know the terminal type. But then why does the Fedora update still work and Debian not using the exact same update gateway. Very odd. I agree, sounds like something broken in sys-firewall given your other UpdateVM is working. You could change your templates to use the same UpdateVM as Whonix if you wanted to confirm. Otherwise, there's nothing special about the sys-firewall AppVM. If you don't mind recreating any firewall rules, try creating a new AppVM and confirm you don't get that TERM warning at the terminal. Next, change anything that points to sys-firewall for networking to the new one, and make it your new UpdateVM? -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d4fc7d1d-e1b2-0f10-a127-a104fe627636%40danwin1210.me.
