KDE 2.1 Beta1 Released

Sunday, 17 December 2000 | Melter

The KDE Team today announced the release of KDE 2.1-beta1. KDE 2.1 constitutes the second major release of the KDE 2 series.

The full announcement is available here.

KDE 2.1-beta1 offers a number of additions, enhancements and fixes over KDE 2.0.1, the last stable KDE release which shipped on December 5, 2000. The major additions are:

A new and much-anticipated theme manager has been added, and many icons have been improved. In addition, semi-transparency (alpha-blending) has been implemented on small images and icons.
Pixie, an image viewer/editor, has been added to the Graphics package.
KDevelop, a C/C++ integrated development environment, has been added to the core KDE distribution. The version being shipped, 1.4beta, is the first version of KDevelop to make use of the KDE 2 libraries and integrate completely with the KDE 2 desktop.
Konqueror, the KDE 2 file manager, can now be configured to provide thumbnail previews for text and HTML files. In addition, the standards-compliant Konqueror now stores bookmarks using the standard XBEL bookmark format; a new bookmark editor complements the new standard. Finally, auto-proxy configuration has been implemented.
KHTML, the HTML widget, now has a special 'transitional mode' which greatly improves its handling of malformed HTML pages. In additon, KHTML now has greatly improved Java support and has added support for Java security (JDK 1.2 or compatible is now required).
The panel (Kicker) has enjoyed significant improvements. An external taskbar has been included (familiar to KDE 1 users), support for sub-panels has been added (which can be separately sized and positioned), an improved external pager (Kasbar) has been added, and support for applets has been improved (including support for WindowMaker dock applets).
ARts, the KDE 2 multimedia architecture, now offers a control module to configure sampling rate and output devices, increased performance, improved user interfaces and a number of additional effects and filters.
For developers, a number of classes have been added to the core libraries, including a class for undo/redo support (KCommand) and a class for editing list boxes (KEditListBox).

Comments:

KOOL! - t0m_dR - 2000-12-17

Off to the download site my friends! PS Thanks KDE people!

Re: WHERE ARE SuSE6.4-KDE2.1beta files?????? - Manni - 2000-12-20

WHERE ARE SuSE6.4-KDE2.1beta files?????? thanks, manni ;)

Re: WHERE ARE SuSE6.4-KDE2.1beta files?????? - Justin Hibbits - 2000-12-21

Just download the sources and compile them yourself. It will work much better that way, and it will be optimized for your computer, not every computer... Justin

Re: WHERE ARE SuSE6.4-KDE2.1beta files?????? - Manni - 2000-12-22

hm, in my opinion, i think it must be better too, compiling the source.., i agree, but, i thought, it takes such a loooong time to compile so much files.., but i will try that :) my maschine: intel 200MMx, 96MB RAM now (but 32 uncached) thanks, manni

Re: WHERE ARE SuSE6.4-KDE2.1beta files?????? - Manni - 2000-12-22

hi justin, i have got another question, do you know why the Size of the source-packages or SuSE7.0-packages are just around 35MB ? i remember, before the size of the packages was somewhat around 50-60MB right ? are there still missing some files ? thanks, manni :)

Re: KOOL! - Starbucks - 2000-12-22

Yup, really cool.. for SuSE 7.0 users: The new release of KDE doesn't seem to work with qt-2.2.1. I tried to install the RPMs for SuSE and it would start before I downloaded the qt-2.2.3 and compiled it. Hope that Helps, Starbuck's

Re: KDE 2.1 Beta1 Released - t0m_dR - 2000-12-17

