On Bullseye (11.5), needrestart seems to think that nextcloud-desktop is
using (or trying to use) an obsolete binary. One solution would be to
provide a backport.

With nextcloud-desktop running, needrestart reports that my user is
running an outdated binary. Shut it down, and needrestart no longer
reports the obsolete binary.

root@hawk:~# needrestart
Scanning processes...                                                           
Scanning candidates...                                                          
Scanning processor microcode...                                                 
Scanning linux images...                                                        

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

User sessions running outdated binaries:
 charles @ session #124: xfce4-session[19932]
root@hawk:~# needrestart
Scanning processes...                                                           
Scanning processor microcode...                                                 
Scanning linux images...                                                        

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.
root@hawk:~#

To determine the culprit, run needrestart -v. If nextcloud is running,
the results should include the line

[main] #2532 uses deleted /memfd:JITCode:QtQml

That process number (2532 here) will show the name of the culprit
process.

root@jhegaala:~# ps aux | grep 2532
charles     2532  0.0  0.7 2697296 58392 ?       SLl  Sep11   0:40 
/usr/bin/nextcloud -session 
23e541bc3-39c1-4c76-9d33-b673c5b89dd4_1647017860_281775
root       36710  0.0  0.0   6376   704 pts/9    S+   12:00   0:00 grep 
--colour=auto 2532
root@jhegaala:~# 


-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Reply via email to