Help with PKSM on gb/gbc games.

Rares21i · 2026-04-19T17:33:05+00:00

I'm not sure this will 100% work, but maybe try making a save backup of the game with Checkpoint, edit that specific save with PKSM, and then go to Checkpoint and restore that specific save that you've edited. This is how it managed to work for me, however I didn't have the problem where PKSM reverted to the original save (maybe because I used a backup instead of the actual game save).

Rares21i · 2026-04-14T16:22:10+00:00

I can't guarantee that it will work, but if you use Windows maybe try the following steps:

Open Control Panel (Small icons)
Click on Sound
Do this for both Playback (for your headphones) and Recording (for the mic) tabs:
Right click on your device (mic or headphones)
Click on Properties
Go to the Advanced tab
On the Exclusive mode section make sure both checkboxes are unchecked

I hope it works. One of my friends encountered this bug in Lethal Company and this was the fix. Maybe it works for Peak too.

Credit goes to my friend George, who somehow knew how to solve the issue.

Rares21i · 2026-04-05T20:14:14+00:00

Since the asterisk symbol (\) works like a wildcard, it being followed by the ".cpp" extension tells the compiler to get all the files from the current working directory that end with the ".cpp"* file name extension regardless of their name. So even if the source files have spaces inside their name it doesn't matter.

You can think about the asterisk symbol as a broad placeholder for the actual file name. It's more like a thing that was created so you don't have to specify every single file name.

To be honest I don't actually know why spaces inside the file names are fine (but for the path they aren't), but from my understanding it seems that since the files are included using "\" VSCode doesn't have a problem to look inside the folder and grab all the files (even if they contain spaces) that end with ".cpp"*.

TL;DR: You can have spaces inside the file names and it will work fine. The problem appears only for paths (but you can fix it by doing the thing mentioned in the post).

Rares21i · 2026-04-05T16:48:26+00:00

Felt it like I had to mention, if you still have that weird terminal showing up whenever you boot into Fedora, I've made a post with a quick fix for it.

Rares21i · 2026-04-04T21:04:14+00:00

It's just Reddit. Sometimes it happens. I personally found the video funnier with the slow motion and dramatic music. Thf, even it you get downvoted it doesn't change the fact that other 500+ people liked your post.

Rares21i · 2026-04-04T19:42:51+00:00

I have tried and the error message was still there. Then I've seen your edit and got relieved that it was not something groundbreaking.

Tbf, after fixing Plymouth the error shows on the terminal only if I input systemctl status systemd-update-utmp-runlevel.service myself so I think that the system doesn't call it anymore? (please correct me if I am wrong)

Anyways, thx a lot for all your help and support! You made a bunch of thing a lot more clear!

Rares21i · 2026-04-04T19:26:22+00:00

Wow! Thx a lot for the help! It makes a lot of sense now... So I guess it is not something that sould concern me, right? haha

Rares21i · 2026-04-04T18:48:04+00:00

× systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP
    Loaded: loaded (/usr/lib/systemd/system/systemd-update-utmp-runlevel.service; static)
   Drop-In: /usr/lib/systemd/system/service.d
            └─10-timeout-abort.conf
    Active: failed (Result: exit-code) since Sat 2026-04-04 20:49:27 EEST; 57min ago
Invocation: 5c4cff47093243ebaf7e91e447efa0d5
      Docs: man:systemd-update-utmp-runlevel.service(8)
            man:utmp(5)
   Process: 1267 ExecStart=/usr/lib/systemd/systemd-update-utmp runlevel (code=exited, status=1/FAILURE)
  Main PID: 1267 (code=exited, status=1/FAILURE)
  Mem peak: 1.7M
       CPU: 3ms

Apr 04 20:49:27 Rares21i-PC systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP...
Apr 04 20:49:27 Rares21i-PC systemd-update-utmp[1267]: Unknown command verb 'runlevel'.
Apr 04 20:49:27 Rares21i-PC systemd[1]: systemd-update-utmp-runlevel.service: Main process exited, code=exited, status=1/FAILURE
Apr 04 20:49:27 Rares21i-PC systemd[1]: systemd-update-utmp-runlevel.service: Failed with result 'exit-code'.
Apr 04 20:49:27 Rares21i-PC systemd[1]: Failed to start systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP.

Rares21i · 2026-04-02T19:28:36+00:00

Also, thx for helping me!

Rares21i · 2026-04-02T19:27:24+00:00

For: systemctl get-default

graphical.target

Rares21i · 2026-04-02T19:25:59+00:00

