Mario, ideally please open a new bug by running 'ubuntu-bug mutter'. Or if that
doesn't work then go here:
https://bugs.launchpad.net/ubuntu/+source/mutter/+filebug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I have the same crash as Rachel whenever I unplug the DVI from my NVidia
graphics card or switch the KVM to another monitor. I use Ubuntu 17.10
latest, with mutter 3.26.2-0ubuntu0.1 installed. This does not fix the
crash.
I also get the assertion:
meta_monitor_manager_get_logical_monitor_from_numb
This bug is closed, rightly or wrongly. It would help us if all further
discussion was in different bugs that are open. Even if it feels like
the same issue as was discussed here...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Now when I switch my display back on again, I see my desktop and open
windows for a short while, and then am immediately kicked out of the
session. Before the entire desktop would die, now I'm just back at user
select screen.
On two separate systems.
--
You received this bug notification because
I was just retested the crash and it goes worse, now it is complete GUI
crash not a "just session kick-out". I have created new bug report
1724557 due the fact that this bug 1717170 has fix released status and
also because the behaviour and logs changed.
--
You received this bug notification beca
Well, only what I have is again part of syslog (attached). If you can
advice me how to provide better logs, it would be appreciated. However,
it seems that the crash now is not caused by monitor switch off but by
switching it on again, according to syslog. Nothing is logged between
switch off and s
Ryzko,
Do you have a stacktrace for the crash you're getting now?
The one related to this title is definitely fixed, and errors.ubuntu.com
confirms it.
What you're getting might be more related to https://pad.lv/1723048 ?
--
You received this bug notification because you are a member of Ubuntu
What I was originally reported is not fixed. It means, gnome-shell session
crash when the monitor is disconnected/switch off or its input is changed.
Mutter and Gnome-Shell updated to:
mutter: 3.26.1-2ubuntu1
gnome-shell: 3.26.1-0ubuntu3
--
You received this bug notification because you are a me
Adding this to *this* bug, despite the "Fix Released", because it
exactly matches the original post for this bug, whereas the others I've
encountered and reported on are different:
Oct 14 20:02:45 fleetfoot gnome-shell[12750]:
meta_monitor_manager_get_logical_monitor_from_number: assertion '(uns
bug #1723615 came up with this fix in place. Whack-a-mole! :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
ma
I had one crash after applying this yesterday (and rebooting): it
crashed right out to the console, not even to the login screen, and when
I tried logging in again the session failed to start. But since a second
reboot it's apparently been fine. This bug went away, and so too has my
bug #1720149 (s
** Changed in: gnome-shell
Status: Unknown => Fix Released
** Changed in: mutter
Status: Unknown => Fix Released
** Changed in: gnome-shell
Importance: Unknown => Medium
** Changed in: mutter
Importance: Unknown => Medium
--
You received this bug notification because you ar
This bug was fixed in the package gnome-shell - 3.26.1-0ubuntu3
---
gnome-shell (3.26.1-0ubuntu3) artful; urgency=medium
* Cherry-pick git_layout-unset-when-headless.patch from gnome-3-26
branch to fix crash bug (LP: #1717170)
-- Jeremy Bicha Fri, 13 Oct 2017 16:10:59 -0400
** Branch linked: lp:~ubuntu-desktop/gnome-shell/ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
manager.c
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell crashes with SIGABRT: mutter:ERROR:backends/m
** Changed in: mutter (Ubuntu)
Status: In Progress => 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/1717170
Title:
gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-mo
I confirm that this crash is fixed by https://github.com/GNOME/gnome-
shell/commit/db43c45b12fbae462857e59dce6849c6aa965091
** Changed in: mutter
Importance: Critical => Unknown
** Changed in: mutter
Status: Confirmed => Unknown
** Changed in: mutter
Remote watch: GNOME Bug Tracker #7
The crash itself is fixed by
https://github.com/GNOME/mutter/commit/f044511037a51ae9c438addf3a8374f559916aae
(part of fixing bug #1722811), so probably we can join the two bugs
together for the ubuntu side.
The root cause of this is probably in a different spot though.
Maybe related to https://bug
It did.Thank you Daniel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
manager.c:2274:meta_monitor_manager_get_
** Changed in: mutter
Status: Unknown => Confirmed
** Changed in: mutter
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell crashes w
We can't change upstream bug link statuses explicitly but removing the
upstream task and recreating it will hopefully do the trick.
** No longer affects: mutter
** Also affects: mutter via
https://bugzilla.gnome.org/show_bug.cgi?id=787637
Importance: Unknown
Status: Unknown
--
You
may be the status of the bag should be changed from "Fix Released" to
"Confirmed". Related GNOME bug #787637 is reopened.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell cra
Also tracking in:
https://errors.ubuntu.com/problem/a9ace2e3301009e3a5344f8dac4e56fc4c23b1b8
** Description changed:
+ https://errors.ubuntu.com/problem/a9ace2e3301009e3a5344f8dac4e56fc4c23b1b8
+
+ ---
+
I'm testing Ubuntu 17.10 installed on Lenovo PC (with Intel Core i5-6500
CPU and Intel
Today the update of mutter to version 3.26.1-1 was installed on my PC by
"apt upgrade" and the issue still persist. Please see attached syslog,
cut from the time of crash (caused by monitor switch off).
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1717170
** Changed in: mutter
Status: Confirmed => 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/1717170
Title:
gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
ma
** Changed in: mutter
Status: Unknown => Confirmed
** Changed in: mutter
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell crashes w
Thank you, yes It seems that the bug report you found on Gnome Bugzilla
is reporting the same type of crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell crashes with SIG
Found it. Gnome Developers are already aware of the crash:
https://bugzilla.gnome.org/show_bug.cgi?id=787637
If you would like to contribute to a speedy resolution then please
comment on that page.
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
--
You received this bug notifica
I mean "~" is your home directory, ".config" is a directory and
"monitors.xml" is the file. :)
Regardless, your original description suggests the invalid config occurs
dynamically. Not necessarily on disk.
** Bug watch added: GNOME Bug Tracker #787637
https://bugzilla.gnome.org/show_bug.cgi?id
hmm, no such file ~/.config/monitors.xml in my home directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1717170
Title:
gnome-shell crashes with SIGABRT: mutter:ERROR:backends/meta-monitor-
man
30 matches
Mail list logo