|
Bugzilla – Full Text Bug Listing |
| Summary: | ksycoca does not seem to be updated after 4.3.5 update causing app crashes | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Lubos Lunak <llunak> |
| Component: | KDE4 Workspace | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P1 - Urgent | CC: | meissner |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 561660 | ||
|
Description
Lubos Lunak
2010-02-17 14:19:13 UTC
I cannot trigger any other crash than in KWrite, and even that one does not happen when run from CLI and after a re-login. There is presumably some strange interaction between the running process using still the old binaries and the new kwrite binary. So we can either just ignore this or make the update say that the session/computer should be restarted. I know the update process can tell to restart the computer after a kernel update. Is it possible to make it also tell the user to restart the desktop session? According to Dirk it's possible to flag update as 'restart your desktop', so that should be done here. |