BTW: In what version is antialiasing supposed/planned to be supported? (I know I , I know , I don't have a lot of patience :-) )

Re: KDE 2.1 Beta1 Released - jimbo - 2000-12-18

Oh, we are many who can't wait for antialiasing. I really really really hope it will be supported in KDE 2.1 and whatever QT (I guess it is mostly a matter of QT support) is current at the time. :-)

Re: KDE 2.1 Beta1 Released - Andreas Joseph Krogh - 2000-12-18

This is a XFree86(and other X-servers) issue. It won't be supported before the X-server supports it(maybe XFree-4.1?) -- Andreas Joseph Krogh <andreak@nettverk.no>

Re: KDE 2.1 Beta1 Released - _ganja_ - 2000-12-20

I spent last night downloading XFree864 from CVS and compiling, now binaries are out! Well, I did it for anti-alias support anyway so no loss. I'm writting this using KDE2's konqy fron CVS (also last night) with anti alias text and it looks great. There is a real easy way (?) to set this up without applying patches to QT etc. A Simple HOWTO based on what I did is below HOWEVER, I have no idea if this is needed for the final 4.0.2 release. Download, make and make install freetype2 from www.freetype.org, this should be a recent CVS checkout or snapshout, i used this: ftp://freetype.sourceforge.net/pub/freetype/unstab le/freetype2-current.tar.gz Download X in source form, create the file: xc/config/cf/host.def To have this line: #define Freetype2Dir /usr/local Make and install X with make World & make install. Get an updated qt that contains the patches to use the new render, the easiest way to do this is to do a qt-copy checkout from kde's anon CVS. This already has the patches applied and a configure option to turn on render use. Configure qt with: ./configure -xft -sm -gif -system-jpeg -no-opengl -no-g++-exceptions make QT...... You now have a QT with render support, anything you compile against it will get anti-aliased text including the whole of KDE2. Good luck!

Re: KDE 2.1 Beta1 Released - _ganja_ - 2000-12-20

Re: KDE 2.1 Beta1 Released - KernelPanic - 2000-12-17

Wohohoa! Dang, I had expected a lot less for a 0.1 version increase! You KDE developers majorly rock! Thank you all!

Re: KDE 2.1 Beta1 Released - Christoph Würstle - 2000-12-17

Hi! Looks very nice! But I can't open images with pixie any more! Konqueror doesn't show gifs and I can't define an jpeg as wallpaper! Is this a bug in this Beta or only on my system? I have Suse Linux 7.0! Thanks Chris!

Re: KDE 2.1 Beta1 Released - Christoph Würstle - 2000-12-17

Now it works! My system was not configured well.... But KDE ist really soooo great! Chris!

Re: KDE 2.1 Beta1 Released - Yann - 2000-12-19

This is not KDE but Qt. You had to recompile Qt with options -gif and -system-jpeg

Re: KDE 2.1 Beta1 Released - JochenReitzig - 2000-12-21

You have to compile qt with ./configure -gif -system-jpeg That should work!

Re: KDE 2.1 Beta1 Released - Manuel Román - 2000-12-17

it's great

Red Hat packages? - Redhat - 2000-12-17

Currently there seems to exist rpm-packages only for Mandrake and SuSe. Is there going to be packages also for other distributions?

Re: Red Hat packages? - Will Stokes - 2000-12-18

How about Slackware and Debian packages? I run Slackware, and a number of my friends do as well. I have a PII 400mhz and it takes a while to compile the entire kde2 source tree and all packages from scratch. several days in fact. Not having Slackware packages around is a big dissapointment. Kde2.0 had them, but kde2.01 does not, how about somebody with a fast computer compiling them and makign them available for kde2.1 final? :) -an anxious Slackware user...

Re: Red Hat packages? - David B. Harris - 2000-12-18

This fellow has a good point. For whatever reason, KDE2 takes a long time to compile. And I don't mean you can go out and get a cut of coffee long. More like you can go out on a date, spend the night, THEN have a cup of coffee. I'm not saying this is anyone's fault - personally, I think KDE2 is very great from a technical standpoint(I mean, I can actually *read* the code), and it's getting very close in terms of great usability. However, since it takes so long to compile, providing binary packages should be pretty high up in the list of priorities for a release. If the KDE release team has decided that "it's the distribution's job", then that's okay, but they should make it known. Thanks for your time, Dave P.S.: I'm running Debian Woody, and if someone on the KDE release team reads this and wants my help, let me know.

Re: KDE 2.1 Beta1 Released - Bård Farstad - 2000-12-17

Any RPM's for Red Hat 7.0 yet? -- Bård Farstad http://zez.org

Re: KDE 2.1 Beta1 Released - ac - 2000-12-17

The best thing to do would be to compile from sources... that would lead to better bug reports. RPM's should be upcoming tho.

Re: KDE 2.1 Beta1 Released - Suksi Suohon - 2000-12-17

If there is available precompiled RPM-packages, I much rather use them than compile the sources myself. Somehow it feels so much better to know that there exists an easy way to remove and update the software if needed. Or does the "make install" always install the self-compiled binaries (etc) on top of the files which came from rpm-packages? In this case that of course wouldn't be any problem...

Re: KDE 2.1 Beta1 Released - SubPar - 2000-12-18

Probably not. You'd likely have to uninstall the RPMs before you build from source. Some distros put the KDE files all over the filesystem rather than keeping KDE in one directory.

right - renaud - 2000-12-19

I agree, a beta release don't really need precompilled packages, only stable releases need.

Re: KDE 2.1 Beta1 Released - David Simon - 2000-12-17

Say, what about noatun, the new media player?

is www.kde.org down? - ac - 2000-12-18

i haven't been able to reach it at all today.

Re: is www.kde.org down? - Tomas - 2000-12-18

Same thing here. The kde sites seem to be down quite often. Then to another thing.. I managed to grab all the KDE rpms for Mandrake 7.2. How should i install these? I shut down X by telinit 3 and tried rpm -F *.rpm but it seems to need libkscan.so.1 I tried to find it on the net but I couldn't. Any hints? Am I doing something wrong here?

Re: is www.kde.org down? - Justin Hibbits - 2000-12-21

Compile the sources, then it will work, or it should... Justin

Re: KDE 2.1 Beta1 Released - younker - 2000-12-18

Why the KOffice doesn't been include? Does Chinese support improve in this version.

Re: KDE 2.1 Beta1 Released - Aegir - 2000-12-18

KOfice will be updated separatly from KDE. The 2 products are too big to insure coordination for updating them together.

Re: KDE 2.1 Beta1 Released - Rod - 2000-12-24

KOfice will be updated separatly from KDE. The 2 products are too big to insure coordination for updating them together. OK... will KOffice as already installed for 2.0.1 work with 2.1Beta1?

