Re: [Cooker] Am now experiencing random lockups...
On Sunday 09 Mar 2003 5:39 pm, N Smethurst wrote: > You say random lockups.. Ok, it may sound bizzare, but I was experiencing > pretty much exactly the same thing with RC1 after I had installed the 4191 > nvidia drivers and UT2003. Everything would freeze occasionally apart from > the mouse pointer. I started noting that the lock ups were happening > mainly when I was doing something in Konqueror (copying a file, renaming, > opening, etc.). Now I have installed RC2 but have yet to install the > nvidia drivers or UT2003 and I have not experienced any of the previous > problems. This may be complete coincidence, but.. I also experienced problems with random lockups when trying to use konqeuror and mozilla. In my case it turned out to be unrelated to the nvidia drivers (it was a problem with my modem), but I read that it can be caused by agp problems at high agp settings. The solution offered was to turn agp down to a lower setting (e.g. 2 instead of 4 or 8). Instructions on how to do this are inside the README file for the nvidia drivers. Why it affects web browsers more than anything else, I don't know. Hope this is of help! Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
Re: [Cooker] KDevelop and Autoconf 2.5x
On Tuesday 10 Dec 2002 4:24 am, Mario Vazquez wrote: > And KDevelop works with autoconf 2.54 with that? And I should add to my previous post, I have only tried it with KDE development files, not with Gnome, terminal, etc... Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
Re: [Cooker] KDevelop and Autoconf 2.5x
On Tuesday 10 Dec 2002 4:24 am, Mario Vazquez wrote: > And KDevelop works with autoconf 2.54 with that? I can only it say that it works for me :-), and It works with whatever autoconf2.5x is in cooker (which I think is 2.54) The main problem is that any old kdevelop projects need to have their admin directory updated - otherwise they will stop compiling with autoconf2.5 installed. But this problem is going to exist whether KDevelop is installed or not - the problem is with the admin/ directory, not with KDevelop as such. (The admin directory contains lots of files which generate the build system for a KDE application - it's all the stuff that runs when you type : make -f Makefile.common ) Cheers Jason > > > From: Jason Wood <[EMAIL PROTECTED]> > > >Reply-To: [EMAIL PROTECTED] > >To: [EMAIL PROTECTED] > >Subject: [Cooker] KDevelop and Autoconf 2.5x > >Date: Tue, 10 Dec 2002 03:19:58 + > > > >Hi, > > > >I have recently had to "rpm -i --nodeps autoconf 2.5x" in order to get it > >installed to play nicely with my KDevelop generated project. > > > >I need autoconf 2.5 because I updated the admin/ directory generated by > >KDevelop to be the same as that in KDE CVS (in the kde-common folder). The > >latest version drops support for autoconf 2.13 > > > >I'm not sure if this is of use to anyone else, but I'm sure I can't be the > >only person who finds the fact that I can't install Kdevelop and > >autoconf2.5 > >at the same time damn annoying :-) so here goes : > > > >1. Grab a recent copy of the admin directory from the kde-common modules > > in KDE cvs > >2. tar.gz it. > >3. copy it to /usr/shar/apps/kdevelop/templates/admin.tar.gz > > > >Newly generated kdevelop projects will now work with autoconf 2.5 (but not > >with autoconf 2.13, but it's ok to have both installed at the same time) > > > >4. To "fix" old kdevelop projects, simply remove the admin directory that > >was > >created by KDevelop and replace it with the same one you copied into the > >kdevelop/templates folder. > > > >I'm not sure if this is of help to packagers :-) I haven't tested this > >beyond > >creating a sample project and checking that it builds and runs correctly, > >and > >I think that step 4 may be a reason not to update the kdevelop package, > > but since you cannot currently install any new KDE software from source > > if you also happen to have KDevelop on your computer, I think that there > > is a case for as well :-) > > > >Cheers, > >Jason > > > >-- > >Jason Wood > >Homepage : www.uchian.pwp.blueyonder.co.uk > > _ > MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. > http://join.msn.com/?page=features/virus -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
[Cooker] KDevelop and Autoconf 2.5x
Hi, I have recently had to "rpm -i --nodeps autoconf 2.5x" in order to get it installed to play nicely with my KDevelop generated project. I need autoconf 2.5 because I updated the admin/ directory generated by KDevelop to be the same as that in KDE CVS (in the kde-common folder). The latest version drops support for autoconf 2.13 I'm not sure if this is of use to anyone else, but I'm sure I can't be the only person who finds the fact that I can't install Kdevelop and autoconf2.5 at the same time damn annoying :-) so here goes : 1. Grab a recent copy of the admin directory from the kde-common modules in KDE cvs 2. tar.gz it. 3. copy it to /usr/shar/apps/kdevelop/templates/admin.tar.gz Newly generated kdevelop projects will now work with autoconf 2.5 (but not with autoconf 2.13, but it's ok to have both installed at the same time) 4. To "fix" old kdevelop projects, simply remove the admin directory that was created by KDevelop and replace it with the same one you copied into the kdevelop/templates folder. I'm not sure if this is of help to packagers :-) I haven't tested this beyond creating a sample project and checking that it builds and runs correctly, and I think that step 4 may be a reason not to update the kdevelop package, but since you cannot currently install any new KDE software from source if you also happen to have KDevelop on your computer, I think that there is a case for as well :-) Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
Re: [Cooker] Ogg vorbis in 9.0 vs. 8.2
On Tuesday 20 Aug 2002 7:35 pm, Jason Wood wrote: > However, I haven't brought > them up to date for a few weeks though, so I will try and let you know how > I get on. Ok, all problems are fixed in the latest rpms. Apologies if my last post was a bit sharp, I just don't like being accused of things I haven't done :-) Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
Re: [Cooker] Ogg vorbis in 9.0 vs. 8.2
On Tuesday 20 Aug 2002 4:27 pm, Guillaume Cottenceau wrote: > You, just like the other people, upgraded your packages with a > "--nodeps" or equivalent to achieve such a results. No surprise > it doesn't work well anymore. Nice conjecture, but I _never_ use nodeps or force, so if the dependencies were broken it was within the rpm's of the time. However, I haven't brought them up to date for a few weeks though, so I will try and let you know how I get on. On a related note, upgrading just kdebase/libs last night via urpmi decided that I didn't require the latest libqt to go with it, breaking kdm & kde until I installed it manually Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
Re: [Cooker] Ogg vorbis in 9.0 vs. 8.2
On Friday 09 Aug 2002 7:35 pm, Brook Humphrey wrote: > Well I didn'try encodeing but xmms plays mp3 just fine ogg doesn't play. So > playback is broke. When I start xmms from the shell, I get this error message : /usr/lib/libvorbisfile.so.3: undefined symbol: vorbis_synthesis_trackonly which I assume is a likely candidate for why ogg support isn't working at the moment. cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
Re: [Cooker] Mesa screw up
On Thursday 27 Jun 2002 4:13 pm, François Pons wrote: > Jeremy Salch <[EMAIL PROTECTED]> writes: > > Last night i updated to the most recent Mesa in Cooker and kde will not > > load at all.. I removed it and downgraded to the one in 8.2 and it > > started working again > > I don't see anything wrong in Mesa package, everything seems to work, it > looks like a build release problem (you have an old kde or compiled with > too old gcc ?). > > François. I discovered and fixed the problem on my computer. The problem stems from all kde programs trying to open the libGL - you get the followeing line when running a kde program from the comman line : Loading required GL library /usr/X11R6/lib/libGL.so.1.2.350 The recent upgrade of Mesa seems to have removed this file, totally breaking kde. I fixed this by adding a simlink to libGL.so.1.2, which seems to work. Cheers, Jason -- Jason Wood I don't give up, I lose interest Homepage : www.uchian.pwp.blueyonder.co.uk