no-way man! My install works great (so far). I did have one problem, but
I was installing on top of the old. I deleted the .kde directories, and
all the kde-related directories in /usr/share, and all the /tmp files
related to kde, then followed the instructions "DO_NOT_READ_THIS" and it
worked
On Monday 05 February 2001 02:46, Christopher Molnar wrote:
>
> In retrospect I should never have asked for and encouraged the unsupported
> directory, as I think it is causing more problems than it is worth.
>
Please don't get discouraged. I really appreciate the unsupported RPMs and
feel tha
See my nexty message. I think your problem is in QTDIR not being set.
It's needed to compile kde apps. Did you keep your old home dir, or totally
reformat your system? Anyways, see if this helps.
-Chris
On Sunday 04 February 2001 12:51, Christopher Molnar wrote:
> First, appologies to al, because I am leaving the origional message and
> just putting my comments into it. Praedor, please look for my notes all
> the way to the bottom. I just thought of something.
[...]
> > As for my system. It is
First, appologies to al, because I am leaving the origional message and just
putting my comments into it. Praedor, please look for my notes all the way
to the bottom. I just thought of something.
On Sunday 04 February 2001 13:39, you wrote:
> I will (somewhat) apologize for my previous tone an
quot;
"Sharing is what makes them powerful."
On Sun, 4 Feb 2001, Christopher Molnar wrote:
> Date: Sun, 4 Feb 2001 11:46:18 -0500
> From: Christopher Molnar <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] kcon
I will (somewhat) apologize for my previous tone and chalk it up to a set of
bad days above and beyond kcontrol problems. From here:
On Sunday 04 February 2001 09:46, Christopher Molnar wrote:
> #1 - the unsupported are not built with cooker. I am starting to suspect
> this is the problem with
On Sunday 04 February 2001 08:46, Christopher Molnar wrote:
> You mention attitude and tone. I am not paid to make these RPM's, I am not
> paid to consistantly fix peoples broken systems. I think you would probably
> get a little tired of 100 emails saying that I caused their systems to die
> afte
> I do not advise going to the new glibc, I differ in the opinion of my
> employers with this (ok, I am now going to get shot) I think that the
> developers of gcc have a reason for advising us not to use the latest
Please convince your employers that you are right (grin). I like
Mandrake but t
#1 - the unsupported are not built with cooker. I am starting to suspect this
is the problem with a lot of the problems. They are also not built for cooker.
#2 - people do not follow directions. Every person who has followed the
directions step by step, not tried to rebuild part of the systems,
"They" full well know what unsupported means. It is OFFICIALLY not
supported. Why? Is it because there is any REAL difference between the
SUPPORTED version (in OFFICIAL cooker) and the "unsupported" versions for
7.2? NO. No difference. The only real difference is the former is built
from
rful."
On Sat, 3 Feb 2001, Christopher Molnar wrote:
> Date: Sat, 3 Feb 2001 21:04:08 -0500
> From: Christopher Molnar <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] kcontrol STILL doesn't function
>
> On Frida
Please post the output of the following commands - do not send to me direct
as others can probably help as well:
rpm -qa|grep kde
rpm -qa|grep koffice
rpm -qa|grep xinitrc
rpm -qa|grep qt
Also an ls -l of all the rpm's you downloaded to isntall.
Read on
On Friday 02 February 2001 15:59,
On Friday 02 February 2001 14:59, you wrote:
> Maybe you don't need to do a clean install. Maybe only KDE, CUPS, xinitrc,
> egcs, ghostscript, arts, jkd, etc. need to be updated. If you know what
> you're doing, then go for it. But to blame Mandrake because your patchwork
> upgrade breaks a beta
On Saturday 03 February 2001 09:57 am, you wrote:
> You have reinstalled kde2.1 on a clean install of 7.2? OK, try this:
>
> Delete your .kderc, do an rm -rf on your $HOME/.kde directory, and then
> delete everything in your $HOME/tmp AND as root delete everything in the
> system /tmp directory.
On Saturday 03 February 2001 03:11 am, you wrote:
> Maybe I had to explain to you in details what is going on when you
> change your Mandrake menus with
> menudrake (read: application links). X-KDE-BaseGroup is nothing but a
> KDE directory in your application links.
> In Mandrake menu this direct
You have reinstalled kde2.1 on a clean install of 7.2? OK, try this:
Delete your .kderc, do an rm -rf on your $HOME/.kde directory, and then
delete everything in your $HOME/tmp AND as root delete everything in the
system /tmp directory.
Reboot (actually rebooting may be overkill but be radic
Thank you. The thing is, however, that I did do anything with menudrake.
Kcontrol was working with (I can't recall precisely) kde 2.1-20010115 but
upon upgrading to kde 2.1-20010118 and then again to 2.1-20010122, kcontrol
didn't work. The only thing changing was the version of kde 2.1.
T
Maybe I had to explain to you in details what is going on when you
change your Mandrake menus with
menudrake (read: application links). X-KDE-BaseGroup is nothing but a
KDE directory in your application links.
In Mandrake menu this directory is subdirectory of Configuration
directory. That's
On Friday 02 February 2001 01:59 pm, you wrote:
> Thank you. BUT saying it 100 times wouldn't fix this. Someone wrote me to
> suggest running kbuildsycoca...as root and as user. I did. The result was
> that root AND user no longer had a functioning kcontrol. Neither had
> kcontrol so I cannot
Thank you. BUT saying it 100 times wouldn't fix this. Someone wrote me to
suggest running kbuildsycoca...as root and as user. I did. The result was
that root AND user no longer had a functioning kcontrol. Neither had
kcontrol so I cannot compare /root/.kde/share/applnk or app/ with any use
On Friday 02 February 2001 08:33, you wrote:
> It is not an option to do a total reinstall...and if that is how Mandrake
> is supposed to work, it is going to LOSE people instead of gain them. One
> should not have to totally reinstall the distro just to upgrade one part of
> it that isn't even
On Friday 02 February 2001 19:29, you wrote:
I really do not know how many time I have to tell you that your problem is in
applnk. If you have Kcontrol as root with all entries listed in kcontrol and
do not have the same as user that means that you messed up with application
links.
1. Check
On Friday 02 February 2001 10:27, you wrote:
> On Friday 02 February 2001 17:33, you wrote:
> > Kcontrol is STILL broken after running kbuildsycoca as root and as user.
> > KDE 2.1 hasn't had it right since its inception.
> >
> > It is not an option to do a total reinstall...
>
> No it is not. Jus
-
> From: Zeljko Vukman [mailto:[EMAIL PROTECTED]]
> Sent: Friday, February 02, 2001 12:28 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] kcontrol STILL doesn't function
>
> On Friday 02 February 2001 17:33, you wrote:
> > Kcontrol is STILL broken after running kbu
]]
Sent: Friday, February 02, 2001 12:28 PM
To: [EMAIL PROTECTED]
Subject: Re: [expert] kcontrol STILL doesn't function
On Friday 02 February 2001 17:33, you wrote:
> Kcontrol is STILL broken after running kbuildsycoca as root and as user.
> KDE 2.1 hasn't had it right since its ince
On Friday 02 February 2001 17:33, you wrote:
> Kcontrol is STILL broken after running kbuildsycoca as root and as user.
> KDE 2.1 hasn't had it right since its inception.
>
> It is not an option to do a total reinstall...
No it is not. Just reinstall KDE.
>and if that is how Mandrake
> is suppo
ore
>
> -Original Message-
> From: Tom Brinkman [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 30, 2001 9:22 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] kcontrol STILL doesn't function
>
>
> "Blank Control Center" (kcontrol)
>
Have you considered doing a clean install of 7.2 and then just going straight
to the KDE2.1 Beta 2? (That's what I did and I've have almost no problems.
It's the most stable KDE2 that I've used yet.) It could be that moving from
one update to another is causing the instability.
M.
On Thursday
What switches should be run with kbuildsycoca? I ran kbuildsycoca by itself
but this didn't fix anything. I still have a useless kcontrol.
On Thursday 01 February 2001 06:34, you wrote:
> Here is an excerpt from another message on the KDE mailing list.
> I too had the empty control center, but
EMAIL PROTECTED]]
Sent: Monday, January 29, 2001 8:43 PM
To: [EMAIL PROTECTED]
Subject: Re: [expert] kcontrol STILL doesn't function
On Monday 29 January 2001 11:54 am, you wrote:
> I just installed the latest KDE2.1 beta for 7.2. All now seems OK (after
I
> again deleted my .kde/
EMAIL PROTECTED]]
Sent: Tuesday, January 30, 2001 9:22 AM
To: [EMAIL PROTECTED]
Subject: Re: [expert] kcontrol STILL doesn't function
"Blank Control Center" (kcontrol)
FWIW, (as user) first thing I did after updating to KDE2b2 was to
make sure everything was working (it was
-Original Message-
From: Kelley Terry [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 29, 2001 8:43 PM
To: [EMAIL PROTECTED]
Subject: Re: [expert] kcontrol STILL doesn't function
On Monday 29 January 2001 11:54 am, you wrote:
> I just installed the latest KDE2.1 beta for 7
"Blank Control Center" (kcontrol)
FWIW, (as user) first thing I did after updating to KDE2b2 was to
make sure everything was working (it was). Then I installed a few apps I
use and made the menu entries using menudrake. Then as has been my habit
with the early updates I made a backup
On Monday 29 January 2001 11:54 am, you wrote:
> I just installed the latest KDE2.1 beta for 7.2. All now seems OK (after I
> again deleted my .kde/ directory and re-setup everything AGAIN) except
> kcontrol. Kcontrol, as with the previous 2.1 iterations, will not work for
> user. As superuser,
35 matches
Mail list logo
