[Bug 240887] x11-wm/xfce4: blank or black window decorations, without rounded borders

2019-09-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240887 Olivier Duchateau changed: What|Removed |Added CC||duchateau.oliv...@gmail.com --

[Bug 240804] x11/xfce4-screensaver: Newly Installed via pkg upgrade Does Not Allow Password Input and xscreensaver No Longer Function Forcing User to Reboot Frequently and/or Data Loss

2019-09-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240804 --- Comment #15 from John --- (In reply to Guido Falsi from comment #12) Re "Somewhere in your messages you ask me not to disable xscreensaver by default...why? Having BOTH enab

[Bug 240811] x11/xfce4-screensaver: Has same names as other screensaver applications in XFCE Settings Autostart GUI

2019-09-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240811 John changed: What|Removed |Added Resolution|FIXED |--- Status|Closed

[Bug 240811] x11/xfce4-screensaver: Has same names as other screensaver applications in XFCE Settings Autostart GUI

2019-09-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240811 --- Comment #17 from John --- In bug #240804 re: "Please don't rush things. "Please let's keep the conversation in one place only. This is one bug. with two strictly related pr

[Bug 240811] x11/xfce4-screensaver: Has same names as other screensaver applications in XFCE Settings Autostart GUI

2019-09-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240811 --- Comment #18 from John --- This bug should remain open until the upstream project has created an acceptable fix to this bug. Sadly the way this FreeBSD bugzilla is configured thereis only an Open or Closed status for the bug. There is

[Bug 240811] x11/xfce4-screensaver: Has same names as other screensaver applications in XFCE Settings Autostart GUI

2019-09-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240811 --- Comment #19 from John --- I had crossed referenced this bug to bug #240810 and bug #240804 on purpose to indicate there is some relationships between this and the other bugs. This was done on purpose to show the relationship of these d