After the 2 latest dom0 Updates telegram desktop doesn’t work anymore.
VM ist debian-10 standalone, also tried fedora-32.
To rule out VM relates issues, I tried a clone of the debian-10 VM that
was made before VM Updates were applied. Still doesn’t work with this
unmodified VM.
When telegram ist started, it blriefly shows the GUI, and then
terminates.
After that, no GUI program in the VM works anymore, but the VM is still
alive and able to show the console.
While telegram desktop is started from the qubes console, the following
messages appear:
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/runtime-user'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to
'/tmp/runtime-user'
[ALSOFT] (EE) Failed to set real-time priority for thread: Operation
not permitted (1)
journalctl shows:
Jan 23 13:24:37 signal pulseaudio[860]: sink cork req state =1, now
state=2
Jan 23 13:24:37 signal pulseaudio[860]: source cork req state
=1, now state=2
Jan 23 13:24:37 signal dbus-daemon[751]: [session
uid=1000 pid=751] Activating via systemd: service
name='org.freedesktop.Notifications' unit='xfce4-notifyd.service'
requested by ':1.17' (uid=1000 pid=978 comm="Telegram/Telegram ")
Jan 23 13:24:37 signal systemd[672]: Starting XFCE notifications
service...
Jan 23 13:24:37 signal dbus-daemon[751]: [session uid=1000
pid=751] Activating service name='org.xfce.Xfconf' requested by ':1.19'
(uid=1000 pid=994
comm="/usr/lib/x86_64-linux-gnu/xfce4/notifyd/xfce4-noti")
Jan 23 13:24:37 signal dbus-daemon[751]: [session uid=1000 pid=751]
Successfully activated service 'org.xfce.Xfconf'
Jan 23 13:24:37 signal qubes-gui[565]: libvchan_is_eof
Jan 23 13:24:37 signal dbus-daemon[751]: [session uid=1000 pid=751]
Successfully activated service 'org.freedesktop.Notifications'
Jan 23 13:24:37 signal
systemd[672]: Started XFCE notifications service.
Jan 23 13:24:42 signal pulseaudio[860]: source cork req state =2, now
state=1
Jan 23 13:24:42 signal pulseaudio[860]: sink cork req state =2, now
state=1
It may be that I’m up to date with current-testing? idk.
Have you tried creating a new AppVM for it? No other apps with these problems? AppVM has free space in /home?
I created a standalone AppVM from debian-11 template as well as a normal AppVM with the template. I updated debian-11 to the latest. Still no success.
Always tried with a fresh VM with 1.9 GB free space on /home.