https://bugs.kde.org/show_bug.cgi?id=522633
Bug ID: 522633
Summary: kunifiedpush-distributor crashes due to null
QWebSocket pointer in AutopushProvider
Classification: I don't know
Product: kde
Version First unspecified
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
**Title**
Crash in `kunifiedpush-distributor`: null `QWebSocket` dereference in
`AutopushProvider::connectToProvider()`
**Product**
KUnifiedPush (`kunifiedpush-distributor`)
**Version**
26.04.2-2.fc43
**Platform**
* Nobara Linux 43 (Fedora 43 based)
* KDE Plasma 6
* Qt 6.10.3
* KDE Frameworks 6.27
---
### Summary
`kunifiedpush-distributor` crashes with SIGSEGV while attempting to reconnect
to the Autopush provider.
The crash is reproducible over a long period (multiple coredumps between May
and July 2026).
---
### Crash location
The debugger consistently reports:
```
QWebSocket::errorString(this = 0x0)
```
called from
```
KUnifiedPush::AutopushProvider::connectToProvider()
autopushprovider.cpp:60
```
The `this` pointer of `QWebSocket` is `nullptr`.
---
### Backtrace
Relevant frames:
```
#8 QWebSocket::errorString(this = 0x0)
#9 KUnifiedPush::AutopushProvider::connectToProvider(...)
autopushprovider.cpp:60
```
The application crashes immediately after entering `QWebSocket::errorString()`.
---
### Observations
The crash happens repeatedly in the same code path.
The debugger shows that the distributor already has registered clients,
including:
```
org.kde.neochat
```
The state of `AutopushProvider` indicates:
```
m_status = NoNetwork
```
at the moment of the crash.
This suggests that the reconnect/error handling path may access a `QWebSocket`
object after it has been destroyed or before it has been created.
---
### Expected behavior
`kunifiedpush-distributor` should gracefully handle network
disconnects/reconnects without dereferencing a null `QWebSocket` pointer.
---
### Actual behavior
`kunifiedpush-distributor` crashes with SIGSEGV.
---
### Additional information
Initially, DrKonqi was unable to generate a crash report because GDB was not
installed on the system.
After installing GDB and using Fedora's debuginfod service, the full backtrace
consistently points to the same location.
The issue has been reproduced multiple times on the same system.
If needed, I can provide:
* full GDB backtrace (`bt full`)
* complete coredump
* KCrash metadata
* journal logs
* exact package versions
--
You are receiving this mail because:
You are watching all bug changes.
