[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwin
Subject:    [Bug 179042] New: KSelectionWatcher doesn't notice composite turned
From:       Marco Martin <notmart () gmail ! com>
Date:       2008-12-29 12:02:54
Message-ID: bug-179042-4790 () http ! bugs ! kde ! org/
[Download RAW message or body]

http://bugs.kde.org/show_bug.cgi?id=179042

           Summary: KSelectionWatcher doesn't notice composite turned on or
                    off
           Product: kwin
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kwin@kde.org
        ReportedBy: notmart@gmail.com


Version:            (using Devel)
Compiler:          gcc (SUSE Linux) 4.3.2 [gcc-4_3-branch revision 141291]  
OS:                Linux
Installed from:    Compiled sources

with svn revision of kdelibs 902833 and kdebase 902828 i have the following
problem (but seems to be there since some time):

in kdelibs/plasma/theme.cpp there is the following code to watch when the
compositing is turned on or off:
char net_wm_cm_name[100];
        sprintf(net_wm_cm_name, "_NET_WM_CM_S%d", screen);
        d->compositeWatch = new KSelectionWatcher(net_wm_cm_name, -1, this);
        connect(d->compositeWatch, SIGNAL(newOwner(Window)), this,
SLOT(compositingChanged()));
        connect(d->compositeWatch, SIGNAL(lostOwner()), this,
SLOT(compositingChanged()));

similar also to kwin/composite.cpp line 122

but in both cases the code doesn't seem to work, in theme.cpp the signal
newOwner()/lostOwner() are never fired
and seems that also lostOwnership() in composite.cpp never get fired.
now i don't know if it's a problem in kwin, in
KSelectionWatcher/KSelectionOwner or in the code that uses it (seems strange
that in 2 diffent places there is the same error?) i also tried to use
kselectionowner in theme.cpp, but also here lostOwnership() never gets fired.

if it counts something i have Nvidia drivers 180.18, but i've heard of people
having the problem in plasma with different hardware setups.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin
[prev in list] [next in list] [prev in thread] [next in thread]