Created attachment 2022992 [details]
File: proc_pid_status

Created attachment 2022993 [details]
File: maps

Created attachment 2022994 [details]
File: limits

Created attachment 2022995 [details]
File: open_fds

Created attachment 2022996 [details]
File: mountinfo

Created attachment 2022997 [details]
File: os_info

Created attachment 2022998 [details]
File: core_backtrace

Created attachment 2022999 [details]
File: dso_list

Created attachment 2023000 [details]
File: var_log_messages

Created attachment 2023001 [details]
File: cpuinfo

Created attachment 2023002 [details]
File: backtrace

Created attachment 2023003 [details]
File: environ

I've just submitted patch that can fix this bug.
See patch attached to KDE bug https://bugs.kde.org/show_bug.cgi?id=472453.

1. Booted Fedora.
2. Opened Konsole, started Krfb.
3. Connected to this VNC session from outside (reproduced using Krdc in CentOS Linux, and RealVNC in Windows).
4. Inside the VNC session window, moved the windows around a little bit; opened Kwrite.
5. As soon as I press any key on the keyboard, Krfb crashes, and VNC session terminates. The key remains "pressed" inside the target system. If this was an alphanumeric key, it begins to be infinitely typed in the active window, until I myself press the same key. If this was a modifier key, like Shift, it becomes "stuck" and affects all the actions as if the real modifier key was being held pressed constantly.


reporter:       libreport-2.17.15
type:           CCpp
reason:         krfb killed by SIGABRT
journald_cursor: s=7a5d0ef34ed049a18d0925cf4a25ee6d;i=937a;b=953cdee3fa0c49d5a5bef0bb411436ef;m=cd949939;t=616cec3ba9a73;x=fe6f0791da6c89fd
executable:     /usr/bin/krfb
cmdline:        /usr/bin/krfb -qwindowtitle Krfb
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.krfb-ef09579b85d6440db1f2bb52ee250c44.scope
rootdir:        /
uid:            1000
kernel:         6.8.7-300.fc40.x86_64
package:        krfb-24.02.1-1.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: std::__glibcxx_assert_fail

After sending the report, I noticed there was an update ready, which also included krfb. I updated it, so now it has version 24.02.2, and tried the new version. It still crashes on the first keypress, but now the pressed key does not remain "stuck", it gets properly released.

Patch is not included in this version. Ask package maintainer to include it or wait for new release.

Is there a place where I could get the ready patch? I'd like to try building the fixed version and checking it out, but I'm not sure what patch you mean. Rawhide has the same version, and I can't find the relevant commits in the krfb upstream.

Patch: https://bugs.kde.org/show_bug.cgi?id=472453#c7
Commit in krfb: https://invent.kde.org/network/krfb/-/commit/6e7a5ba56966ea1b67400be9ab7c82885abb76be

FEDORA-2024-4a61fcd745 (krfb-24.02.2-3.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-4a61fcd745

Thanks!
I've installed that test version into Fedora 40, and while the crash indeed seems to be gone, unfortunately, it has other critical issues.

I'm not too much familiar with bug reporting policy here, sorry. So should I report them as separate bugs or continue here?

FEDORA-2024-4a61fcd745 has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-4a61fcd745`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-4a61fcd745

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

> I'm not too much familiar with bug reporting policy here, sorry. So should I report them as separate bugs or continue here?

Please report it as separate issue.
And search for existing bug reports: https://bugs.kde.org/buglist.cgi?component=general&list_id=2699446&product=krfb&resolution=---

1. Start krfb in wayland session.
2. Connect from another pc to krfb by krdc or remmina.
3. Try keyboard input in any text field.

Result: krfb crashes.
Expected: keyboard input works normally.


reporter:       libreport-2.17.15
type:           CCpp
reason:         krfb killed by SIGABRT
journald_cursor: s=ed77079b78f042abace4c37c8c4f13fb;i=2a33f6;b=e198d8a5ff0845ef81bc82638a7ac662;m=1b27fd080;t=6179d7acc2f21;x=592da076c9aee114
executable:     /usr/bin/krfb
cmdline:        /usr/bin/krfb -qwindowtitle Krfb
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-org.kde.krfb-4c09a30040f44e898e119c3306004e88.scope
rootdir:        /
uid:            1000
kernel:         6.8.8-300.fc40.x86_64
package:        krfb-24.02.2-2.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: std::__glibcxx_assert_fail

According to file /usr/src/debug/krfb-24.02.2-2.fc40.x86_64/framebuffers/pipewire/pw_framebuffer.cpp, line 515 my patch still is not applied.
I'll try to figure out why.

I mean those lines is unchanged  but should (from krfb-24.02.2-2.fc40.x86_64):
```
QPoint PWFrameBuffer::cursorPosition()
{
    return d->cursor->position;
}
```

Build 24.02.2-2.fc40 doesn't have this patch applied, while 24.02.2-3.fc40 got it.
So wait for version 24.02.2-3.fc40 in stable repo.

FEDORA-2024-4a61fcd745 (krfb-24.02.2-3.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.