Hi all!
I've recently installed 15.0-RELEASE on an Intel NUC and then ran the beta script to install KDE/Wayland as depicted in this FreeBSD YouTube video.
All the packages installed fine, and KDE 6.4.5 works great.
However, I notice that after KDE puts the display to sleep, after a sufficient period of time, it no longer wakes with keyboard or mouse input.
The situation is always the same. The system shares a multi-input monitor with another computer, which gets used throughout most of the day. In the later hours, I'll switch display input to the nucbsd system. However, I can confirm that the system will wake and allow me to unlock the desktop earlier in the morning before I switch over to the other computer. However, some time after 2:00-3:00p, the display no longer wakes.
Caps Lock and Num Lock still toggle as expected. And I can Ctrl-Alt F1-F8 and get a tty login prompt. So, the system hasn't crashed or hard-locked. When I then try to Ctrl-Alt F9 back to the Wayland display, I see the SDDM login screen, and the Xorg X-shaped cursor/pointer is active allowing me to move it around the screen, but I can't click on anything nor get any normal keyboard reaction (beyond tty switching). Also I notice that the time on the SDDM screen is about the time I last successfully logged on the day before. So, it's like there's some residual frame or image stuck in the buffer but doesn't actually render a functional screen.
To clear the issue, I flip back to tty F1, log in, and then issue a safe reboot. When the system reboots, I see the now working SDDM login, and I can successfully login, as expected. When I'm done later in the evening, I'll walk away letting KDE put the display back a sleep. And as I mention earlier, the next morning first thing, I'll be able to login to the KDE lock screen before switching to the other display input. So, something happens after that.
Looking in /var/log/messages, I see only a few DBUS errors:
I'm not really familiar enough with other log files to know what's significant. So, I'm hoping someone can suggest further steps to continue troubleshooting.
Thanks!
I've recently installed 15.0-RELEASE on an Intel NUC and then ran the beta script to install KDE/Wayland as depicted in this FreeBSD YouTube video.
All the packages installed fine, and KDE 6.4.5 works great.
However, I notice that after KDE puts the display to sleep, after a sufficient period of time, it no longer wakes with keyboard or mouse input.
The situation is always the same. The system shares a multi-input monitor with another computer, which gets used throughout most of the day. In the later hours, I'll switch display input to the nucbsd system. However, I can confirm that the system will wake and allow me to unlock the desktop earlier in the morning before I switch over to the other computer. However, some time after 2:00-3:00p, the display no longer wakes.
Caps Lock and Num Lock still toggle as expected. And I can Ctrl-Alt F1-F8 and get a tty login prompt. So, the system hasn't crashed or hard-locked. When I then try to Ctrl-Alt F9 back to the Wayland display, I see the SDDM login screen, and the Xorg X-shaped cursor/pointer is active allowing me to move it around the screen, but I can't click on anything nor get any normal keyboard reaction (beyond tty switching). Also I notice that the time on the SDDM screen is about the time I last successfully logged on the day before. So, it's like there's some residual frame or image stuck in the buffer but doesn't actually render a functional screen.
To clear the issue, I flip back to tty F1, log in, and then issue a safe reboot. When the system reboots, I see the now working SDDM login, and I can successfully login, as expected. When I'm done later in the evening, I'll walk away letting KDE put the display back a sleep. And as I mention earlier, the next morning first thing, I'll be able to login to the KDE lock screen before switching to the other display input. So, something happens after that.
Looking in /var/log/messages, I see only a few DBUS errors:
Dec 16 10:02:46 nucbsd dbus-daemon[2648]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.6" (ui
d=1000 pid=2815 comm="") interface="org.freedesktop.ConsoleKit.Seat" member="Inhibit" error name="(unset)" requested_reply="0" d
estination="org.freedesktop.ConsoleKit" (uid=0 pid=2786 comm="")
Dec 16 14:41:39 nucbsd console-kit-daemon[2786]: WARNING: failed to revoke access. Error: Bad address
Dec 16 14:41:39 nucbsd syslogd: last message repeated 5 times
Dec 16 14:42:51 nucbsd reboot[1566]: rebooted by zachw
I'm not really familiar enough with other log files to know what's significant. So, I'm hoping someone can suggest further steps to continue troubleshooting.
Thanks!
