>>  /usr/libexec/xdg-desktop-portal[7391]: A backend call failed: Inhibiting 
>> other than idle not supported
>
>Please provide more information:
>What desktop are you using?

Mate

>Does this happen immediately after restarting your computer without
>running any other apps?

I seldom restart this box.  The first such message is logged on 2026-07-28 
11:45, which is far away from any dpkg installation or update, and I see 
nothing apparent in the logs before that time.  At that time I was regularly 
working on this box, and I don't remember noticing anything strange.

>Is there anything interesting in the output of systemd-inhibit ?

I did not know about systemd-inhibit.  I do not see anything suspicious, but 
again I do not know how it usually behaves

WHO             UID  USER PID     COMM            WHAT                          
                        WHY                                         MODE
NetworkManager  0    root 1744    NetworkManager  sleep                         
                        NetworkManager needs to turn off networks   delay
Realtime Kit    0    root 1539    rtkit-daemon    sleep                         
                        Demote realtime scheduling and stop canary. delay
UPower          0    root 563180  upowerd         sleep                         
                        Pause device polling                        delay
pot             1000 pot  7558    mate-power-mana 
handle-power-key:handle-suspend-key:handle-lid-switch Mate power manager 
handles these events     block
teams-for-linux 1000 pot  3434946 teams-for-linux sleep                         
                        Application cleanup before suspend          delay
xscreensaver    1000 pot  7561    xscreensaver-sy sleep                         
                        lock screen on suspend                      delay

6 inhibitors listed.

>Is there anything related in your systemd journal (maybe run sudo journalctl 
>-b )

No, boot was far away.

Looking at the logs, something made me suspicious and I restarted 
telegram-desktop, which stopped the behaviour that I had reported.

Here are the lines in syslog that relate to telegram-dsktop after restart:

dbus-daemon[6168]: [session uid=1000 pid=6168 pidfd=5] Activating service 
name='org.telegram.desktop' requested by ':1.35' (uid=1000 pid=7501 
comm="mate-panel" label="unconfined")
dbus-daemon[6168]: [session uid=1000 pid=6168 pidfd=5] Successfully activated 
service 'org.telegram.desktop'
org.telegram.desktop[4025135]: error: empty dic file
org.telegram.desktop[4025135]: Hash Manager Error : 2
org.telegram.desktop[4025135]: QPainter::begin: Paint device returned engine == 
0, type: 2
org.telegram.desktop[4025135]: QWidget::render: Cannot render with an inactive 
painter
org.telegram.desktop[4025135]: QRhiGles2: Failed to make context current. 
Expect bad things to happen.
dbus-daemon[6168]: [session uid=1000 pid=6168 pidfd=5] Activating service 
name='org.freedesktop.Notifications' requested by ':1.701' (uid=1000 
pid=4025135 comm="/usr/bin/telegram-desktop" label="unconfined")

Reply via email to