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

            Bug ID: 527319
           Summary: Bug in recent update Fedora Plasma Mobile Spin. Plasma
                    Version 6.7.5.
    Classification: Plasma
           Product: plasma-mobile
      Version First unspecified
       Reported In:
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Shell
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected]
  Target Milestone: ---

This bug report was created with the help of ChatGPT

# Plasma Mobile 6.7.5: Wallpaper configuration crashes plasmashell (SIGSEGV) —
disabling window bindings fixes crash

## Summary

Opening the desktop wallpaper configuration in Plasma Mobile 6.7.5 causes
`plasmashell` to crash with SIGSEGV.

The crash occurs during QML component initialization in
`PlasmaQuick::ConfigView::setSource()`, with the fault occurring inside Qt's
QML binding evaluation code.

**Disabling the two window-property bindings in `AppletConfiguration.qml`
completely resolves the issue.** The wallpaper configuration interface then
opens and functions correctly.

## Environment

- Distribution: Fedora Linux 44, Plasma Mobile Spin
- Device: Lenovo ThinkBook 14 G4 IAP
- Display: 1920 × 1080, Wayland session
- Plasma Mobile: 6.7.5-1.fc44
- Plasma Workspace: 6.7.5-1.fc44
- KWin: 6.7.5-1.fc44
- KDE Frameworks: 6.31.0
- Qt Base: 6.11.2-3.fc44
- Qt Declarative: 6.11.2-2.fc44
- Plasma shell: `org.kde.plasma.mobileshell`

## Steps to reproduce

1. Log into a Fedora 44 Plasma Mobile session.
2. Open the desktop/homescreen wallpaper configuration.
3. Observe that the configuration interface fails to open and `plasmashell`
crashes.
4. The Plasma shell subsequently restarts.

The issue began following an update from Plasma 6.6.4 / Qt 6.10.2 to Plasma
6.7.5 / Qt 6.11.2.

## Expected behavior

The wallpaper configuration interface should open normally, allowing selection
and configuration of desktop wallpapers.

## Actual behavior

`plasmashell` terminates with SIGSEGV while constructing the containment
configuration interface.

The journal includes:

```text
Could not find wallpaper plugin ""
file:///usr/share/plasma/shells/org.kde.plasma.mobileshell/contents/configuration/AppletConfiguration.qml:75:9:
QML ConfigListPage: Created graphical object was not placed in the graphics
scene.
Process (plasmashell) dumped core.
```

Relevant stack frames:

```text
QV4::ExecutionEngine::toVariant()
QQmlBindPrivate::postEvalEntry()
QQmlBind::eval()
QQmlBind::componentComplete()
QQmlObjectCreator::finalize()
QQmlComponentPrivate::complete()
PlasmaQuick::ConfigView::setSource()
ContainmentConfigView::init()
DesktopView::showConfigurationInterface()
```

## Investigation

The configured wallpaper plugin is valid and installed.

The saved containment configuration contains:

```ini
[Containments][1]
plugin=org.kde.plasma.folder
wallpaperplugin=org.kde.image
```

The installed wallpaper metadata identifies the plugin as `org.kde.image`.

The running Plasma shell also confirms the correct wallpaper identifier through
D-Bus:

```text
wallpaperPlugin = org.kde.image
```

The Plasma scripting interface reports:

```text
Desktop 0: id=1, screen=0, wallpaperPlugin=org.kde.image
```

Therefore, although the journal reports an empty wallpaper plugin identifier,
neither the saved configuration nor the running desktop containment appears to
have an invalid wallpaper selection.

## Confirmed workaround

File:

```text
/usr/share/plasma/shells/org.kde.plasma.mobileshell/contents/configuration/AppletConfiguration.qml
```

Original lines 62–66:

```qml
Binding {
    // Window bindings
    root.Window.window.flags: Qt.FramelessWindowHint
    root.Window.window.visibility: Window.Maximized
}
```

Temporarily removing this `Binding` block and restarting
`plasma-plasmashell.service` allows the wallpaper picker to open successfully.

No other configuration changes or package downgrades were required.

This strongly implicates one or both window-property bindings, or their
interaction with Qt's QML initialization lifecycle.

It is not yet established which of the two property assignments is responsible.

## Additional observations

A separate Fedora Plasma Mobile installation on an HP touchscreen all-in-one
computer previously experienced a closely related crash when opening wallpaper
configuration. That installation was subsequently reinstalled and became
stable.

The ThinkBook provides a more useful reproduction because the wallpaper
selector worked before the system update and the failure was reproduced
consistently afterward.

## Suggested investigation

Examine the `Binding` block targeting `root.Window.window.flags` and
`root.Window.window.visibility` during construction of
`AppletConfiguration.qml`.

Possible areas to investigate include window attachment initialization timing,
whether `root.Window.window` is available when the bindings are evaluated, and
behavior changes in Qt 6.11's QML binding engine.

The successful workaround provides a narrow starting point for identifying the
underlying defect.

## Attachments available

- Full `plasmashell` coredump backtrace
- Journal output showing the crash and QML warnings
- Fedora DNF update transaction history
- Original and modified QML configuration file details


***
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


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

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

Reply via email to