Follow Slashdot blog updates by subscribing to our blog RSS feed

 


Forgot your password?
Close
typodupeerror
×
KDE GUI

KDE 2.2.1 Up 336

Posted by CmdrTaco from the time-to-compile dept.
Igloo Boy writes: "The most excellent KDE developers have made KDE 2.2.1 available for download. Please check the mirrors before you flood ftp.kde.org. I will now crawl back into my igloo and warm up next to my Athlon. It gets really hot from all this compiling." Or you could just call out those 3 little letters that make ya feel so good ... a-p-t. I'm installing now. Hope you guys fixed all the bugs I reported!
This discussion has been archived. No new comments can be posted.

KDE 2.2.1 Up More

KDE 2.2.1 Up

Comments Filter:
  • Does anyone know of a good doc on upgrading a kde 2.1.1 install (mandrake 8 standard) to a 2.2.1 without seriously breaking it. When I logged into the ftp server there were like 100 files that I was told to download. Yes, I'm going to Debian soon..just humor me here :)
    • Why not just use MandrakeUpdate ? Simple and easy.
      • Personally I've never been able to find good HTTP sources for MandrakeUpdate - they're all in France and take megs just to update the packages they have, then inevitably they are versions behind in something I'm looking for. Anyone know of any good HTTP sources for MandrakeUpdate?
      • upgrade properly to kde2.2 for many people-- I spent time searching the web after my initial failures. I worked many many hours trying to cajole it, eventually resorting to trying urpmi and then just rpm.

        During a series of unnistall/reinstalls of Mandrake 8.0:
        I tried uninstalling kde first, then not installing it
        I wrote down every dependancy urpmi said it couldn't solve... but eventually none of it would install without a force-- even after trying to manually install the dependencies.

        I did succeed a few times in getting it all installed (after a force).. but seg faults seemed to occur too frequently-- something I judged to be most likely broken dependencies despite my efforts. I guess I'll be waiting for 8.1 ... or at least until I find a good faq on properly manually resolving dependencies.

        I was really looking forward to the new kdevelop and enhancements to KDE. I'll get them eventually, but the instant gratification person in me is disapointed.
    • I usually just install the src in to /usr. That's where all the mandrake kde binaries, shared files, etc are too. I just overwrite them
    • Might take a while ATM 'coz they're in deep-freeze for 8.1 but normally less than 24hrs before a new set of RPMs exist.

    • Re:Upgrading... (Score:2, Informative)

      by RadioheadKid ( 461411 )
      Last time I upgraded Mandrake 8.0 to KDE 2.2 and used urpmi as it says in the README [sourceforge.net] and it worked perfectly. Its just kinda scary when you have to tell it to break all the dependancies.
  • Is there a way to get KDE 2.2.anything for Debian without going to unstable release? That is the most annoying thing I find about *all* the distributions. You either use their packages and are stuck with what they got, or you use source and don't ever use any packages that have dependancies on the stuff you compiled in source. As a result I usually end up just getting source. But I am *trying* to give Debian and the much touted apt a chance. However, I don't feel like going to unstable, and bugs in KDE2 and other packages frozen in stable/testing have been annoying me.
    • debian unstable is hardly unstable. I don't see any reason *not* to run debian unstable unless your system is a critical production server or something. I have no problems and I've been using sid for a while.


      siri

      • Re:A-P-T? (Score:3, Informative)

        by reverius ( 471142 )
        I've lost my entire debian system twice due to using the unstable version.

        By upgrading to the latest unstable software on a daily basis, my system was completely trashed.

        First it was a glibc problem (I don't remember what), then it was an overwritten file that caused me to not be able to log in. I had to re-install the whole system, and I've used Debian Stable ever since.

        There are some ways you can make Debian Stable a lot more modern than you might think...

        kde.debian.net [debian.net] gives you the latest KDE...

        Ximian [ximian.com] offers the latest gnome for Debian potato (stable)...

        and gnulpr [sourceforge.net] offers a printing system (easily set up) that can be installed through apt with debian stable.

        • Re:A-P-T? (Score:3, Informative)

          by z4ce ( 67861 )
          If you don't know how to fix library problems, do nott use unstable. They will happen. However, you can fix them. That's what emergency disks are for. Boot off your emergency disk, download + install the old library or a new fixed one. Most of the time you don't even have to get that drastic though.. you can either go into single user mode or boot the kernel with init=/bin/sh before you go losing your system you might want to talk with the people in #debian irc.openprojects.net I can almost guarantee your system wasn't actually lost.. I've been dist-upgrading to unstable everyday to every other day now for the last say two years or so.

          Ian
          • Yeah... the glibc problem I didn't have to re-install for, like I said, that one was just an annoyance (having stuff broken and all)...

            but the problem I had to re-install to fix was when some kind of password file (I don't remember what) was overwritten by an unstable base package accidentally, and my system did not know who I was and had no way of logging in at all (no users or passwords). :)

            Theoretically I could've fixed this by replacing the files with a bootdisk... but I didn't.
            • A while ago debian/iunstable did nuke the pam libraries, so you couldn't login, yes.

              This did not require a reinstall. I heard you could've started in single-user mode, but I just went with "init=/bin/bash" at the LILO: prompt - and there you go. Logged in as root on your machine. Then you remount root sa read-write (mount -oremount,rw /), mount the other dirs that might get updated (/var, /usr etc) and run apt-get update&&apt-get dist-upgrade.

              Ok, so I had an unusable machine for a day. Luckily I noticed this on the non-vital machine first. (:
        • ...and it never will be. There are too many changes in libraries, etc. and the backporting would not only be way more work than it is worth, but then you wouldn't have a very "stable" environment due to a lack of testing, which is why you use a stable environment in the first place, right?

          Many people are using Debian testing and unstable with quite good results. I am using Potato (stable) with KDE 2.1.2 and am very happy with it. Woody should be out next spring with KDE 2.2 and I can wait until then, myself.

          Cheers.........
          • Hmm... you're right. :)

            I am running Potato, and the KDE off of kde.debian.net [debian.net]... and I assumed it was the latest one ('cause it says 2.x on their web page).

            I never bothered to check what version I had (I don't actually run it; I just use kword and konqueror).
            • I never bothered to check what version I had...

              Yeah, and that's the point for me: I just don't see any reason to go to Woody. I use Mozilla0.9.4 as my browser, and I can't think of anything that 2.2.1 has that 2.1.x doesn't, at least that I want or need.

              How wonderful that Linux has gotten to the point that I can be 6 months (or more) behind the times and not even care. :)
      • you didn't get the libpam-so bug that disabled logins. ;-)
    • yes, look on the debian site for non-official package mirrors, or do it yourself. The latter isnt too hard, just read the basic debian-maintainer guide to setup a debian package build tree for each tarball, edit debian/rules to have the basic commands to configure and make the package, and edit one or 2 other files. Then dpkg-buildpackage, and you've taken a source tarball and built a deb package out of it. It is very handy for getting random tarballs, yet maintain them withing the packaging system.

      -- runs unstable
    • Yesterday I compiled 2.2.1 against qt-2.3.1, all from src archives following all instructions. Konqueror seems to be faster, Knode appears to be slower. Dunno why Knode takes so much time to connect to a news server. Lat year I compiled 2.1.1 from src and all was OK.
      • Oh, I forgot to say I never use pre-compiled KDE .deb packages. Once I installed pre-compiled KDE 2.0 and it didn't integrate very well. Since than I am compiling KDE and have no any problems with it on Debian. This is Potato.
    • Yes, there is! (Ignore all the people who say there isn't... it's extremely easy to do.)

      Check out KDE.DEBIAN.NET [debian.net]. They have apt lines for Potato (stable) for the latest KDE release.

  • List of mirrors (Score:5, Informative)

    by chrandgull ( 454594 ) on Tuesday September 18, 2001 @10:38PM (#2318326)
    In case kde.org is slashdotted, here is a list of mirrors.

    .at (Austria)

    ftp://gd.tuwien.ac.at/hci/kde (++)
    .ch (Switzerland)

    ftp://sunsite.cnlab-switch.ch/mirror/kde (++)
    .cz (Czech Republic)

    ftp://sunsite.mff.cuni.cz/MIRRORS/ftp.kde.org/pu b/ kde/ (++)
    "ftp://ftp.fi.muni.cz/pub/kde (++)
    .de (Germany)

    ftp://ftp.de.kde.org/pub/kde (++)
    ftp://ftp.archive.de.uu.net/pub/kde (++)
    ftp://ftp.fh-dortmund.de/pub/unix/kde.mirror (++) (stable tree only)
    ftp://ftp.fh-heilbronn.de/pub/mirrors/kde (++)
    ftp://ftp.fu-berlin.de/pub/unix/X11/gui/kde (++)
    ftp://bolugftp.uni-bonn.de/pub/kde (++)
    ftp://ftp.gwdg.de/pub/x11/kde (++)
    ftp://ftp.rz.uni-wuerzburg.de/pub/unix/kde (++)
    ftp://ftp.tu-chemnitz.de/pub/X11/kde (++)
    ftp://ftp.uni-bayreuth.de/pub/X11/gui/kde (++)
    ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp. kd e.org/pub/kde (++)
    ftp://sunsite.informatik.rwth-aachen.de/pub/Linu x/ kde (++)
    ftp://mimas.germany.net/pub/master.kde.org (+) (part only)
    .pl (Poland)

    ftp://ftp.task.gda.pl/pub/linux/kde (++)
    ftp://ftp.tuniv.szczecin.pl/pub/kde (++)
    ftp://kde.fnet.com.pl/pub/kde (++) (debian only)
    ftp://ftp.task.gda.pl/pub/unix/kde (++) (Gdansk)
    ftp://sunsite.icm.edu.pl/pub/unix/kde (++)
    ftp://ftp.man.olsztyn.pl/pub/linux/kde (++) (Olsztyn)
    Northern Europe
    .dk (Danmark)

    ftp://sunsite.auc.dk/pub/X/kde (+)
    ftp://ftp.dkuug.dk/pub/kde (+) (stable and part of unstable)
    .fi (Finland)

    ftp://ftp.funet.fi/pub/mirrors/ftp.kde.org/pub/k de (-)
    .se (Sweden)

    ftp://ftp.dataplus.se/pub/linux/kde (++)
    ftp://ftp.se.kde.org/pub/kde (++)
    ftp://ftp.sunet.se/pub/X11/kde (++)
    Southern Europe
    .gr (Greece)

    ftp://ftp.duth.gr/pub/kde (++)
    .hr (Croatia)

    ftp://ftp.linux.hr/pub/kde (-- stable tree only
    .it (Italy)

    ftp://ftp.futuretg.com/mirrors/ftp.kde.org/pub/k de / (++) (stable tree only)
    ftp://ftp.unina.it/pub/kde (--)
    .tr (Turkey)

    ftp://ftp.tr.kde.org/pub/kde (++) (stable tree only)
    .yu (Yugoslavia)

    ftp://ftp.kde.org.yu/mirrors/ftp.kde.org (++)
    Western Europe
    .be (Belgium)

    ftp://ftp.belnet.be/pub/mirror/ftp.kde.org/pub/k de / (++)
    ftp://ftp.easynet.be/kde (++)
    .es (Spain)

    ftp://ftp.dit.upm.es/linux/mirrors/ftp.kde.org/p ub /kde (+) (stable tree only)
    ftp://ftp.tsc.uvigo.es/pub/linux/kde (++)
    .fr (France)

    ftp://ftp.uvsq.fr/pub/X11/kde (++)
    ftp://ftp.lip6.fr/pub/X11/kde (++)
    .ie (Ireland)

    ftp://ftp.esat.net/mirrors/ftp.kde.org/pub/kde (++)
    .nl (Netherlands)

    ftp://ftp.nl.uu.net:/pub/kde (++)
    .pt (Portugal)

    ftp://ftp.dei.uc.pt/pub/kde (++)
    ftp://ftp.eq.uc.pt/pub/software/unix/KDE (+)
    ftp://ftp.esoterica.pt/pub/mirrors/kde (-)
    .uk (United Kingdom)

    ftp://ftp.net.lut.ac.uk/kde (++)
    ftp://sunsite.doc.ic.ac.uk/Mirrors/ftp.kde.org/p ub /kde (++)
    ftp://ftp.uk.kde.org/pub/kde (+)
    ftp://ftp.mirror.ac.uk/sites/ftp.kde.org/pub/kde (++)
    ftp://ftp.newnet.co.uk/pub/unix/kde (++)
    Eastern Europe
    .bg (Bulgaria)

    ftp://ftp.digsys.bg/pub/kde (++)
    .ro (Romania)

    ftp://ftp.lbi.ro/pub/Linux/KDE (++)
    ftp://ftp.tuiasi.ro/pub/mirrors/ftp.kde.org/pub/ kd e (++)
    ftp://mirror.itcnet.ro/pub/kde (++) (stable tree only)
    .ru (Russia)

    ftp://ftp.chg.ru/pub/X11/kde (++)
    Asia/Australia
    .au (Australia)

    ftp://ftp.au.kde.org/pub/kde (++)
    .cn (China)

    ftp://ftp.turbolinux.com.cn/pub/mirrors/kde (+)
    .hk (Hong Kong)

    ftp://ftp.dll.com.hk/pub/mirrors/KDE (++)
    .il (Israel)

    ftp://ftp.iglu.org.il/pub/KDE/ (++) (without snapshots)
    .jp (Japan)

    ftp://casper.yz.yamagata-u.ac.jp/mirror/kde (-)
    ftp://ftp.lab.kdd.co.jp/X11/kde (++)
    ftp://mirror.nucba.ac.jp/mirror/KDE (++)
    ftp://sunsite.sut.ac.jp/pub/archives/linux/X/kde (++) (stable tree only)
    .kr (Republic of Korea)

    ftp://linux.sarang.net/mirror/desktop/kde (++)
    ftp://ftp.kreonet.re.kr/pub/tools/X11/kde (+) stable tree only
    .sg (Singapore)

    ftp://kde.lugs.org.sg/pub/kde.org (++)
    .th (Thailand)

    ftp://ftp.nectec.or.th/pub/mirrors/kde (+)
    .tw (Taiwan)

    ftp://ftp2.sinica.edu.tw/pub2/wmgrs/kde (++)
    ftp://linux.cis.nctu.edu.tw/packages/X/wm/kde (+) stable tree only
    Africa
    .na (Namibia)

    ftp://ftp.na.kde.org/pub/kde (++)
    .za (South Africa)

    ftp://ftp.sun.ac.za/sites/ftp.kde.org/pub/kde (++)
    America and Generic
    .br (Brazil)

    ftp://ftp.matrix.com.br/pub/kde (++)
    .cr (Costa Rica)

    ftp://ftp.ucr.ac.cr/pub/Unix/linux/kde (++)
    .com

    ftp://ftp.linuxberg.com/pub/KDE (++) (stable tree and apps only)
    .edu

    ftp://csociety-ftp.ecn.purdue.edu/pub/kde (++) (West Lafayette, IN, USA)
    ftp://canine.resnet.gatech.edu/pub/kde (+) (stable tree only)
    ftp://metalab.unc.edu/pub/Linux/X11/kde (+) (stable tree only)
    ftp://ftp.rutgers.edu/pub/kde (++) (US east coast)
    ftp://mirror.chpc.utah.edu/pub/kde (++)
    .net

    ftp://download.sourceforge.net/pub/mirrors/kde (++)
    ftp://ftp.archive.de.uu.net/pub/kde (+) (Germany)
    ftp://ftp.esat.net/mirrors/ftp.kde.org/pub/kde (++) (Ireland)
    ftp://mimas.germany.net/pub/master.kde.org (-) unstable only (Germany)
    .org

    ftp://ftp.us.kde.org/pub/kde (++) (Caldera Inc.)
    ftp://ftp.vlug.org/software/kde (++) (Victoria, BC, Can)

    Download (worldwide) by http
    http://ftp-stud.fht-esslingen.de/pub/Mirrors/ftp .k de.org/pub/kde (++)
    http://gd.tuwien.ac.at/hci/kde (++)
    http://www.cee.odu.edu/kde/ (++)
    http://download.sourceforge.net/mirrors/kde (++)
    http://ftp.eq.uc.pt/software/unix/KDE (+)
    http://ftp.matrix.com.br/pub/kde (++)
    http://ftp.fi.muni.cz/pub/kde (++)
    http://www.mirror.ac.uk/sites/ftp.kde.org/pub/kd e (++)
    http://www.uwm.edu.pl/pub/linux/distributions/sl ac kware (++) (Olsztyn)
  • Once KDE and Konqueror offer complete active X controls in a sane environment, that will be enough for me to switch from Gnome. I am constantly stuck having to either walk to a new machine or reboot just to administer my NT boxes, and it really is a pain in the ass.
    As for the look and feel of KDE, I really don't care for it. I prefer Gnome, I prefer the apps which are specific to gnome, and will continue to use gnome, especially if Helix ever gets it to install on Slackware any time soon.
    However, if I was to replace all the windows boxes in the company, I would most certainly choose KDE, as I feel it is a more business centric desktop, and the windows users wouldn't feel completely alienated.
    • Gnome or KDE on Slackware would be kinda hard without a good package management system... well, okay, not that hard... but it wouldn't be as easy to resolve dependancies with a system that doesn't have that capability.

      That said, I still use Slackware occasionally because I like compiling stuff from source and actually having control over what's on my system (not to mention the fact that I love the BSD startup system instead of the horrid SysV style.) :)
    • In my experience, kde's "feel" is a lot better. It is a lot more tightly intregrated. As for the look, I don't think any gtk theme can match mosfet's liquid theme. For the look it provides, you'd expect the traditional eye candy bloat, but it's actually really really fast. I also tend to like kde apps more because they tend to intregrate better with each other and the desktop.
    • Once KDE and Konqueror offer complete active X controls in a sane environment, that will be enough for me to switch from Gnome. I am constantly stuck having to either walk to a new machine or reboot just to administer my NT boxes, and it really is a pain in the ass.

      Since it really is Microsoft's fault for not using Java or something else portable for their admin tools in the first place, complain to Microsoft. Ask them to rewrite the NT admin tools to use standards, and/or to Open Source the ActiveX environment so that people can write tools for it (1) without expensive licences and (2) without putting their code at risk.

      Alternatively, use VNC, it's free and cross-platform.

      Final alternative, use the (ghasp) command-line tools. Many competent NT admins practically never leave the command line. You can even put up a telnet (if you are sure there are no sniffers on your LAN) or ssh daemon and use that.

      --OR-- since NT is such a PiTA to admin, ditch it.

      Put a Mandrake box in there and use your choice of WebMin or LinuxConf for web-based admin, or install one of the many other fine admin packages, or (ghasp again) use ssh and that dreaded command line. If you need to do that last from Windows, go to Google and type putty and click feeling-lucky. Small, secure, no DLLs, no problemo. Follow the link at the bottom of the page for a point-and-click Windows-based ssh file manager.

  • Man, they release versions quickly. It seems like I just finished compiling KDE 2.2! I really look forward to this one though, because 2.2 is great, and it can only get better.

    Maybe my netscape plugins won't segfault in konqueror this time :)

  • apt isn't a pancea (Score:3, Informative)

    by dvdeug ( 5033 ) <dvdeug&email,ro> on Tuesday September 18, 2001 @10:43PM (#2318355)
    Of course, apt won't install KDE 2.2.1 right now, since unstable has some library version problem (at least on my system.) Probably something got hung in incoming and it will just clear itself up in a few days.
    • Yep.

      You can, however, manually download and install kdelibs3_2.2.1-1.i386.deb and libarts_2.2.1-1.i386.deb from http://incoming.debian.org. After that, apt-get will be your friend again. :-)

      • thanks for the tip. those were the nasty little packages:) installed those manually, and now apt has only 51 more to go as i write. i guess this is to be expected being from "unstable" :) thanks a lot ivan! keep up the great work; it is much appreciated.

        i feel sorry for redhat users. i read a lot of posts about the dependency hell they went through on the upgrade to kde 2.2.
    • apt can only -get the packages that are available, or that the dependencies are fulfilled on. Debian is usually behind other distros when it comes to the latest software, but it's just rock stable and also very secure. Nothing else compares.

      I'm running Potato with KDE 2.1.2 and am very happy with it (using Mozilla0.9.4 as my browser, which is very nice). Woody will be out next year and KDE 2.2.1 with it. I can wait. :)
      • While Potato is most certainly behind other distros, Sid is definitely not. Potato is absolutely wonderful for servers, but I'm not sure why you'd want to use it for your desktop. Sid is, if anything, far ahead of all other distros when it comes to binary packages. They're there faster, they're better, and they're easier to install:)

        Besides, so long as you don't have a nightly dist-upgrade cron job, Sid is at the very least as stable as most other distros:)
        • I tried Sid (when KDE 2.2 first came out), and it worked more or less, but fonts were all screwed up and there were a couple of things that were broken ( I forget what now). I decided to just go back to Potato.

          I don't see any reason to upgrade until Woody is ready since I'm not missing anything. I have a mailserver/firewall on my DSL connection at mattyt.net and I access my mail there using Pine (from anywhere, even Windoze using PuTTY, gawd I love Linux!) and I also have IMP installed so I can get my mail through a browser.

          On my workstation, XMMS plays mp3's, smpeg-gtv plays .mpg's (I haven't found anything to reliably play .avi's, suggestions?), Mozilla0.9.4 is GREAT!, and KDE 2.1.2 is really nice. Yes, KDE 2.2.x is faster and has a few more features, but I have a 750mhz machine with 256mb so speed isn't really an issue and, as I said, I'm not missing anything.

          Sometimes Sid, or even Woody, breaks things and I'm tired of mucking about with things. Potato is just totally rock stable and provides everything I want, so I just use it.

          Cheers! :)

  • 2.2.1 Changelog? (Score:1, Redundant)

    by antdude ( 79039 )
    Anyone have it? No one in irc.kde.org seems to know at the moment. :)

    • Re:2.2.1 Changelog? (Score:2, Informative)

      by KeLp ( 2927 )
      Fortunatly they used the same naming scheme for their html files as they had for previous change logs :)

      http://www.kde.org/announcements/changelog2_2to2 _2 _1.html

  • Mirrors (Score:1, Informative)

    by nomis80 ( 181676 )

    The right URL for FTP mirrors would be http://www.kde.org/mirrors.html [kde.org].

  • Last stable release until February (Score:5, Informative)

    by infiniti99 ( 219973 ) <justin@affinix.com> on Tuesday September 18, 2001 @10:53PM (#2318385) Homepage
    According to this release plan [kde.org], KDE 2.2.1 will be the last stable KDE release for quite some time. Planned for release in February is KDE3.0, which will essentially be the same 2.x architecture but based on Qt 3.0 [trolltech.com]. They are going to call it KDE3.0 mainly because it will break binary compatibility with 2.x. It will not be a rewrite like KDE2 was.

    Of course, KDE is notorious for frequent releases, so I would imagine there will be betas / release candidates every 6 weeks or so until the final 3.0.

    Happy downloading/compiling/etc!
  • I didn't even realize it was just released, I went to the mirrors for 2.2 and saw 2.2.1
    RPMs upgraded smooth, without even a second thought with Caldera 3.1

  • Changes between 2.2 and 2.2.1 (Score:5, Informative)

    by CtrlPhreak ( 226872 ) on Tuesday September 18, 2001 @10:56PM (#2318401) Homepage
    Link:Changes [kde.org] Changes between KDE 2.2 and KDE 2.2.1

    This page tries to present as much as possible of the problem corrections that occurred in KDE between the 2.2 and 2.2.1 releases. The primary goals of the 2.2.1 release being more complete documentation and translations, the amount of code change is quite minimal - only the most critical bugs have been fixed, the rest of the development is currently being done in the branch that will lead to the KDE 3.0 release.

    General
    • Many improvements to translations and documentation
    kdelibs
    • arts: compile fixes, single threaded option.
    • KRFCDate: fix for eastern timezones.
    • KTempFile: fix for problem when fileExtension contained "X".
    • Improved checking for IPv6 support.
    • KPasswordEdit: slightly better in understanding non-ASCII characters.
    • KXMLGUI: fix for problem with reading xml file completely.
    • KFile: file preview fixes.
    • KHTML: Various html & CSS fixes.
    • Improved large file support.
    • HTTP: Better support for https through proxy.
    • HTTP: Improved handling of HTTP-cookies.
    • HTTP: Fixed security problem with abuse of HTTP POST.
    • Optimisations to improve KDE startup time.
    • KDED: All tasks can now be disabled through config file.
    • KSpell: support for Lithuanian and Belarusian.
    • KSSL: OpenBSD fixes.
    kdeaddons
    • User Agent plugin: various fixes.
    • Kate Plugins: made translatable.
    kdeadmin
    • KPackage: various fixes.
    • Kwuftpd: various fixes.
    kdeartwork No changes kdebase
    • Kate: corrected bug wrt last line.
    • Desktop Wallpaper: small fixes.
    • KControl: fixes for NetBSD & OpenBSD info.
    • KDesktop: fix problem with icon positions on desktop.
    • KDesktop: fixed sever bug where renaming a file on the desktop would destroy it.
    • Kicker: mini-pager can be used to switch desktop during drag&drop.
    • AudioCD: Vorbis fixes.
    • IMAP: Handle folders that contain # or ? in their names correctely.
    • SMB: Better error reporting.
    • Thumbnail io-slave: fixes.
    • klipper: changes in configuration file format.
    • Konqueror: compile fixes.
    • Konqueror:minor fixes.
    • Konsole: many fixes.
    • Konsole: added --noxft option to disable AA.
    • Konsole: added "tripple click" support.
    • KPersonalizer: Fixed bug that inadvertently turned "shade hover" on. (This makes the window roll up till only the title bar is left when the mouse is over the title bar for some time)
    • ScreenSavers: show screen saver in front of the desktop instead of behind it.
    • KSMServer: Provide error diagnostics for common KDE instalation problems.
    • KSysGuard: various fixes.
    • KWin B2 decration: fixes.
    • KWin: Fix for freeze with CDE-style alt-tab.
    • Netscape Plugin Scan: Don't crash on incompatible libs.
    kdebindings
    • Many updates.
    kdegames
    • KAtomic: Fixed various incorrect chemical names.
    kdegraphics
    • kdvi: various fixes.
    • kgv: small fixes.
    • kview: various fixes.
    kdemultimedia
    • Some compile fixes.
    • noaun: small fix.
    kdenetwork
    • KMail: various fixes.
    • KNode: Fix 1e9 problem.
    • KPgp: various fixes.
    KDEPIM
    • korganizer: small fix.
    • kpilot: fix syncing problems.
    KDESDK
    • kbabel: small fix.
    KDEToys
    • KScore: small fix.
    KDEUtils
    • Kab: compile fix.
    • Kpm: fix for Linux 2.4.
    KDdevelop
    • kdevelop: avoid khtml crash on restoring files also with KDE-2.2.0
    • kdevelop: gcc 3.0 compile fix.
    • kdevelop: Fix find dialog.
    • kdevelop: Various fixes.
    KDoc No changes.
  • Knode 0.61 in the newest KDE 2.2.1 takes too much time to connect to my news server. Kmail pulls email out of some public POP3 servers just fine, but it takes too much time to connect to POP3 of my ISP. I was playing with settings for POP3, it didn't help. The same problems I had in KDE 2.2. In a previous KDE ver 2.1.1 everything was OK. Still not sure are these things some bugs. Positive side: Konqueror is noticable faster here on this system, even for Athlon 1.2GHz.

  • objprelink (Score:5, Informative)

    by dimator ( 71399 ) on Tuesday September 18, 2001 @11:38PM (#2318483) Homepage Journal
    Don't forget the objprelink [att.com]. I've used it to build Qt and KDE 2.2 and it has made a difference. (Although windows is still faster, UI-wise.)

    • Although objprelink looks useful, I believe ELF shared libraries already do this for the calls that they make (via the Procedure Linkage Table). So, I think you could get a similar result by compiling your KDE applications as shared libraries. For example, konqueror's main() function would become konq_main(), and the konqueror program could be installed as a shared library, plus a trivial program for the actual konqueror executable:

      main(int argc, char **argv, char **envp) {
      return konq_main(argc, argv, envp);
      }

      The disadvantage of this approach would be that you would pay the other performance costs of compiling everything with Position Independent Code (-fPIC), but the advantage would be that you would probably break up the non-library part of the program into other libraries that might be useful to other programs.

      "Small programs; big libraries" seems to a common characteristic among the most popular Graphical User Interface systems. Maybe there would be an advantage to taking that to the extreme.

  • rpm hell (Score:2, Interesting)

    by acm ( 107375 )
    First I have to say that I am such a HUGE fan of KDE and am ever appreciative of the quality software that their team puts out.

    Unfortunately, it's been my experience that on Red Hat systems, KDE is impossible to upgrade. I'm not an expert linux user by any means, but I feel comfortable with most aspects of my system. None the less, when installing KDE I seem to find myself deep within the trenches of rpm-hell. Most replies to people with similiar afflictions seem to say, "well, find all the dependancies, it'll be good for you." However, after 50 or so .rpm's, and a seemingly ever-growing list, I gave up. Can you blame me?

    acm
    • kde is what made me switch from redhat to debian. There was so much KDE 1.x shit in RH 6.2 that I couldnt find and get rid of, that my built-from-source kde 2.1.1 would not work at all and hosed parts of my system.


      After using apt, I can't see why anyone would want to deal with "RPM hell".


      siri

    • bitch at redhat to make kde the default desktop
      • Good idea - please report this feature request in Bugzilla [redhat.com] in the "distribution" component.

        Maybe it'll make some of the people in control see reason. ;)

    • Only Red Hat (Score:2, Interesting)

      by ChrisWong ( 17493 )
      The problem is only with Red Hat, because they have decided not to provide KDE RPMs to upgrade their released distributions. Those RPMs you see for Red Hat are for their beta. You are expected to upgrade to the still-in-beta Red Hat 7.2 to get the latest KDE.
  • Are there any RPMs anywhere for RedHat 7.1 (seawolf)? The only ones on ftp.kde.org seem to be for 7.2beta (roswell)...

    • I figure the Roswell binaries should work on 7.1. I've been using Roswell, so I don't know for sure. You may have to update quite a few packages first. But there are binaries in Red Hat's Rawhide that you could try.

      ftp://ftp.redhat.com/pub/redhat/linux/rawhide/i3 86 /RedHat/RPMS

    • Re:RedHat binaries for stock 7.1 (seawolf) (Score:4, Troll)

      by Nailer ( 69468 ) on Wednesday September 19, 2001 @01:44AM (#2318695)
      /me mutters something *very nasty* about Bero

      If its like KDE 2.2.0, Bero built them for 7.2. If you're silly enough to be running the stable release, you should rebuild every SRPM by hand, and then install a bunch of nonstable non-KDE apps

      That's REALLY REALLY DUMB and is wasting vast quantities of everyone's time on the various KDE mailing lists.

      Go here [opennms.org] to get properly built, working 2.2 packages for 7.1. With any luck our mate ben should make 2.2.1 ones real soon.

      Otherwise, ask the Freshrpms [freshrpms.net] guy. Need a working package for anything for a Red Hat system? This guy is nice enough to take requests too.

      • I realize that this might be causing problems for some people, but there reasons are simple: timing issues.

        Try maintaining 215 packages while not giving up your own devel projects, and you'll know what I mean.

        If a day had 48 hours, I'd of course provide RPMs for 7.1, 7.0 and probably even 6.x - but the way things are now, I simply don't have the time to set up boxes with old systems to rebuild the packages and work around legacy compiler bugs (egcs 1.1.x is a pain).

        If you want to rebuild them, feel free to do so. In the mean time, I think it's more important to have a nice KDE in the upcoming release, so that's what I'm focusing on.

  • Mirror (Score:2, Informative)

    by Kevin DeGraaf ( 220791 )
    Mirror located here: kde-2.2.1 [calvin.edu]. Have fun!

  • QT 3.0 (Score:1)

    by acm ( 107375 )
    I have a question for any KDE developers/junkies out there. What are the advantages of porting KDE to QT 3.0? How will it affect the end user? Thanks.
    • QT 3.0 is supposed to have a universal component model QCOM (runs across windows/linux/os x). My understanding is that KDE 3.0 is not much more than a recompile against QT 3.0 thereby breaking binary compatibility with previous KDE compiled against QT 2.3.x. However, since QT 3.0 has a brand new component model, future KDE releases after KDE 3.0 could start taking advantage of it I suppose.

    • One of the main features is the bidi support - QT3 have full bidi support.

      .To show hebrew/arabic (and other right to left languages) properly , you must have bidi support.

      Currently , bidi support for linux is only provided by some hacks [iglu.org.il]. The KDE team did a good job when they added limited bidi support to konqueror so now we can browse logical hebrew websites. But once the KDE3 port is done, all the KDE/QT 3 applications will fully support BIDI (koffice too, hopefully).

    • One thing comes to mind that'll make my life a lot easier. GTK has separate cut-n-paste for the mouse buttons and the keyboard. IOW, Ctrl-V will only paste what you copied with Ctrl-C and the middle mouse button will only paste what you highlighted with the mouse. QT 3 will have this. In QT 2.3, they're not separated.
  • What!! No Mandrake 8.0 RPMS?!?!?! We've been disenfranchised!!!

  • Athlon ... (Score:3, Interesting)

    by purplemonkeydan ( 214160 ) on Wednesday September 19, 2001 @12:16AM (#2318561)
    I will now crawl back into my igloo and warm up next to my Athlon. It gets really hot from all this compiling.

    Hope that heat sink is on nice and tight. You know what happens [tomshardware.com] if it isn't ...
  • So how does one define a desktop PC anymore? My linux box does not look like your linux box does not look or feel like my co-workers linux box. The core may be the same, or damn close to it, but the part you interact with can be so many things these days that it makes my head spin.So, how do *you* introduce someone to "linux"? CLI, KDE, Gnome, Blackbox, Windowmaker or what? You almost know that when corporations start to adopt linux on the desktop that they are going to go with KDE for the most part, though Ximian Gnome may have a fighting chance in some arenas. But what about you, the non-corporate linux user? Where do you want to see the desktop go and why?

  • Distro elitism (Score:1, Flamebait)

    by ryanvm ( 247662 )
    Or you could just call out those 3 little letters that make ya feel so good ... a-p-t.

    Granted, this mention was fairly benign - but am I the only one who finds the Debian elitism around here just a little bit annoying?

    First Slashdotters ragged on everyone that didn't use Linux. Then that got boring and now everyone who doesn't use Debian is clueless. Let me guess, next target: GNOME users.

    Where will you people stop with your Taco worship?

    Oh and by the way - mod me as a troll, I don't give a fuck. I gots karma to burn.

    • Granted, this mention was fairly benign - but am I the only one who finds the Debian elitism around here just a little bit annoying?

      Nope. What's truly ironic about Debian is that it's supposed to be the purest form of Free Software, yet most of the Debian users I've talked to get irritated when I mention that I prefer compiling programs from source instead of just downloading a binary.

      • There's no way of putting this without seeming:

        • Smarmy
        • Elitist
        • Pedantic
        • Trivial

        ...But, you have heard of "apt-get source xxx", right?

        (Very VERY usefull in the frequently-named dependency-conflict situations above: Don't have a version of "foo" that works with "bar-1.2.3-10"? "apt-get -b source foo".....

    • First Slashdotters ragged on everyone that didn't use Linux. Then that got boring and now everyone who doesn't use Debian is clueless. Let me guess, next target: GNOME users.

      Nah, Linux itself is too easy for the elite. BSD is the way to go now.
    • It works well in Connectiva and Mandrake, both of which are RPM based. Which is a good thing, as RPM is the Linux Standard Base packaging system, and far more used.

      Debian's has some advantages in terms of packaging
      1. Lots of available packaged software
      2. A good set of packaging guidelines

      Neither issue is to do with packaging systems but rather higher level tools and other considerations.

      Red Hat could just as easily put KDE 2.2.1 in their up2date mirrors, but they don't. Which is a damned pity.
    • Granted, this mention was fairly benign - but am I the only one who finds the Debian elitism around here just a little bit annoying?


      I'm with you... I actually tried out Debian on an old machine because of the huge support it seems to have here. I don't know, I guess if you insist on running Linux, apt is a nice tool. But I still prefer the pkgsrc/ports collection for ease of use and graspability for newbies like myself.

      But hey, what do I know.

      (Incidentally, a good friend of mine who has been running Linux since before the 1.0 kernel is using Mandrake now. I wonder if the "gotta be l33t" posturing goes away after a few years?)

      --saint

  • Speaking of KDE... (Score:5, Insightful)

    by Teancom ( 13486 ) <david&gnuconsulting,com> on Wednesday September 19, 2001 @01:19AM (#2318657) Homepage
    I've been a Gnome + Enlightenment man ever since the 0.14 days of E and the initial betas of Gnome. *Hated* the whole KDE 1.x line, from the looks to the "usability" to the looks.... ;-) Anyways, I followed the party line, accepted that KDE was evil because of the whole QT thing, couldn't stand the looks (did I mention that?) and even when they started shipping themes, they were all butt ugly. Well, the 2.0 release rolled around, I heard good things, wasn't interested. 2.1 came, wackos were raving about konqueror on /., I was running sid so I said "what the heck" and installed it.

    Instant love.

    Kmail is the client that I've always wanted for linux, and could never find. It is the *only* client that has managed to pull me away from my beloved mutt. Nice. Clean. Simple. Stable. Luckily, I don't need imap support (though it has been in the last couple versions, it's pretty beta'ish), ldap, smtp-auth, or any other "esoteric" feature. Gpg-support works quite well, it just rocks *quietly*.

    Konsole was a delight. I had previously tried super-term (I think) that had the same basic idea (multiple terms in one window) but the interface was clunky enough it was unusable (at the time, haven't tried it in a couple years). shift-arrow to cycle through the terms, instant configurability (i.e., no editing Eterm config files by hand), again, just plain rocked.

    Konqueror. Don't really have much to say that hasn't already been said. About the only thing I *don't* use it for is managing files :-) Dunno if it's just habit, or if it's a failing in gui fm's, but if I want to move a file, I alt-tab to konsole, then "cp ~/fi[tab] /tm[tab]ba[tab]foo.gz" and I'm done. I truly can't imagine /any/ gui that could improve on that. But as a web browser, it is more stable than IE (not that IE is stable, but it still locks up on me occasionaly, whereas with the stable releases of KDE, a crash is noteworth), pretty standards compliant, and if it supported https through an authenticating proxy, I would be 97% of the way to removing all other browsers from my machine.

    Kdevelop and kde-designer (though that's not really a KDE project) rock my world. I am a crappy coder, and fairly inexperienced in c++, but I have been able to help out the main kpilot developer simply by recreating the kpilot config screens in designer, allowing him to focus on getting usb support up to speed rather than rewriting the interface. I know there are some old-school programmers shaking their head at these new-fangled gui toys that lower the bar so much, but anything that allows a newbie like me to help out with one of his favorite OS projects and actually make a difference (the next version of kpilot that ships will be with my GUI) is nothing but a good thing.

    Anyways, to make a long story short (heh), if you haven't tried KDE since the 1.x days, this is the time. You will be pleasantly suprised, and may even make the switch. If not, then happy Gnomeing, or BlackBoxing, or WindowMakering, or CommandLineCommandoing. Just have fun! The world is too great a place to worry about what other people are using for their desktop.

    • I truly can't imagine /any/ gui that could improve on that.

      Then try this: start Konqueror as a file manager, and select 'Open a terminal' from the 'Window' menu. And there, you have the best of both worlds. Of course, you can drag'n'drop files and directories from the FM subwindow to the terminal one. I still find it a bit rough (as of KDE 2.1 anyway), but it's a nifty feature that certainly has a brilliant future ahead of it! :)

    • Anyways, to make a long story short (heh), if you haven't tried KDE since the 1.x days, this is the time. You will be pleasantly suprised, and may even make the switch. If not, then happy Gnomeing, or BlackBoxing, or WindowMakering, or CommandLineCommandoing. Just have fun! The world is too great a place to worry about what other people are using for their desktop.

      What I've been doing for ages is pretty desktop-agnostic: I use WindowMaker because it's (IMHO) far cleaner than KDM or Gnome's WM, doesn't have any sign of a taskbar or "start/K/footprint" button and pretty much stays the hell out of my way.

      I've found a certain fondness for the rightclick on the desktop menu -- it takes no room and can be called up anywhere. The clip and dock are a bit of a pain in my arse but I think that's more because I haven't sat down in all these years and really tried to make them do what I want.

      One Dockapp I've been meaning to write for a long time now is a replacement for KDE and Gnome's "system tray" -- the docapp could hold 9 16x16 "systray" icons and would pass off the approprate mouseclicks/movements to the apps as normal. I've seen a few Dockapps that swallow other apps but it's not quite the same idea.

      One thing I wish I could have in any WM is the ability to bind keys to applications. I'd love to have my alt-backspace pull up the next LICQ message like I did in Windows but I haven't figured out a way to either make LICQ see the key nor have WindowMaker pass it off. Perhaps in my copious spare time I can figure it out. :-)

  • Training and Planning are the keys. (Score:4, Interesting)

    by foo fighter ( 151863 ) on Wednesday September 19, 2001 @02:56AM (#2318815) Homepage
    Linux is soooo ready for the desktop. I know this comes up every time KDE or Gnome are brought up, but it actually pains me to keep hearing ignorant arguments.

    The Windows 98SE desktop (and 2000, XP, etc.) in its default installation is not office desktop ready. There are several confusing or worthless icons that need to be cleaned up, display properties to adjust, shortcuts to create, etc. I've spent at least 40 hours honing my company's system images to get them 'just right'.

    I haven't used Gnome at work, and so can't comment on it. But I've set up KDE systems and it didn't take me near 40 hours to set up 'just right'.

    And guess what I found out? When I put new employees/users through their mandatory IT training they picked up on KDE at least as fast as with Windows. Most of these users have had very little computer experience.

    I wish I had better documented this when I started. But the users were able to use their word processor and spreadsheet, surf the web, check and send e-mail, print, use network storage and printers, and not fuck up their workstation at least as well on KDE 2.2 as on Windows 98SE.

    The key here, and the key that seems to be missing in all other discussions on this topic, is that the users were trained to use KDE. I don't know of any organization with a moderately organized IT system that doesn't have a training department or IT training of some sort.

    I've found it's easier to teach users Linux than Windows, so here's what all you code monkeys and sys admins need to do: teach the teachers linux. They'll see that it's easier to use and to teach and will back you up when you go to the CTO/CIO.

    KDE is great. It is ready for the desktop. Get your training department's shit together and teach users how to use linux. Plan and test the desktop and start menu so your people can use it. No one can figure out how to use a computer by just sitting in front of one, they need to be taught. It's easier to teach if you're the one who's set the system up.

    Honing our Windows images has dramatically cut Help Desk calls. I'm sure the Help Desk techs will be showering me with even more free lunches and drinks on them when Linux spreads throughout our organization.

    Get to it!
    • KDE is great. It is ready for the desktop. Get your training department's shit together and teach users how to use linux.

      You're forgetting the small matter of KDE not supporting MS Office

  • Well done, TurboLinux, KDE. (Score:3, Informative)

    by Karma Sucks ( 127136 ) on Wednesday September 19, 2001 @05:35AM (#2319028)
    "In response to customer demand, we have made KDE the default desktop environment in the latest release of our Turbolinux Workstation product," said Dino Brusco, VP of Marketing at Turbolinux Inc. "Our customers really appreciate the features and stability that KDE provides and we will be offering this latest version of KDE in an upcoming release of our Turbolinux Server product."

    (from: http://www.kde.org/announcements/announce-2.2.1.ht ml)

    Well, this just just goes to show that all that hard work from the KDE camp has paid off, despite poor advertising and marketing when compared to the competition. Good job all around!

Slashdot Top Deals

Arithmetic is being able to count up to twenty without taking off your shoes. -- Mickey Mouse

Close