[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Stéphane, please subscribe to bug 1866368 for your issue. Based on the
information in comment #8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866222
Title:
GNOME Shell crashed with signal 11
To
Stéphane, please do not comment on this bug. Instead please open a new
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866222
Title:
GNOME Shell crashed with signal 11
To manage notifications
I will look into it.
Here is how to reproduce the bug very easily:
- open LibreOffice Writer
- open Firefox
- resize and move the windows so that they don't overlap
- drag the Firefox tab (not window) over LibreOffice
Then you instantly get the crash.
--
You received this bug notification
Hello Stéphane Witzmann (swzn),
Please:
https://wiki.ubuntu.com/DebuggingProgramCrash
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866222
Title:
GNOME Shell crashed with signal 11
To
Here is the backtrace and registers.
At first I couldn't reproduce the bug by just moving youtube videos (in
firefox) around. But then when I had a document in LibreOffice Writer open
(which is the situation I was in over the last few days of crashes), it
happened very easily.
---
Thread 1
Here is a log with a few crashes. It seems to always come after a few of
these:
Mar 6 01:24:57 wolfenstein rtkit-daemon[1197]: Supervising 9 threads of 5
processes of 1 users.
Mar 6 01:30:29 wolfenstein rtkit-daemon[1197]: message repeated 19 times: [
Supervising 9 threads of 5 processes of 1
Unfortunately the bug is still incomplete because all we have is:
[79676.217368] jik-x1 gnome-shell[3082]: GNOME Shell crashed with
signal 11
meaning nobody can possibly work on this yet.
Next time it happens, please reboot and then immediately run:
journalctl -b-1 > prevboot.txt
and
I already have the workaround in bug 994921 and have for a long time. My
system has generated and reported crashes as recently as February 28.
There's no crash for this in /var/crash.
There's no crash for this on errors.ubuntu.com.
For some reason, when this crash occurs it's not generating a
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
Thanks for the bug report. There is a hint of the issue in the attached
logs:
[79661.914093] jik-x1 gnome-shell[3082]: 0x1800143: frame_complete callback
never occurred for frame 464843
[79661.914311] jik-x1 gnome-shell[3082]: 0x1800143: frame_complete callback
never occurred for frame 464842
Got the same bug (GNOME Shell crashed with signal 11 after a short video
freeze) on 20.04. It's pretty recent, it's been crashing my computer a
couple of times a day since March 3 (according to the logs). I keep my
computer updated every day. Seems to happen when I move a video from one
monitor to
12 matches
Mail list logo
