Date: Sun, 13 Oct 2019 14:53:33 +0000 From: bugzilla-noreply@freebsd.org To: xfce@FreeBSD.org Subject: [Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots Message-ID: <bug-241219-28711-Jb9dACG0Hh@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-241219-28711@https.bugs.freebsd.org/bugzilla/> References: <bug-241219-28711@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D241219 --- Comment #5 from John <jlmales@gmail.com> --- (In reply to Guido Falsi from comment #3) I do not need to provide output from "ps -ax | grep -i saver". I know only= one screensaver was running at any given time. I have stated which screensaver= was initially running and just fine prior to this bug. I also stated only one screensaver was running at time of bug and there was no screensaver issue p= rior to the upgrade of 12 October 2019 14:58+000 UTC. I also stated how I tested both screensavers x11/xfce4-screensaver and x11/xscreensaver ensuring only = one screensaver was running at time and ensuring a clean slate by rebooting and= not just killing process and starting a new/different screensaver process that = may leave artifacts that could either cause the same bug to occur when otherwise would not or cause a different bug that would otherwise not occur when star= ing system with a clean slate. One has to test from known reference point. This is why the first thing I = did was reboot the system after the upgrade. There are key libraries that were upgraded which means all kinds of mismatched structures/offsets and similar that can result with such core system and/or DE libraries upgraded unless t= he system is rebooted after such key core libraries are upgraded. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-241219-28711-Jb9dACG0Hh>