gnome-shell[1493]: segfault at 20 ip 00007fe7ecafeb17 sp 00007fff5e70ba60 error 4 in libmutter-2.so.0.0.0[7fe7eca11000+156000]
I have this exact segfault too. I’m on a cherry trail atom z8350.
Previously this segfault didn’t occur and the system went to suspend and it could be brought up via keyboard.
I didn’t want it to suspens so changed the suspend settings which didn’t change anything.
Suspend still occurred every 5 min.
So I did disabled suspend via the command line through systemctl.
Then the libmitter2 segfault kept occurring and eventually made the system run out of memory.
I’ll try and get a core dump if it’s available. But my problem is the libmitter2 segfault.
I thought 18.04 defaults to xorg. Why is libmitter2 even segfaulting???
gnome-shell[1493]: segfault at 20 ip 00007fe7ecafeb17 sp 00007fff5e70ba60 error 4 in libmutter- 2.so.0. 0.0[7fe7eca1100 0+156000]
I have this exact segfault too. I’m on a cherry trail atom z8350.
Previously this segfault didn’t occur and the system went to suspend and it could be brought up via keyboard.
I didn’t want it to suspens so changed the suspend settings which didn’t change anything.
Suspend still occurred every 5 min.
So I did disabled suspend via the command line through systemctl.
Then the libmitter2 segfault kept occurring and eventually made the system run out of memory.
I’ll try and get a core dump if it’s available. But my problem is the libmitter2 segfault.
I thought 18.04 defaults to xorg. Why is libmitter2 even segfaulting???