Bug 326843 - Visual desktop glitches with live usb
Summary: Visual desktop glitches with live usb
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 4.11.2
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: KWin default assignee
URL: https://dl.dropboxusercontent.com/u/1...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-29 18:06 UTC by Vasilis Toumpakaris
Modified: 2014-09-06 21:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
thomas.luebking: Gallium3D+
thomas.luebking: nouveau+


Attachments
glxinfo (43.42 KB, text/plain)
2013-10-30 21:34 UTC, Vasilis Toumpakaris
Details
KWin supportInformation on fedora 20 (4.48 KB, text/plain)
2013-11-14 23:51 UTC, Vasilis Toumpakaris
Details
KWin Support Information on fedora 20 (2) (5.11 KB, text/plain)
2013-11-14 23:59 UTC, Vasilis Toumpakaris
Details
Kubuntu 14.10 beta 1 32bit (506.60 KB, image/png)
2014-08-30 18:22 UTC, Vasilis Toumpakaris
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Vasilis Toumpakaris 2013-10-29 18:06:49 UTC
These are my pc's specifications:
Intel Core2 CPU  6300 1.86GHz || RAM 2001 MiB || ASUS INC. P5B-VM
nVidia G73 [GeForce 7300 GT] [10de:0393] {nvidia}

I had a similar problem with gnome too which is partialy fixed. 
https://bugzilla.gnome.org/show_bug.cgi?id=709036

Reproducible: Always
Comment 1 Christoph Feck 2013-10-29 19:39:22 UTC
Could you describe the glitches you see? Does it happen with compositing disabled or using only XRender compositing type? Also, please add output of this command:

qdbus org.kde.kwin /KWin supportInformation
Comment 2 Christoph Feck 2013-10-29 19:43:13 UTC
Oh, there is a video linked, that pretty much describes the issues, still the technical information requested in comment #1 are needed.
Comment 3 Vasilis Toumpakaris 2013-10-29 20:55:50 UTC
I think this command Is not correct. OS does not accept it. 

qdbus: could not find a Qt installation of ''

I have also add that I tested opensuse 13.1 whith the same issue and now I'm downloading Mageia cauldron. It's weird but when I tested kubuntu 13.10 when was in beta state it hasn't this issue.
Comment 4 Thomas Lübking 2013-10-29 21:05:40 UTC
(In reply to comment #3)
> I think this command Is not correct.
Command is perfect, OS is broken ("incomplete")

See whether you got "qdbus-qt4" and otherwise install the package that contains qdbus on ubuntu (That *should* be qt or qt4)

For the beginning at least provide the ouput of "glxinfo" and then run "kcmshell4 kwincompositing" and try setting the compositor backend to xrender.
Comment 5 Vasilis Toumpakaris 2013-10-30 21:34:56 UTC
Created attachment 83235 [details]
glxinfo
Comment 6 Vasilis Toumpakaris 2013-10-30 21:41:58 UTC
Xrender compisitor backend does the trick. Also, I tried Mageia 4 alpha 3... There was no issue.
I installed "qdbus-qt5" and "mesa utils" for glxinfo.
Comment 7 Vasilis Toumpakaris 2013-10-30 21:57:21 UTC
Kubuntu is with nouveau preinstalled but mageia was with nvidia driver preinstalled.
Comment 8 Thomas Lübking 2013-10-30 22:04:24 UTC
> OpenGL vendor string: nouveau
> OpenGL renderer string: Gallium 0.4 on NV4B
> OpenGL version string: 2.1 Mesa 9.2.1
> OpenGL shading language version string: 1.20

You might want to try the nvidia blob (304.xxx should still support your GPU) or (if possible) updating to MESA 9.2.2

If you've now "qdbus" available, please still provide the supportInformation (with troublesome GL compositing)

--
Most likely driver bug, eventually running into GLX_ARB_create_context troubles with MESA
Comment 9 Vasilis Toumpakaris 2013-10-30 22:10:38 UTC
I have qdbus but it says the same error I wrote in comment #3. Can I do something for it?
Comment 10 Thomas Lübking 2013-10-30 22:18:33 UTC
Seems to be a Ubuntu thing:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1177823

Comment #5 there has a promising workaround and the other solutions are to install qt[45]-default qttools[45]-dev-tools # [45] likely meaning 4 OR 5
Comment 11 Martin Flöser 2013-11-12 05:56:33 UTC
setting to upstream - not much we can do as it's a live CD.
Comment 12 Vasilis Toumpakaris 2013-11-12 19:50:56 UTC
I am so sorry, system didn't let me install those packages and a gave up. It was difficult to navigate the ui this way. Opensuse 13.1 continues to have this bug. Can I install kubuntu without this bug if it is resolved downstream? What "setting to upstream" means? Thanks in advance.
Comment 13 Thomas Lübking 2013-11-12 20:10:25 UTC
You can install about any distro as long as it provides your the nvidia binary blob and be pretty sure to not encounter this issue (by using the nvidia driver instead of the nouveau one)

"resolved upstream" is twisted - Martin marked the bug downstream ("distro") because the live system bundles a trouble making driver.

The issue about  missing qdbus installation is completely orthogonal to this - you just got to install the package that ships the binary. Distro hopping won't help you the least on this.
Comment 14 Vasilis Toumpakaris 2013-11-14 23:48:54 UTC
kdelibs (4.11.3) in fedora 20 and openGL 3.1 compositing type solves the issue on nouveau.
Comment 15 Vasilis Toumpakaris 2013-11-14 23:51:30 UTC
Created attachment 83574 [details]
KWin supportInformation on fedora 20
Comment 16 Vasilis Toumpakaris 2013-11-14 23:55:55 UTC
(In reply to comment #14)
> kdelibs (4.11.3) in fedora 20 and openGL 3.1 compositing type solves the
> issue on nouveau.

It's not true. :(
Comment 17 Vasilis Toumpakaris 2013-11-14 23:59:57 UTC
Created attachment 83575 [details]
KWin Support Information on fedora 20 (2)

This is with opengl enabled.
Comment 18 Vasilis Toumpakaris 2014-08-30 18:22:17 UTC
Created attachment 88501 [details]
Kubuntu 14.10 beta 1 32bit
Comment 19 Thomas Lübking 2014-08-30 18:30:31 UTC
Since the chip/driver according to the glxinfo you posted doesn't support the OpengGL Core profile anyway, i'd simply try to avoid it.
Ie., set compositing to OGL 2.0 and (from other bugreports about incapable HW) then rather reboot and see what happens.
Comment 20 Vasilis Toumpakaris 2014-09-06 21:39:15 UTC
Oh, I see.It seems GPU just showed it's age.