[Bug 1889090] Re: GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion in meta_monitor_manager_xrandr_update_screen_size

2020-08-11 Thread zasran
Yes, https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.2
fixed the issue for me, thanks!

-- 
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/1889090

Title:
  GNOME Shell doesn't start Ubuntu session with 3.36.4 as per assertion
  in meta_monitor_manager_xrandr_update_screen_size

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1889090/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1887998] Re: Update to 3.36.4 and SRU it

2020-07-27 Thread zasran
I have the same problem,
https://launchpad.net/ubuntu/+source/mutter/3.36.4-0ubuntu0.20.04.1 does
not fix it. Unfortunately I cannot switch to Wayland because it doesn't
start on my system (video card: 00:02.0 VGA compatible controller: Intel
Corporation Iris Plus Graphics 655 (rev 01)).

Symptom is that after waking up from sleep I get white screen of death
that says what the bug description says ("Oh no! Something has gone
wrong. A problem has occurred and the system can't recover. Please log
out and try again.") and I have to click the Log out button at which
points it lets me log in again. Sometime it does the same thing again
right after logging in.

Syslog message are also pretty much the same as from other comments,
here you can see it failing twice, first up while running then right
after re-login.

Jul 27 00:30:31 jojda gnome-shell[4633]: gvc_mixer_card_get_index: assertion 
'GVC_IS_MIXER_CARD (card)' failed
Jul 27 00:30:32 jojda gnome-shell[4633]: **
Jul 27 00:30:32 jojda gnome-shell[4633]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:32 jojda gnome-shell[4633]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:32 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled restart 
job, restart counter is at 1.
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session (session: 
ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session (session: 
ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Stopped target GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Stopping GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Starting GNOME Shell on X11...
Jul 27 00:30:33 jojda gnome-shell[15068]: Enabling experimental feature 
'x11-randr-fractional-scaling'
Jul 27 00:30:33 jojda gnome-shell[15068]: **
Jul 27 00:30:33 jojda gnome-shell[15068]: 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda gnome-shell[15068]: Bail out! 
mutter:ERROR:../src/backends/x11/meta-monitor-manager-xrandr.c:211:meta_monitor_manager_xrandr_update_screen_size:
 assertion failed: (width > 0 && height > 0 && scale > 0)
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Main process 
exited, code=dumped, status=6/ABRT
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Failed with 
result 'core-dump'.
Jul 27 00:30:33 jojda systemd[4297]: Failed to start GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME Shell on X11.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME X11 Session.
Jul 27 00:30:33 jojda systemd[4297]: Dependency failed for GNOME X11 Session 
(session: ubuntu).
Jul 27 00:30:33 jojda systemd[4297]: gnome-session-x11@ubuntu.target: Job 
gnome-session-x11@ubuntu.target/start failed with result 'dependency'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-session-x11.target: Job 
gnome-session-x11.target/start failed with result 'dependency'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.target: Job 
gnome-shell-x11.target/start failed with result 'dependency'.
Jul 27 00:30:33 jojda systemd[4297]: gnome-shell-x11.service: Scheduled restart 
job, restart counter is at 2.
Jul 27 00:30:33 jojda systemd[4297]: Stopped GNOME Shell on X11.

-- 
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/1887998

Title:
  Update to 3.36.4 and SRU it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887998/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 777452] Re: Huge number of 'Disk Utility' notification windows

2011-07-26 Thread zasran
No fix planned?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/777452

Title:
  Huge number of 'Disk Utility' notification windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/777452/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 777452] Re: Huge number of 'Disk Utility' notification windows

2011-05-26 Thread zasran
Turning off the notifications - is that supposed to be a solution or
workaround? Cause I want the notification, just not infinite number of
alert boxes.

The alert boxes are the notifications, they belong to /usr/lib/notify-
osd/notify-osd. So how is this not a notify-isd bug? I mean even if not
used correctly the notifications (in the form of alert boxes) should not
kill X server (which is what happens if it runs unattended for few
days). A service that is so central to the usage of system (lot of
programs use notifications) should be rock solid. Not kill X server at
slightest misuse (more DOS attack than literally kill).

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/777452

Title:
  Huge number of 'Disk Utility' notification windows

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs