Replies: 2 comments 1 reply
-
My guess is that it's related to the Please confirm if that's the case. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I read both of those threads and wasn't able to see a way to verify if it
is related or not.
How do i check?
Thx,
Josh
…On Mon, Nov 4, 2024 at 5:44 PM Soumya Deb ***@***.***> wrote:
My guess is that it's related to the labwc change.
More details: #52 <#52> & #53
<#53>
Please confirm if that's the case.
—
Reply to this email directly, view it on GitHub
<#54 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEEWF7EKEF5CJCRSBPZVP6TZ672GVAVCNFSM6AAAAABRC6PHPCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJUHAYDOOA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, thanks very much for making PIOSK! I have been using it quite happily for a couple weeks. But today, I decided to wipe, and re-install the pi image (and kiosk), and now, PIOSK is not opening the browser on boot. The web interface is working, and able to reboot etc, but it's just not launching chromium. I am able to manually open chromium from the desktop just fine.
This is a pi 5, running the latest RPI OS 32-bit. Same hardware that was running flawlessly for many weeks.
Do you have any ideas?
Beta Was this translation helpful? Give feedback.
All reactions