Thanks. That's bug 1864326 as I suspected in comment #24.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
Ok, I've reported it as bug #1871554.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
mutter:ERROR:../src/core/window.c:4841:set_workspace_state:
Do you mean I should recreate this exact same bug and then report it as
another one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
Thanks. The log in comment #27 doesn't seem to provide clarification
other than it *doesn't* look like this bug at all, or any crash for that
matter. And the link in comment #28 is not retraceable :(
So I think we were right to call this bug closed in comment #24. But
also you seem to be
Do you mean a link to the original crash? This one has the same date as
the bug report:
https://errors.ubuntu.com/oops/4bb4a564-f475-11e9-b5e5-fa163e102db1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Output of journal -b0"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849249/+attachment/5348700/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I would like to verify *which* crash that is. Can you please attach a
log:
journalctl -b0 > journal.txt
and/or identify a crash report link?
Look at https://errors.ubuntu.com/user/ID where ID is the content of
file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links
to recent
Oh, I spoke too soon. I tested it yesterday and it passed, but today it
failed. I had geany on the primary monitor this time.
** Changed in: gnome-shell (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Weird. I can't find an exactly matching upstream bug. And the closest
fix I can find was mutter!1029 which was released in 3.35.90 already.
Regardless, the original reporter says it is fixed AND the ubuntu error
tracker says the crash hasn't occurred since version 3.34.1.
If you experience any
This is fixed for me in gnome-shell 3.36.0-2ubuntu2, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
** Changed in: gnome-shell
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
Still happens every time in gnome-shell 3.36.0-2ubuntu1 / geany
1.36-1build1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
** Changed in: gnome-shell
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #944
https://gitlab.gnome.org/GNOME/mutter/issues/944
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/mutter/issues/944
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
** Description changed:
https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b
- https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8
gnome-shell crashes with this bug every time that:
* I am editing a file in geany
* I open the Find window
Also tracking in:
https://errors.ubuntu.com/problem/a3cac4e2a5f6847233c7e4fd6cb99b9428f60ad8
as well the existing:
https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b
** Tags added: focal
** Description changed:
This is still 100% reproducible with with an up-to-date Ubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
I also see this assertion with a slightly different line number:
[ 4892.053454] desktop gnome-shell[4423]:
mutter:ERROR:../src/core/window.c:4849:set_workspace_state: assertion
failed: (workspace == NULL)
I installed Pro Motion NG from cosmigo.com through Wine (Ubuntu
repository). The crash
I updated the description to note that the text being searched for is
not found in the document (which is the case of course for an empty
document).
** Description changed:
https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b
gnome-shell crashes with this bug every
I just discovered that on my laptop this bug only applies to X11
sessions, not to Wayland sessions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
I have confirmed that it will not crash if I have a single monitor.
In duel monitor mode, i can also reconfirm that after updating
(strangely) Chrome browser that the window manager will crash, but will
restart -- prior to the update it would crash and not restart.
--
You received this bug
@jagosta: does it only crash if the dialogs are on different monitors?
That's what I find.
FWIW, I tried the live USB, but ootb Ubuntu 19.10 doesn't recognise the
HDMI monitor, so I can't do dual displays, and I also tried a VirtualBox
guest, but even after installing Ubuntu 19.10 and guest
Additional thought on my scenario ... I was also working in a duel
monitor mode when gnome crashed. In my case Thunderbird was on my
primary monitor, and the thunderbird dialog came up on my secondary
monitor. Interacting with this dialog is when gnome crashes.
--
You received this bug
Regarding comment #10 that this may be this user's specific issue. I
have opened bug #1850833 that is classified as a duplicate of this bug.
I have also provided in that bug a cleaner path to reproduce.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I also removed solaar, which had an indicator (but I think it's showing
through app-indicators), with no luck.
I also tried changing the screen configuration to laptop on the left,
monitor on the right, and the bug is still present.
--
You received this bug notification because you are a member
I removed all those extensions (and mate-optimus as well), so
~/.local/share/gnome-shell/extensions/ is completely empty, but the bug
is still there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Maybe the usual thing is indeed your workspace/monitor layout.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849249
Title:
gnome-shell crashed with SIGABRT:
I can't find any other reports of this crash other than the above link
for automatic crash reports. And even then we've only observed the crash
8 times globally, ever.
Sounds like there's something unusual about this machine so please start
by uninstalling (don't just disable) these extensions:
I can't find any other reports of this crash other than the above link
for automatic crash reports. And even then we've only observed the crash
11 times globally, ever. 8 times in eoan and 3 times in bionic.
Sounds like there's something unusual about this machine so please start
by uninstalling
Can I provide any other information to help speed this along? This is a
pretty severe problem - it's annoying because gnome-shell freezes for a
long time before restarting, and then it's extremely annoying because
you lose any data in applications that don't survive the restart.
** Description
Thanks for the bug report. Tracking in:
https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b
** Summary changed:
- gnome-shell crashed with SIGABRT
+ gnome-shell crashed with SIGABRT:
mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed:
(workspace
31 matches
Mail list logo
