Continuo a vedere una finestra di dialogo di "errore interno" all'avvio (vedi sotto per l'intestazione del file .crash).
Nota, /usr/lib/virtualbox/VirtualBoxVM non esiste (dal riavvio dell'ultima coppia) e l'errore continua a essere visualizzato.
Ecco l'output di ls /var/crash :
(base) [email protected]:~$ ls -l /var/crash
total 24480
-rw-r----- 1 au whoopsie 16389469 Jan 2 09:36 _usr_bin_pulseaudio.1000.crash
-rw-rw-r-- 1 au whoopsie 0 Jan 2 09:36 _usr_bin_pulseaudio.1000.upload
-rw------- 1 whoopsie whoopsie 37 Jan 2 09:36 _usr_bin_pulseaudio.1000.uploaded
-rw-r----- 1 root whoopsie 8655015 Jan 8 00:23 _usr_lib_virtualbox_VirtualBoxVM.0.crash
-rw-r--r-- 1 root whoopsie 10082 Jan 8 00:17 virtualbox-dkms.0.crash
Ecco l'intestazione (meno il coredump) di /var/crash/_usr_lib_virtualbox_VirtualBoxVM.0.crash :
ProblemType: Crash
Architecture: amd64
Date: Fri Jan 8 00:23:30 2021
DistroRelease: Ubuntu 20.04
ExecutablePath: /usr/lib/virtualbox/VirtualBoxVM
ExecutableTimestamp: 1591443097
ProcCmdline: /usr/lib/virtualbox/VirtualBoxVM --comment w10 --startvm 6bad7132-1231-4cf8-8ac2-5a2a99493c86 --no-startvm-errormsgbox
ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
ProcMaps: Error: [Errno 13] Permission denied: 'maps'
ProcStatus:
Name: VirtualBoxVM
Umask: 0002
State: S (sleeping)
Tgid: 3479
Ngid: 0
Pid: 3479
PPid: 1866
TracerPid: 0
Uid: 1000 1000 1000 1000
Gid: 1000 1000 1000 1000
FDSize: 64
Groups: 4 24 27 30 46 120 131 132 1000
NStgid: 3479
NSpid: 3479
NSpgid: 3477
NSsid: 3138
VmPeak: 382984 kB
VmSize: 371348 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM: 69868 kB
VmRSS: 68296 kB
RssAnon: 17056 kB
RssFile: 51240 kB
RssShmem: 0 kB
VmData: 39764 kB
VmStk: 132 kB
VmExe: 40 kB
VmLib: 80832 kB
VmPTE: 404 kB
VmSwap: 0 kB
HugetlbPages: 0 kB
CoreDumping: 1
THP_enabled: 1
Threads: 3
SigQ: 0/256693
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000001001000
SigCgt: 0000000180000000
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000
CapBnd: 000000ffffffffff
CapAmb: 0000000000000000
NoNewPrivs: 0
Seccomp: 0
Speculation_Store_Bypass: thread vulnerable
Cpus_allowed: ffffffff
Cpus_allowed_list: 0-31
Mems_allowed: 00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000000,00000001
Mems_allowed_list: 0
voluntary_ctxt_switches: 1149
nonvoluntary_ctxt_switches: 65
Signal: 6
Uname: Linux 5.8.0-36-generic x86_64
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
Risposta accettata:
Vorrei rimuovere i file:
sudo rm /var/crash/_usr_lib_virtualbox_VirtualBoxVM.0.crash
sudo rm /var/crash/virtualbox-dkms.0.crash
Vedi questo articolo per ulteriori informazioni:
https://itsfoss.com/how-to-fix-system-program-problem-detected-ubuntu/
Modifica:
Vale la pena notare, non sosterrei la disabilitazione di Apport, come fa l'autore dell'articolo. In base alla mia esperienza, ho eliminato /var/crash/ quando questi popup iniziano a comparire ad ogni riavvio è sufficiente e abbastanza conveniente.