Recent Apt Update package wayfire causes desktop to logout when HDMI input source is changed on my monitor #217
Comments
|
If you update to the latest version of wayfire now in apt, this should be fixed, but I do not understand why HDMI input changes should have caused the problem to occur - leaving this open until you can confirm that the patch fixes it. |
|
Yes the patch now fixes it when I switch HDMI inputs. |
|
Ok, thanks for confirming! |
"hotplug" 🙂 |
|
I know this issue is close, but I've noticed this happen to me as well even on the latest wayfire package ( Oh, one other thing that might be pertinent is that I use |
Hi! |
|
So I dont understand why the case is closed, if I face it today with newest upgrades |
Because the issue which was causing the problem as previously reported was found and fixed, and those who had originally reported it confirmed that the problem had gone away. So if you are still seeing a similar problem, either a) you do not actually have the fix, or b) what you are seeing is a different problem which happens to have the same symptoms, or c) it is specific to your hardware, such as your particular model of monitor. To eliminate a), please download the latest OS image (4 July 2024) from https://www.raspberrypi.com/software/operating-systems/, flash it to a new SD card, and see if the problem still occurs. |
|
Dear Simon,
Thank you for your answer!
Once again I did exactly all as you wrote: installed with Raspberry Pi
Installer the latest (recommended!) 64 bit OS of 4 July 2024 with all
upgrades.
So the OS completely is up to date.
Raspberry PI 400.
Monitor - Philips 278E9Q
Then I turned off my PC which connected to the second monitor port -
Display Port.
GUI Screen Blanking - OFF
Then I simply turned off the monitor's power and after a while (about 10 -
15 minutes) turned it on again.
And my session was LOG OUT, I only saw an invitation to log in!
The most unpleasant thing in this situation is that this does not always
happen, but sporadically.
It seems user "mgriego" already wrote about a similar situation!
I am forced to use an older version on another SD card, which does not have
this bug, which is unacceptable for Raspberry permanent online work.
I hope we will fix it!
Sincerely yours
Sasha
пт, 12 июл. 2024 г. в 11:13, Simon Long ***@***.***>:
… So I dont understand why the case is closed, if I face it today with
newest upgrades
Because the issue which was causing the problem as previously reported was
found and fixed, and those who had originally reported it confirmed that
the problem had gone away.
So if you are still seeing a similar problem, either a) you do not
actually have the fix, or b) what you are seeing is a different problem
which happens to have the same symptoms, or c) it is specific to your
hardware, such as your particular model of monitor.
To eliminate a), please download the latest OS image (4 July 2024) from
https://www.raspberrypi.com/software/operating-systems/, flash it to a
new SD card, and see if the problem still occurs.
—
Reply to this email directly, view it on GitHub
<#217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVF7AKFOCIZEEW3BLNJOZ5TZL6F3VAVCNFSM6AAAAABDX5OHYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRVGA2TSMJSGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
In that case, please try switching to the new labwc compositor to see if that fixes the problem. Open a terminal, run raspi-config, and under Advanced Settings -> Wayland, choose option 3, labwc, then reboot. |
|
With labws I haven't encountered our problem yet.
Maybe it's OK.
I tried with Screen Blanking OFF and with Screen Blanking ON.
And then I tried with
xset s 300 300
And I will continue testing for some time.
On the other hand, the monitor does not sleep neither after 300 seconds nor
after any other time.
Why can't OS just turn off the HDMI signal after a set period of
inactivity???
After all, this is exactly what people want and stumble upon problems like
ours in search of a solution.
вс, 14 июл. 2024 г. в 13:12, Simon Long ***@***.***>:
… In that case, please try switching to the new labwc compositor to see if
that fixes the problem.
Open a terminal, run raspi-config, and under Advanced Settings -> Wayland,
choose option 3, labwc, then reboot.
—
Reply to this email directly, view it on GitHub
<#217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVF7AKC6RBVIVXAHZJL47ILZMJFIVAVCNFSM6AAAAABDX5OHYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGI4TCMRWHE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
That's not going to work. xset, as the name suggests, is for X settings. It has no effect under Wayland. The only way to blank the screen under labwc is by calling wlopm to power down the monitor, and not all monitors respond correctly to this. |
|
I really appreciate your quick responses.
Generally there is no need to power down the monitor.
When the monitor is turned on but there is no signal source,
most monitors will automatically enter sleep mode.
It seems to me (I am not an expert of RPI) there are no simple ways on
Raspberry Pi 400 put a monitor into sleep mode by just putting hdmi signal
down.
So like OS Windows does.
Ok, we could use screensavers. But it is not a sleep mode.
пн, 15 июл. 2024 г. в 11:48, Simon Long ***@***.***>:
… And then I tried with xset s 300 300
That's not going to work. xset, as the name suggests, is for X settings.
It has no effect under Wayland.
The only way to blank the screen under labwc is by calling wlopm to power
down the monitor, and not all monitors respond correctly to this.
—
Reply to this email directly, view it on GitHub
<#217 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AVF7AKDWVAOAU7JEIOHLVOTZMOEHXAVCNFSM6AAAAABDX5OHYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXHE4TEMZRGE>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Dear Simon,
I am happy to inform you that my dream of putting the monitor to sleep mode
has come true on the version listed below
(by disabling xscreensaver and entering some xset commands),
and therefore I do not see any point in using later versions with their
bugs and difficulties.
Thank you for your cooperation!
***@***.***:~ $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
***@***.***:~ $ uname -a
Linux raspberrypi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023
aarch64 GNU/Linux
***@***.***:~ $ xset q
Screen Saver:
prefer blanking: yes allow exposures: yes
timeout: 300 cycle: 300
Colors:
default colormap: 0x20 BlackPixel: 0x0 WhitePixel: 0xffffff
Font Path:
/usr/share/fonts/X11/Type1,built-ins
DPMS (Energy Star):
Standby: 300 Suspend: 300 Off: 300
DPMS is Enabled
Monitor is On
пн, 15 июл. 2024 г. в 13:53, Тофик Шахуев ***@***.***>:
… I really appreciate your quick responses.
Generally there is no need to power down the monitor.
When the monitor is turned on but there is no signal source,
most monitors will automatically enter sleep mode.
It seems to me (I am not an expert of RPI) there are no simple ways on
Raspberry Pi 400 put a monitor into sleep mode by just putting hdmi signal
down.
So like OS Windows does.
Ok, we could use screensavers. But it is not a sleep mode.
пн, 15 июл. 2024 г. в 11:48, Simon Long ***@***.***>:
> And then I tried with xset s 300 300
>
> That's not going to work. xset, as the name suggests, is for X settings.
> It has no effect under Wayland.
>
> The only way to blank the screen under labwc is by calling wlopm to power
> down the monitor, and not all monitors respond correctly to this.
>
> —
> Reply to this email directly, view it on GitHub
> <#217 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AVF7AKDWVAOAU7JEIOHLVOTZMOEHXAVCNFSM6AAAAABDX5OHYWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXHE4TEMZRGE>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
On my RPi 5 running 64-bit bookworm desktop OS, there was a recent apt update that upgraded several packages.
After the upgrade, when I changed the input on my HDMI monitor from INP1 (RPi) to INP2 (PC) then back to INP1 (RPi) my desktop session ended and I was at the login screen. Everything running in my session was lost.
I traced the issue down to the update package wayfire.
If I revert to the previous apt release of wayfire, the problem does not occur. The problem re-occurs when I re-install the update wayfire package.
Recent changes to wayfire from the changelog in the update are:
wayfire (0.7.5-1
bpo11+1rpt32) bookworm; urgency=medium-- Simon Long [email protected] Tue, 20 Feb 2024 14:07:02 +0000
wayfire (0.7.5-1
bpo11+1rpt31) bookworm; urgency=medium-- Simon Long [email protected] Mon, 05 Feb 2024 08:35:12 +0000
I'm not sure what my HDMI monitor is doing when I change the input source, but I suspect it's probably something to do with power saving modes. But, what ever my HDMI display is "saying" to the RPi is causing the RPi to end my desktop session and log me out.
The text was updated successfully, but these errors were encountered: