https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219

--- Comment #4 from John <jlma...@gmail.com> ---
(In reply to Guido Falsi from comment #2)

This bug is not the same as bug #240804.

This bug is not when both screensavers x11/xfce4-screensaver and
x11/xscreensaver are active.  I did state "The bug is identical for both
x11/xfce4-screensaver and x11/xscreensaver.  I needed to determine if the issue
was  x11/xfce4-screensaver or x11/xscreensaver, therefore I had to test both 
x11/xfce4-screensaver and x11/xscreensaver to determine if (I was not
expecting) both to fail, let alone fail exactly the same way.

I did state "both x11/xfce4-screensaver and x11/xscreensaver fail in exact same
manner".  That means they failed in exact same manner and does not mean both
screensavers were running at same time.

The bug is when either screensaver ..." I should know both screensavers cannot
be active as I was the one that reported bug #240804.

At time of this bug and for few weeks I had only the x11/xfce4-screensaver
configured to run at XFCE startup.  I checked a few times via a forced reboot
that the bug would still occur with x11/xfce4-screensaver still enabled.  Once
that was confirmed, I would disable x11/xfce4-screensaver and then enable
x11/xscreensaver.  To my surprise the exact same bug occurred.  This likely
meant the bug was not x11/xfce4-screensaver or x11/xscreensaver.  I have been
running the system since with both x11/xfce4-screensaver and x11/xscreensaver
disabled and as expected no issue as no screensaver is enabled.

I did not state "you say that you performed pkg upgrade on 12 October 2019
14:58+000 UTC and x11-wm/xfce4-wm was the only package updated".  I did state:

"I have logged this issue against x11-wm/xfce4-wm as it is the only package
that was in the 'pkg upgrade' 12 October 2019 14:58+000 UTC that I can guess as
the package causing the bug."

The key point here I am stating I do not know the package that may be the cause
of this bug and why I chose the ports package I did to report the bug.

You state "later you state also xorg-libraries-7.7_4 was upgraded. So what
really happened?"  What I stated was:

"One possible consideration for cause of this bug is via the 12 October 2019
14:58+000 UTC "pkg upgrade" is:

xorg-libraries-7.7_4 (direct dependency changed: libXScrnSaver)"

I was trying to suggest a port as possible cause to the bug instead of my guess
that x11-wm/xfce4-wm is the source of the bug.  

You will note I have referred to the same "pkg upgrade" in all of the
references to the update that caused this bug.  That being the 12 October 2019
14:45+000 FreeBSD Upgrade.  The attached file for the bug shows the packages
and versions installed prior to the 12 October 2019 14:45+000 FreeBSD Upgrade,
The details of the 12 October 2019 14:45+000 FreeBSD Upgrade that occurred, and
other information I cause my system to generate automatically when starting
terminal session.

I should not have to:

"Just to be on the safe side, since you keep experiencing this issue, have you
tested forcing reinstallation of all the affected packages with fresh ones?

For all I mean at least all of XFCE, Xorg libraries, xscreensaver."

Clearly there is a bug.  Clearly something is wrong.  The bug of what is wrong
and why bug occurred after the packages updated, installed and reinstalled from
the 12 October 2019 14:45+000 FreeBSD Upgrade is the bug at hand.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-xfce@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xfce
To unsubscribe, send any mail to "freebsd-xfce-unsubscr...@freebsd.org"

Reply via email to