On Tuesday, March 20, 2018 at 3:13:13 PM UTC+1, Fernando wrote: > On Tuesday, March 20, 2018 at 11:00:55 AM UTC-3, Yuraeitha wrote: > > On Tuesday, March 20, 2018 at 2:43:49 PM UTC+1, Fernando wrote: > > > This is more of a warning for those using Debian Testing. I updated my > > > Debian Testing template this morning and I couldn't start any app since. > > > I am using Qubes 3.2. > > > > > > Using qvm-run does not report any errors, not sure if I should check any > > > specific logs. > > > > > > As a workaround I'm using another template with Debian 9. > > > > > > Regards, > > > > > > Fernando. > > > > If I read this right, Debian 8 fails, but Debian 9 doesn't? > > It might also be a good idea to switch to Debian 9 anyhow, we're getting > > closer and closer to end-of-life for Debian 8, which is the 6th of June, > > 2018 https://wiki.debian.org/DebianReleases > > > > Also which updates was it? Were they of Debian origin? Qubes origin? > > I don't have Debian 8 installed. Debian Testing is ahead of Debian 9. > > I cannot tell exactly which update it was since I updated both qubes and the > different templates. Since Debian 9 is working normally, I assume this > happens due to a recent update to Debian Testing. > > Also, this only seems to affect graphic apps (terminal, emacs, etc). My > split-gpg backend domain still works with Debian Testing. > > If someone wants me to perform additional testing to assist debugging just > let me know.
aha, I see. I can't test this my self as I'm on Qubes 4, and this update I either already installed, or it's not arriving for Qubes 4, right now I have no pending current-resting updates for Debian 9. Can you do an update on debian-9 without accepting the updates, and then copy-paste it here? If you feel uncomfortable with that, you can also make a clone of it before doing it, though it shouldn't be needed as long as you decline the updates. The developers can probably debug this without having us do this, but it might cut the work burden for them if we can identity the specific package causing the problem. Be careful you don't hit y instead of t in the command below though, they're right next to each others on the keyboard, and it'd be fatal if it auto-installs those current-testing. So double-check before you hit enter, or copy/paste it over. Step1: user@debian-9:~$ sudo apt-get update -t *-testing && sudo apt-get dist-upgrade -t *-testing Step2: Decline the updates, don't accept them. Step3: copy-paste the print-out of the downloadable content to your post here. Step4: To clean up any potential leftovers from testing, although it's mostly only needed on fedora, but for good measures sake. user@debian-9:~$ sudo apt-get clean It's a bit of a problem that you upgraded dom0 though, since it's now no longer in sync with your other templates. I assume the only one not in sync is your debian-9 template though? It might be a good idea to keep track of which domU template isn't in sync with dom0 anymore, so you can correct it if you experience new future problems. -- 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/9e5be0be-93a6-44b6-bf86-88f245dcf224%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