Re: KDE 2.1 Beta1 Released (auto-proxy config) - Michael Goffioul - 2000-12-18

How do I setup auto-proxy configuration. I didn't find anything in web config of kcontrol.

Re: KDE 2.1 Beta1 Released (auto-proxy config) - tbarka - 2001-09-03

please See: http://home.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html

Controversity: KDE admirer, who hates using it! - Peter Kese - 2000-12-18

I have been using kde 1.1 for some time but then had to switch to windows for a while. Now I got the chance to install KDE-2.0.1 on my home machine and found out there are a couple of things I really dislike. (I am using Mandrake7.2) My problem is that, although it takes only an hour to install Linux, it takes a week to configure KDE to work. The first thing is that the default window controls are so unlike windows. With KDE you have to click on the leftmost button to close a window, with windows you click on the rightmost button. Now, with kde I ended up maximizing (or whatever that feature was) windows all the time. It is really annoying and I couldn't figure out how to change that although I was serching through the whole control center. There might be some themes that have more windows (or even KDE1) like functionality, but in Mandrake 7.2 there aren't. I am not such a fan of Widnows, I just I have to switch between Linux and Windows a lot and really dont like such inconsistencies. Yuck. The second thing is the Konsole. It just happens that I don't like the default color schemes anyway. Well let's face it: half of them are black on white or white on black. Oh, of course there is also the transparency feature, which fails to refresh whenever you switch virtual desktops or restart a KDE session so why having it anyway. Well there is no feature to set up say a yellow or white letters on dark blue or gray backgrond. And why am I complaining about that? Because that is a standard. You can do that Gnome, you can do that with xterm, you can even do that in THE Microsoft Windows. Hell, you could even do that with the old kvt (the KDE1 terminal program). Apparently someone had decided it was wise to trade a useful custom color selection feature buggy transparency feature. And I guess that was just because GNOME had such a feature. Why the hell is it, that everything has to be so 'feature complete' but noone thinks about useability. I would be gladly willing to get rid of 70% of the configurability in the control center just for some rationality about what users really need. I am writing this comment on Windows while waiting to cool down enough to give KDE another try. Well maybe until the the KDE 2.1 might as well arrive. Hell I am not willing to spend my life configuring and hacking things I needn't have to. And by the way, I guess the worst thing that happened to Linux desktops is Themeability. Now no one gives a damn what the default desktop looks like, because everyone pretends things can be fixed with different themes. Sorry, Peter

Re: Controversity: KDE admirer, who hates using it! - garion - 2000-12-18

To move your cloise box from teh left side to the right, right click on the windows title bar, go to decorations, choose one you like. Most of them, the close is on the right... --Garion

Re: Controversity: KDE admirer, who hates using it! - Torsten Rahn - 2000-12-18

Even better: in KDE 2.1 the close-button is on the right by default. And please don't forget: KDE 2.x is a complete rewrite, so nobody actually "removed" features. Expect to get full control over your colors in konsole soon. Greetings, Tackat

Re: Controversity: KDE admirer, who hates using it! - David Johnson - 2000-12-18

Aargh! That's so brain dead! It's too easy to hit the close button by mistake when it's only 2 pixels away from minimize.

Re: Controversity: KDE admirer, who hates using it! - Torsten Rahn - 2000-12-18

