https://bugs.kde.org/show_bug.cgi?id=524615

            Bug ID: 524615
           Summary: Plasma mobile 6.6.6 homescreen crashes after switching
                    from folio to halcyon and back again.
    Classification: Plasma
           Product: plasma-mobile
      Version First unspecified
       Reported In:
          Platform: postmarketOS
                OS: Linux
            Status: REPORTED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

***
If you're not sure this is actually a bug or valid feature request, instead
post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Do not paste LLM output.

Please remove this comment after reading and before submitting - thanks!
***

DESCRIPTION
I installed postmarketOS on my pixel 3a XL using the 20260814 prebuilt images.
Soon after installing and before installing any apps, I changed the homescreen
to halcyon from the default (which seems to have been folio) and back to folio.
This caused the homescreen to be replaced by an error message stating "Error
loading applet: package  does not exist." There is a double space between
"package" and "does" in the error message. The middle plasma button is
unresponsive.

STEPS TO REPRODUCE
1. Long press homescreen
2. Tap "settings"
3. Tap "change homescreen"
4. select halcyon and apply
5. select folio and apply

OBSERVED RESULT
Homescreen replaced by giant error message, centre plasma button on button
navigation unresponsive.

EXPECTED RESULT
Homescreen should switch back to folio

SOFTWARE/OS VERSIONS
Operating System (available in the Info Center app, or by running `kinfo` in a
terminal window):
KDE Plasma Version: 6.6.6
KDE Frameworks Version: 6.26.0
Qt Version: 6.11.1

ADDITIONAL INFORMATION
I attempted to fix it with TTYescape but likely due to misconfiguration on my
part, it didn't work. I fixed it by reflashing the phone from my computer with
fastboot.

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

Reply via email to