Thanks. Bug 1884925 only confirms that:
[70766.731562] eva1 gnome-shell[3790]: toggling down object GInotifyFileMonitor
that's already queued to toggle up
[70766.734900] eva1 gnome-shell[3790]: GNOME Shell crashed with signal 5
[70766.734900] eva1 gnome-shell[3790]: == Stack trace for context
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
(ie is it safe to power on my computer after doing so or should i be
changing the password or something? )
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell
done. hope i didn't just give away too much info
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882410
Title:
GNOME Shell crashed with signal 5
Status in gnome-shell package
Good, bug 1884925 is what I need to look at then. But I can't because it
is private. Are you able to set bug 1884925 to public?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
the file was in /var/crash hence where bug #1884925 's contents came
from
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882410
Title:
GNOME Shell crashed with signal 5
Status
Try this:
Settings > Privacy > Diagnostics > Send error reports to Canonical =
Automatic
then reproduce the crash and hopefully errors.ubuntu.com will show it.
Although I would hope that even with 'Manual' set you would find the
crash file in /var/crash ..?
--
You received this bug
still nothing in https://errors.ubuntu.com/user/ID since 2017
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882410
Title:
GNOME Shell crashed with signal 5
Status in
We still don't have any usable information here, sorry. Please follow
all the steps in comment #2 again.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
done
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1882410
Title:
GNOME Shell crashed with signal 5
Please try using 'apport-cli' instead of 'ubuntu-bug'. Please also
follow all the steps in comment #2.
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
actually that little error window has a bunch of data in it
stack seems to be
() at /usr/lib/libgjs.so.0
() at /usr/lib/libgjs.so.0
() at /usr/lib/libgjs.so.0
i'm going to try installing the symbols for that and reproduce again
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete =>
reproduced and got a crash file
but...
themusicgod1@eva1:~$ ubuntu-bug /var/crash/_usr_bin_gnome-
shell.1001.crash
consistently results in Sorry, Ubuntu 20.04 has experienced an internal
error
If you notice further problems, try restarting the computer
stack:
/usr/bin/gnome-shell
--
You
alas there are 2 files in /var/crash neither of them line up with when
the crash happened
nothing in https://errors.ubuntu.com/user/ID since 2017
I've made the change to /etc/apport/crashdb.conf (that was the
workaround right?)
we'll see when it happens again after I reboot next
--
You
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
15 matches
Mail list logo
