public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: trying KDE (again)
Date: Tue, 14 Feb 2006 15:49:19 -0600	[thread overview]
Message-ID: <200602141549.19456.bss03@volumehost.com> (raw)
In-Reply-To: <1139926292.16084.4.camel@orpheus>

On Tuesday 14 February 2006 08:11, Iain Buchanan <iaindb@netspace.net.au> 
wrote about 'Re: [gentoo-user] Re: trying KDE (again)':
> aha, thank you for that great explanation.  However, I have edited
> xorg.conf as required with
>
> Section "Extensions"
>    Option "Composite" "Enable"
> EndSection
>
> and
>
> Option "RenderAccel" "true"
> Option "AllowGLXWithComposite" "true"
>
> (I have an ati) but I still get the control centre message about
> translucency not available...  (of course, I restarted X :)  Also, is
> there supposed to be a command called kompmgr? I can't locate it.

Yeah, kompmgr is the KDE-ized version of xcompmgr.  You may have to set a 
USE flag to get it installed.  Are you using the monolithic ebuild (kde), 
metapackage (kde-meta), or some other set of packages?

I'm using the metapackage and I get kompmgr like so:
# equery b $(which kompmgr)
[ Searching for file(s) /usr/kde/3.5/bin/kompmgr in *... ]
kde-base/kwin-3.5.1 (/usr/kde/3.5/bin/kompmgr)
# emerge -pv '=kde-base/kwin-3.5.1'

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] kde-base/kwin-3.5.1  USE="arts kdeenablefinal xcomposite 
xinerama -debug" 0 kB

Total size of downloads: 0 kB

I bet 'xcomposite' is the critical USE flag.

Also, I would suggest your turn on the backing store.  It's another 
modification to xorg.conf, but it should pay off with less CPU usage.  The 
gentoo wiki should provide instructions on exactly how to modify your 
xorg.conf.

-- 
Boyd Stephen Smith Jr.
bss03@volumehost.com
ICQ: 514984 YM/AIM: DaTwinkDaddy
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-02-14 21:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 23:35 [gentoo-user] trying KDE (again) Iain Buchanan
2006-02-13 23:54 ` Hemmann, Volker Armin
2006-02-14  5:34   ` Iain Buchanan
2006-02-14  6:40     ` [gentoo-user] " Harm Geerts
2006-02-14  7:12       ` Iain Buchanan
2006-02-14  9:41         ` Boyd Stephen Smith Jr.
2006-02-14 13:26           ` Ernie Schroder
2006-02-14 19:05             ` Roy Wright
2006-02-14 21:57             ` Boyd Stephen Smith Jr.
2006-02-14 14:11           ` Iain Buchanan
2006-02-14 21:49             ` Boyd Stephen Smith Jr. [this message]
2006-02-14 22:09             ` Richard Fish
2006-02-15  0:06               ` Zac Slade
2006-02-15 12:44                 ` Iain Buchanan
2006-02-15 14:56                   ` Zac Slade
2006-02-15 15:11                   ` Richard Fish
2006-02-14 12:33         ` Uwe Thiem
2006-02-14 15:06     ` [gentoo-user] " Hemmann, Volker Armin
2006-02-14 23:35       ` Iain Buchanan
2006-02-14 18:00     ` Paul Varner
2006-02-14 16:08 ` Richard Fish
2006-02-14 23:44   ` Iain Buchanan
2006-02-20 23:48     ` [gentoo-user] trying KDE (konsole placement) Iain Buchanan
2006-02-21  0:11       ` Martins Steinbergs
2006-02-21  0:24         ` Iain Buchanan
2006-02-21  1:13       ` Peter Ruskin

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=200602141549.19456.bss03@volumehost.com \
    --to=bss03@volumehost.com \
    --cc=gentoo-user@lists.gentoo.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