Hello,
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.)
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.
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.
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.
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...
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.
--
Gary
Sent from seele.gvsu.edu
1:35pm up 22:28, 3 users, load average: 0.05, 0.19, 0.68
Mandrake Linux release 8.3 (Cooker) for i586
=============================================================================
Founder GVLUG.
Chief Systems Architect, S4, Inc. - OS Department.
Chairman and Project Lead of the E-media Committee of AltReal.
PHONE : 331-0542
EMAIL : [EMAIL PROTECTED]
[EMAIL PROTECTED]
=============================================================================