In the current default the close button is FOUR pixels away from the other buttons (unlike the other buttons which are seperated by a distance of 2 pixels. If you should still have problems with that then you might want to choose one of the alternate windowmanager styles. Greetings, Tackat

Re: Controversity: KDE admirer, who hates using it! - Henry Stanaland - 2000-12-19

Why not make the positions of buttons an option? I know in Gnome, using the AquaX theme, you have the choice of "Windows style, Mac Style, KDE style" & etc, which addresses this issue perfectly. I don't know how the themeing works, but why not fix it now before it's too late?

Re: Controversity: KDE admirer, who hates using it! - Nicolas - 2000-12-18

I vote for the close-button on the left, like 2.0.0 and 2.0.1 releases. It's soo easy to use for crazy mouses and little brains like mine: left to kill, right for other operations. If it's not the default on 2.1, I hope there will be an "original KDE2" decoration. More seriously, I think it's important for KDE to have a stable default decoration and theme. If this changes on each release, people will not feel "at home" and will have to re-learn their desktop. Another thing: If users are focused on this kind of left/right button problem, that means potential deep problems like stability are very far from KDE2. Quite a good news!

Re: Controversity: KDE admirer, who hates using it! - KDE User - 2000-12-18

You may want to consider dumping KWin for another window manager. KWin is extremely ugly-looking and seems to violate X11 standards in at least one place (send_event field in XEvent structure). There is a lot of other window managers available that are more mature, configurable, and better looking (WindowMaker,Enlightenment,IceWM,etc.)

Dumping KWin - Peter Kese - 2000-12-18

That would not be fair. I do believe in KDE. I do believe they (we) can make a good Window Manager. If I didn't care, I wouldn't have written that complaint anyway.

Re: Dumping KWin - KDE User - 2000-12-18

That would not be fair. I do believe in KDE. I do believe they (we) can make a good Window Manager. If I didn't care, I wouldn't have written that complaint anyway. I am sure KDE team can (theoretically) write a good window manager. But the current fact is that KWin is nowhere near available alternatives. And I do not see why anyone would use substandard software out of plain patriotism, when better alternatives are available.

Re: Dumping KWin - Another KDE user - 2000-12-21

And how can the window manager be changed in KDE? It should be in the Control Center, but haven't found it there.

Re: Dumping KWin - KDE User - 2000-12-21

I think you can do it by manually modifying startkde script. There is no way to do it from the Control Center. I do not use startkde script at all, just run a few useful KDE2 applications that work and ignore the rest.

Re: Controversity: Repost - Peter Kese - 2000-12-18

I am sorry, about the previous post. I have been a little bit pissed. I am a Linux supporter and I have even been developing it. I know things are getting solved and I guess I should better not complain about that. I guess I am the kind of guy, who could easily sit down and fix all these things and share them with others. I enjoy coding C++ very much. But with this matter, it comes down to principles. I keep trying to convince people to dump Windows and switch to Linux instead. Then, one day, I try to update my own Linux installation and end up with a pile of problems. Those problems weren't there in kde1. Kvt worked fine and window buttons were exactly where I wanted them. Now since everyone made such a big deal out of kde2, I expected things to get even better. But it didn't. You know my perspective about windows/window managers was that they let me have 10 consoles open at the same time as well as some 15 web browser widnows. What I want most from kde is to help me handling that 25 windows without interfeering too much. I won't repeat that I have found some glitches with kde2. I got used to a certain standard and then I was forced to change it. By the same guys. It reminds me of the Microsoft attitude: "Standards are great, everyone should have its own." Why did some developers thought of changing things in such a way, that they break previous kde standards. I find it difficult to forgive such a policy. At least I should have an option to stick with my old kvt instead of forcing me to work with konsole. I don't blame kde not having antialiased fonts because I know how difficult it is to achieve. But I do blame the developer of konsole for spending heaps of time to support the transparency instead of spending probably less than 1 hour for customized colors. Do you think I am wrong to expect developers to keep with certain standards? I understand (now) you can select your own window button placement with kde2, but why was the default set in a different way that kde1 users were used to? Do you think I should better sit down and fix things (like konsole) myself? I am not sure that would fix things in long run, I guess it is better to make a loud knock on some doors. Which doors?

Re: Controversity: Repost - Justin - 2000-12-18

Hmm. I don't think there is anything wrong with putting the close button on the left as default. Sure, it's not the same as KDE1, but the KDE team wanted to change it. The close button on the right has long been debated as the wrong place to put it (at least when it's near other non-destructive buttons). Just because it was placed on the right in KDE1, does it mean the KDE developers must put it there until the end of time? They want to make the Unix desktop different than Windows. At least they give you an option to change it to the right side. Isn't this enough? By the way, if you want to alter your Konsole colors, have a look in this directory: /opt/kde/share/apps/konsole All of the schema files are in there. Twiddle to your heart's content! It would be nicer if this was in a configuration dialog someplace, but this should do for your purposes. If you don't have root access, try using the same folder in your ~/.kde directory. Usually you can override the system default settings in there. Anyway, KDE is constantly a work in progress, and it's doing great. And it's *not* Windows. Just remember that. -Justin

Re: Controversity: Repost - Glen Ditchfield - 2000-12-19

<blockquote>The close button on the right has long been debated as the wrong place to put it (at least when it's near other non-destructive buttons).</blockquote> I agree that close-at-right is wrong, but I liked the Motif approach: on the left, have a button that brings up the Window Operations menu (what you get now by right-clicking the title bar). Make double-click on that button close the window. Then remove the close button entirely; accidental window closure becomes unlikely. Oh, yes, and make Alt-Space the keyboard shortcut that posts the Window Ops menu. MS Windows works much the same way, except it has a close button. I gather that this behaviour was inherited from some ancient IBM standard.

Re: Controversity: Repost - Aaron J. Seigo - 2000-12-18

> You know my perspective about windows/window > managers was that they let me have 10 consoles > open at the same time as well as some 15 web > browser widnows. What I want most from kde is to > help me handling that 25 windows without > interfeering too much. I agree... I'm running KDE2.1 from CVS and here is how I have it helping me manage those windows: <UL> <LI> I have a child panel with a task bar and pager at the top of my screen <LI> The taskbar has a little drop down menu that lists every window on every desktop just in case the buttons themselves aren't enough <LI> The pager has a button that shows a small snapshot of each desktop, very nice for visual recognition <LI> I'm using the RiscOS decorations which, although very unlike MSWindows, has some VERY nice features, like the button that temporarily hides a window until you click on another window. at that point the window you clicked on becomes the front window and the hidden window(s) pop(s) up in the background. <LI> I have assigned accelerator keys to swtich between desktops either by number or left/right <LI> Instead of having 10 consoles open, i have one Konsole, with 10 sessions started in it which i can easily switch between using Shift + Left/Right or by clicking on their icons in the tool bar (also have turned off the menu bar, scroll bar (i have a scroll mouse), and window borders... lots of screen real estate saved) </UL> with all these spanky features in KDE2 i manage a 6 desktop KDE session with dozens upon dozens of windows and apps running without breaking a sweat. i think that perhaps the problems you are encountering are from the newness of KDE2. 2.1 is very usable (and nice looking to boot) but does not do things how they are done in MS Windows just because they are done that way in MS Windows. instead KDE2 implements things in ways that makes the sense (most of the time, anyways). It honestly takes about 30 minutes to get used to once you are all set up (this is from watching co-workers sitting down to their new KDE2 desktops)

Re: Controversity: Repost - David B. Harris - 2000-12-18

Standard are okay, but keep something in mind, AT ALL TIMES. When a standard is WRONG, change it. Having the close button only a few pixels away from non-destructive buttons is a very bad thing. It violates so many user-interface guidelines it's funny. And those guidelines were written by people who spent years testing these sorts of things on people completely unfamiliar with computers. Just because you don't like something doesn't mean it shouldn't be changed. Microsoft changes things to cause other people harm; so don't even try to bring them into this discussion. Now, I know that there have been people saying that they're going back to the status quo for 2.1, and if they're right, I'm saddened. Oh, and to correct another poster: generally, people who are developing Linux as an alternative to Windows arn't trying to make it *different* than Windows, they're trying to make it BETTER than Windows. Just to clear that up. Dave

Re: Controversity: Repost - Justin Hibbits - 2000-12-21

Hey, you would make a fine addition to the bde crew, just pop over to http://www.blackholepro.org/ or, if that doesn't work(it is a free site) go to http://black-hole.iwarp.com/ I am the head of the bde project, a very new, innovative, customizable-to-the-point-of-insanity desktop interface that will give the true meaning to customizability. It uses an XML GUI interface to make GUI designing very customizable, and it dynamically creates the gui on startup, so that the user can redefine the gui just by editing the XML file. If you're interested, drop me a mail. Justin

Don't feed the trolls - Warning - 2000-12-19

Don't feed the trolls people.. This one's pretty obvious.

Re: Controversity: KDE admirer, who hates using it! - Brian Gallaway - 2001-05-14

When I first installed Mandrake 7.2 with KDE 2.0, I found it difficult to get used to the close button on the left, so I changed my Decoration to KDE1. After a while, I decided that I liked the look of the KDE2 Decoration enough that I'd try to get used to the close button on the left. I had kind of assumed that logic dictated that the close SHOULD be on the left anyhow, and after getting used to it I found this to be correct. Now I'm getting ready to upgrade to KDE2.1 and am kind of ticked they moved the damn thing back. I find the new buttons too small and the new icons ugly compared to the 2.0 ones (I really like the 2.0 ones). If nothing else, I would have liked to see an option to get the KDE2.0 title bar as a Decoration, since it looked better anyhow in my opinion. I certainly don't expect them to keep the close on the left as default, especially since they are trying to bring over Windows user's without frustrating them. If there is any way to get the KDE2.0 Decoration in KDE2.1, could somebody please post a reply and let me know. I'm going to back up a bunch of my old files from Mandrake 7.2, so if I just need to hack in something from KDE2.0 I can do that. If not, I guess I'll just bear it until KDE2.2, and hope a good option presents itself.

Re: Controversity: KDE admirer, who hates using it! - Brian Gallaway - 2001-07-18

Now I feel dumb. About 2 days after I posted this I installed Mandrake 8.0 and found the Laptop decoration to be the KDE 2.0 one. Sorry for the unnecessary flame. Brian

Re: Controversity: KDE admirer, who hates using it! - nani - 2001-06-09

Re: KDE 2.1 Beta1 Released - Houdini - 2000-12-18

I must say that I'm impressed. I'm running the current CVS, and Kde2 developers did so many improvements in such a short time (just 6 weeks after release of KDE 2.0). That proves that they've chosen the right way to go. They created a base, and now C++ & QT show their superiority. Reusability of code accelerates development of new applications and addons to existing ones. I feel that they can now do anything they want in no time. Congratulations.

Re: KDE 2.1 Beta1 Released - jpmfan - 2000-12-18

2.1 Beta 1 is cool! KDE just gets better and better. Unlike people who have been finding "issues" with it, I am very happy with it! Remember, it's open source software, so if you don't like the custom colors in konsole or whatever, change KDE so you can configure your own. I am running 2.1 Beta 1 with the latest XFree86 4.0.2 from CVS and anti-aliased fonts work perfectly - well done Keith P. and all the QT developers. konsole works properly now and it all looks very professional... Keep up the good work guys... (you never know, I might get round to helping you :-))

Re: KDE 2.1 Beta1 Released - heroo - 2000-12-19

dito

Re: KDE 2.1 Beta1 Released: SuSE 7.0 RPMs - Paul C. Leopardi - 2000-12-19

Thanks! I've downloaded and installed KDE 2.1 from the SuSE 7.0 RPMs and have found some improvements and a few bugs. Improvements (at least for me): 1. The new SuSEconfig.kdm2 now configures kdm properly for KDE2. 2. The new version of kdm has a shutdown that works properly. Bugs (at least on my SuSE 7.0 system): 1. Out of the box, konqueror can't find Java 1.2. Java 1.2 does not install automatically in the SuSE 7.0 installation and it is not included in the SuSE 7.0 RPMs for KDE 2.1. After learning this, I then installed the IBM Java 2 JRE from the SuSE 7.0 CDs. Soon I will have another look at the KHTML doco to see if I can configure Java 1.2 properly. 2. Color blending in the title bar of windows seems to no longer work. Perhaps this is a side-effect of the new themes.

Re: KDE 2.1 Beta1 Released: SuSE 7.0 RPMs - Paul C. Leopardi - 2000-12-19

Oh, and another bug: 3. kpackage still does not know about RPMs and as a result, can't find the installed RPMs. I had to use Kpackviewer and yast instead last night. Yes, I know I need to report these via the normal channels. I will soon enough.

Re: KDE 2.1 Beta1 Released: SuSE 7.0 RPMs - Richard Moore - 2000-12-19

Please us the bug reporting system to report bugs rather than just talking about them here (feel free to discuss them here too of course). If you don't send them through the bug reporter then there is a good chance they will be overlooked. With regard to the actual bugs you're talking about: <ul> <li>KPackage supports RPM just fine. You have some sort of installation problem. It may be that this is related to the packaging of the SuSE RPMs, so I suggest you report it to SuSE (after checking their support database). <li>Not installing a JVM is not a bug, it's a feature. Not all users want Java, and the JVMs are only available for a subset of the platforms supported by KDE. Add to this the huge size of a complete Java 2 run time and various licensing issues, and you can see why we leave it to the distribution. <li>The titlebar stuff depends on which WM theme you are using. Without knowing this no one can help you. </ul>

Re: SuSE 7.0 RPMs: Java now works - Paul C. Leopardi - 2000-12-19

I will post details on kde-user and suse-linux-e soon.

Re: KDE 2.1 Beta1 Released - Franky - 2000-12-19

Great work! But I have one problem: I am using SuSE 7.0 and KDE 2.0 found my mixer device. But KDE 2.01 and KDE 2.1 Beta1 doesn't find my mixer. Whats can I do?

Re: KDE 2.1 Beta1 Released - dazk - 2000-12-19

Hiho, Are other apps finding your mixer? Is the mixer device /dev/mixer ? Do you have permission to read and write to it? If you answered all these questions with yes, I've no idea. If you can't access /dev/mixer try setting permissions correctly. I think you need both. Hope that helped, Richard

Re: KDE 2.1 Beta1 Released - KernelPanic - 2000-12-21

Just so you'll know, I have the same problem with my alsa-card (a sb pci 128). Well, I can wait for 2.2, hehe...

Re: KDE 2.1 Beta1 Released - dazk - 2000-12-19

Hi there, I just installed the new Beta from source on RH7 with all available updates installed and QT-2.2.3 installed from source. KDE sits in it's own directory with a symlink pointing to it from /usr/local/kde. ld.so.conf contains /usr/local/kde/lib and PATH contains /usr/local/kde/bin. The new system was compiled with the Symlink in place and QTDIR and KDEDIR set to the correct directories. All other versions worked perfectly (2.0, 2.0.1) that way but with the new version I have a problem. Before I started the new version, i created a new user for test purposes only (to have a clean user without existing .kde), started KDE2.1b1 via kdm and after successfull login the splashscreen stops after "starting system services" it disappears and after a while I get a message wich asks if dcopserver is started. Any suggestions? Thanx, Richard

Re: KDE 2.1 Beta1 Released - Erik Hill - 2000-12-19

Okay, I'm a Linux Mandrake 7.2 user (but I've replaced the standard X-Windows 4.01 install with a 3.3.6 because my video card does not support the 4.01 drivers). You know, I write software for a living, but it is still very difficult for me to get the KDE 2.0 installed and running. Is there a fast way to do this, or at least sample it before I tear my system apart to get it installed? The RPM's I've looked at seem to require that even very deep, highly inter-dependant libraries be replaced, those I've seen, even if they are in a directory lablelled "Mandrake 7.2" seem to require packages and updates that I can't find! I really just want to use the latest build for a bit before I commit to the work involved in learning how to update so much of my system. What would be nice would be a step by step instructions for installing the RPM's. I've seen this for compiling from the source but if installing the RPM's is so involved, certainly compiling from source is going to be worse. Like I've said, I've got a Mandrake 7.2 system with the current (2.???) KDE installed off of the CD. It seems by the screenshots and error reports that a WHOLE LOT has happened since then. Maybe I should switch to debian -- the thinking is -- it seems to be easier to update (though perhaps harder to install the first time). Any ideas? Erik Hill

Re: KDE 2.1 Beta1 Released - Erik Hill - 2000-12-19

I just wanted to add that, at this point, I also wonder if someone will allow me to log into their system (using an X-Server) so that I can sample the look-and-feel of KDE 2.1beta. Perhaps Mandrake Cooker is the way to go? I hear it has a very late version of KDE on it and therefore has all the libraries it might need installed already. Erik Hill

Re: KDE 2.1 Beta1 Released - Daniel - 2000-12-19

Well, I'm still a relatively newbie, and I installed Debian in the old days in a bit of an effort, but the new version is much easier. It is starting to autodetect lots of hardware as Mandrake. I recomend it *very* much...It is the only distribution that made me stick to linux because I installed kde-2 very easily. Daniel

Re: KDE 2.1 Beta1 Released - Shift - 2000-12-20

Debian didn't detect my ATI card and my Haupauge TV card but Mandrake 7.2 do it ... and moreover it autoconfigure them. Debian is cool (I also have it on my PC) but Mandrake is cool too : I recomend it *very* much ;-)

Re: KDE 2.1 Beta1 Released - bbqPorkChop - 2000-12-19

I also use Mandrake 7.2 and had problems installing KDE2.1 beta using rpm -Uvh *.rpm. So the fix that worked for me was to uninstall all of the equivalent KDE2.0 packages with using the --nodeps. I then installed all of the new KDE2.1 beta packages with rpm -i *.rpm. Rebooted just for the hell of it and was using KDE2.1 beta without doing anything else. I must say it is more stable in my opinion then the 2.01 release!!

Re: KDE 2.1 Beta1 Released - Erik Hill - 2000-12-19

Thank you for your help, I will try this (and also, eventually, (I keep promising myself), Debian). Now I am installing a clean Mandrake 7.2 installation and then I will do the process you've outlined. I guess the answer is, the packages THINK they need the very latest versions of everything, but in fact, it runs on whatever Mandrake 7.2 happens to install by default. I see this as a bug in the packages, it should not require (in the package) any later version of anything than it actually requires. Where are these packages? KDE 2.1 intended for installation on Mandrake 7.2? Erik

Re: KDE 2.1 Beta1 Released - bbqPorkChop - 2000-12-19

just to clarify ... I didn't skip on any requirements. The problems I had were related to the fact that I was intalling over the old KDE2.01 packages. The reason why said to use the --nodeps option is because when I tried to remove the old KDE2.01 it said there was some gnome applet, kdesdk and some other (not at my computer right now) packages that relied on the KDE2.01 packages. But since I was going to install the equivalent KDE2.1 beta packages I didn't want to remove those other packages. This worked for me so I hoped it works for you.

Re: KDE 2.1 Beta1 Released - Erik Hill - 2000-12-20

Ok, but how did you get KDE 2.0.1 to work? Do you know offhand which KDE (and how would I find out?) is installed by default on Mandrake 7.2? My "About KDE" (remember that I've installed only the default Mandrake 7.2 installation) calls itself "K Desktop Environment. Release 2.0 Release Candidate 1 >= 20001002mdk" Is this the same as 2.0.1?

Re: KDE 2.1 Beta1 Released - bbqPorkChop - 2000-12-21

I got KDE2.0.1 to work the same way. Depending on which version of Mandrake 7.2 to have it will depend on which version of KDE you received. The early retail version did not come with an official release of KDE2.0 it came with KDE1.99. The download version of Mandrake 7.2 and the second retail version was released with the official KDE2.0 version. But you should be able to upgrade to the latest version by using the method above. If you need any help e-mail me at coatesp@hotmail.com.

Re: KDE 2.1 Beta1 Released - Erik Hill - 2000-12-21

Great -- multiple versions of Mandrake 7.2 .... I thought the "7.2" WAS the version number! :) Anyway, thank you, and I will in fact try that. I'm transmitting the KDE 2.1 package to my laptop now (through, of all things, a null-modem cable) so I'll give that a shot. Erik

Re: KDE 2.1 Beta1 Released - Prana - 2000-12-21

Automatic install (like Debian's apt-get) in Mandrake: urpmi packagename.i586.rpm Uninstall automatically (including dependencies): urpme packagename.i586.rpm That'll make your life so much easier compared to Redhat's RPM management

KDE not for ADMINISTRATORS??? - Asif Ali Rizwaan - 2000-12-19

Hi, I really love KDE, and am impressed with KDE 2.0. I strongly believe that KDE 2.1 will supersede all other desktop environments. KDE does have many Good applicatons, utilities, games, web browser, file manager. But still KDE lacks many simplifying utilities, applications, wizards, etc. for Administrators. The Administrator has to struggle with all these, and delve into the man pages and howtos to do the job. It is really hard work for them. The KDE team is very efficient in creating good Apps, wizards etc., I request you to kindly make some Wizards and Applications BOTH Client and Server for Configuring and using these: a. Network (kdenetwork) 1. DNS 2. DHCP 3. NFS 4. Sendmail 5. FTP 6. Telnet 7. Sendmail 8. Apache 9. Database server/client 10. File and print b. Security (SeKurity) 11. Firewall (FireWalK) 12. Proxy Server (ProKsy) 13. SSH (KSSH) 14. PGP (EnKryptor) c. Hardware (KHardware) 15. X Configuration (Xkonfig)(like in Corel Linux) 16. Printer (KUPS) 17. Scanner (SKanner) 18. Hardware AutoDetection (DeteKtor) When I saw Corel Linux, I was impressed with what they have done to KDE 1.1.x. Why is it that KDE team haven't took notice of the pain and suffering of System and Network Administrators? Why use Command Line Interface when we have such a great Desktop environment? Why do you think that administrators are not humans :)? I know that work is going on, but this part (the administration) did not got much attention by the great KDE Team. I trust KDE developers and the KDE team and believe that you will create such Administration Wizards, Utilities, and Apps for Administrators just like you have done for the user community! I request you humbly to kindly think about it and make some really cool Administration stuff! Thanks a lot, you are doing the right thing! Yours truly, Rizwaan.

Re: KDE not for ADMINISTRATORS??? - bbqPorkChop - 2000-12-19

KDE may not have all of the above mentioned features but you should check out Mandrake's DrakConf utility ... you may be suprised by what you find. www.mandrake.com

Re: KDE not for ADMINISTRATORS??? - Evandro - 2000-12-19

kde is a desktop that works on many UNIX systems, and to get those things done you should use the tools provided with your distribution or the software you want to configure. for linux systems you can use linuxconf, drakconf, rh control-panel, rh setup and many others.

Re: KDE not for ADMINISTRATORS??? - Dirk Manske - 2000-12-20

>1. DNS >2. DHCP >3. NFS >4. Sendmail >5. FTP >6. Telnet >7. Sendmail >8. Apache >9. Database server/client >10. File and print Most of these tasks/configuration files are much too complex for a GUI. I think a GUI for administration/configuration of server tasks would be the wrong way (the M$-Way). Administators must be able to maintain a server over a slow dialup line, all you need is ssh and vi. I do not want to install X and K on a server.

Re: KDE not for ADMINISTRATORS??? - Another KDE user - 2000-12-21

What if you have a small (low load) server? Having X installed and running by default wouldn't be that bad. If your system boot in runlevel 3 you can run the program with a remote XWindow server ;-) If you can't do that, here is another solution: $ X :0 $ export DISPLAY=:0 $ yourAdmProgram & and when you are done kill the X server. Greetings

Re: KDE not for ADMINISTRATORS??? - richie123 - 2000-12-23

My prefered solution for remote admin is web based configureation , since you can have a ssl enable connection, and the convience of giu configuration that works with any operating system. Check out webmin and be prepared to be amazed.

Re: KDE not for ADMINISTRATORS??? - Dirk Manske - 2000-12-23

I know webmin. I do not like it much, always there is a cause to use ssh. You cannot write webmin modules for every purpose.

Re: KDE not for ADMINISTRATORS??? - dazk - 2000-12-20

Hi there, KHardware is somewhat there, at least for information purposes. Try kcminfo. For the other tools, well, go and get yourself a copy of the open source book on how to develop KDE2 Apps and go ahead ;). Once you create an app that is good enough I'm sure the maintainers will think about including it in the standard distribution. For now, try to find what you are looking for on freshmeat. Greetings and have a nice holiday, Richard

Re: KDE not for ADMINISTRATORS??? - Michael Goffioul - 2000-12-20

For what concerns the CUPS system, a quite complete and powerful administration tool already exists, which is called KUPS. Maybe you already know, but have a look at http://cups.sourceforge.net/kups/index.html.

Re: KDE not for ADMINISTRATORS??? - Joakim Ganse - 2000-12-20

I agree. There is to few good administrator utilitys for KDE. And I don't mean utilitys for adminitrating the box you're sitting on but a server someware else. Right now I'm using Webmin with SSL but it would be nice to do it straight from KDE.

Re: KDE not for ADMINISTRATORS??? - fernando - 2002-07-22

sorry that i disturb your discussion for something other. i try to bring sendmail running over webmin, but it dont works, and i dont know what i do wrong. i try to get mails from an account with..sorry "outlook express". but its didnt work, can you give me some tipps to configure sendmail? thanks alot

If anyone cares.... - Brendan - 2000-12-20

The former problem I was having with KDE 2.0 and 2.0.1 libmimelib on Redhat 7, (see <A HREF="http://dot.kde.org/976035423/976046093/976148930/">KDE 2.0.1 Problem</a> ) has magically disappeared when I installed KDE 2.1 beta. I'm using it now, in fact. Thanks, Brendan

It's incredible - Kaufman - 2000-12-20

I just compiled the Dec 17th CVS snapshot with --disable-debug and --enable-final, it's lightyears faster than 2.0.1, stable and the new features are greatly appreciated. The Dec 20th snapshot is out, I'll compile it later.

kdesupport-2.1beta1.tar.bz2 missing?? - Billy - 2000-12-20

Isn't there a tarball for kdesupport? What gives? And why kdesupport is ho huge in the CVS (9MB)? Billy

Re: kdesupport-2.1beta1.tar.bz2 missing?? - Evandro - 2000-12-20

you can use kdesupport-2.01 or 20001217/20.

Where's the kdesupport-package? - Newbie - 2000-12-24

Hi, tried to compile the whole thing for the first time (was using the rpm's for SuSe 6.4 before), but i'm getting some messages about missing lib's. The Comp. FAQ tells about: Compile qt first (is working), then kdesupport then kdelibs and the rest in any order. But?? where the heck do i find the kdesupport package?? i'd appreciate some help

Re: Where's the kdesupport-package? - Evandro - 2000-12-24

you can use kdesupport 2.01 or the current snapshot.