User logged out when TV is turned off and on again
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
A computer running Ubuntu 17.10 and Gnome is connected to a single monitor (Sony Bravia TV) via HDMI. While logged in with applications open if the TV is turned off and back on again the user will be logged out. Once logged back in to the same account all applications are closed.
I can continue to run commands via SSH while the TV is off/user is logged out so the computer is still awake.
All power management settings are disabled in the Gnome settings manager. If the TV is left on the computer will stay logged in indefinitely.
I have also tried disabling all related TV settings including "Power off HDMI devices with the TV".
Below are the logs from journalctl
. When the TV is powered off nothing changes, the below are from immediately after the TV is powered back on. It appears that gnome-shell
is crashing but how do I work out what is causing the issue?
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] connect method
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] disconnect method
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] emit method
Feb 5 19:04:48 mini kernel: [ 2081.251322] gnome-shell[3355]: segfault at d0000021b ip 00007fc4e88cb233 sp 00007fff175dc828 error 4 in libgbm.so.1.0.0[7fc4e88c8000+d000]
Feb 5 19:04:48 mini update-notifier[3643]: Error reading events from display: Broken pipe
Feb 5 19:04:48 mini qbittorrent[3597]: Error reading events from display: Broken pipe
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE)
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: Fatal server error:
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE) failed to read Wayland events: Connection reset by peer
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE)
Feb 5 19:04:48 mini gnome-session-binary[3324]: Unrecoverable failure in required component org.gnome.Shell.desktop
Feb 5 19:04:48 mini gnome-session-binary[3324]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Feb 5 19:04:48 mini gnome-session[3324]: gnome-session-binary[3324]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
gnome hdmi tv
add a comment |Â
up vote
0
down vote
favorite
A computer running Ubuntu 17.10 and Gnome is connected to a single monitor (Sony Bravia TV) via HDMI. While logged in with applications open if the TV is turned off and back on again the user will be logged out. Once logged back in to the same account all applications are closed.
I can continue to run commands via SSH while the TV is off/user is logged out so the computer is still awake.
All power management settings are disabled in the Gnome settings manager. If the TV is left on the computer will stay logged in indefinitely.
I have also tried disabling all related TV settings including "Power off HDMI devices with the TV".
Below are the logs from journalctl
. When the TV is powered off nothing changes, the below are from immediately after the TV is powered back on. It appears that gnome-shell
is crashing but how do I work out what is causing the issue?
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] connect method
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] disconnect method
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] emit method
Feb 5 19:04:48 mini kernel: [ 2081.251322] gnome-shell[3355]: segfault at d0000021b ip 00007fc4e88cb233 sp 00007fff175dc828 error 4 in libgbm.so.1.0.0[7fc4e88c8000+d000]
Feb 5 19:04:48 mini update-notifier[3643]: Error reading events from display: Broken pipe
Feb 5 19:04:48 mini qbittorrent[3597]: Error reading events from display: Broken pipe
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE)
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: Fatal server error:
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE) failed to read Wayland events: Connection reset by peer
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE)
Feb 5 19:04:48 mini gnome-session-binary[3324]: Unrecoverable failure in required component org.gnome.Shell.desktop
Feb 5 19:04:48 mini gnome-session-binary[3324]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Feb 5 19:04:48 mini gnome-session[3324]: gnome-session-binary[3324]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
gnome hdmi tv
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
A computer running Ubuntu 17.10 and Gnome is connected to a single monitor (Sony Bravia TV) via HDMI. While logged in with applications open if the TV is turned off and back on again the user will be logged out. Once logged back in to the same account all applications are closed.
I can continue to run commands via SSH while the TV is off/user is logged out so the computer is still awake.
All power management settings are disabled in the Gnome settings manager. If the TV is left on the computer will stay logged in indefinitely.
I have also tried disabling all related TV settings including "Power off HDMI devices with the TV".
Below are the logs from journalctl
. When the TV is powered off nothing changes, the below are from immediately after the TV is powered back on. It appears that gnome-shell
is crashing but how do I work out what is causing the issue?
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] connect method
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] disconnect method
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] emit method
Feb 5 19:04:48 mini kernel: [ 2081.251322] gnome-shell[3355]: segfault at d0000021b ip 00007fc4e88cb233 sp 00007fff175dc828 error 4 in libgbm.so.1.0.0[7fc4e88c8000+d000]
Feb 5 19:04:48 mini update-notifier[3643]: Error reading events from display: Broken pipe
Feb 5 19:04:48 mini qbittorrent[3597]: Error reading events from display: Broken pipe
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE)
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: Fatal server error:
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE) failed to read Wayland events: Connection reset by peer
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE)
Feb 5 19:04:48 mini gnome-session-binary[3324]: Unrecoverable failure in required component org.gnome.Shell.desktop
Feb 5 19:04:48 mini gnome-session-binary[3324]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Feb 5 19:04:48 mini gnome-session[3324]: gnome-session-binary[3324]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
gnome hdmi tv
A computer running Ubuntu 17.10 and Gnome is connected to a single monitor (Sony Bravia TV) via HDMI. While logged in with applications open if the TV is turned off and back on again the user will be logged out. Once logged back in to the same account all applications are closed.
I can continue to run commands via SSH while the TV is off/user is logged out so the computer is still awake.
All power management settings are disabled in the Gnome settings manager. If the TV is left on the computer will stay logged in indefinitely.
I have also tried disabling all related TV settings including "Power off HDMI devices with the TV".
Below are the logs from journalctl
. When the TV is powered off nothing changes, the below are from immediately after the TV is powered back on. It appears that gnome-shell
is crashing but how do I work out what is causing the issue?
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] connect method
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] disconnect method
Feb 5 19:04:48 mini gnome-shell[3355]: WARNING: addSignalMethods is replacing existing [0x557d6a2b4db0 Gjs_ShowAppsIcon.dash-item-container] emit method
Feb 5 19:04:48 mini kernel: [ 2081.251322] gnome-shell[3355]: segfault at d0000021b ip 00007fc4e88cb233 sp 00007fff175dc828 error 4 in libgbm.so.1.0.0[7fc4e88c8000+d000]
Feb 5 19:04:48 mini update-notifier[3643]: Error reading events from display: Broken pipe
Feb 5 19:04:48 mini qbittorrent[3597]: Error reading events from display: Broken pipe
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE)
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: Fatal server error:
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE) failed to read Wayland events: Connection reset by peer
Feb 5 19:04:48 mini org.gnome.Shell.desktop[3355]: (EE)
Feb 5 19:04:48 mini gnome-session-binary[3324]: Unrecoverable failure in required component org.gnome.Shell.desktop
Feb 5 19:04:48 mini gnome-session-binary[3324]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
Feb 5 19:04:48 mini gnome-session[3324]: gnome-session-binary[3324]: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11
gnome hdmi tv
gnome hdmi tv
edited Feb 5 at 22:14
asked Feb 5 at 22:08
0x6C77
1115
1115
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Issue traced to gdm
. Installing lightdm
seems to fix.
sudo apt-get install lightdm
Suggestion found in this bug report[1]
[1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
Issue traced to gdm
. Installing lightdm
seems to fix.
sudo apt-get install lightdm
Suggestion found in this bug report[1]
[1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908
add a comment |Â
up vote
1
down vote
accepted
Issue traced to gdm
. Installing lightdm
seems to fix.
sudo apt-get install lightdm
Suggestion found in this bug report[1]
[1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908
add a comment |Â
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Issue traced to gdm
. Installing lightdm
seems to fix.
sudo apt-get install lightdm
Suggestion found in this bug report[1]
[1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908
Issue traced to gdm
. Installing lightdm
seems to fix.
sudo apt-get install lightdm
Suggestion found in this bug report[1]
[1] https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1714908
answered Feb 5 at 22:30
0x6C77
1115
1115
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1003376%2fuser-logged-out-when-tv-is-turned-off-and-on-again%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password