Summary: | Plasmashell crashes in TaskManager::TaskGroupingProxyModel::Private::sourceRowsAboutToBeRemoved() on external screen re-connection | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | cemkaya.boun <cemkaya.boun> |
Component: | Task Manager and Icons-Only Task Manager | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | aleixpol, kde, nate, notmart, qydwhotmail |
Priority: | NOR | Keywords: | drkonqi, multiscreen |
Version: | 5.27.3 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
cemkaya.boun@gmail.com
2023-04-05 21:09:01 UTC
It's crashing in `Q_EMIT q->dataChanged(parent, parent);` Code says this: const QModelIndex parent = q->index(j, 0); q->beginRemoveRows(parent, mapIndex, mapIndex); rowMap[j]->remove(mapIndex); q->endRemoveRows(); // Various roles of the parent evaluate child data, and the // child list has changed. Q_EMIT q->dataChanged(parent, parent); Could it be that when we remove the rows, the parent gets cleaned and becomes nullptr? Ir shouldn't. (In reply to Nate Graham from comment #1) > Could it be that when we remove the rows, the parent gets cleaned and > becomes nullptr? Ideally it shouldn't, as the signal is "about"ToBeRemoved. The question is why `QQuickRepeater::setModel` was called again. It should only be called when a new task manager is added. No more reports since April. Maybe this got fixed since then? Is it still happening, Cemkaya? (In reply to Nate Graham from comment #3) > No more reports since April. Maybe this got fixed since then? Is it still > happening, Cemkaya? Hi, I do not have access to the external screen now, but I can get back to you next week. Thanks for your help! (In reply to cemkaya.boun@gmail.com from comment #4) > (In reply to Nate Graham from comment #3) > > No more reports since April. Maybe this got fixed since then? Is it still > > happening, Cemkaya? > > Hi, I do not have access to the external screen now, but I can get back to > you next week. Thanks for your help! I can confirm that the bug is not present anymore. External screen works as intended. Excellent, thanks for following up! *** This bug has been marked as a duplicate of bug 474768 *** |