On 03/30/17 14:24, Paolo Galtieri wrote: > Folks, > I have 2 F25 systems that have been updated today. These 2 systems > share a monitor. One system is attached via a kvm switch to the > monitor, the other system is attached via hdmi. This morning and > twice this evening a problem has started to manifest itself. This > configuration has been working fine for several years. I will call > the systems A and B, system A is attached to the monitor via hdmi, > system B via VGA. If I switch to system A for a while and then try to > switch back to system B the monitor instead of staying on VGA cycles > from VGA to DVI to HDMI and returns to system A. I can ssh into > system B and everything looks fine, i.e. things that were running > under my user id are still running, e.g. chrome and firefox. I looked > at /var/log/messages and I see this: > > Mar 29 23:00:02 jackstraw systemd: Stopping User Manager for UID 0... > Mar 29 23:00:02 jackstraw systemd: Stopped target Default. > Mar 29 23:00:02 jackstraw systemd: Stopped target Basic System. > Mar 29 23:00:02 jackstraw systemd: Stopped target Sockets. > Mar 29 23:00:02 jackstraw systemd: Closed D-Bus User Message Bus Socket. > Mar 29 23:00:02 jackstraw systemd: Stopped target Timers. > Mar 29 23:00:02 jackstraw systemd: Stopped target Paths. > Mar 29 23:00:02 jackstraw systemd: Reached target Shutdown. > Mar 29 23:00:02 jackstraw systemd: Starting Exit the Session... > Mar 29 23:00:02 jackstraw systemd: Received SIGRTMIN+24 from PID 17588 > (kill). > > This was at the time I switched from system A to system B. Each of > the other times I saw this problem I see the same set of messages in > the log file. Can someone explain what they mean and could they be > the cause of the problem? > > I see the same messages on the other system, but there they were part > of other messages related to rebooting the system. > > The only way I can recover is reboot the system. > > Here's my video card info: > > 01:00.0 VGA compatible controller: NVIDIA Corporation G86 [GeForce > 8500 GT] (rev a1) > > Any assistance is appreciated. Since everything is still running as it was it sounds similar to problems with monitors not coming back from sleep. Couple of questions. 1. Are you using the nouveau driver or the nVidia driver for your card? 2. Are you running GNOME under Wayland or X11? If you are using X11, and since you can ssh into the system, what is the output if you do... ssh systemB export DISPLAY=:0 xrandr Using my system as an example, does doing something like this bring the monitor back? [egreshko@meimei ~]$ acer Last login: Thu Mar 30 15:24:26 2017 from 192.168.1.18 [egreshko@acer ~]$ export DISPLAY=:0 [egreshko@acer ~]$ xrandr Screen 0: minimum 8 x 8, current 1280 x 800, maximum 8192 x 8192 VGA-0 disconnected (normal left inverted right x axis y axis) TV-0 disconnected (normal left inverted right x axis y axis) LVDS-0 connected primary 1280x800+0+0 (normal left inverted right x axis y axis) 331mm x 207mm 1280x800 59.91*+ HDMI-0 disconnected (normal left inverted right x axis y axis) [egreshko@acer ~]$ xrandr --output LVDS-0 --off [egreshko@acer ~]$ xrandr --output LVDS-0 --auto -- Fedora Users List - The place to go to get others to do the work for you _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
