I did use the -f flag and that is what caused the problem I think (Mind you I'm using the latest beta of kde). The file conflicts seemed trivial - as previously mentioned it seemed to baulk at existing graphics images in the kde tree. Obviously something else has changed in the systems ability to find basic pathways, because in .xinitrc it no longer can do the 'exec startkde', but it can do 'exec /opt/kde/bin/startkde'
Does this ring a bell with anyone - maybe its something to do with my personal kde configuration files. Regards Richard On Fri, 25 Feb 2005 08:59 am, Aaron Griffin wrote: > On Fri, 25 Feb 2005 08:03:15 +1100, Richard Terry <[EMAIL PROTECTED]> wrote: > > Working again including nvidia with the temporary fix I posted earlier. > > > > However there is still some underlying problem in the system which I > > don't have time to fix. But it raises a problem I've noted before in ARCH > > upgrades, that sometimes the upgrade will crash when a file exists in the > > filesystem that it decides not to overwrite. I would have thought there > > should be some mechanism in the package to detect that and simply make a > > backup file, and alert the user to the fact. > > > > Regards > > > > Richard > > You can use the -f flag to force overwrites... however there shouldn't > be any file conflicts... what was the conflict? > > _______________________________________________ > arch mailing list > [email protected] > http://www.archlinux.org/mailman/listinfo/arch _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
