Created attachment 50820 [details] screenshot of Konq after the scroll wheel has been used Version: unspecified (using KDE 4.5.0) OS: Linux When I am in a KDE application and I use my mouse scroll wheel to scroll a window the information is so distorted or smeared that I can't read it. Some time if I scroll one line at a time it is okay. Other versions of KDE4 also had this problem BUT version 4.4.4 had no problems. This occurs even if compositing is turned off. It does not occur though if I use a different window manager and scroll the same kde program that consistently gives me trouble when running KDE 4.5. It makes KDE unusable. Reproducible: Always Steps to Reproduce: This is done with a GeForce4 nVidia AGP card. Open KDE app while running KDE 4.5 and use the mouse wheel to scroll. Actual Results: See attached image of Konqueror... it is not too bad... some time it is so bad that there is just vertical lines (smeared). Expected Results: Scrolling with mouse wheel so that info continues to be readable. It appeared to me that the upgrade did not change the xorg file as it had a July date and I installed 4.5 in August. (I am using the same nVidia driver as the previous version. I will provide you with any other information to get this problem solved. Version 4.4.4 was perfect so it can be fixed. I classify this as major because it renders KDE unusable for me.
Iirc there's some kind of conflict between Qt and one (or more) of the OSX dockers (awn, cairo-dock, some other? - i frankly forgot) one's breaking the X11 access of the other... -> in caser that's not a plasma panel: disable the docker, logout and in to ensure that's not it (but i actually guess it is) Esp. w/o compositing there's few chance that this is related to the WM at all (did you really mean that it's related to the WM and not to the entire DE?)
Thomas, you were correct. I disabled Cairo-dock and everything seems to scroll correctly now. Thank you... I wish I had known that a few versions ago. :) And yes, you are right in saying that it is probably the DE causing the problem... the KDE desktop -- because other desktops seem to have no problem working with KDE apps when cairo-dock is running. So will this remain as an open bug report? (Or is this a programming issue between QT and KDE that QT will not change?) And I may be wrong, but this may specifically only be an issue with legacy nVidia cards -- as others are using cairo-dock with KDE, seemingly without any problems. (In reply to comment #1) > Iirc there's some kind of conflict between Qt and one (or more) of the OSX > dockers (awn, cairo-dock, some other? - i frankly forgot) one's breaking the > X11 access of the other... > -> in caser that's not a plasma panel: disable the docker, logout and in to > ensure that's not it (but i actually guess it is) > > Esp. w/o compositing there's few chance that this is related to the WM at all > (did you really mean that it's related to the WM and not to the entire DE?)
(In reply to comment #2) > And yes, you are right in saying that it is probably the DE causing the > problem... the KDE desktop -- because other desktops seem to have no problem > working with KDE apps when cairo-dock is running. Yesno, sorry: that was "aside" the cairo dock issue. You could only try to bisect the offending applications (eg. konsole and plasma-dektop use ARGB windows just like the docker, this could cause it) -> open an xterm, call - killall konsole (ensure there's no important CLI process running in some konsole ;-), - kquitapp plasma-desktop - launch cairo dock & konqueror (or whatever) - see whether the issue remains - run "plasma-desktop", see again. to be on the safe side regarding the WM impact, you can eg. "usr/bin/compiz --loose-binding --replace --keep-desktop-hints ccp &" to run the above w/ and w/o kwin (it links plasma and i frankly don't knwo whether it uses ARGB windows for eg. the tabbox or so as well) The bug (if ARGB related) would however most likely be in Qt, Cairo, X11 or your driver, ie. upstream :-(
Okay, I did the testing you suggested and I still get the smeared scrolling without the plasma-desktop. (That rules out the plasma-desktop.) When I restarted plasma-desktop it seemed to give me errors, most of which I don't know what they are -- take a look and see if any are relevant to this problem: ---------------------------------- tim@kubuntu64:~/Documents$ plasma-desktop <unknown program name>(3363)/ kdemain: !!{} STARTUP TIME 55461240 START (line: 48 ) QDBusObjectPath: invalid path "" Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible plasma-desktop(3364)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "/home/tim/.kde/share/apps/RecentDocuments/snapshot1.png.desktop" not found plasma-desktop(3364)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "/home/tim/.kde/share/apps/RecentDocuments/[2].desktop" not found plasma-desktop(3364)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "/home/tim/.kde/share/apps/RecentDocuments/xorg.conf.desktop" not found plasma-desktop(3364)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "/home/tim/.kde/share/apps/RecentDocuments/statement.qfx.desktop" not found plasma-desktop(3364)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "/home/tim/.kde/share/apps/RecentDocuments/tim.desktop" not found plasma-desktop(3364)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "/home/tim/.kde/share/apps/RecentDocuments/TiddlySnip+1.21beta-cbr3.6.8.xpi.desktop" not found plasma-desktop(3364)/kdecore (services) KServiceFactory::findServiceByDesktopPath: "/home/tim/.kde/share/apps/RecentDocuments/kmymoney2-developer@lists.sourceforge.net.desktop" not found QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible Invalid D-BUS interface name 'org.kde.plasma-desktop.PlasmaApp' found while parsing introspection QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible QMetaObject::invokeMethod: No such method PlasmaApp::loadCommandLineOptionsForNewInstance() tim@kubuntu64:~/Documents$ QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible QWidget::setMinimumSize: (/Plasma::Dialog) Negative sizes (-1,-1) are not possible ---------------------------------- (In reply to comment #3) > (In reply to comment #2) > > And yes, you are right in saying that it is probably the DE causing the > > problem... the KDE desktop -- because other desktops seem to have no problem > > working with KDE apps when cairo-dock is running. > > Yesno, sorry: that was "aside" the cairo dock issue. > > You could only try to bisect the offending applications (eg. konsole and > plasma-dektop use ARGB windows just like the docker, this could cause it) > > -> open an xterm, call > - killall konsole (ensure there's no important CLI process running in some > konsole ;-), > - kquitapp plasma-desktop > - launch cairo dock & konqueror (or whatever) > - see whether the issue remains > - run "plasma-desktop", see again. >
(In reply to comment #3) > to be on the safe side regarding the WM impact, you can eg. "usr/bin/compiz > --loose-binding --replace --keep-desktop-hints ccp &" to run the above w/ and > w/o kwin (it links plasma and i frankly don't knwo whether it uses ARGB windows > for eg. the tabbox or so as well) > Sorry... I don't quite understand... should I install compiz as I currently don't have any trace of compiz on my computer?
the plasma output is harmless. you don't have to install compiz, but since you mentioned it wouldn't occur on other DEs and afaik only compiz & e17 can do GL compositing (being a requirement to trigger this clash between cairo-dock and Qt) i just was guessing you used compiz (since it's more common) So, what other DE did you try to trigger this conflict then (w/o issues) since if you were not (GL) compositing and therefore likely not running the docker (at least not in an ARGB mode), there'd be obviously no clash ... However, i just googled and it seems cairo-dock triggers ARGB windows bypassing Qt (and everything else), try (with running cairo-dock) launching an offended application like XLIB_SKIP_ARGB_VISUALS=1 konqueror since you'd ahve to add this for all applications you could also export it in ~/.xprofile and unset the variable for cairo dock and some applications that require it (like plasma-desktop) XLIB_SKIP_ARGB_VISUALS="" plasma-desktop ... or you try another docker ;-)
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
No response; assuming it was fixed since then.