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

Nate Graham <n...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDSINFO                   |CONFIRMED
          Component|Quick Settings              |general
            Summary|Configurações do sistema    |Setting
                   |fecha iniesperado           |Kirigami.FormData.buddyFor
                   |                            |to a null item crashes the
                   |                            |calling app
     Ever confirmed|0                           |1
   Target Milestone|---                         |Not decided
            Product|systemsettings              |frameworks-kirigami
           Assignee|plasma-b...@kde.org         |kdelibs-b...@kde.org
         Resolution|BACKTRACE                   |---
                 CC|                            |m...@ratijas.tk,
                   |                            |notm...@gmail.com
            Version|5.27.4                      |5.105.0

--- Comment #3 from Nate Graham <n...@kde.org> ---
Ok, so here's what appears to be happening. Your activities database has become
corrupted:

> kf.activitiesstats: [Error at ResultSetPrivate::initQuery]:  QSqlError("11", 
> "Não foi possível obter a linha", "database disk image is malformed")

This causes the grid of "Frequently used" pages to not be populated. Then when
we try to set the buddy for the label to the grid's first child item, it
crashes because there are no child items. Because that page is the thing that
gets shown when System Settings launches, it crashes on launch.

Looks like Kirigami.FormLayout doesn't handle the case of the object specified
by Kirigami.FormData.buddyFor being null.  We could work around this in the
code for the Quick Settings page, but ideally it would be fixed in Kirigami so
that app-specific workarounds aren't ever required anywhere.

Armando, you should be able to fix this yourself by deleting your kactivities
database and letting it get re-created. Delete
`~/.local/share/kactivitymanagerd/resources/database*` on your system and then
System Settings shouldn't crash anymore.

Finally, if you can attach
~/.local/share/kactivitymanagerd/resources/errors.log, we may be able to see
what happened to the database.

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

Reply via email to