[Bug 1734044] Re: gnome-shell crashes when monitor turned off or switch kvm [meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_mo
This bug was reported for Ubuntu Desktop 17.10. I would like to add that the problem when disconnecting the only monitor also occurs when using Ubuntu Desktop 18.04 LTS (latest updates Jul19,2018). gnome-shell will not always crash but the desktop becomes unusable when using x11vnc. The new report#1782573 is already marked as a duplicate. https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1782573 https://www.dropbox.com/s/a8jjnw14uhtibzk/ubuntu1804-x11vnc- disconnected-monitor-fatal.mp4?dl=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734044 Title: gnome-shell crashes when monitor turned off or switch kvm [meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1734044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782573] [NEW] Remote X11vnc session unusable due to crash in gnome-shell when disconnecting HDMI monitor under Ubuntu Desktop 18.04 LTS
Public bug reported:
Expect to happen: I can use X11VNC when the monitor is disconnected.
What happens instead: remote X11vnc session unusable due to crash in
gnome-shell when disconnecting HDMI monitor under Ubuntu Desktop 18.04
LTS
I'm using a stable system that works fine when the monitor is connected;
also X11VNC works fine.
But I want to access the GUI remotely via X11VNC when the HDMI monitor
is disconnected then the system is not usable (lots of gnome-shell
errors in syslog) and sometimes the gnome-shell will also segfault (the
segfault is not in this bugreport). The X11 remote viewer is full of
clutter (see screencast).
Please see below for the syslog entries when disconnecting the monitor
with no X11VNC active, and the syslog entries when the monitor is
disconnected and starting X11VNC.
Gist: https://gist.github.com/pantaluna/c4f69f367611c596d10919f3c80e1a0d
X. VIDEO: X11VNC monitor disconnected.
https://www.dropbox.com/s/a8jjnw14uhtibzk/ubuntu1804-x11vnc-disconnected-monitor-fatal.mp4?dl=0
X. System
https://gist.github.com/pantaluna/c4f69f367611c596d10919f3c80e1a0d
- Ubuntu Desktop 18.04 LTS (latest updates until Jul19,2018 14:00h).
- Intel HD Graphics 530
$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$ root@s3black:~# apt-cache policy gnome-shell
gnome-shell:
Installed: 3.28.2-0ubuntu0.18.04.1
Candidate: 3.28.2-0ubuntu0.18.04.1
Version table:
*** 3.28.2-0ubuntu0.18.04.1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
3.28.1-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
$ lspci -nnk | grep -i -A3 "vga" | grep 'in use'
Kernel driver in use: i915
$ lshw -C video
*-display
description: VGA compatible controller
product: HD Graphics 530
vendor: Intel Corporation
physical id: 2
bus info: pci@:00:02.0
version: 06
width: 64 bits
clock: 33MHz
capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0
resources: irq:127 memory:de00-deff memory:c000-cfff
ioport:f000(size=64) memory:c-d
X. GIST: Syslog entries when disconnecting the HDMI cable.
egrep --ignore-case "gnome|hdmi" /var/log/syslog
Jul 19 14:37:53 s3black kernel: [ 943.153341] i915 :00:02.0: HDMI-A-1:
EDID is invalid:
Jul 19 14:37:53 s3black kernel: [ 943.153347] [00] BAD 00 ff ff ff ff ff
ff 00 ff ff ff ff ff ff ff ff
Jul 19 14:37:53 s3black kernel: [ 943.153349] [00] BAD ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff
Jul 19 14:37:53 s3black kernel: [ 943.153351] [00] BAD ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff
Jul 19 14:37:53 s3black kernel: [ 943.153353] [00] BAD ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff
Jul 19 14:37:53 s3black kernel: [ 943.153354] [00] BAD ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff
Jul 19 14:37:53 s3black kernel: [ 943.153356] [00] BAD ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff
Jul 19 14:37:53 s3black kernel: [ 943.153358] [00] BAD ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff
Jul 19 14:37:53 s3black kernel: [ 943.153360] [00] BAD ff ff ff ff ff ff
ff ff ff ff ff ff ff ff ff ff
Jul 19 14:37:55 s3black gnome-shell[2017]: JS WARNING:
[resource:///org/gnome/shell/ui/workspaceThumbnail.js 903]: reference to
undefined property "_switchWorkspaceNotifyId"
Jul 19 14:37:56 s3black gnome-shell[2017]:
meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int)
number < g_list_length (manager->logical_monitors)' failed
Jul 19 14:37:56 s3black gnome-shell[2017]:
meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL'
failed
Jul 19 14:37:56 s3black gnome-shell[2017]: JS ERROR: TypeError:
this._monitor is
undefined#012DockedDash<._resetPosition@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1089:17#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012DockedDash<._init@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:416:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012_Base.prototype._construct@resource:///org/gnome/gjs/modules/_legacy.js:18:5#012Class.prototype._construct/newClass@resource:///org/gnome/gjs/modules/_legacy.js:114:32#012DockManager<._createDocks@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1717:20#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22#012DockManager<._toggle@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1663:9#012wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
Jul 19 14:37:56 s3black gnome-shell[2017]: st_widget_get_theme_node called
on the widget [0x5650fe2d6c30 StButton.app-well-app ("33")] which is not in the
stage.
Jul 19 14:37:56 s3black gnome-shell[2017]:
[Bug 1519331] Re: Postfix cannot resolve DNS if network was unavailable when it was started, such as on a laptop
>@Marius Gedminas (mgedmin)
>Curiously, I never saw this problem on my laptop in Ubuntu versions
>up to and including 16.04 LTS.
>I'm seeing a lot of this problem ever since I upgraded to 16.10 LTS.
I experienced the same issues when deploying Ubuntu 16.10 to a new
MiniPC (opposed to Ubuntu 14.x that worked fine).
I have finally found an automated solution for this: enable the
NetworkManager-wait-online.service and deploy a custom script that
restarts the postfix service +-5 minutes after the machine has booted
(assuming that the wireless connection is active by then).
A. Enable this.
It is a generic approach that might be beneficial for other service than
Postfix as well so I keep it in the script.
systemctl enable NetworkManager-wait-online.service; systemctl status
NetworkManager-wait-online.service;
B. Add a customer Systemd timer + service
@info The timer will start ONCE, {x} minutes after the machine was booted.
nano /etc/systemd/system/mjd-restart-postfix-after-wlan-connected.timer
[Unit]
Description=(timer)mjd-restart-postfix-after-wlan-connected
[Timer]
OnBootSec=5min
[Install]
WantedBy=timers.target
nano /etc/systemd/system/mjd-restart-postfix-after-wlan-connected.service
[Unit]
Description=mjd-restart-postfix-after-wlan-connected
[Service]
Type=oneshot
ExecStart=/bin/sh -ec "systemctl restart postfix; systemctl status postfix;
uname -a | /usr/bin/mailx -s \"Server (`hostname`): postfix was restarted.\"
yourem...@gmail.com"
MYUNIT=mjd-restart-postfix-after-wlan-connected
MYTIMER=${MYUNIT}.timer
systemctl enable ${MYTIMER}; systemctl status ${MYTIMER};
systemctl list-units --all | grep "${MYUNIT}"
systemctl status ${MYUNIT}
C. Restart
reboot
# wait 5 minutes
D. Check
MYUNIT=mjd-restart-postfix-after-wlan-connected
MYTIMER=${MYUNIT}.timer
systemctl status ${MYTIMER}
If the contents of these 2 config files (one of Resolve and one of Postfix) are
not the same then the issue is PROBLEMATIC (Postfix started before LAN/WLAN
gets connected).
cat /etc/resolv.conf
cat /var/spool/postfix/etc/resolv.conf
E. Info
@doc https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331
@doc https://wiki.archlinux.org/index.php/Systemd/Timers
@doc qshape deferred
@doc cat /var/log/syslog | egrep "NetworkManager|postfix"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519331
Title:
Postfix cannot resolve DNS if network was unavailable when it was
started, such as on a laptop
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1519331/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1424013] Re: Compiz high CPU and UI freeze on NVIDIA after fix for #269904 in trusty-updates
RE: Testing request. Hi, I have installed on top of Ubuntu 14.0.4.02 LTS the update of compiz which is in the repo trusty-proposed and it works fine. Thanks! Procedure: # 1. Added repo trusty-proposed. # 2. Package upgrade. # compiz:all/trusty-updates 1:0.9.11.2+14.04.20140714-0ubuntu1 upgradeable to 1:0.9.11.3+14.04.20150122-0ubuntu1 $ apt-get install --only-upgrade compiz FYI: -$ glxinfo | grep OpenGL renderer string OpenGL renderer string: GeForce 7050 PV / nForce 630a/integrated/SSE2 - GPU Hardware: nVidia GeForce 7050 PV / nForce 630a (rev a2). - nVidia Driver http://www.nvidia.com/Download/driverResults.aspx/77034/en-us Linux x64 (AMD64/EM64T) Display Driver Version: 304.1230 Release Date: 2014.7.10 Operating System: Linux 64-bit Language: English (US) File Size: 68.00 MB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1424013 Title: Compiz high CPU and UI freeze on NVIDIA after fix for #269904 in trusty-updates To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1424013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
