Maybe try to uninstall all installed nvidia drivers, and then run your machine with vesa. I know oft Solus Linux that this was a bug in nvidia drivers.
Carl-Valentin Schmitt <cv.schm...@gmail.com> schrieb am So., 5. Aug. 2018, 23:54: > Is this a machine with nvidia graphics card and nvidia drivers? > > Riccardo Gagliarducci <inl...@libero.it> schrieb am So., 5. Aug. 2018, > 23:51: > >> I'm leaving for holidays, may I freeze this bug until end of August? >> >> In dmsg, I found: >> [ 6737.746966] gnome-shell[2131]: segfault at 663466343778 ip >> 00007f0a52cf3c31 sp 00007ffd58e51e98 error 4 in libgobject- >> 2.0.so.0.5600.1[7f0a52cbe000+52000] >> >> But I'd like to investigate more... >> Thank you, >> Riccardo >> >> >> Il giorno sab, 04/08/2018 alle 02.21 +0200, Simon Richter ha scritto: >> > Hi, >> > >> > On 04.08.2018 01:32, Riccardo Gagliarducci wrote: >> > >> > > after firmware update it still happens ~once a day, >> > > still without doing anything particular. >> > >> > Is anything listed in the kernel log? >> > >> > After a crash, log back in, then, as root: >> > >> > # cat /proc/uptime >> > >> > The first number is the number of seconds the system is running. >> > >> > # dmesg >> > >> > This will dump the kernel logfile to the console. At the beginning of >> > each line is a timestamp. The uptime you got earlier gives you a >> > rough >> > estimate which lines are recent, these have a good chance of being >> > related. >> > >> > Simon >> > >> >>
