Bug 517731 - Lancelot has unrequired black border
Summary: Lancelot has unrequired black border
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kdeplasma-addons
Version: 11
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: kde-4.3.0
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-16 12:59 UTC by Anne
Modified: 2009-08-25 11:55 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-08-25 06:46:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Anne 2009-08-16 12:59:58 UTC
Description of problem:
Black border surrounds Lancelot menu - not intended by the developer

Version-Release number of selected component (if applicable):


How reproducible:
Constant

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

http://ivan.fomentgroup.org/blog/2009/08/16/black-border-around-lancelot/

Developer remarks:
While compiling Lancelot, you should
ensure the presence of libXcomposite,
libXrender and libXdamage development files.

requesting that users should alert distros by filing a bug report

Comment 1 Rex Dieter 2009-08-17 12:46:10 UTC
We did build it with the requisite libs, last I checked.

rpm -q kdeplasma-addons please.

Comment 2 Rex Dieter 2009-08-17 12:49:13 UTC
confirmed added as of

* Thu Jul 16 2009 Rex Dieter <rdieter> - 4.2.96-2
- BR: libXcomposite-devel (lancelot eye-candy)

included in builds currently in updates-testing.

Comment 3 Lukáš Tinkl 2009-08-17 13:02:55 UTC
As per http://websvn.kde.org/?view=rev&revision=1012081, the only needed extension is XRender.

Comment 4 Anne 2009-08-17 15:24:18 UTC
rpm -q kdeplasma-addons please.
kdeplasma-addons-4.3.0-0.4.fc11.i586

My lancelot menu closely matches the example posted by the developer at http://imagebin.ca/view/h1oGpJ.html

Comment 5 Rex Dieter 2009-08-17 16:25:15 UTC
The aforementioned blog mentioned the bad-looking when compositing (aka desktop effects) are *off*.  Ie, if effects aren't enabled, you'll see that, regardless of whether it was built with libXcomposite or not.

Comment 6 Lukáš Tinkl 2009-08-17 16:49:10 UTC
Ye because it misses (missed) the XRender extension (not XComposite) :)

Comment 7 Rex Dieter 2009-08-17 17:06:50 UTC
it = what here?  the pkg?  X extension?

Fwiw, the what's used in cvs currently is:
BuildRequires: libXcomposite-devel libXrender-devel libXdamage-devel

though it appears clear now that those != libXrender-devel aren't really needed afterall.

Comment 8 Anne 2009-08-17 17:37:30 UTC
Ah - I missed the significance of that.  Desktop effects are off by default on this laptop.  I can confirm that when I enable them the black border disappears.  Guess this warrants NOTABUG :-)  Sorry for the noise

Comment 9 Jaroslav Reznik 2009-08-18 07:59:49 UTC
Actually it's an upstream bug, they should ship opaque theme for Lancelot as it's stated in comments in the blog post. It should be reported upstream as they don't care about desktops with composite off. And unfortunatelly gfx drivers are not ready to ship KDE with composite on :(

Comment 10 Kevin Kofler 2009-08-25 06:46:19 UTC
This issue should be resolved in Fedora 10 and 11 with the KDE 4.3.0 update, which just got pushed to stable. If the issue persists after upgrading to KDE 4.3.0, please report that fact in this bug report.

Comment 11 Anne 2009-08-25 11:55:36 UTC
Still on the same laptop, where desktop effect on are unacceptably slow - I am fully updated and running 4.3.  The issue remains.  With compositing on both the border disappears and the Black-on-Black menu (https://bugs.kde.org/show_bug.cgi?id=204641) disappear.  With compositing off both are present.  This appears to be a problem with some but not all themes.  My preferred theme is Oxyglass.  The default themes shipped with KDE do not have the problem.  Some third-party ones do, and some don't, so it's just a case of experimenting.


Note You need to log in before you can comment on or make changes to this bug.