public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Uwe Thiem <uwix@iway.na>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE 4.0.2 and composite
Date: Wed, 12 Mar 2008 19:07:06 +0200	[thread overview]
Message-ID: <200803121907.06582.uwix@iway.na> (raw)
In-Reply-To: <20080312163406.20473674@zaphod.digimed.co.uk>

On Wednesday 12 March 2008, Neil Bothwick wrote:
> On Wed, 12 Mar 2008 18:15:45 +0200, Uwe Thiem wrote:
> > > Which version of the driver are you using? I have an IGP
> > > chipset and use x11-drivers/xf86-video-openchrome-0.2.901 from
> > > the Sabayon overlay.
> >
> > I tried 0.2.2 from portage and an svn checkout from
> > openchrome.org.
>
> I can't see openchrome in 
portage.http://www.tectonic.co.za/http://www.tectonic.co.za/

Go to x11-drivers/xf86-video-via. Look into the ebuilds. It actually 
is openchrome. At least I think it is.


> I'm not using composite, it's a MythTV frontend, but I am using all
> the accelerationy bits. It's a lot more stable than the svn build I
> used to use.

Uh-huh! Without actually using composite in KDE, it is working here as 
well. 

Anyway, I tried 0.2.901. No joy. I have had it for today. Have 
rebooted so often, I feel like using the other OS. ;-) Tomorrow I'll 
be too busy (have got the holy duty to feed myself).

I will probably give it another try coming weekend. Unmerge the whole 
of KDE 4.0.2 and re-emerge it again. Maybe, I missed one small bit 
when recompiling stuff, though I can't think of with one. Recompiled 
everything in KDE that has the USE flag xcomposite plus kdelibs, 
although they don't don't listen to xcomposite.

If I'll succeed somehow I'll report back here. If not, well, I'll give 
up on the whole thing, stay without the effects in KDE and wait for 
the Easter Bunny to provide me with a decent video card. ;-)

Uwe 

-- 
Informal Linux Group Namibia:
http://www.linux.org.na/
SysEx (Pty) Ltd.:
http://www.SysEx.com.na/
-- 
gentoo-user@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-12 17:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 18:58 [gentoo-user] KDE 4.0.2 and composite Uwe Thiem
2008-03-11 19:23 ` Gustavo Campos
2008-03-11 19:26 ` Alan McKinnon
2008-03-11 19:47   ` Uwe Thiem
2008-03-11 19:53     ` Michal 'vorner' Vaner
2008-03-11 20:04       ` Jesús Guerrero
2008-03-12  5:07       ` Uwe Thiem
2008-03-12  7:32         ` Alan McKinnon
2008-03-12  9:45           ` Gustavo Campos
2008-03-12 10:44           ` Uwe Thiem
2008-03-12 14:12             ` Alan McKinnon
2008-03-12 14:51               ` Uwe Thiem
2008-03-12 15:51                 ` Neil Bothwick
2008-03-12 16:15                   ` Uwe Thiem
2008-03-12 16:34                     ` Neil Bothwick
2008-03-12 17:07                       ` Uwe Thiem [this message]
2008-03-12 17:34                         ` Neil Bothwick
2008-03-12 18:14                           ` Uwe Thiem
2008-03-12 19:23                             ` Neil Bothwick
2008-03-12 15:58                 ` Alan McKinnon
2008-03-12 16:17                   ` Uwe Thiem
2008-03-11 19:56     ` Alan McKinnon
2008-03-11 19:43 ` Volker Armin Hemmann
2008-03-11 20:01   ` Alan McKinnon

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=200803121907.06582.uwix@iway.na \
    --to=uwix@iway.na \
    --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