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
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-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
buffer:
I can't see any problem in the files attached so far. We need a log file
covering the period of time when the problem actually happened. To get
that please:
1. Reproduce the problem.
2. Reboot and then immediately run:
journalctl -b-1 > prevboot.txt
and then attach the file
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-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell
** 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)
**
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
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.
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
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop
** Package changed: gnome-shell (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
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-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
** Package changed: glib2.0 (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
gnome-shell trap int3 no desktop ("Impossible to lock surface front
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-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
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-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1826025
Title:
You have been subscribed to a public bug:
After upgrade to 19.04, gnome-shell crashes on boot, leaving blinking
cursor.
[ 498.989821] traps: gnome-shell[4066] trap int3 ip:7f7b604e6955
sp:7fff92106950 error:0 in libglib-2.0.so.0.6000.0[7f7b604ad000+8]
Restarting gdm3 service results in the
The file 'journal.txt' is created in the current directory when you run:
journalctl -b0 > journal.txt
But if you have successfully removed 'xserver-xorg-video-intel' then you
may not need to do anything more. Did that fix it?
--
You received this bug notification because you are a member of
@EDEMPCO I haven't had the issue since I updated to Ubuntu 18.04 (or
stopped using the 4.13.x series on 16.04). Are you using the kernel
provided by the distribution? Can you try running one of the 4.10.x
kernels to see if that fixes it? Also are you sure you have this
specific bug, and not any of
Since 18.04 is the latest LTS, how does this change get distributed to
those of us who rely on the LTS to be upgraded and effective until the
next LTS? In other words, how and when does it get integrated into
18.04LTS?
--
You received this bug notification because you are a member of Ubuntu-X,
Public bug reported:
At several times boot stops and each time no boot menu (Grub)
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Thank you for your bug report. Could you add your journalctl log to the
bug after hitting the issue?
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of
--- Comment From heinz-werner_se...@de.ibm.com 2019-04-30 09:21 EDT---
Due to the fact that LLVM 8 is already available with 19.04. I will change the
target to 19.04
** Tags removed: targetmilestone-inin1910
** Tags added: targetmilestone-inin1904
--
You received this bug notification
In a side conversation I was told that LLVM 8.0.0 is sufficient for now.
Hence the headline was changed to 19.04 and I'm going to close it as Fix
Released.
** Changed in: llvm-toolchain-8 (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: ubuntu-z-systems
Status:
Hey, could you tell me how to get the journal.txt file.
after I run journalctl -b0 > journal.txt nothing happens. i removed the
i915 driver and reset it.
On Wed, Apr 24, 2019 at 7:00 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> This looks like a low level problem. So either in
** Changed in: mutter
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1826316
Title:
[amdgpu] Wayland sessions detect 4K screens (3840x2160) as
Public bug reported:
Desktop wallpaper and lock screen wallpaper corrupted after waking up
the system
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules:
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
** Changed in: mutter (Ubuntu)
Status: New => Triaged
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: New => Triaged
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Importance: Undecided => Low
--
You
Also affecting me. Dell Inspiron 5379
Linux danny-Inspiron-5379 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.04
DISTRIB_CODENAME=disco
DISTRIB_DESCRIPTION="Ubuntu 19.04"
--
You received this bug notification
27 matches
Mail list logo
