The driver involved should be also be fixed including this:
https://cgit.freedesktop.org/drm/drm-
tip/commit/?id=4751cf733a1170876dd5ac46f225f5a25f59a67f
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => In Progress
** Also affects: linux (Ubuntu)
Importance: Undecided
St
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1754949
Title:
gnome-shell crashed wi
** Tags added: cosmic
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1754949
Title:
gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
from meta_renderer_nati
Bump. This is the 3rd most common gnome-shell crash right now.
** Changed in: gnome-shell (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/17
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Won't Fix
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => In Progress
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
** Changed in
** Description changed:
https://gitlab.gnome.org/GNOME/mutter/issues/70
https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665
+
+ https://salsa.debian.org/gnome-team/mutter/merge_requests/6
---
The crash was reported after booting and logging in to an X.Org sess
Temporarily reopening the gnome-shell task, just so people can find the
bug. And are less likely to create more duplicates.
** Changed in: gnome-shell (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is su
I haven't seen this crash, since I disabled Wayland in
/etc/gdm3/custom.conf:
[daemon]
# Uncoment the line below to force the login screen to use Xorg
WaylandEnable=false
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubunt
That's correct. Because the "meta_renderer_native" part is Wayland-only
:)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1754949
Title:
gnome-shell crashed with SIGSEGV in meta_gpu
And so is "meta_gpu_kms".
So this is a Wayland-only crash.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1754949
Title:
gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc
Fix is in salsa now, will be in ubuntu at next sync.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/17549
This bug was fixed in the package mutter - 3.28.3-2
---
mutter (3.28.3-2) unstable; urgency=medium
* Team upload
[ Iain Lane ]
* debian/gbp.conf: Set the upstream branch to upstream/3.28.x, since we've
branched for experimental now.
[ Marco Trevisan (Treviño) ]
* d/p/n
** Description changed:
+ [ Description ]
+
+ GNome shell crashes after Xorg loggin
+
+ [ Test case ]
+
+ From GDM login in a GNOME Ubuntu session (so Xorg).
+ It should start with no issues
+
+ [ Regression potential ]
+
+ We were deferencing a NULL pointer while outputting an error.
+ This
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification b
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Fix Released
** No longer affects: gnome-shell (Ubuntu Bionic)
** Changed in: mutter (Ubuntu Bionic)
Status: New => In Progress
** Changed in: mutter (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: mutter
The drm_mode_get_hv_timing() function (used in the required kernel
commit) depends on a non trivial amount of other changes, and I don't
think a backport would be easy, or safe. That commit will be available
in Linux 4.17, though, so we are going to get the fix in Ubuntu 18.10.
** Changed in: linu
Hello Ferdinand, or anyone else affected,
Accepted mutter into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1
---
mutter (3.28.3-2~ubuntu18.04.1) bionic; urgency=medium
* No-change backport from unstable to bionic
mutter (3.28.3-2) unstable; urgency=medium
* Team upload
[ Iain Lane ]
* debian/gbp.conf: Set the upstre
** Summary changed:
- gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
+ gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from
meta_renderer_native_finish_frame()
** Information type changed from Private to Public
--
You received this bug notification becaus
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.ne
Upstream bug report:
https://gitlab.gnome.org/GNOME/mutter/issues/70
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1754949
Title:
gnome-shell crashed with SIGSEGV in meta_gpu_
The crash occurs on this line of code:
g_warning ("Failed to set CRTC mode %s: %m",
crtc->current_mode->name);
As crtc is not NULL it must be current_mode or name that has an invalid
value.
** Tags added: wayland wayland-session
** Description changed:
+ https://gitlab.gnome.org/GNOME/mu
Also tracking in
https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665
** Description changed:
https://gitlab.gnome.org/GNOME/mutter/issues/70
+ https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665
---
The crash was reported after booting and
Looks similar to:
https://errors.ubuntu.com/problem/b0adc3c02c0ba6f5e7fafd72721ff0050a8a88f4
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1754949
Title:
gnome-shell crashed w
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1754949
Title:
gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode()
from meta_renderer_native
26 matches
Mail list logo