Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
There appear to neither be any relevant crash files (there are a couple
which predate upgrading this system to focal), nor are there any reports
on errors.u.c for this whoopsie-id.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-ses
** Changed in: gnome-session (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1871580
Title:
Session killed instead of suspended on s
In that case please reproduce the problem and then immediately run:
journalctl -b0 > journal.txt
and send us the resulting file.
If you have to reboot before you are able to run journalctl then please
run:
journalctl -b-1 > prevjournal.txt
instead.
--
You received this bug notification b
Session lock invoked manually (~11:00:00), lock screen displays, click
mouse to get unlock.
Screen freezes for ~10 seconds, then blanks briefly and shows login
screen.
Looks like gnome-shell crashing at about 11:00:26 - interesting lines:
Apr 08 11:00:26 kallisti gnome-shell[23758]:
clutter_act
Thanks, that makes more sense, now why is apport not catching that one?
Could you look if there is something registered in /var/log/apport.log?
does it makes a difference if you
$ sudo service apport start force_start=1
then trigger the issue and see if apport picks the problem
--
You received
Lots of repetitions of:
```
ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: called for pid 7223, signal
11, core limit 0, dump mode 1
ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: executable:
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 7294) Wed Apr 8 1
Deleting the old _usr_bin_gnome-shell.1000.crash and collecting a fresh
one.
However, a quick bit of experimentation appears to show that this crash
only occurs with extensions enabled - after globally disabling
extensions it appears to no longer occur. I haven't bisected extensions
individually,
could you use 'ubuntu-bug _usrcrash' to report the issue, adding the
dump to a comment like you did isn't really useful. If that's an
extension doing then it would be nice knowing which one but it's
probably not a gnome-session/shell issue at this point
--
You received this bug notification b
Uploaded in #1871580. Looking through gnome-shell issues, #1868440 looks
like it might also be the same thing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1871580
Title:
Sess
*** This bug is a duplicate of bug 1868440 ***
https://bugs.launchpad.net/bugs/1868440
** This bug has been marked a duplicate of bug 1868440
gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
--
You received this bug notification because you are a member of Desktop
Pac
11 matches
Mail list logo
