Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

! Important: loginscreen after ~30min -> piSignage not usable anymore! #252

Open
Quietscher opened this issue Mar 15, 2024 · 118 comments
Open

Comments

@Quietscher
Copy link

autologout
Morning!
After about 30 min, the greeter appears and is overlaid on top of piSignage.
Therefore, the Signage is not usable anymore.

System:

  • Raspberry Pi 5
  • Player Version 5.1.1
  • Already did: sudo apt update; sudo apt -y full-upgrade

More information:
It seems to be the same problem as in ISSUE, but the issue's naming is misleading.
We tried to solve the issue by ourselves but couldn't fix it.
We found out:

  • It is the greeter that is shown
  • It may be a problem of the switch to Wayland / Wayfire
    -> On the internet there are dozens of solutions for X11 but barely for Wayland
    -> the configs (LightDm, freedesktop, wayfire.ini ...) seemed to be already set correctly, but still the greeter appears
  • It may be that the greeter is shown because of inactivity

Resources we found, but that couldn't solve the problem:



- Further to this topic [https://forums.raspberrypi.com/viewtopic.php?p=2175546#p2175546](https://forums.raspberrypi.com/viewtopic.php?p=2175546#p2175546)

Please let me know if other information is required or if you found a fix.

@Quietscher
Copy link
Author

These are the processes that run when the login screen appears

root     21804  0.0  0.1  29532  6272 ?        Sl   16:08   0:00 lightdm --session-child 18 21
lightdm  21891  0.0  0.2  16184  8704 ?        Ss   16:08   0:00 /lib/systemd/systemd --user
lightdm  21892  0.0  0.0  36304  3896 ?        S    16:08   0:00 (sd-pam)
lightdm  21911  0.0  0.1  48276  6144 ?        Ssl  16:08   0:00 /usr/bin/pipewire
lightdm  21912  0.0  0.3 106032 14392 ?        S<sl 16:08   0:00 /usr/bin/pulseaudio --daemonize=no --log-target=journal
lightdm  21913  0.1  4.0 384564 164864 ?       Ssl  16:08   0:00 /usr/bin/wayfire -c /usr/share/greeter.ini
lightdm  21918  0.0  0.0   7392  3712 ?        Ss   16:08   0:00 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
lightdm  21973  0.0  0.0   2140  1152 ?        S    16:08   0:00 /bin/sh -c /usr/sbin/pi-greeter
lightdm  21974  0.2  3.9 268988 162700 ?       Sl   16:08   0:00 /usr/sbin/pi-greeter
lightdm  21982  0.0  0.1  44004  6272 ?        Ssl  16:08   0:00 /usr/libexec/gvfsd
lightdm  21987  0.0  0.1  56472  5632 ?        Sl   16:08   0:00 /usr/libexec/gvfsd-fuse /run/user/106/gvfs -f
root     22005  0.0  0.1  11040  4736 ?        S    16:08   0:00 lightdm --session-child 11 15

@Quietscher
Copy link
Author

Is there any new information on this issue yet?

@mano1979
Copy link

Is there any new information on this issue yet?

Have you burned the image to the sd card with pi imager? If so, did you use the extra settings to add wifi and ssh credentials while burning the image?

I did that too and had to log in each time the pi booted. But after doing a fresh install, (download the image again because the already present image is now corrupted), the pi logs in automatically.

@Quietscher
Copy link
Author

Hey @mano1979 👋
No we used Balena Etcher, but I don't think that's the problem. We don't have any issues with ssh, wifi or login, but rather the raspberry / piSignage decides to logout after about 30min.

@Quietscher
Copy link
Author

I even wrote a script that simulates user input via pressing keys and moving the mouse. The tool is called ydotool.
But it does not work either

@Quietscher
Copy link
Author

@mano1979 do you have the newest piSignage version running? And do you get the logout screen after a certain time?

@Quietscher
Copy link
Author

Okay new Info:
It does not seem to be a issue of inactivity:

  • a local script to simulate activity was running without effect
  • real input over a connected mouse also had no effect

in both cases the login screen appears after 30 min.

@colloqi
Copy link
Owner

colloqi commented Mar 25, 2024

Hi

We have observed when weblinks are used session getting closed and hence it goes back to login screen as bookworm has 2 users account (pi & root). We are actively monitoring the issue and working. Sometime the issue appears when you aplly the following commands (first one is to bring the OS up to date abd second one is to indicate HDMI is always connected)

Can you try if these help you?

sudo apt update && sudo apt -y full-upgrade &
sudo sed -i 's/$/ vc4.force_hotplug=1/' /boot/firmware/cmdline.txt

@Quietscher
Copy link
Author

Quietscher commented Mar 25, 2024

I already tried > sudo apt update && sudo apt -y full-upgrade &
I will try the 2cnd command now

@Quietscher
Copy link
Author

Bildschirmfoto 2024-03-25 um 11 13 12

When using

sudo apt update && sudo apt -y full-upgrade & sudo sed -i 's/$/ vc4.force_hotplug=1/' /boot/firmware/cmdline.txt

The content is displayed outside of the monitor and the monitor only shows "piSignage"

@Quietscher
Copy link
Author

Quietscher commented Mar 25, 2024

And when i do sudo sed -i 's/$/ vc4.force_hotplug=0/' /boot/firmware/cmdline.txt
the login screen still appears after 30min, but it displays my pages correctly

@colloqi
Copy link
Owner

colloqi commented Mar 25, 2024

It needs reboot after the command, if it still persists, till we solve, can you use 5.1.0-legacy if it is Pi 4?

@Quietscher
Copy link
Author

Yes i did reboot it in between.
I have a pi 5 with v5.1.1

@Quietscher
Copy link
Author

Bildschirmfoto 2024-03-25 um 11 13 12 When using

sudo apt update && sudo apt -y full-upgrade & sudo sed -i 's/$/ vc4.force_hotplug=1/' /boot/firmware/cmdline.txt

The content is displayed outside of the monitor and the monitor only shows "piSignage"

Is there a fix for this?
This seems to work against the login screen, but as i wrote, the display does not display my content but piSignage

@Quietscher
Copy link
Author

Ah nope my bad, id did not work either

@Quietscher
Copy link
Author

Okay new Info: It does not seem to be a issue of inactivity:

  • a local script to simulate activity was running without effect
  • real input over a connected mouse also had no effect

in both cases the login screen appears after 30 min.

I wonder why and where this comes from...

@Mkragholm
Copy link

This is very similar to the issue I had where it needed a password on every reboot.
That issue is solved in Issue #246 - give that a shot.

@Quietscher
Copy link
Author

Thanks for the info, but that did not help. I tried it already

@Quietscher
Copy link
Author

I don't get the sign in screen on reboot, but after 30min

@stormvansoldt
Copy link

These are the processes that run when the login screen appears

root     21804  0.0  0.1  29532  6272 ?        Sl   16:08   0:00 lightdm --session-child 18 21

I'm really curious where this process is being generated from. Maybe check the crontab?

Does lightdm have any useful messages in /var/log?

@Quietscher
Copy link
Author

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=863
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/01_debian.conf
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.00s] DEBUG: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ‘gio-vfs’
[+0.01s] DEBUG: Monitoring logind for seats
[+0.01s] DEBUG: New seat added from logind: seat0
[+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.01s] DEBUG: Seat seat0 has property CanMultiSession=no
[+0.01s] DEBUG: Seat seat0: Starting
[+0.01s] DEBUG: Seat seat0: Creating user session
[+0.01s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+0.32s] DEBUG: Seat seat0: Creating display server of type wayland
[+0.32s] DEBUG: Seat seat0: Plymouth is running on VT 1, but this is less than the configured minimum of 7 so not replacing it
[+0.32s] DEBUG: Quitting Plymouth
[+0.38s] DEBUG: Using VT 7
[+0.38s] DEBUG: Launching process 997: /usr/share/dispsetup.sh
[+0.39s] DEBUG: Process 997 exited with return value 0
[+0.39s] DEBUG: Seat seat0: Exit status of /usr/share/dispsetup.sh: 0
[+0.39s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.39s] DEBUG: Session pid=1000: Started with service 'lightdm-autologin', username 'pi'
[+0.39s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.39s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.42s] DEBUG: Session pid=1000: Authentication complete with return value 0: Success
[+0.42s] DEBUG: Seat seat0: Session authenticated, running command
[+0.42s] DEBUG: Registering session with bus path /org/freedesktop/DisplayManager/Session0
[+0.42s] DEBUG: Session pid=1000: Running command /etc/X11/Xsession /usr/bin/wayfire-pi
[+0.42s] DEBUG: Creating shared data directory /var/lib/lightdm/data/pi
[+0.42s] DEBUG: Session pid=1000: Logging to .xsession-errors
[+0.78s] DEBUG: Activating VT 7
[+0.80s] DEBUG: Activating login1 session 1
[+0.80s] DEBUG: Seat seat0 changes active session to 1
[+0.80s] DEBUG: Session 1 is already active
[+2191.81s] DEBUG: Session pid=1000: Exited with return value 255
[+2191.82s] DEBUG: Seat seat0: Session stopped
[+2191.82s] DEBUG: Seat seat0: Stopping display server, no sessions require it
[+2191.82s] DEBUG: Seat seat0: Display server stopped
[+2191.82s] DEBUG: Seat seat0: Active display server stopped, starting greeter
[+2191.82s] DEBUG: Seat seat0: Creating greeter session
[+2192.13s] DEBUG: Seat seat0: Creating display server of type wayland
[+2192.13s] DEBUG: Using VT 8
[+2192.13s] DEBUG: Launching process 22405: /usr/share/dispsetup.sh
[+2192.14s] DEBUG: Process 22405 exited with return value 0
[+2192.14s] DEBUG: Seat seat0: Exit status of /usr/share/dispsetup.sh: 0
[+2192.14s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+2192.14s] DEBUG: Session pid=22408: Started with service 'lightdm-greeter', username 'lightdm'
[+2192.14s] DEBUG: Releasing VT 7
[+2192.24s] DEBUG: Session pid=22408: Authentication complete with return value 0: Success
[+2192.24s] DEBUG: Seat seat0: Session authenticated, running command
[+2192.24s] DEBUG: Session pid=22408: Running command /usr/bin/wayfire-pi -c /usr/share/greeter.ini
[+2192.24s] DEBUG: Creating shared data directory /var/lib/lightdm/data/lightdm
[+2192.24s] DEBUG: Session pid=22408: Logging to /var/log/lightdm/seat0-greeter.log
[+2192.50s] DEBUG: Activating VT 8
[+2192.51s] DEBUG: Activating login1 session c1
[+2192.55s] DEBUG: Seat seat0 changes active session to c1
[+2192.55s] DEBUG: Session c1 is already active
[+2193.65s] DEBUG: Greeter connected version=1.26.0 api=1 resettable=false
[+2194.05s] DEBUG: Greeter start authentication for pi
[+2194.05s] DEBUG: Session pid=22622: Started with service 'lightdm', username 'pi'
[+2194.05s] DEBUG: Session pid=22622: Got 1 message(s) from PAM
[+2194.05s] DEBUG: Prompt greeter with 1 message(s)

