From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70169] New: taskbar is white when using kwin GLES
Date: Sat, 05 Oct 2013 15:47:19 +0000 [thread overview]
Message-ID: <bug-70169-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3007 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=70169
Priority: medium
Bug ID: 70169
Assignee: dri-devel@lists.freedesktop.org
Summary: taskbar is white when using kwin GLES
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: ken20001@ukr.net
Hardware: x86-64 (AMD64)
Status: NEW
Version: 9.2
Component: Drivers/Gallium/r600
Product: Mesa
With the latest release of Mesa taskbar became white (not transparent) using
kwin GLES. With usual kwin it is transparent.
OS: Kubuntu 13.10 x86_64
Kernel: 3.12RC3
Graphics: Radeon HD 2600 XT
kwin_gles --replace &
[1] 2533
eugene@desktop:~$ QDBusConnection: session D-Bus connection created before
QCoreApplication. Application may misbehave.
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 14: reading
configurations from ~/.fonts.conf is deprecated.
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in
another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in
another thread
eugene@desktop:~$ OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV630
OpenGL version string: OpenGL ES 3.0 Mesa 9.2.0
OpenGL shading language version string: OpenGL ES GLSL ES 3.0
Driver: R600G
GPU class: R600
OpenGL version: 3.0
GLSL version: 3.0
Mesa version: 9.2
X server version: 1.14.3
Linux kernel version: 3.12
Direct rendering: yes
Requires strict binding: no
GLSL shaders: yes
Texture NPOT support: yes
Virtual Machine: no
kwin(2533) KWin::EglOnXBackend::init: Cannot enable v-sync as max. swap
interval is 0
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in
another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in
another thread
kwin(2533): Failed to compile fragment shader:
"0:2(14): error: no precision specified this scope for type `vec4'
0:4(13): error: no precision specified this scope for type `float'
0:5(13): error: no precision specified this scope for type `float'
0:6(13): error: no precision specified this scope for type `float'
0:7(13): error: no precision specified this scope for type `float'
0:8(13): error: no precision specified this scope for type `float'
0:9(13): error: no precision specified this scope for type `float'
0:10(13): error: no precision specified this scope for type `float'
0:14(7): error: no precision specified this scope for type `vec4'
kwin(2533): Failed to link shader:
"error: program lacks a fragment shader
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4332 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-10-05 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 15:47 bugzilla-daemon [this message]
2013-10-05 15:49 ` [Bug 70169] taskbar is white when using kwin GLES bugzilla-daemon
2013-10-07 19:24 ` bugzilla-daemon
2013-10-08 18:11 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-70169-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).