[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-linux
Subject:    RE: [kde-linux] "setting up interprocess communication" freeze
From:       Luke Q Campagnola <lcampagn () Mines ! EDU>
Date:       2005-03-22 22:07:35
Message-ID: Pine.A41.4.58.0503221505540.183932 () slate ! Mines ! EDU
[Download RAW message or body]

Found a workaround on nVidia's forum, seems to work for me:

  Option "RenderAccel" "false"




On Tue, 22 Mar 2005, Daevid Vincent wrote:

> So Jani was right. I unmerged my 1.0.7167 drivers and installed the previous
> 6629 drivers. Changed NOTHING else. And now KDE 3.4 works as expected. So I
> just don't get it. Why the hell does KDE care what video card I'm using or
> driver? Gnome, XFCE, and twm all worked just fine with Xorg and the new
> drivers. LAME! This seems that KDE should be talking to X which talks to
> nvidia driver. Isn't that the whole point of the API?
>
> > -----Original Message-----
> > From: Daevid Vincent [mailto:daevid@daevid.com]
> > Sent: Tuesday, March 22, 2005 1:01 PM
> > To: kde-linux@kde.org
> > Cc: 'Jani "Grönberg"'
> > Subject: [kde-linux] "setting up interprocess communication"
> > freeze withnvidia drivers?
> >
> > Interesting. I am running the 1.0.7167-r1 nvidia driver but
> > my kernel is the
> > same as it was for the other KDE versions that did work
> > 2.6.10-gentoo-r6.
> >
> > So is anyone out there running this version of nvidia driver with KDE?
> >
> > And can someone tell me how to install the previous version
> > 1.0.6629 of the
> > nvidia driver to test to see if this hypothesis is correct
> > (namely that
> > nvidia fcsked me).
> >
> > > -----Original Message-----
> > > From: Jani "Grönberg" [mailto:jag@oneccuva.org]
> > > Sent: Tuesday, March 22, 2005 12:22 PM
> > > To: daevid@daevid.com
> > > Subject: Fwd: Re: KDE 3.3.2 "setting up interprocess
> > > communication" freeze
> > >
> > > Apparently I cannot post through the gmane gateway but I
> > find it more
> > > convenient than subscribing. If you still have the problem perhaps
> > > this message is of some help. If you need further
> > assistance just mail
> > > me back, but be aware that I'm leaving for a vacation and will not
> > > read mail for at least a week.
> > >
> > "Daevid Vincent" <daevid@daevid.com> writes:
> >
> > > Now I'm really getting annoyed. I tarballed my .kde* dirs
> > and so KDE fires
> > > up to the point of the initial asking my keyboard and how
> > many effects I
> > > want and stuff. Then locks up at the same damn spot. UGH!
> > How am I the
> > ONLY
> > > person to experience this in all of Gentoo/KDE users out there?
> > >
> > [I already sent a reply to this via news.gmane.org, but it hasn't
> > appeared in the group. This will also probably go to recycle bin, but
> > on the off chance that they are held up by human moderator]:
> >
> > I experienced exactly the same symptoms after upgrading to 2.6.11.2
> > kernel and, since it doesn't build with older version, to non-stable
> > nvidia drivers (1.0.7167-r1). The fault appears to be with these
> > drivers.
> >
> > I tried with my older stable kernel (2.6.10-gentoo-r6) and new drivers
> > -> same lockup. However, 2.6.10-gentoo-r6 + stable nvidia drivers
> > (1.0.6629-r1) work just fine (like they used to).
> >
> > //jani
> >
> > --
> > A
> >
> > ___________________________________________________
> > This message is from the kde-linux mailing list.
> > Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
> > Archives: http://lists.kde.org/.
> > More info: http://www.kde.org/faq.html.
> >
>
> ___________________________________________________
> This message is from the kde-linux mailing list.
> Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
> Archives: http://lists.kde.org/.
> More info: http://www.kde.org/faq.html.
>
___________________________________________________
This message is from the kde-linux mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde-linux.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.

[prev in list] [next in list] [prev in thread] [next in thread]