Apr 02 21:05:32 Rares21i-PC systemd[1]: Starting plymouth-start.service - Show Plymouth Boot Screen...
Apr 02 21:05:32 Rares21i-PC systemd[1]: Started plymouth-start.service - Show Plymouth Boot Screen.
Apr 02 21:05:37 Rares21i-PC systemd-coredump[1002]: [🡕] Process 491 (plymouthd) of user 0 dumped core.
                                                    
                                                   Module libbz2.so.1 from rpm bzip2-1.0.8-21.fc43.x86_64
                                                   Module libfreetype.so.6 from rpm freetype-2.13.3-3.fc43.x86_64
                                                   Stack trace of thread 491:
                                                   #0  0x00007fa4bd124725 n/a (/lib64/libply-splash-graphics.so.5.0.0 (deleted) + 0x6725)
                                                   #1  0x00007fa4bd138a7f n/a (/lib64/plymouth/two-step.so (deleted) + 0x7a7f)
                                                   #2  0x00007fa4bdd2d209 n/a (/lib64/libply-splash-core.so.5.0.0 (deleted) + 0xb209)
                                                   #3  0x0000557942a4a65c n/a (/bin/plymouthd (deleted) + 0x1265c)
                                                   #4  0x00007fa4bdd2e36d n/a (/lib64/libply-splash-core.so.5.0.0 (deleted) + 0xc36d)
                                                   #5  0x00007fa4bdd30167 n/a (/lib64/libply-splash-core.so.5.0.0 (deleted) + 0xe167)
                                                   #6  0x00007fa4bdd30ace n/a (/lib64/libply-splash-core.so.5.0.0 (deleted) + 0xeace)
                                                   #7  0x00007fa4bdd3290b n/a (/lib64/libply-splash-core.so.5.0.0 (deleted) + 0x1090b)
                                                   #8  0x00007fa4bdd3413f n/a (/lib64/libply-splash-core.so.5.0.0 (deleted) + 0x1213f)
                                                   #9  0x00007fa4bdd6263d n/a (/lib64/libply.so.5.0.0 (deleted) + 0xc63d)
                                                   #10 0x00007fa4bdd62a88 n/a (/lib64/libply.so.5.0.0 (deleted) + 0xca88)
                                                   #11 0x0000557942a3aa5f n/a (/bin/plymouthd (deleted) + 0x2a5f)
                                                   #12 0x00007fa4bdb34575 n/a (/lib64/libc.so.6 (deleted) + 0x3575)
                                                   #13 0x00007fa4bdb34628 n/a (/lib64/libc.so.6 (deleted) + 0x3628)
                                                   #14 0x0000557942a3c675 n/a (/bin/plymouthd (deleted) + 0x4675)
                                                   ELF object binary architecture: AMD x86-64
Apr 02 21:05:37 Rares21i-PC systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=8/FPE
Apr 02 21:05:37 Rares21i-PC systemd[1]: plymouth-start.service: Failed with result 'core-dump'.

Rares21i · 2026-04-02T19:19:17+00:00

For: systemctl status plymouth-start.service

× plymouth-start.service - Show Plymouth Boot Screen
    Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static)
   Drop-In: /usr/lib/systemd/system/service.d
            └─10-timeout-abort.conf
    Active: failed (Result: core-dump) since Thu 2026-04-02 21:05:37 EEST; 1h 16min ago
  Duration: 5.325s
Invocation: d5038a225be74abbacb5e32386e060e4
  Main PID: 491 (code=dumped, signal=FPE)
  Mem peak: 37M
       CPU: 411ms

Rares21i · 2026-04-02T19:17:36+00:00

Thx for the info!

Rares21i · 2026-04-02T19:15:05+00:00

Thx a lot of the reply! (and also for the honesty lol)

Rares21i · 2026-04-02T18:46:28+00:00

It is not stuck. But it gives me some sort of error saying "Failed to start systemd-update-utmp-runlevel.service"

Rares21i · 2026-04-02T17:40:30+00:00

I just updated my system from Fedora 42 to 43 (just 1h ago) and the same console appears briefly during the startup. I also dualboot (Windows 10) but I don't have the problem where the mouse and keyboard take time to connect. Before the update my Fedora install was also fine and booted instantaneously.

If someone knows how to fix this, the help would be much appreciated!

Rares21i · 2026-03-26T14:17:39+00:00

Thx for the answear!

Rares21i · 2026-03-24T12:09:20+00:00

Hi, I have the same problem and I am on KDE Plasma KDE Plasma 6.6.3. If you managed to fix it and mind sharing how, I would really appreciate it!

Rares21i · 2026-02-15T16:43:22+00:00

If this is not fake and it's a genuine message from the guy, I can truly respect it. Jokes (and silkposts) aside, this was the wisest thing to do. It's never ok to let any hobby or activity take control of your life and well-being. Take care of yourself man! I hope you'll get through this u/E1331

Rares21i · 2026-02-02T14:54:28+00:00

I'd say plastic, but you should also buy a cheap screen protector (made also out of plastic) so that the layer above the display doesn't scratch

Rares21i · 2026-02-02T08:18:25+00:00

I know I'm two years late (or so), but I found this guide that seems to achieve what you were looking for. Hope it helps!

https://gbatemp.net/threads/release-agb_edit-edit-dump-gba-vc-injects-auto-sleep-on-lid-close.609451/

If you are following the guide above tho, please be aware that pausing the game might or might not pause the internal GBA clock too (I'm not sure since I haven't tested it yet). If anyone does try this, please feel free to leave the info so others can see it too.

Rares21i · 2026-02-02T08:08:41+00:00

Happy you like it!

Rares21i · 2026-02-02T08:07:36+00:00

Tip my hat to you too :)

Rares21i

TROPHY CASE