James,
I think this bug is fixed, and we just have too many spurious bug links
pointing here due to similar stack traces. If you can share a link to
one of your recent crash reports it would be most helpful.
--
You received this bug notification because you are a member of Desktop
Packages,
Not sure if you will find this useful, but for me this bug occurs
regularly with a very common pattern.
I use a VPN to access my companies network when working remotely. I also
regularly use Nautilus to sftp mount remote servers in my companies data
centers. I use vscode as an IDE to edit C++
It appears that in the recent past this crash became so prolific that it
might have been confused for other similar crashes in day to day bug
maintenance. For example, the link
https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
is actually a different crash with a
Benjamin, out of interest: Do you see the crash with both sessions? X
and waylan?
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP
Wayland of course. Just suggesting that switching to Wayland might fix
your problem.
--
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/1748450
Title:
gnome-shell crashed with
@vanvugt Seeing this VERY regularly in cosmic, too. Just came back here
to re-check the status of this long-term annoying issue.
The fact is, that gnome shell provides me a VERY poor UX experience:
Logged out for the session more than 10mins? Type your password and go
get take a coffee, because
What?! Two reports from cosmic
https://errors.ubuntu.com/problem/8ef857b2fe07d60742cd02d7d8f988f78ecd0f95
Or three, if you count bug 1773308.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Tags added: cosmic
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler() from
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: mutter (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: gnome-shell (Ubuntu Bionic)
Status: Fix Released =>
mutter (3.28.1-1ubuntu1) bionic; urgency=medium
* Add xwayland-use-g_autoptr-for-GError-in-xserver_died.patch,
xwayland-Don-t-abort-if-Xwayland-crashes.patch:
- Cherry picked from upstream, to reduce noise of mutter on crashes
which are actually caused by XWayland (LP: #1748450)
** Changed in: gnome-shell (Ubuntu Bionic)
Assignee: Jean-Baptiste Lallement (jibel) => (unassigned)
--
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/1748450
Title:
** Description changed:
[Impact]
* Xwayland is failing frequently (not crashing), which triggers a crash
- in gnome-shell because gnome-shell doesn't know how to survive without
- Xwayland.
+ in gnome-shell because gnome-shell doesn't know how to survive after
+ Xwayland has reset itself.
** Description changed:
+ [Impact]
+
+ * Xwayland is failing frequently (not crashing), which triggers a crash
+ in gnome-shell because gnome-shell doesn't know how to survive without
+ Xwayland.
+
+ * The frequent gnome-shell crashes create frequent problem reports and
+ annoying dialogs for
I have a similar problem
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1765461
with Ubuntu 18.04 and Gnome 3.28.1
corrado@corrado-bb-0418:~$ inxi -Fx
System:Host: corrado-bb-0418 Kernel: 4.15.0-15-generic x86_64 bits: 64 gcc:
7.3.0
Desktop: Gnome 3.28.1 (Gtk
*** This is a duplicate of bug 1505409, but is being kept separate so as
to automatically collect duplicate reports since the stack trace
signature has changed recently. Any resolution and discussion should
occur in bug 1505409. ***
--
You received this bug notification because you are a member
This report:
https://errors.ubuntu.com/problem/7576bbf83cb88a0b3a870e1371dd86416b23c4b3
suggests the wave of unreadable stack traces this week was perhaps due
to an update to glib2.0, because:
/lib/x86_64-linux-gnu/libglib-2.0.so.0.5600.0 (deleted)
So they are almost certainly all duplicates
I always get this bug when I start with an Xorg session. I started with
a Wayland session and didn't get the bug.
--
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/1748450
Title:
I had the same issue with Ubuntu 18.40 (final Beta) and HP EliteBook 850
G5 and reported the bug 1762814 and the solution (or rather workaround)
for me was to blacklist amdgpu and this gnome shell crash, all the boot
errors and suspend issues were gone.
How to blacklist amdgpu is described here:
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: High
Status: Triaged
** Changed in: gnome-shell (Ubuntu Bionic)
Assignee: (unassigned) => Jean-Baptiste Lallement (jibel)
** Tags removed: rls-bb-incoming
--
You received this bug notification because you are a member of
Nobody needs to provide more information here, thanks.
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort() from
** Tags removed: rls-bb-notfixing
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler()
Actually the login screen is using eglnative, which has Xwayland running
in the background. Same as a Wayland session.
--
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/1748450
Title:
No, the login screen is using Wayland. You don't get a choice. You only
choose what gets used after the login screen.
--
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/1748450
Title:
No, yours crashed in Wayland (the login screen) too:
"CurrentDesktop: GNOME-Greeter:GNOME"
--
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/1748450
Title:
gnome-shell crashed with
Yeah and that's actually good news.
I had feared the switch to Xorg by default would mean this bug wouldn't
happen often enough for us to collect good data in 18.04 (since the
related apport bug fix last week). But it turns out this will happen
plenty often enough still.
--
You received this
I checked tens of duplicates and all the crashes happen from the login
screen (XDG_CURRENT_DESKTOP=GNOME-Greeter:GNOME)
--
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/1748450
Bug 1760448 is from the login screen:
"CurrentDesktop: GNOME-Greeter:GNOME"
So it is Wayland, not Xorg.
--
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/1748450
Title:
gnome-shell
Yes, at least the bug I reported was from Ubuntu 18.04 which doesn't use
Wayland by default.
--
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/1748450
Title:
gnome-shell crashed
This bug is indeed meant to be wayland only. Which duplicates are from
Xorg?
Note that the login screen (gdm3) is using wayland by default. So your
system may report this crash even if you only use Xorg sessions.
--
You received this bug notification because you are a member of Desktop
There is a mix of duplicates with and without Wayland. Mine was without
Wayland.
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP in
I'm readding rls-bb-incoming. Something looks wrong here, 1. due to the
comment of Amr Ibrahim saying he was not using wayland 2. Wayland is not
the default on 18.04 3. Several reports are not tagged with wayland-
session, so these users were unliky running wayland.
** Tags added: rls-bb-incoming
My bug is a duplicate, but I don't use Wayland.
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort() from
Thanks Seb. I was about to remove that tag for the same reason.
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort()
Changing to rls-bb-notfixing, that's wayland specific which is not our
default session and lacks info, we can target the xwayland issue if we
get proper reports that tell us more about the bug
** Tags removed: rls-bb-incoming
** Tags added: rls-bb-notfixing
--
You received this bug notification
We hope the fix for bug 1746874 (released last night) will help to
figure this out.
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP
** Tags added: rls-bb-incoming
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler()
Knarf, that sounds possibly unrelated to this bug. Please log a new bug
for that.
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP
gdm3 no mouse function but move.
gnome Displaysystems not boot and then boot no mouse function but move.
lightdm goes into Automatic login. why? Have changed this manually.
gdm3 is Ubuntu adjusted, why. But no mouse function to change this, no
click possible.
--
You received this bug
** Tags added: artful
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler() from
** Tags added: bugpattern-needed
--
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/1748450
Title:
gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler()
40 matches
Mail list logo