[Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219 --- Comment #6 from Guido Falsi --- (In reply to John from comment #4) > This bug is not the same as bug #240804. I did not say it is the same, only that it looks very similar. There is clearly some language barrier between me and you. I'm not a native English speaker, so sometimes I could misunderstand you or not express myself clearly in English. Please try to give me some leeway. I'm trying to help you, but we need to cooperate, I'm not saying the bug does not exist and never thought it, so no need to be defensive about this. > 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. I agree there is something broken after the upgrade. But I don't know what and the information you provided is not shedding light for me. I use the term "issue" and "something broken" to generally describe unexpected ot unwanted behaviour. The word bug, to me, means a programming error in some software, in the source code. For reasons I will explain shortly while we are evidently seeing an unwanted behaviour I cannot be sure such a behaviour is caused by a software bug. I need you to perform some tests to try to understand the cause of this unwanted behaviour. I have tried to reproduce the issue on my system but I could not. This reply of yours gave me new information I could not gather from your previous message, that the issue appears with any of the two screensavers in isolation, this makes it even more improbable that the problem is caused by a single bug. it's quite improbable for the same programming error causing the same broken behaviour to be present in two separate projects developed by different people. Now, about the tests, I asked you to reinstall a bunch of software because my previous experience with FreeBSD ports (and also with software on other OSes) has shown that in the life of a system with the periodic updating of software, which causes updating of libraries without updating the software depending on them sometime misalignments happen. In some cases new library versions have slight incompatibilities or internal structures change that software inappropriately access directly or other such things. When this happens strange problems show up which are difficult to diagnose and are not really bugs but problems which show up on specific PCs and nowhere else and can only be solved by reinstalling the right piece of software, but that's not easy to guess. You issue looks to me like a possible case of misalignment brought by incremental updates with time, so I'm kindly asking you, as a test, to try reinstalling the libraries on which xscreensaver an xfce4-screensaver depend on and see if the problem just goes away. (In reply to John from comment #5) While the specific output from ps I asked for may not be needed, it was a very fast thing to do, as I said I have no idea what is causing your issue, I've not been able to reproduce it, I'm trying to gather information, and since I'm not infallible I also can make mistakes in the process. Anyway, while I generally agree that testing should start from known reference point unluckily debugging issues on a live system is not pure science, and it's quite difficult to get a known reference point. That's also why I'm asking you to try reinstalling some packages, to be sure we are using a coherent set of libraries and binaries, because that could not be the case on a system which has been getting incremental updates over time. -- 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"
[Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219 --- Comment #5 from John --- (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 prior 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 staring 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 the system is rebooted after such key core libraries are upgraded. -- 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"
[Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219 --- Comment #4 from John --- (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"
[Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219 Guido Falsi changed: What|Removed |Added Flags|maintainer-feedback?(xfce@F |maintainer-feedback+ |reeBSD.org) | --- Comment #3 from Guido Falsi --- In detail what could be useful is simply the output of: ps -ax | grep -i saver thanks. -- 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"
[Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219 Guido Falsi changed: What|Removed |Added Status|New |Open CC||madpi...@freebsd.org --- Comment #2 from Guido Falsi --- Hi, I'm not sure I understand your description of the issue. It looks very similar to bug #240804. You say "(current configurations for both)" what does this mean? That both are enabled at the same time in XFCE? this cannot work, you need to enable only one. Also 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, but later you state also xorg-libraries-7.7_4 was upgraded. So what really happened? Also, while I know this is no solution, rebooting looks overkill, I think killing the screensaver process as root should unlock your session (although I have not tested it so I could be wrong), you can do this by going to a virtual terminal with ctrl-alt-1 or also connecting via ssh . 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. Finally you have provided a wealth of information in your console output, but I could not find a list pf running processes (output of ps(1)) in there, created while the bug is happening, that is, while the screen is locked and you're unable to unlock it. That could at least make it clear if one or both screensavers are running. -- 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"
[Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219 John changed: What|Removed |Added CC||jlma...@gmail.com --- Comment #1 from John --- 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) -- 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"
maintainer-feedback requested: [Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots
Bugzilla Automation has asked freebsd-xfce mailing list for maintainer-feedback: Bug 241219: x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219 --- Description --- 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. If this is an incorrect guess for ports package as cause then for certain the bug "Summary" will need to be changed to reflect the ports package causing the issue once confirmed as the source of the bug. Since doing a FreeBSD "pkg upgrade" 12 October 2019 14:58+000 UTC both x11/xfce4-screensaver and x11/xscreensaver fail in exact same manner resulting in user having to force a system reboot or power cycle the system. The last 'pkg upgrade" done was 02 October 2019 0326+000 UTC where both x11/xfce4-screensaver and x11/xscreensaver behaved as expected. The bug is identical for both x11/xfce4-screensaver and x11/xscreensaver. The bug is when either screensaver activates to black screen (current configurations for both) neither mouse nor keyboard activity results in the dialog box appearing asking for user password to unlock the screen. Both have been extensively tested and always fail exactly as described. ___ 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"
[Bug 241219] x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241219 Bug ID: 241219 Summary: x11-wm/xfce4-wm: FreeBSD Update Causes XFCE Screensavers Causes User Forced Reboots Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: x...@freebsd.org Reporter: jlma...@gmail.com Assignee: x...@freebsd.org Flags: maintainer-feedback?(x...@freebsd.org) Created attachment 208272 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=208272=edit Console when system was booted days prior to 12 October 2019 14:45+000 FreeBSD Upgrade and the Upgrade Leading to Bug 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. If this is an incorrect guess for ports package as cause then for certain the bug "Summary" will need to be changed to reflect the ports package causing the issue once confirmed as the source of the bug. Since doing a FreeBSD "pkg upgrade" 12 October 2019 14:58+000 UTC both x11/xfce4-screensaver and x11/xscreensaver fail in exact same manner resulting in user having to force a system reboot or power cycle the system. The last 'pkg upgrade" done was 02 October 2019 0326+000 UTC where both x11/xfce4-screensaver and x11/xscreensaver behaved as expected. The bug is identical for both x11/xfce4-screensaver and x11/xscreensaver. The bug is when either screensaver activates to black screen (current configurations for both) neither mouse nor keyboard activity results in the dialog box appearing asking for user password to unlock the screen. Both have been extensively tested and always fail exactly as described. -- 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"
