starred/xiosk

Fork 0

mirror of https://github.com/debloper/xiosk.git synced 2026-04-26 21:35:51 +03:00

[GH-ISSUE #77] Force closing chromium makes PiOSK unable to relaunch. #62

New issue

Closed

opened 2026-03-03 11:14:04 +03:00 by kerem · 5 comments

kerem commented

2026-03-03 11:14:04 +03:00

Owner

Originally created by @jussihi on GitHub (May 9, 2025).
Original GitHub issue: https://github.com/debloper/xiosk/issues/77

After killing chromium with killall chromium, PiOSK won't start chromium ever again, even after a reboot.

Removing chromium's singletonlock file seems to help:
rm -rf ~/.config/chromium/SingletonLock

Some others have had similar problems:
https://github.com/puppeteer/puppeteer/issues/4860

Maybe add this to the runner before launching chromium?

Originally created by @jussihi on GitHub (May 9, 2025). Original GitHub issue: https://github.com/debloper/xiosk/issues/77 After killing chromium with `killall chromium`, PiOSK won't start chromium ever again, even after a reboot. Removing chromium's singletonlock file seems to help: `rm -rf ~/.config/chromium/SingletonLock` Some others have had similar problems: https://github.com/puppeteer/puppeteer/issues/4860 Maybe add this to the runner before launching chromium?

kerem

2026-03-03 11:14:04 +03:00

closed this issue
added the
wontfix

invalid
labels

kerem commented

2026-03-03 11:14:05 +03:00

Author

Owner

@debloper commented on GitHub (May 12, 2025):

Thanks for the report (and the fix).
Not quite sure the course of action.
I'm keeping this issue open for now.

@debloper commented on GitHub (May 12, 2025): Thanks for the report (and the fix). Not quite sure the course of action. I'm keeping this issue open for now.

kerem commented

2026-03-03 11:14:06 +03:00

Author

Owner

@jeffsilverm commented on GitHub (Jun 22, 2025):

The error message is more helpful than most error messages, but not quite helpful enough. The error messages are:

[17695:17695:0622/004816.835439:ERROR:chrome/browser/process_singleton_posix.cc:358] The profile appears to be in use by another Chromium process (10233) on another computer (frmwk16). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium.
[17695:17695:0622/004816.835573:ERROR:chrome/browser/ui/views/message_box_dialog.cc:198] Unable to show message box: Chromium - The profile appears to be in use by another Chromium process (10233) on another computer (frmwk16). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium.

It would be nice if the error message specified precisely what file to delete or how to unlock the profile. In my case, I used the find(1) command to find the SingletonLock file (and several variants of its spelling) with no obvious hits.

I am running Chromium version 137.0.7151.103 snap on Ubuntu 24.04.2 LTS.

Uninstalling and reinstalling chromium using snap cleared the problem, but I do not recommend this solution unless all else fails. Once that was done, I tried started chromium 3 times and could not reproduce the failure.

What I would like is for the error messages to be more specific: what command does the user use to "unlock the profile", please? Thank you.

@jeffsilverm commented on GitHub (Jun 22, 2025): The error message is more helpful than most error messages, but not quite helpful enough. The error messages are: ``` [17695:17695:0622/004816.835439:ERROR:chrome/browser/process_singleton_posix.cc:358] The profile appears to be in use by another Chromium process (10233) on another computer (frmwk16). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium. [17695:17695:0622/004816.835573:ERROR:chrome/browser/ui/views/message_box_dialog.cc:198] Unable to show message box: Chromium - The profile appears to be in use by another Chromium process (10233) on another computer (frmwk16). Chromium has locked the profile so that it doesn't get corrupted. If you are sure no other processes are using this profile, you can unlock the profile and relaunch Chromium. ``` It would be nice if the error message specified precisely what file to delete or how to unlock the profile. In my case, I used the `find(1)` command to find the SingletonLock file (and several variants of its spelling) with no obvious hits. I am running Chromium version 137.0.7151.103 snap on Ubuntu 24.04.2 LTS. Uninstalling and reinstalling chromium using snap cleared the problem, but I do not recommend this solution unless all else fails. Once that was done, I tried started chromium 3 times and could not reproduce the failure. What I would like is for the error messages to be more specific: what command does the user use to "unlock the profile", please? Thank you.

kerem commented

2026-03-03 11:14:06 +03:00

Author

Owner

@debloper commented on GitHub (Jul 3, 2025):

Don't login to chromium or sync with existing profiles.
Use a fresh/clean profile.

Instead of reinstalling, I think (but haven't verified) that you could simply log out of your chromium profile, and that should have fixed the issue.

Still keeping it open for verification.

@debloper commented on GitHub (Jul 3, 2025): Don't login to chromium or sync with existing profiles. Use a fresh/clean profile. Instead of reinstalling, I think (but haven't verified) that you could simply log out of your chromium profile, and that should have fixed the issue. Still keeping it open for verification.

kerem commented

2026-03-03 11:14:06 +03:00

Author

Owner

@jeffsilverm commented on GitHub (Jul 4, 2025):

I am unable to reproduce the problem. Could the error message be made clearer, please?

@jeffsilverm commented on GitHub (Jul 4, 2025): I am unable to reproduce the problem. Could the error message be made clearer, please?

kerem commented

2026-03-03 11:14:06 +03:00

Author

Owner

@debloper commented on GitHub (Jul 4, 2025):

@jeffsilverm sorry for not clarifying in my previous message... the error you've mentioned is from Chromium, and not from PiOSK.

If I were in your shoes, I'd either kill chromium (PID 10233) on hostname frmwk16 or, log out of the Chromium profile from the Pi where you're trying to run PiOSK on.

Again, this is unrelated to PiOSK. This is Chromium trying to keep its profile data integrity in check by not allowing multiple instances of the profile simultaneously from your Framework Laptop and the Raspberry Pi.

@debloper commented on GitHub (Jul 4, 2025): @jeffsilverm sorry for not clarifying in my previous message... the error you've mentioned is from Chromium, and not from PiOSK. --- If I were in your shoes, I'd either kill chromium (PID 10233) on hostname `frmwk16` or, log out of the Chromium profile from the Pi where you're trying to run PiOSK on. Again, this is unrelated to PiOSK. This is Chromium trying to keep its profile data integrity in check by not allowing multiple instances of the profile simultaneously from your Framework Laptop and the Raspberry Pi.

kerem referenced this issue

2026-03-03 11:14:23 +03:00

[PR #67] [MERGED] Compositor agnostic, systemd service implementation #90

kerem referenced this issue

2026-03-03 11:14:23 +03:00

[PR #62] [CLOSED] Systemd update #91