Bug 89202 - KDE looses previous settings and componets stop working
Summary: KDE looses previous settings and componets stop working
Status: RESOLVED DUPLICATE of bug 12620
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-09 23:21 UTC by Elias Pouloyiannis
Modified: 2004-09-11 12:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Elias Pouloyiannis 2004-09-09 23:21:26 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc (GCC) 3.4.1 20040831 Red Hat 3.4.1-10 (Fedora core test)
OS:                Linux

This is a really strange bug!!!!!!!!!!!!!!!!

At some point in time various KDE components stop working
1. The taskbar shows only some of the windows that are open. Specifically after the crash it will only show the
the windws that were in the active virtual Desktop, even after a Desktop switch
2. The System tray won't work after a relogin
3. The Window list button will not work
4. The Pager suffers the same problems the taskbar has

perhaps there are more that i didnt see

The problem started after a recent CVS upgrade.
The taskbar, sytem tray and pager problems are fixed if i close the appropriate applets and reload them
The Window list problem is fixed when i run somthing like: dcop kicker kicker restart

I have tried removing completely the old configuration and making a new one but after 1 or two relogins in the system the same problem arises, so i guess it's not a problem on old configuration files not being parsed corectly

The only thing is that I have used the kiosktool (also recently updated) to minimise the configuration steps needed so It could be related to that

a really really weird bug

Thanks in advance
Comment 1 Rex Dieter 2004-09-10 14:20:03 UTC
I've seen the same thing, and traced it to the immodule patch(es) redhat/fedora puts in their qt package.
Comment 2 Maksim Orlovich 2004-09-10 15:36:21 UTC
There was some identical-sounding breakage due to some patch SUSE put in triggering an X bug... Seli, could you please share the details?
Comment 3 Elias Pouloyiannis 2004-09-10 18:36:43 UTC
It's true right before updating from CVS i did an update from the 3.3.2 to qt-3.3.3 from fedora binaries

I do have qt-copy from CVS. Do you think updating from that will sort out the problems?

Right now i cleaned up my old configuration again, (I kept them safe of course) and made i clean install. Seems to work but then again, i thought the same thing right before every crash
Comment 4 Lubos Lunak 2004-09-11 12:57:47 UTC

*** This bug has been marked as a duplicate of 12620 ***