@Quietscher
Copy link
Author

This is in the forever out log, when the greeter appears

2024-04-02T08:19:59: (chromium-browser:21847): Gtk-WARNING **: 08:19:59.379: Theme parsing error: gtk.css:5:116: 'height' is not a valid property name
2024-04-02T08:19:59:
2024-04-02T08:19:59: (chromium-browser:21847): Gtk-WARNING **: 08:19:59.379: Theme parsing error: gtk.css:5:142: 'max-height' is not a valid property name
2024-04-02T08:19:59: [21847:21847:0402/081959.475262:ERROR:policy_logger.cc(157)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the --enable-chrome-browser-cloud-management command line flag to enable it if you are not using the official Google Chrome build.
2024-04-02T08:19:59:
2024-04-02T08:19:59: DevTools listening on ws://127.0.0.1:46383/devtools/browser/6d9f1c5f-bfb3-40ba-a717-caa1fbeb6594
2024-04-02T08:19:59: [21847:21977:0402/081959.769976:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
2024-04-02T08:19:59: [21847:21977:0402/081959.771155:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
2024-04-02T08:19:59: [21847:21977:0402/081959.771600:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
2024-04-02T08:19:59: close object 1: Invalid argument
2024-04-02T08:19:59: close object 2: Invalid argument
2024-04-02T08:19:59: close object 3: Invalid argument
2024-04-02T08:19:59: close object 4: Invalid argument
2024-04-02T08:19:59: close object 5: Invalid argument
2024-04-02T08:19:59: close object 6: Invalid argument
2024-04-02T08:20:03: close object 1: Invalid argument
2024-04-02T08:20:03: close object 2: Invalid argument
2024-04-02T08:20:03: close object 3: Invalid argument
2024-04-02T08:20:04: close object 4: Invalid argument
2024-04-02T08:20:04: close object 5: Invalid argument
2024-04-02T08:20:04: close object 6: Invalid argument
2024-04-02T08:20:19: puppeteer close event for http://localhost/mywebsite: undefined
2024-04-02T08:20:19: Browser stopped with code 1 and signal null
2024-04-02T08:20:19: [22033:22033:0402/082019.501816:ERROR:wayland_connection.cc(196)] Failed to connect to Wayland display: Connection refused (111)
2024-04-02T08:20:19: [22033:22033:0402/082019.501884:ERROR:ozone_platform_wayland.cc(264)] Failed to initialize Wayland platform
2024-04-02T08:20:19: [22033:22033:0402/082019.501899:ERROR:env.cc(257)] The platform failed to initialize. Exiting.
2024-04-02T08:20:19: Puppeteer launch exception Error: Failed to launch the browser process! undefined
2024-04-02T08:20:19: [22033:22033:0402/082019.501816:ERROR:wayland_connection.cc(196)] Failed to connect to Wayland display: Connection refused (111)
2024-04-02T08:20:19: [22033:22033:0402/082019.501884:ERROR:ozone_platform_wayland.cc(264)] Failed to initialize Wayland platform
2024-04-02T08:20:19: [22033:22033:0402/082019.501899:ERROR:env.cc(257)] The platform failed to initialize. Exiting.
2024-04-02T08:20:19:
2024-04-02T08:20:19:
2024-04-02T08:20:19: TROUBLESHOOTING: https://pptr.dev/troubleshooting
2024-04-02T08:20:19:
2024-04-02T08:20:19: *** puppeteer launch error, not proceeding

@stormvansoldt
Copy link

Thanks for that output, I have a few PiSignage devices on the latest 5.X version and I haven't been able to re-create the issue.

What does your playlist look like/what type of content does it contain?

@Quietscher
Copy link
Author

It's just some webpages that are served on a locally running nginx. It is a compiled Vue project with routing.

@stormvansoldt
Copy link

stormvansoldt commented Apr 2, 2024

EDIT: It's been about an hour and the sign is still going strong. Maybe give this a try
EDIT 2: Two hours, still coming along fine. I also found another config to change that's a little less hack-y, but @Quietscher I'm curious to hear your results if you get a chance to try this.

This is a REALLY stupid workaround and might not even solve the core issue, but here's what I'm testing right now:

sudo sed -i '/^autostart0/ s/./#&/' /etc/wayfire/greeter.ini
sudo reboot now

Basically just disabling the greeter altogether. I already confirmed the player still boots normally with this change and currently have it cycling through a few selfhosted web pages. I'll update once I hit the 30-minute timer

@AbhijithBn
Copy link

Hi @Quietscher

We are actively working on this issue.

Can you try the following?

  1. In the file /etc/lightdm/lightdm.conf, search for the following lines, uncomment it and change the values accordingly
greeter-user=pi
pam-greeter-service=lightdm-autologin

This should autologin pi user and also prevent Chrome from throwing Invalid user/auth errors.

  1. In the file /etc/wayfire/greeter.ini, comment the line

#autostart0 = /usr/sbin/pi-greeter

This should prevent the greeter UI from showing up.

Please let us know if this solves the issue. We will be testing the same too.

Thank you for all your previous debug logs and patience.

@Quietscher
Copy link
Author

Ok I'll first try @AbhijithBn approach, i will let you know about the results. Afterwards if the problem still occurs i will try your approach @stormvansoldt. Thanks for now!

@Quietscher
Copy link
Author

Also btw, can you add an option to set the cursor position? at the moment it is centered on the screen (but invisible) and therefore it triggers a hover effect on my website that i am showing, that should not occur.
Or is there an option to move it after startup (e.g. to a screen corner)

@Quietscher
Copy link
Author

Ok with @AbhijithBn Solution the screen now just turns black after 30min

@Quietscher
Copy link
Author

ah okay @stormvansoldt solution is the same as @AbhijithBn solution:
#autostart0 = /usr/sbin/pi-greeter

I am sorry but it does not work as intended. the screensaver might be gone, but now the screen is just black by itself

@Quietscher
Copy link
Author

The Asset cant cause the issue. The assets did not change between the versions. They are Weblinks (CORS supported).

@colloqi
Copy link
Owner

colloqi commented Apr 10, 2024

Is there any chance we can get those links to test here?

@Quietscher
Copy link
Author

Okay yesterday it happened again. But that must have been after 6h or more

@Quietscher
Copy link
Author

OK so, I cant ssh to it anymore, I cant open the terminal even with a keyboard connected to the pi, the picture is frozen and the Pi 5 lamp that is usually shining in bright green is shining less but still a little green. The fan spinns, but not constant, it seems to try to process sth.

@Quietscher
Copy link
Author

The only way I can get out of this by now is by unplugging the Pi from the powersource and replugging it in. This seems like a major bug.

@AbhijithBn
Copy link

AbhijithBn commented Apr 11, 2024

Before you unplug the power supply can you try the following?

df -h
du /home/pi/apps-data/.config/chromium -h -d 1
du /home/pi/apps-data/.config/chromium/weblink-0 -h -d 1

@Quietscher
Copy link
Author

OK so, I cant ssh to it anymore, I cant open the terminal even with a keyboard connected to the pi, the picture is frozen and the Pi 5 lamp that is usually shining in bright green is shining less but still a little green. The fan spinns, but not constant, it seems to try to process sth.

Please read.
I can't because it does not recognize any input. Additionally it does not show any cursor. AND I cant ssh.

@AbhijithBn
Copy link

It is still connected to your open-source server right?
You can issue those commands and send us the output.

@Quietscher
Copy link
Author

I am sorry that is not possible.
This is the only hints I have.
pi
image

@Quietscher
Copy link
Author

The pi is not connected

@AbhijithBn
Copy link

AbhijithBn commented Apr 11, 2024

Is there any chance we can get those links to test here?

Is this possible

Can you keep your Player connected to pisignage.com instead of open-source server while we figure out this issue?

@Quietscher
Copy link
Author

These are the assets:
image

@Quietscher
Copy link
Author

The assets can't be a problem. They did not change.

@Quietscher
Copy link
Author

It's just some webpages that are served on a locally running nginx. It is a compiled Vue project with routing.

Here it is written, what the Signage should present

@Quietscher
Copy link
Author

Does this help? Do you have an Idea where the problem is buried? 😅 I did not change anything but upgraded the system to the 5.1.2 version.

@colloqi
Copy link
Owner

colloqi commented Apr 15, 2024

5.1.4 should address this issue or a simple Raspberry OS update and upgrade as explained in https://forums.raspberrypi.com/viewtopic.php?p=2211369

@Quietscher
Copy link
Author

It's updated now, ill let you know if the issue still persists.
The issue that the cursor triggers hover effects still persists!

@AbhijithBn
Copy link

HI @Quietscher
Can you send us a video of the issue ?

@Quietscher
Copy link
Author

The cursor just triggers hover effects

@Quietscher
Copy link
Author

because its in the middle of the screen

@AbhijithBn
Copy link

We are not able to replicate it at our end. A video would help us in figuring out the issue.

@Quietscher
Copy link
Author

image the tile is in the middle of the screen no cursor is visible, still the hovereffect is triggered. when connecting a mouse the cursor becomes visible and one additionally sees that the cursor is indeed in the middle of the screen

@AbhijithBn
Copy link

Is it possible to remove the hover listener on the element via code?
Users have not reported this issue so far and hence not sure if we can do anything about this.

@Quietscher
Copy link
Author

i can try this later, i hope it does not trigger hover effects. Is there a possibility to just move it via default to a corner? e.g. top left?
This would be great.
Or as mentioned, that you can set the default cursor position in piSignage Server.

@Quietscher
Copy link
Author

Imagine Users displaying Websites, in any case you dont want to have the cursor triggering any effects in the center of the screen

@AbhijithBn
Copy link

Not sure if we can do anything about it at the moment. So please disable hover effects in your website design by disabling event listeners. That should solve this issue.

@Quietscher
Copy link
Author

I know.
There are libraries to move the cursor via code. That would be nice, that you just move it to a corner, than no one will probably have weired effects resulting from the cursor. 👍

@AbhijithBn
Copy link

Let us know if any of those libraries work for you 😁

@colloqi
Copy link
Owner

colloqi commented Apr 17, 2024

Also, we hide the cursor using wayfire plugin

@Quietscher
Copy link
Author

Also, we hide the cursor using wayfire plugin

That's not what I am talking about.
Yes, you cannot visibly see the cursor, but it is there, in the middle of the screen doing side effects to the assets the piSignage shows.
My idea is that you move it to a corner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants