Is KDE 3.2 ready for prime time?
I just noticed a couple more posts (the ones about gaim and kbear) that suggest people are having a lot of trouble with KDE 3.2. For myself, it still is giving me big problems, most noticeably the fact that the desktops don't show up on the panel (the bar across the bottom of the screen). And my attempts to install it by several methods have been only partly successful. The problems have included but not been limited to dependency failures that I have few clues for resolving. If someone asked me at this point if they should install KDE 3.2, I'd say no. Whatever improvements it may provide are not worth the hassle of the installation problems. Unless you're one of those folks that likes living on the bleeding edge, of course. Paul Abrahams
On Wed, 4 Feb 2004 13:44:30 -0500
"Paul W. Abrahams"
If someone asked me at this point if they should install KDE 3.2, I'd say no. Whatever improvements it may provide are not worth the hassle of the installation problems. Unless you're one of those folks that likes living on the bleeding edge, of course.
Even if it is a pain to waste time in customization and I love well chosen defaults, you can have the pager back (and many other things as well just right clicking on the bar at the bottom, select Add->Applet->Pager... The "Control Center" is somewhere in the menu. I still have to look around. Till now everything is working including Kdevelop stable. I'll test more on the notebook before updating my development workstation. I thought I'd wait more SUSE build but at the end I updated at least one box today.
* Paul W. Abrahams (abrahams@acm.org) [040204 10:55]:
I just noticed a couple more posts (the ones about gaim and kbear) that suggest people are having a lot of trouble with KDE 3.2. For myself, it still is giving me big problems, most noticeably the fact that the desktops don't show up on the panel (the bar across the bottom of the screen). And my attempts to install it by several methods have been only partly successful. The problems have included but not been limited to dependency failures that I have few clues for resolving.
If someone asked me at this point if they should install KDE 3.2, I'd say no. Whatever improvements it may provide are not worth the hassle of the installation problems. Unless you're one of those folks that likes living on the bleeding edge, of course.
I had absolutely no trouble installing it on my 9.0 workstation in the office or on my 8.2 box at home. For some reason 3.2 makes the bass really sensitive..this may be an arts issue. I just turned down the bass a bit and I have normal sound. There are deps that 3.2 has that 3.1.5 didn't have but those are all on the ftp sites. I used apt in both cases to upgrade and it was pretty painless. -- Linux User #147972 ---===--- mailto:ben@whack.org -- "There is no need to teach that stars can fall out of the sky and land on a flat Earth in order to defend religious faith."
On Wednesday 04 February 2004 2:00 pm, Ivan Sergio Borgonovo wrote:
Even if it is a pain to waste time in customization and I love well chosen defaults, you can have the pager back (and many other things as well just right clicking on the bar at the bottom, select Add->Applet->Pager...
Thanks muchly for the hint -- that solved the problem. But it does raise the question: how is someone supposed to guess that "Pager" is what provides the desktop windows on the panel? Or even that the problem is solved by adding something to the panel rather than reconfiguring the panel in some non-obvious way? Paul Abrahams
On Wednesday 04 February 2004 2:00 pm, Ben Rosenberg wrote:
I had absolutely no trouble installing it on my 9.0 workstation in the office or on my 8.2 box at home. For some reason 3.2 makes the bass really sensitive..this may be an arts issue. I just turned down the bass a bit and I have normal sound. There are deps that 3.2 has that 3.1.5 didn't have but those are all on the ftp sites. I used apt in both cases to upgrade and it was pretty painless.
I tried to do it with apt, using the instructions on the apt4suse site particular to KDE 3.1 -> KDE 3.2, and I encountered dependency failures that killed the installation. I wonder what you did that I didn't do. The other methods that have been suggested are: 1. red-carpet (which I ultimately succeeded with) 2. rpm -Fvh ftp://ftp.us.kde.org/pub/kde/stable/3.2/ix86/9.0/*.rpm 3. Pointing Yast at the ftp location cited above. [2] failed consistently on a variety of errors, most often some globbing problem. [3] probably doesn't work at all because Yast2 expects some additional directory structure between 9.0 and the packages, namely, /suse/i586. It would be interesting to hear if anyone has actually succeeded with either [2] or [3]. Paul Abrahams
On Wed, 4 Feb 2004 15:10:39 -0500
"Paul W. Abrahams"
On Wednesday 04 February 2004 2:00 pm, Ivan Sergio Borgonovo wrote:
Even if it is a pain to waste time in customization and I love well chosen defaults, you can have the pager back (and many other things as well just right clicking on the bar at the bottom, select Add->Applet->Pager...
Thanks muchly for the hint -- that solved the problem.
But it does raise the question: how is someone supposed to guess that "Pager" is what provides the desktop windows on the panel? Or even that the problem is solved by adding something to the panel rather than reconfiguring the panel in some non-obvious way?
Well it always had that name... Actually today I've been brave... I wrote down the packages that apt was going to uninstall, realized it was nothing important to me, and on the second box everything went smooth and config were preserved. My development box is runnink KDE 3.2 and apt-get -s upgrade doesn't list any package ;) And I found some nice applet (dict and app launcher) that I find pretty useful, plus some nice style back after updating to new qt made them disappear in 3.14. Satisfied. Tomorrow I'll be enough in good mood to put up a Debian or FreeBSD development server :P
Paul,
stuff deleted
I tried to do it with apt, using the instructions on the apt4suse site particular to KDE 3.1 -> KDE 3.2, and I encountered dependency failures that killed the installation. I wonder what you did that I didn't do.
The other methods that have been suggested are:
1. red-carpet (which I ultimately succeeded with) 2. rpm -Fvh ftp://ftp.us.kde.org/pub/kde/stable/3.2/ix86/9.0/*.rpm 3. Pointing Yast at the ftp location cited above.
stuff deleted
I would be interested in knowing how you got red carpet to work. I followed the messages that Anders Johansson posted, but wasn't successful. I downloaded rug and rcd, started the rcd daemon. I ran rug install red-carpet and got the error message red-carpet not found in any subscribed channel. i saw the suggestion to run rug subscribe redcarpet2 as suggested by Anders, but got the message invalid channel. I tried numerous variations of redcarpet2, such as red-carpet2 red-carpet, redcarpet, always with the same error message of invlaid channel. If I try rug service-add http://opencarpet.org I get an error messaage related to SOAP. I am using SuSE 9.0 and kde 3.2. i upgraded to 3.2 by downloading the rpms from ftp.us.kde.org and using rpm -Uvh to install, so it isn't a question of getting 3.2, just of how to use red-carpet. Mike -- Michael A. Coan Woodlawn Foundation 524 North Avenue, Suite 203 New Rochelle, NY 10801-3410 tel 914-632-3778 fax 914-632-5502
Paul W. Abrahams wrote:
On Wednesday 04 February 2004 2:00 pm, Ben Rosenberg wrote:
I had absolutely no trouble installing it on my 9.0 workstation in the office or on my 8.2 box at home. For some reason 3.2 makes the bass really sensitive..this may be an arts issue. I just turned down the bass a bit and I have normal sound. There are deps that 3.2 has that 3.1.5 didn't have but those are all on the ftp sites. I used apt in both cases to upgrade and it was pretty painless.
I tried to do it with apt, using the instructions on the apt4suse site particular to KDE 3.1 -> KDE 3.2, and I encountered dependency failures that killed the installation. I wonder what you did that I didn't do.
The other methods that have been suggested are:
1. red-carpet (which I ultimately succeeded with) 2. rpm -Fvh ftp://ftp.us.kde.org/pub/kde/stable/3.2/ix86/9.0/*.rpm 3. Pointing Yast at the ftp location cited above.
[2] failed consistently on a variety of errors, most often some globbing problem.
[3] probably doesn't work at all because Yast2 expects some additional directory structure between 9.0 and the packages, namely, /suse/i586.
It would be interesting to hear if anyone has actually succeeded with either [2] or [3].
Paul Abrahams
SuSE's site provides the packages to upgrade to KDE 3.2 but the instructions on updating are vague and unhelpful. Following their instructions resulted in a broken KDE installation. One solution was to roll back to the KDE installation provided on the original DVD. Using YaST2, all KDE packages were removed and Gonme installed, even if some dependencies were broken. After this, the KDE was restored. After restoring to the default KDE, packages on KDE's ftp site were downloaded and installed. Instructions provided on the website are brief but concise. A few installed packages had dependency issues. These application were removed using YaST. For example, among other applications, K3B had to be removed. After this the installation when smoothly. KDE 3.2.1 was successfully installed and is a big improvement on KDE 3.1.4 or 3.1.5.
participants (5)
-
Ben Rosenberg -
Ivan Sergio Borgonovo -
LW999 -
Michael A Coan -
Paul W. Abrahams