-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gary Greene wrote:
| Hello,
|
| Sorry if you already got this once. I had a few settings wrong on my
box (due
| to the upgrade...) So, here we are again...
|
| I recently moved up to a fully cooker environment to get some of the
recent
| updates (KDE 3.0.1, gcc 3.1.1, et al) Anyway very nice so far, but
with the
| good comes a few bug reports...
|
| KDE stuff first:
|
| 1) KDM: I've noticed a slight security problem with kdm, or rather in
| kdm_greet, I think. When I set it (kdm) to not show users, it works
fine as
| long as I log in to and out of the root account only. However, when I
use my
| perssonal account then log out again, the users are shown again
(including
| root.)
This is a known issue with msec since 8.2. This is how to fix it:
[bgmilne@bgmilne bgmilne]$ cat /etc/security/msec/level.local
#!/usr/bin/python
from mseclib import *
allow_user_list(0)
|
| 2) Kpersonalizer: I know that this has been reported on-list before,
however,
| I may have it tracked down. I appears that kpersonalizer seems to be
ignoring
| the /usr/share/config/kpersonalizerrc all together. Additionally,
| kpersonalizer.cpp seems to be re-writing the
| ~/.kde/share/config/kpersonalizerrc every time (and promptly ignores
it if
| you're root).
|
| 3) Ksplash/ML: I can add new themes but, I can't seem to be able to
configure
| any of them for my personal tastes. Additionally, the rpm doesn't put
entries
| into the new style menu, only the original KDE menu.
What do you mean by the original KDE menu? I was under the impression it
should only be accessible from kcontrol (KDE Control Centre).
|
| 4) KOffice: I installed using the isos on the ftp.sunet.se mirror and
noticed
| that koffice is not on the disc. Additionally, at that time it was in
contrib
| not in main, whereas the i18L stuff for it WAS in main. I finally got
it and
| installed it. It's rpm too does not create entries in the other menus,
only
| the KDE original.
The ISOs are snapshots of cooker, and as such aren't meant to be
complete, only enough to 1)Test installation fuctionality changes, and
2)Get you a system which is capable of installing the rest of cooker.
Again, what do you mean by KDE original menus? What is the configuration
of your menus (in menudrake?).
|
| 5) the KDE rpms: this is more of a question than a bug report: why is
it that
| the srpms are mark not to build if you have their counterparts installed
| already? This makes it difficult to try and fix things in the code and
then
| rebuild the package. I was snooping around in the kdebase-3.0.1 code
to see
| if I could fix the bugs myself, but it won't let me build the package
since I
| have kdebase-3.0.1 installed already. This shouldn't matter since I'm
doing
| this as a user not as root. Also I noticed a few switches in the spec
file
| that I don't know how to call at build. The way I learned rpm was just
to do
| a:
|
| rpm -ba package.spec
|
| and that would build it. With these specs, I don't know how best to
build them
| since they have no documentation about how they are to be built.
rpm --rebuild package-version-relmdk.src.rpm
or:
rpm -ivh package-version-relmdk.src.rpm
rpm -ba `rpm --eval "%{_specdir}"`/package.spec
Check the mandrake rpm howto on how to ensure you are setup correctly
for this (ie non-root building etc).
|
| 6) KDE and other DE's as a whole: Why are we putting them in the /usr
| heirarchy? KDE and GNOME should be located in /opt/<DE name> as per
LSB and
| FHS recommendation. 90% of the distributions put them there, why don't
we? If
| it's only to remain RH compatible, let's cut the crap. Mandrake isn't
close
| to being RedHat-compatible nor is Red Hat a Mandrake-compatible distro.
| Mandrake may be based on Red Hat historically, but it is not compatible
| anymore. This also allows the Mandrake KDE developement team to add
different
| versions of these DEs without requiring MAJOR changes to the /usr
filesystem
| nor major hacks to the build process. Please let's make them
compatible with
| majority of the GNU/Linux base, put them back into /opt.
|
| Non-KDE stuff:
|
| 1) Webmin: I use it a lot for samba administration on my network, I go
to use
| it and lo, it won't start since it can't resolve my IP to hostname. I
tried
| using a vanilla copy (0.980-1) from www.webmin.com with the same
results. If
| I install an earlier vanilla version (0.970-1), it runs.
|
| 2) Mozilla v1.0.0: PSM again and Java support. but you already know about
| that...
|
Either:
1)Deal with having no Java
2)Run RPMs built with gcc2.9x like those I have made available (for 8.2)
at http://ranger.dnsalias.com/mandrake/mandrake8.2
3)Convince SUN to release a JRE/JDK compiled with gcc>=3.1.0
4)Fix kaffe or other open-source JRE implementations to support
JRE>=1.3.0 functionality.
| Like I said, over-all cooker is almost at release quality, but small
things
| are making it not what I would classify as production material yet.
That's why it's cooker!
- --
|----------------Registered Linux User #182071-----------------|
Buchan Milne Mechanical Engineer, Network Manager
Cellphone * Work +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering http://www.cae.co.za
GPG Key http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9B06HrJK6UGDSBKcRAq25AJ9NpmMyn1pS+iMCTyWTFTI6PfZC1gCgxpBE
xGJeZHAK4TN01T9a/VjufZg=
=9NNo
-----END PGP SIGNATURE-----
