Cannot start apps using template based on Debian Testing

46 views
Skip to first unread message

Fernando

unread,
Mar 20, 2018, 9:43:49 AM3/20/18
to qubes-users
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.

Yuraeitha

unread,
Mar 20, 2018, 10:00:55 AM3/20/18
to qubes-users

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?

Fernando

unread,
Mar 20, 2018, 10:13:13 AM3/20/18
to qubes-users

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.

Yuraeitha

unread,
Mar 20, 2018, 11:03:54 AM3/20/18
to qubes-users

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.

Unman

unread,
Mar 20, 2018, 2:24:56 PM3/20/18
to Fernando, qubes-users
Despite your warning I've just updated my template on 3.2 , and things
seem to be working fine.
Actually, if the qube is not running and I select from menu, then no
window appears, but selecting from the menu again opens the window.
Also, starting using qvm-run just works. (I have most mapped to
keyboard shortcuts and they work fine.)

Can you try an update again?

Fernando

unread,
Mar 20, 2018, 2:50:36 PM3/20/18
to qubes-users

Hi Unman,

I haven't received more updates from debian testing repos, so no changes.

I did experience the issue with windows appearing after seconde attempt, this was already reported a long time ago and I recall this could be fixed with an env variable.

From what your "menu" reference I assume we are using different desktop managers? I'm using i3, perhaps that's part of the mix.

Unman

unread,
Mar 20, 2018, 3:40:23 PM3/20/18
to Fernando, qubes-users
Ah, OK I'm using KDE.
Maybe the issue IS i3.
AS always with testing, let's see what happens down the line.


Fernando

unread,
Mar 24, 2018, 12:28:11 PM3/24/18
to qubes-users

As you said, this was just a glitch in testing. I run a large upgrade today and everything seems to be back on its feet.

This was a good reminder to keep the stable debian template handy just in case.

Reply all
Reply to author
Forward
0 new messages