Bug#427468: closed by Sune Vuorela <debian@pusling.com> (Re: Bug#427468: mime-types / ksycoca broken after upgrade)

[Helen Faulkner <helen@debian.org>]

reopen 427468
severity wishlist
reassign 427468 kdelibs4c2a
thanks mate!


Hi again,

Thanks for the quick response :)

I doubt that users would find that information file for kdelibs4c2a (in fact I 
doubt that most users would even know that package to report such a bug against 
- I certainly didn't).

I suggest that you put in a debconf interaction with the user that works as 
follows when the relavant parts of kde are being upgraded.

1) If kde is running, warn the user that:
2) kde might need to be restarted, to avoid weird things happening, but
3) don't restart kde until you have finished updating your system (since the 
process updating the system might be part of kde, and we don't want to interrupt 
that).

I think this would inform the users about the need to restart kde after an 
upgrade much more effectively, since they would have to acknowledge the warning 
as part of the install process.

Cheers,

Helen




Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> #427468: mime-types /  ksycoca broken after upgrade,
> which was filed against the kdebase package.
>
> It has been closed by Sune Vuorela <debian@pusling.com>.
>
> Their explanation is attached below.  If this explanation is
> unsatisfactory and you have not received a better one in a separate
> message then please contact Sune Vuorela <debian@pusling.com> by replying
> to this email.
>
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
>
>
>
> ------------------------------------------------------------------------
>
> Subject:
> Re: Bug#427468: mime-types / ksycoca broken after upgrade
> From:
> Sune Vuorela <debian@pusling.com>
> Date:
> Mon, 4 Jun 2007 12:25:11 +0200
> To:
> 427468-done@bugs.debian.org
>
> To:
> 427468-done@bugs.debian.org
>
>
> On Monday 04 June 2007, Helen Faulkner wrote:
>
> > Anyway, I figured something was wrong with kde in general, so I ran a
> > couple of things from konsole to see what it said. The output is below. 
> > Then, seeing the errors about KSycoca, I ran "kbuildsycoca", which seems to
> > have fixed the problem (the last call of konqueror in my output below seems
> > to have worked fine).  
>
> Occasionally kde bumps its internal database version and format. A rerunning 
> of kbuildsycoca rebuilds its database with the new format.
> kbuildsycoca is also run when you log in, so we generally just advice people 
> to log out and back in.
>
> > However I suspect that many users wouldn't know to 
> > try this, so would be stuck with a "broken" konqueror, kwrite, and probably
> > other kde stuff as well (hence the "important" severity call).
>
> We are trying to just educate the users to know that after a kde upgrade, it 
> is normally required to restart kde.
>
> We can't just restart peoples kde in postinst, so people will have to do it 
> themselves.
>
> > There still seem to be problems with my system, see the errors in the
> > output, even after running kbuildsycoca.
>
> it is quite normal to have lots of konsole output running kde applications.
>
> > Sending this bug to kdebase because I don't know which package it belongs
> > to, but I suspect something deep in the workings of kde.
>
> it is in kdelibs4c2a stuff has changed.
>
> There is already a file in place that tells bugreporters against kdelibs4c2a 
> the following:
>
>
> | Reporting bugs for KDE packages
> | -------------------------------
> |
> | KDE does not support beeing upgraded while running. If you do so, you may
> | encounter weird bugs (empty menus or configuration dialogs e.g.), and even
> | crashes.
> |
> | If you recently upgraded kdelibs and/or kdebase packages, please consider:
> |  * exiting your current KDE session.
> |  * ensuring that no more KDE process is still running, especially the 
> |    processes  named (list beeing non-limitative): dcopserver, kded, 
> |    ksmserver... 
> | * log in KDE again.
> |
> | Then try to reproduce you bug. If it's not reproducible, then please do not
> | report it.
>
> As we can't do anything else than inform our users, I am marking this bug as 
> done.
>
> /Sune