Re: Fresh F8 to F9 upgrade - can't start KDE - "Call to lnusertmp failed..."

On Wednesday 25 June 2008 10:58:48 Rex Dieter wrote:
> You need to start from a desktopmanager with ConsoleKit support, so
> doing anything else is not recommended.


Why is this required? I am running KDE SVN on F9. The only patch I have 
needed to apply is the one to make $KDEDIR/share/applications/kde4 appear 
before the system ones. Are the other patches in the KDE srpms required? I 
have noticed some significant slowdown in KDE apps overall, but have so fat 
attributed that to compiling in debug mode.


I am experiencing a memory leak with Xorg when desktop effects are enabled 
(both on kde-redhat packages and on self-compiled KDE SVN). Xorgs leaks 
memory on every transition effect when switching desktops (among other leaky 
locations). This is related to the following bugs, I think:
  http://bugs.freedesktop.org/show_bug.cgi?id=16316
  https://bugzilla.redhat.com/show_bug.cgi?id=443239
Other than this pretty nasty issue, I haven't needed any patches for 
anything. FWIW, I am on an x86_64 machine with the latest ati drivers, 
pixman, libdrm and mesa from koji while using a Radeon X1650 with the radeon 
driver.


If anyone can show me how to get a valgrind log when running X as a regular 
user, I could provide valgrind logs, etc. for the bugs above. (Valgrind 
won't let me run setuid apps under its control.)


Regards,
Ravi

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php