Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Great!
By the way, one possible reason why you were unable to follow comment #2
is that gdm is designed to catch mutter/gnome-shell crashes in the
Wayland backend (which it tries first). If such a crash occurs then it
is meant to automatically fall back to Xorg.
Regardless of whether the automati
I didn't know how to log into "Ubuntu" instead of "Ubuntu on Wayland"
since I only got a blinking cursor and no logon prompt. I edited
/etc/gdm3/custom.conf and rebooted.
Successfully got a GUI logon prompt and was able to log in to the
desktop.
--
You received this bug notification because you
** Changed in: mutter
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surfac
Also, to avoid Wayland fully, please edit /etc/gdm3/custom.conf and
uncomment:
#WaylandEnable=false
then reboot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Titl
** No longer affects: linux (Ubuntu)
** Summary changed:
- gnome-shell trap int3 no desktop (Matrox MGA G200eW fails when calling
gbm_surface_lock_front_buffer)
+ gnome-shell trap int3 no desktop ("Impossible to lock surface front buffer:
Function not implemented" on Matrox graphics card)
** C
Tracking upstream (I think) in
https://gitlab.gnome.org/GNOME/mutter/issues/57
** Package changed: gdm3 (Ubuntu) => linux (Ubuntu)
** Summary changed:
- gnome-shell trap int3 no desktop (MGA G200eW fails when calling
gbm_surface_lock_front_buffer)
+ gnome-shell trap int3 no desktop (Matrox MGA
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bu
** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock
** Package changed: glib2.0 (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock su
It appears this message keeps happening with the gnome-shell crash:
"Impossible to lock surface front buffer: Function not implemented"
that's from mutter's "native" (Wayland) backend:
next_bo = gbm_surface_lock_front_buffer (gbm_surface);
if (!next_bo)
{
g_error ("Impossible to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bug
Uninstalled xorgxrdp, no change:
/var/log/apport.log:
ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: called for pid 2790, signal
5, core limit 0, dump mode 1
ERROR: apport (pid 3174) Tue Apr 30 16:47:43 2019: executable:
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: appor
apport is enabled.
>From /var/log/apport.log.1:
ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: called for pid 2699, signal
5, core limit 0, dump mode 1
ERROR: apport (pid 3078) Wed Apr 24 08:55:18 2019: executable:
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pi
Without having a backtrace it's a bit tricky to debug.
To figure out why apport isn't working, could you look at the content of
/var/log/apport.log to see if there is anything useful there? Maybe try
enabling apport by editing /etc/default/apport and restarting.
If apport doesn't work for some re
The log also has
'[ 601.234] (EE) mga: The PCI device 0x532 at 01@00:03:0 has a kernel module
claiming it.
[ 601.234] (EE) mga: This driver cannot operate until it has been unloaded.
[ 601.235] (EE) [drm] Failed to open DRM device for pci::02:00.0: -2'
Unsure that has to do with the iss
** Changed in: glib2.0 (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => High
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
** Also affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop
Status in gnome-shel
20 matches
Mail list logo
