[plasmashell] [Bug 519874] plasmashell and ksplashqml crash with SIGBUS (signal 7) - aarch64 with Fcitx 5 Qt6 platform input context plugin when updating the client-side UI via DBus.

2026-05-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=519874

--- Comment #16 from [email protected] ---
OK, I will
Might have to wait a bit, I'm busy lately—with final exams, the CET-4
English test, and so on...

TraceyC  于 2026年5月22日周五 04:06写道:

> https://bugs.kde.org/show_bug.cgi?id=519874
>
> TraceyC  changed:
>
>What|Removed |Added
>
> 
>  Resolution|BACKTRACE   |UPSTREAM
>  Status|NEEDSINFO   |RESOLVED
>
> --- Comment #15 from TraceyC  ---
> (In reply to xusu616 from comment #14)
> > Perhaps because many ARM packages are built using automated scripts?
> > I don't know how they do it... Maybe I should report this there?
>
> Since you said this:
> > The officially pre-built package from Arch Linux ARM triggers the bug,
> but my locally compiled version does not
>
> It does seem that the thing causing the crash is in the pre-built package.
> I do
> recommend reporting the issue to Fcitx
> https://github.com/fcitx/fcitx5/issues
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 519874] plasmashell and ksplashqml crash with SIGBUS (signal 7) - aarch64 with Fcitx 5 Qt6 platform input context plugin when updating the client-side UI via DBus.

2026-05-21 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=519874

TraceyC  changed:

   What|Removed |Added

 Resolution|BACKTRACE   |UPSTREAM
 Status|NEEDSINFO   |RESOLVED

--- Comment #15 from TraceyC  ---
(In reply to xusu616 from comment #14)
> Perhaps because many ARM packages are built using automated scripts? 
> I don't know how they do it... Maybe I should report this there?

Since you said this:
> The officially pre-built package from Arch Linux ARM triggers the bug, but my 
> locally compiled version does not

It does seem that the thing causing the crash is in the pre-built package. I do
recommend reporting the issue to Fcitx
https://github.com/fcitx/fcitx5/issues

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 519874] plasmashell and ksplashqml crash with SIGBUS (signal 7) - aarch64 with Fcitx 5 Qt6 platform input context plugin when updating the client-side UI via DBus.

2026-05-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=519874

--- Comment #13 from [email protected] ---
I rebuilt fcitx5-qt from source using makepkg(change to debug version, but
didn't trigger the bug), and the crash no longer occurs. 
The officially pre-built package from Arch Linux ARM triggers the bug, but my
locally compiled version does not
Then, I can't gdb it with names.

Arch Linux no longer uses the method of installing debug packages in favor of a
network method. However, this method is not always reliable on the ARM
architecture, so I tried compiling these packages to reproduce the
problemBut failed
I even reinstall the system,but still have this problem
I even had my system freeze a few times during compilation.
(In reply to TraceyC from comment #11)
> Thanks for the backtrace. Unfortunately it's incomplete and missing debug
> symbols for the following lines that we need to figure out exactly what's
> going wrong:
> 
> 
> #14 0xa452dcac in ?? () from /usr/lib/libFcitx5Qt6DBusAddons.so.1
> #15 0xadf2c004 in ?? () from /usr/lib/libQt6Core.so.6
> #19 0x8d2a08fc in ?? () from /usr/lib/libQt6DBus.so.6
> 
> Could you please install debug packages and attach a new symbolicated
> backtrace generated by using `coredumpctl gdb` in a terminal window? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports for details about how to do this. Thanks
> again!

I rebuilt fcitx5-qt from source using makepkg(change to debug version, but
didn't trigger the bug), and the crash no longer occurs. 
The officially pre-built package from Arch Linux ARM triggers the bug, but my
locally compiled version does not
Then, I can't gdb it with names.

Arch Linux no longer uses the method of installing debug packages in favor of a
network method. However, this method is not always reliable on the ARM
architecture, so I tried compiling these packages to reproduce the
problemBut failed
I even reinstall the system,but still have this problem
I even had my system freeze a few times during compilation.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 519874] plasmashell and ksplashqml crash with SIGBUS (signal 7) - aarch64 with Fcitx 5 Qt6 platform input context plugin when updating the client-side UI via DBus.

2026-05-16 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=519874

--- Comment #14 from [email protected] ---
Perhaps because many ARM packages are built using automated scripts? 
I don't know how they do it... Maybe I should report this there?

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 519874] plasmashell and ksplashqml crash with SIGBUS (signal 7) - aarch64 with Fcitx 5 Qt6 platform input context plugin when updating the client-side UI via DBus.

2026-05-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=519874

--- Comment #12 from [email protected] ---
(In reply to TraceyC from comment #11)
> Thanks for the backtrace. Unfortunately it's incomplete and missing debug
> symbols for the following lines that we need to figure out exactly what's
> going wrong:
> 
> 
> #14 0xa452dcac in ?? () from /usr/lib/libFcitx5Qt6DBusAddons.so.1
> #15 0xadf2c004 in ?? () from /usr/lib/libQt6Core.so.6
> #19 0x8d2a08fc in ?? () from /usr/lib/libQt6DBus.so.6
> 
> Could you please install debug packages and attach a new symbolicated
> backtrace generated by using `coredumpctl gdb` in a terminal window? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports for details about how to do this. Thanks
> again!

I ran thread apply all backtrace full with debuginfod enabled, but those lines
still show question marks.

Please note that I am running Arch Linux ARM (aarch64) on an Android tablet
(Xiaomi Pad 5). The official Arch Linux ARM repositories do not provide debug
packages or a debuginfod server for aarch64, and the x86 debuginfod server does
not cover ARM builds. Building a package as large as Qt6 with debug symbols
locally on this tablet might seem impractical.

If there's absolutely no other way, I will do it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[plasmashell] [Bug 519874] plasmashell and ksplashqml crash with SIGBUS (signal 7) - aarch64 with Fcitx 5 Qt6 platform input context plugin when updating the client-side UI via DBus.

2026-05-15 Thread TraceyC
https://bugs.kde.org/show_bug.cgi?id=519874

TraceyC  changed:

   What|Removed |Added

Summary|plasmashell and ksplashqml  |plasmashell and ksplashqml
   |crash with SIGBUS (signal   |crash with SIGBUS (signal
   |7) on Wayland on aarch64|7) - aarch64 with Fcitx 5
   |(ARM64) (arch Linux arm on  |Qt6 platform input context
   |nabu)   |plugin when updating the
   ||client-side UI via DBus.

-- 
You are receiving this mail because:
You are watching all bug changes.