- Xscreensaver disable check for update install#
- Xscreensaver disable check for update update#
- Xscreensaver disable check for update password#
The tests are time consuming as there are reboots and waiting time for the screensaver to activate. desktop files for autostart as per bug #240810 and but #240810. I was so tired I really made a mess of what was to be two simple updates to bug #240810.īefore I was to bed I made the changes to the XFCE. I was not up again until late today and have a number of eMail I needed to do and updates related bug #240801 and bug # 240811. I still have few to open unrelated to this issue. It was a very unexpected long day as result of multiple FreeBSD bugs. (In reply to Guido Falsi from comment #8) Were you using xcreensaver before you installed xfce4-screensaver for testing? Is it possible this may have some root cause for who and when gets the screensaver keyboard? Perhaps this means either one of the startup screensaver entries is for each or only one for both entries? It appears both screensavers are running. I have looked in the various directories of /home/keypunch/.config/xfce4 and cannot find any autostart relate files, let alone if text based.Īs to the issue with the xfce4-screensaver not taking control of keyboard I assume you have not had that challenge in your testing. Is there a file, obviously text file, that keeps this XFCE autostart configuration in it? If so maybe best to find that file and attach its contents before making any XFCE4 startup configuration changes. (In reply to Guido Falsi from comment #4)Īgree having two identical "Screensaver (Launch screensaver and locker program)."Įntries is likely not good. Sadly LXDE does not work in FreeBSD even though LXDE works just fine in OpenBSD. I have not used XFCE for some years, but used it for some years before I discovered LXDE about 7 years ago. If I need to add screensaver back in will I need to add any options or such. Please advise if both "Screensaver (Launch screensaver and locker program)." entries should be disabled and/or deleted and/or if I will need to add xscreensaver back in.
Xscreensaver disable check for update install#
This means I do not recall if xscreensaver was in the XFCE autostart then or prior to the pkg upgrade install that included a new install xfce4-screensaver: 0.1.8. I have not looked at this autostart since the first week after I installed FreeBSD 11.3 mid July 2019 when I added gkrellm, and disabled Notes and Clipman. There are two entries, both ticked, listed as "Screensaver (Launch screensaver and locker program)." There is no xscreensaver entry in the XFCE autostart. (In reply to Guido Falsi from comment #1)
Xscreensaver disable check for update password#
I do not have a working phone SD card that would have allowed taking a video of the issue with the xfce4-screensaver not accepting any keyboard input for password in the widget for password (as xscreensaver also has).
Xscreensaver disable check for update update#
This XFCE4 related update makes the use of the system completely useless and makes using FreeBSD DE useless. Unable to find any settings for xfce4-screensaver-0.1.8 via settings menu that would make sense of xfce4-screensaver-0.1.8 and xscreensaver-5.43_1 co-existing. Was forced to reboot FreeBSD system with data loss of data not able to access and not saved as not expecting a completely different and likely conflicting with xscreensaver-5.43_1 situation. xfce4-screensaver-0.1.8 would not accept any keyboard input and therefore unable to unlock the XFCE4 session. I was away from the machine for a bit and opon return instead of the xscreensaver-5.43_1 screen that was always displayed when the XFCE4 needed to be unlocked with xfce-4.12_1 a lockscreen clearly fome XFCE (xfce4-screensaver-0.1.8) displayed. The reboot and CLI startx (to start xfce4 by default) proceeded just fine, and clearly a new look an feel for XFCE4. The pkg upgrade proceed with no issues and the FreeBSD 11.3 based system was immediately rebooted by me not only due to the extent of the many upgraded XFCE4 packages, but there was an update for xorg-server: 1.18.4_11,1 -> 1.18.4_12,1. Console from boot time with pkg list and pkg upgrade leading to bugĪfter doing a pkg update 20190925 02:19+0000 UTC that performed many XFCE updates that seemed related to "Installed packages to be UPGRADED:" xfce: 4.12_1 -> 4.14 based set of updates there was "New packages to be INSTALLED:" xfce4-screensaver: 0.1.8.
0 kommentar(er)
