After some delay caused by a severe hardware failure on KDE's ftp server,
the KDE Project has announced
the official release of KDE 2.2. This release brings a lot of goodies,
including: faster startup times (using the experimental
objprelink
method) and performance; numerous improvements to HTML rendering
and JavaScript support; the addition of IMAP support (including SSL and
TLS) to KMail; a new plugin-based print architecture with integrated
filter and page layout capabilities; a number of new plugins for Konqueror
(including a Babelfish translator, an image gallery generator, an HTML
validator and a web archiver); native iCalendar support in KOrganizer; and
a new personalization wizard. Compaq
has also announced the addition of KDE to
Tru64. Time to tell the boss to forget XP, and use KDE (hmmmm, back in my college days that would have made a nice chant: 'Forget XP, use KDE', . . .).
KDE 2.2 Ships (Visit an FTP Server Near You)
Dot Categories:
Comments
Yes I have a similar problem. I have rh7.1 I notice that kded is running twice when I do a
ps aux.
Hmm, what about switching to debian :)
Why don't you guys satisfy the RPM dependencies, that is what they are for!
If you install with --nodeps or whatever, yes you are bound to get problems.
Besides, there should be different RPMs for different versions (of your OS), and they should install smoothly. If not, ask the packager.
I agree a lot of dependecies to be satisfied but it is worth it. I use RedHat 7.1 and installed all the updates from the beta/roswell dir on one of the mirrors that where not in the non-kde dir except for python as that breaks my favourite card game pysol. I had to disable auth in /etc/fam.conf for programs to load corectly, I think that may be due to the fact I use ldap, anyone comment? DON'T use nodeps or force unless you are positive it won't break something you need.
I have had no problems except for cosmetic ones like icons missing etc and the system has been up 3 days so far. A few sites crash konq but that has always been there and java still does not work correctly with 1.3 from Sun, can anyone recommend one that does?
Good luck to all who go down this path, try it on a system that does not matter if you blow it away, not your production system until your are sure all is fine:-) On the other hand wait for 7.2 or what ever but you do have it backed-up don't you?
Colin
You may ignore the kdesupport dependency. RPM 4.0.3 has not been released yet as stable for RH71 by RedHat itself, although I did not run into any troubles without it (using --force and --nodeps).
libcrypto.so.2 and libssl.so.2 although are a little nastier. These are neede for HTTPS. What you might try is to create links from the openssl libraries, which might work ( it does for me ). OpenSSL is actually at 0.9.6b, and I really have no idea which library provides the correct dependency. Python you might only need if you actually use Python for scripting or you are developing with it yourself.
The biggest problem I ran into was installing FAM. Therefore see my site at http://www.aerie.at/rh71kde/
CU Roland
there is actually a non-kde directory that isn't off the RPMS dir, it is off a parent dir.
It has all of the packages you will need to support kde 2.2
Ev.
I'm aware of these extra files, they
did not solve many dependency problems.
Martin.
Last night new rpm came in for the non-KDE bunch. But two problems remain:
KPackage won't work with my (RH 7.1) rpm-package, the upgrade to the rpm-packages in non-KDE breaks dependency with glibc. No way here!
Second problem is although I have installed everything that lies below 2.2./rpm/redhat/7.x except of rpm-4.0.3-x there is _always_ a core-file in $HOME when logging out of KDE.
try this:
gdb -core $HOME/core. it will tell you what program (probably a non kde program since kde programs have crash dialogs) generated the core dump.
then do
gdb -core $HOME/core /path/to/program
and type 'bt'
and copy the output to a file and send it as a bug report to the maintainer of that program.
OK, I have the same problem with 2.1.1 (RH 7.1). This is the backtrace:
#0 0x40ccd00a in chunk_free (ar_ptr=0x40d75f00, p=0x34768) at malloc.c:3125
#1 0x40cccd59 in __libc_free (mem=0x808a7e0) at malloc.c:3054
#2 0x40c0a136 in __builtin_delete (ptr=0x808a7e0) from /usr/lib/libstdc++-libc6.2-2.so.3
#3 0x4077875d in QObject::~QObject () from /usr/lib/qt-2.3.0/lib/libqt.so.2
#4 0x4053799e in KInstance::~KInstance () at eval.c:41
#5 0x404d2e05 in KApplication::~KApplication () at eval.c:41
#6 0x40566f99 in KUniqueApplication::~KUniqueApplication () at eval.c:41
#7 0x4114ee62 in main () from /usr/lib/kdesktop.so
#8 0x0804a49b in strcpy () at ../sysdeps/generic/strcpy.c:31
#9 0x0804add1 in strcpy () at ../sysdeps/generic/strcpy.c:31
#10 0x0804b2a6 in strcpy () at ../sysdeps/generic/strcpy.c:31
#11 0x0804bff1 in strcpy () at ../sysdeps/generic/strcpy.c:31
#12 0x40c69177 in __libc_start_main (main=0x804bc20 , argc=2, ubp_av=0xbffffbfc, init=0x8049764 <_init>, fini=0x804c460 <_fini>,
rtld_fini=0x4000e184 <_dl_fini>, stack_end=0xbffffbec) at ../sysdeps/generic/libc-start.c:129
Looks like a delete[] problem, no ?
I'm in a similar (identical?) situation. Here's the details after upgrading sh-*, glibc*, and the other recommended rpms from rawhide;
$ file core;
"core: ELF 32-bit LSB core file of 'kdeinit' (signal 11), Intel 80386, version 1"
$ gdb ~/core
"... This GDB was configured as "i386-redhat-linux"..."/home/USERNAME/core":
not in executable format: File format not recognized
(gdb) bt
No stack."
Before updating glibc* and sh-* from Rawhide, gdb did report the same 12 line output as Biswa mentioned in his/her reply. For completeness, here are a few more details...
$ cat ~/.xsession-errors;
"DCOPServer up and running.
kdeinit: Shutting down running client.
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/USERNAME/.DCOPserver_localhost.localdomain_:0
and start dcopserver again.
---------------------------------
kdeinit: Communication error with launcher. Exiting!
KDE Daemon (kded) already running.
KLauncher: Exiting on signal 11
kdeinit: Communication error with launcher. Exiting!
connect() failed: : Connection refused"
Note that ~/.DCOPserver_* was removed after each crash before attempting to run KDE again. Runlevels were switched from 5 to 3 to 5 and ps and kill were used to locate and kill any stray DCOP processes before running KDE from gdm again.
Solved this; I didn't upgrade enough libraries. All (?) of the libs from non-kde and kdoc from noarch are required or kdeinit will crash with the current RH KDE rawhide rpms.
First, install everything from Redhat's update page to make sure that your system is current. Then install everything from the non-KDE directory except openssl* and rpm-*. After that openssl should install cleanly.
Then go to rpmfind.net and get and install the latest versions (Rawhide) of the following:
sh-utils
glibc
glibc-*
After that installing the latest rpm-* works with --nodeps (it still breaks gnorpm and a few minor things, maybe updating them would solve the dependency problems).
Then use --nodeps and --force to install all kde packages, as they still require efax, libsane and python2, which at least I don't need.
It works: I'm typing this in KDE2.2, which is wonderful by the way :) Thanks a lot, KDE folks!
Oh only a few details - just change glibc ! Ha, ha ha ! Doing in such way I can install even Microsoft Office on my RedHat ( but MS doesn't call its distribution "RH7.1 rpms" ). Can't all this stuff be succesfully recompiled on a standard RedHat distribution ?
> Then go to rpmfind.net and get and install the
> latest versions (Rawhide)
Rawhide is the unstable version of RedHat. It is not 7.1. Why KDE packages have been compiled for Rawhide and not for RH 7.1?
Hmmm...this seems to be common problem for
OSS sw developement.
I can understand that sw is developed using the not-yet-released tools and libraries, but usually,
when the product finally comes out - all required stuff has already been deliverd to endusers with
OS upgrades.
For developers/packagers I would like to make a wish, that when something is released, it should
install cleanly to latest *intact* OS (wether it is RH, Debian, Solaris, etc).
_That_is_sharing_the_responsibility_areas_.
If this kind of situation continues, we will never gain mainstream users from the EvilEmpire!
BR,
J
PS: I at least leave sw uninstalled if it needs removing original libs from system.
I would also suggest getting the Red Hat Raw Hide
FAM package (version 10) rather than the one in
non-kde, as this seems to fix some problems.
hehe...
nothing against KDE - but it sounds like you guys have a simple case of rpm hell...
I've never had a problem installing from source on an 'rpm-free' system...
(reminds of the little lady walking out of the house at the end of Poltergeist - 'this distribution is rpm-free' - *tears* *joy* *relief*
sorry... couldn't resist ;-)
I think it should be possible for the guys working on KDE (by the way, they are doing a great job!) to make rpms for standard installations (e.g. RH 7.1) and not for patched
or beta versions. Otherwise people like me (i think i am not alone), who like linux for years,
are getting tired about this mess. It would be sad if such a great project like KDE dies because
it's not possible to provide packages for different distributions. And to have different
ones is one of the great things on linux !!
I hope I'm sounding not too angry.
Bye
Do you even pay attention to the KDE developer community? The KDE developers DO NOT MAKE ANY binary distributions, including RPMS. They just release source. The individual distributions make the packages. If you must blame someone, blame the distro package maintainers, not the KDE developers.
Discovered the joy of Linux, and switched back to Windows. Linux is a beautiful operating system. You have the source code, you're in control. There's something for everybody. You don't have to pay extra for tools like Photoshop, it includes them. No program takes over a part of your system for its own advertising.
KDE is a great part of the OS, and it gets better with every upgrade. One goal is in mind, and that is to improve the experience. With Windows, it's to make $ by forcing people over to your technology.
After a little while, it becomes part of the next version of the distribution, and can be simply installed.
Plus, all the big distributions do have packages. Just download and install. If you read the instructions, installation goes smoothly.
There will always be those who want to be free. That's why as long as the medium (computers) exists, KDE will never die.
Read the README - you need to update to the packages in the non-kde directory. It has all the updates and extra packages our KDE 2.2 build depends on.
It also states you can safely use --nodeps if you're using a stoneage version of KOffice or anything else that requires kdesupport.
I tried, and go a dependency telling me my RH7.1 glibc is too old. If i upgrade that i guess the next dependency will be the kernel. Something is wrong here. The acclaimed RH7.1 packages are NOT for RH7.1 - it's as simple as that. It's a set of rpm's seemingly more tuned to the RH7.2 beta relase.
I tried to install KDE 2.2 on my system .After installing almost all dependencies (rpms), I have left with one rpm 4.0.3.rpm .When I tied to install it showed lot of other dependencies ,so I ommitted that and I installed KDE using --force option.Everything was okay till ,I tried to open kpackage which is dependant on latest rpm.After that Konqueror refuse to show up.Can anyone help me out
KDE team something similar to RedCarpet to overcome these issues
Not much you can do other than upgrade your RPM or downgrade your other packages. There's a reason they make you add --force to the command-line to install if dependencies fail; it often causes problems exactly like this.
I installed all latest rpms including glibc and rpm
I guess it is due to some other issue.When I invoked Konqueror from Ximian Gnome ,it worked fine.But it fails to show up from KDE.Any help !.
I just installed KDE 2.2 and I am pretty impressed by the overall first feeling. I could not figure out however how to turn off the fading of button texts in the taskbar, if the text is to long to be fully displayed. Any ideas?
It's not configurable.
Trying to use the audiocd slave i always encounter the error message "file or directory / does not exist" with kde2.2. Following the faq I tried "cdparanoia -vsQ" and I do see a track list for the audio cd.
ls -l /dev/sg0
"cr--r--r-- 1 root disk 21, 0 Aug 6 2000 /dev/sg0"
Oh yes, I am using scsi-ide emulation for a plextor cdrw.
try audiocd:/?device=/dev/sg0
(and if it does not work, try giving yourself write permissions also, and more important, you also need read access to scd0 i think)
audiocd:/?device=/dev/sg0 did not work (I had tried that before). I had to give write permissions to the normal user to make it work. Now I am trying to figure out how to convince the audiocd slave to use my http proxy for connecting to cddb...
Thanks for your help!
I believe there is a KControl module to configure the default cdrom device, CDDB settings, etc. It is Sound->AudioCD ?? (I'm trying to remember, I'm in windoze right now).
I had the same problems (root only was able to access the cdrom via audiocd:/)
Users who were / should have been;) allowed to play with the cd-dev are in group cdrom;
ls -l /dev/scd* ==> root.cdrom brw-rw----
Solution to this was:
I had to set /dev/sg* to the same perms like scd*, even when specifying that /dev/scd1 should be used (in kcontrol)
Hope this will help ...
Alex
That worked for me too....I'm using ide-scsi emulation, and changing the permissions for /dev/sg* works.... audiocd io slave is an awesome feature :-)
In the wonderful vein of users *always* clamoring for more, more, more: Does anyone know the new release date for KOffice 1.1 final?
Don't get me wrong - I am overjoyed at 2.2, I just really want to play with all the new printing in KWord, and shrug off the last bit of "VNC into the windows machine" that remains by converting all my files to KWord and KSpread.
--
Evan
http://developer.kde.org/development-versions/koffice-1.1-release-plan.html
Okay - color me dumb. Not only did I search for that, I *was* there, and misread it (either that, or it changed just recently). I read it as the final release occuring on the 12th. Thanks for the (repeated) pointer. ;)
--
Evan (Who is logged in as root under startx to look for Vorbis and docbook rpms... 2.2 soon!).
This is absolutely ridiculous! I am using Mandrake 8.0, and for what is supposedly a great integration, it is seemingly impossible to upgrade to 2.2! The never-ending heirarchy has mad me angry to no end! After an hour and a half of searching for this and that, and this and that, and then this and then that, I now have a headache and have given up! I don't plan on trying again either. This is exactly the type of thing that makes Gnome more attractive!
I think it's wrong to blame such problems on KDE, as I just moved from Mandrake (having similar experiances) to SuSe 7.1. Even though it's an old copy of SuSe (they're up to 7.2), the website still provides RPM's for KDE 2.2, and a lot of applications for download.
I download them, run:
rpm --nodeps --force -Uvh *.rpm
on the base files, and then the same later on the multimedia/koffice/apps stuff, restart the XServer, and I'm done. :-)
Mandrake has a great installer, but it drops you in a real mess when it's done.
If you have to use --nodeps and --force then your install is broken and you're not any better off running SuSE over Mandrake.
> and then the same later on the multimedia/koffice/apps stuff, restart the XServer, and I'm done. :-)
Yup... I downloaded the Vorbis RPMs from their site, and every dependancy except docbook_4 was satisfied. After installing with nodeps and force, it looks to work great (except antialiasing is broken on G400/dual head in new and amusing ways).
Anybody know what docbook_4 is (and/or wanna fix the G400 driver's antialiasing issues?).
Oh, and if it's not too much trouble, can the developers provide world peace, promote literacy and give us all a slice of cake with the next release? I think that's all that's left. ;)
--
Evan
I installed LM8.0 as it was so easy to get everything up and running. The ease of installation is however deceptive, as trying to do anything slightly out of the ordinary afterwards caused me endless headaches.
I have subsequently moved to Debian Linux and I am a happy camper.
Everybody .. move to Debian already :)
P.S. I have not used SUSE at all, so I have no idea how friendly SUSE is to upgrade
That's funny, 'cause I'm using must-pull-our-teeth-to-include-kde Debian and have been tracking the updates every couple days or so. And all it takes is a simple apt-get dist-upgrade.
Ok, so I'm a distro trolling bitch. Sue me. Moral of the story, blame the guys who *distribute* the binaries, not the guys who write the source.
Erik
Installing the Mandrake8 packages were in fact extremely easy. Just do
urpmi.addmedia kde22 file://directory-where-you-put-the-rpm-files
Then, for instance do 'urpmi kdebase' which will take care of any dependencies.
This was all in the README file accompanying the packages.
KDE 2.2 installation on my Mandrake 8 box couldn't have been easier. All I have to do was a "rpm -Uvh * --force --nodeps". Everything is working fine now and KDE 2.2 rocks.
Running MandrakeFreq 2 here and had no real problems.
I had a few dependancies crop up with Kdevelop and the dependancies had dependancies. So in the end i left Kdevelop out.
The only other dependancy problem i had was for the nsplugins; it required netscape-common and netscape isn't included with MandrakeFreq2. I installed it with nodeps since i have Mozilla 0.9.3 installed and it worked fine.
Other than that things are going great. There's been one crash of X caused by Konqi when trying to access hotmail (not sure what the exact problem was, i wasn't the one using it at the time).
I'm very impressed with 2.2 and my thanks go out to the KDE team for creating such a wonderful desktop environment.
Audio grabbing in Konqueror is a nice feature, but the binarey packages only come with ogg support and not with mp3 support too.
O.K. I understand, that for patent reasons the library for mp3 can't be included in the binary packages. But isn't it possible, that the grabbing IO-Slave autodetect at runtime if a mp3 library is installed? If it detect the library it can also show the mp3 directory. At the moment the library is only detected at compile time. I think a detection at runtime is much better because the grabbing IO-Slave needn't compiled and only the mp3 library must be compiled and installed in the system.
If autodetection at runtime is not possible, at least a small source package with only the source needed to compile the grabbing slave should be on the KDE download page.
Actually... it is.
You see, I haven't any mp3 encoding library, and no mp3 was shown in audiocd, but when I installed mp3encode, voilá! Audiocd detected it and show the mp3 option.
I think libmp3 from the lame project is used by the grabbing IO Slave. Hmm. What Is needed for mp3 grabbing in Konqueror?
In theory just a mp3 encoder installed on your system.
I'm lazy so I don't compiled lame, but found a encoder named mp3encode (hehehe what a name) and installed the rpm here, just it, nothing more, and then mp3 option shows up on kcontrol and konqueror audiocd kio.
I have lame compiled and installed but no mp3 option is shown by KDE. My opinion is that KDE needs libmp3 from the new lame versions. At least the KDE 2.2 beta version works after recompiling the grabbing slave with installed libmp3.
Mayby I should try with mp3encode. But first I must find mp3encode.