I've got one thing to add to this 3.2 thread. If you haven't already grabbed it, do it now! My install went off without any trouble (SuSE 9.0, using the supplementary KDE3.2 rpm's from ftp.suse.com). The only downsides that I've noticed: - no plugger - no suse help (big deal, I've got the manuals) - microsoft office mimetype bindings changed to koffice, rather than OpenOffice. All my love to the koffice team, but it's not really practical yet as an msoffice interoperability solution. Anyway, easily chaned those back. - Suse Icon theme disappeared. So the KMenu and the home directory and stuff look different now. No big deal. And the upsides, too many to list. Read them for yourself at www.kde.org, but certainly the main improvements for me are in the KDE PIM suite. KOrganizer, KArm, Kopete, KWallet, KMail, they all rock my world. thank you for listening... :) Craig

http://www.suse.de/de/private/download/linuks/index.html Zitat von "Paul W. Abrahams" :

On Friday 06 February 2004 1:34 am, Craig Ambrose wrote:

...

I've got one thing to add to this 3.2 thread. If you haven't already grabbed it, do it now! My install went off without any trouble (SuSE 9.0, using the supplementary KDE3.2 rpm's from ftp.suse.com).

Could you provide the complete URL?

Paul Abrahams

-- To unsubscribe, email: suse-kde-unsubscribe@suse.com For additional commands, email: suse-kde-help@suse.com Please do not cross-post to suse-linux-e

I don't know much about what particular problems happened with Paul's installation, but here's a listing of what I did, and on what sort of system, in the help that it will increase the chances of having a successfull KDE3.2 install. This is fairly long, so don't bother reading on if you're not interested. Firstly, I got all the RPM's I needed. I went here on the web: http://www.suse.com/us/private/download/linuks/index.html And selected my version of SuSE. I'm running a pretty fresh version of SuSE 9.0, only installed this week. I've done all the online updates, and installed a few extra programs via YaST, but that's it. The website then points you at various directories on the ftp server. I went and downloaded all the rpm's from: "KDE Base Packages": ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.0/base/ and "KDE Applications" ftp://ftp.suse.com/pub/suse/i386/supplementary/KDE/update_for_9.0/applications No doubt there are mirrors, but I didn't find any Australian ones and the download took almost 24 hours, despite ADSL crawling along at around 5Kb/s. Obviously I didn't need everything in the applications directory, but I noticed that there were a lot of almost core KDE packages there (kdemultimedia, kdepim) and a few snazzy apps I hadn't heard of, so I decided to get them all. When I had all the rpm's downloaded, I copies them all into a single directory on my hard drive, and tried (from within that directory). rpm -Uvh --test *.rpm The U is for upgrade of course, v and h are just for pretty output formatting. The --test ensures that nothing actually happens, this is just a trial run. The result was about 20 missing dependencies. So with that in mind, I opened the YaST software installer and starting searching for those packages. It's easier to check the box that says "provides" so that your package search also checks against what the package provides. In most cases, I simply found the packages I needed, and selected them for installation. In some cases, upon finding out what sort of software I was installing, I decided that I didn't need to install that particular kde application, so I removed it from my install directory. The end result. All dependencies were satisfied, except for kdebase-SUSE conflicting with kdebase. I'll clarify here, that I didn't use any packages from outside of the SuSE 9.0 distribution except for those that I downloaded initially from the SuSE server. I think that doing so would be unwise. I then logged out of KDE (just back to kdm), switched to a different virtual console (eg: CTRL-ALT-F3) and logged in as root. Then I removed the kdebase-SUSE package. rpm -ev kdebase-SUSE (I'm not sure I've got that package name right here, but you'll see what it is). A of conflicts popped up, for kde help packages, so I had to remove them too. No drama. Then, the big install. rpm -Uvh *.rpm No dependencies failed, but after preparing the installation I did get some errors that more than one package was trying to install the same file. These files looked like icons, and desktop links, and a few other things, and so I decided to take the plunge and do it anyway. To get rpm to push on despite the error, I used: rpm -Uvh --replacefiles *.rpm No other errors. Everything worked fine there. Then, don't forget to run SuSEconfig! After that, switch back to terminal 7, and login. Everything is new, shiny and sexy. The only slight downsides were things I mentioned in my previous post. I hope that helps others reproduce my good experiences. I guess that if you are at all concerned about it, just wait for SuSE to incorporate it officially. Craig

I've finally solved the sound problem, though I have no idea why the KDE 3.2 installation provoked it. I had to change an obscure setting in the driver for my sound card (a Via 8235), which I did via Yast.

What obscure settings? My soundcard stopped working after the KDE 3.2 final (Santa Cruz/Turtle Beach with the CS4614/22/24 CrystalClear SoundFusion Accelerator driver). Good thing I still had my old SB120, which works fine.

But since your installation was successful, let me ask whether you've encountered the other problems I've reported:

1. Are your Konqueror fonts tiny when viewing Google?

No, they look fine to me. Other then the sound card incident, I had no problems at all getting 3.2 installed. I even installed it while being in KDE. Yast took care of all dependencies.

2. Can you get an icon for Yast2 or Gaim?

I would guess that these icons were provided by kdebase3-SuSE, which had to be removed. When you go to the creator of the Crystal icons website (www.everaldo.com) and download and install the Crystal SVG set, you get them all back. You'll have two entries of the same icon set in your control panel though. If that bothers you, you might be able to just overwrite the Crystal folder (it's on /opt/kde3/share/icons) with the new icon set.

3. Another big irritant I forgot to mention: does your SuSE help still have a search function? Mine doesn't (and it did when I was running KDE 3.1.4).

I removed the link to SuSE help a while ago, now when I call susehelp a konqueror window pops up with all sorts of links, but no search. My guess, it was probably included in kdebase3-SuSE. It's really too bad that SuSE packed all those little things in a package which is dependent on KDE 3.1.x. Cheers, -- Sabine

On Friday 06 February 2004 20:11, Paul W. Abrahams wrote:

On Friday 06 February 2004 9:35 pm, Sabine wrote:

...

...

I've finally solved the sound problem, though I have no idea why the KDE 3.2 installation provoked it. I had to change an obscure setting in the driver for my sound card (a Via 8235), which I did via Yast.

What obscure settings? My soundcard stopped working after the KDE 3.2 final (Santa Cruz/Turtle Beach with the CS4614/22/24 CrystalClear SoundFusion Accelerator driver). Good thing I still had my old SB120, which works fine.

It was support for DSX, whatever that is. The three settings were 0(auto), 1 (enable) and 2 (disable). It was set on 0 and I changed it to 2.

The driver mentioned above doesn't offer this specific setting. It offers only something with OSS, some amplifier setting and a thinkpad related setting. Options are 0 and 1. I tried different settings, but it doesn't work. Oh well... it was worth a try though. Thanks for the tip. Maybe it's a problem with this driver itself or even the card (although it still works under Win2K). Cheers, -- Sabine

On Saturday 07 February 2004 10:23, Paul W. Abrahams wrote:

A useful test of what's going on is to run alsaconf (as root). As the last step in the configuration it tries to play a sound. Before I fixed my sound card settings, alsaconf would hang up when trying to play the sample. My guess is that it's unlikely that alsaconf will neither get stuck nor produce a sound.

Another useful test is to use the aplay program from a command line to play a wave file directly. That bypasses any KDE funninesses.

I turned arts off and ran alsaconf and picked my Santa Cruz Turtle Beach soundcard. This time it actually did produce sound. But only during the alsa setup, not through any application. I ran the alsconf on the old soundcard, had sound, then things got sort of mixed up (in /etc/modules.conf), so I removed the sound cards via yast, made sure this was reflected in modules.conf, disabled and enabled the sound in the KDE control center (I have no idea why I did that and it might not be necessary at all) and reinstalled the Santa Cruz (yast), and all over a sudden I had sound. I rebooted to see if it sticks, and it did. Now arts is running, and I have sound. First only the apps in kde played sound, but not xmms. Apparently an alsa plugin setting got changed, after fixing that I have my sound back. I really have no idea, why it worked now, since I did remove my sound cards before. The only new thing I introduced was that I stopped arts before I set up the soundcard. Maybe that was the trick? Anyways, it works now. Thanks for the tip with alsaconf, it made me look at this from a different angle. Cheers, -- Sabine

On Saturday 07 February 2004 4:15 am, Oliver Schwabedissen wrote:

Am Freitag, 6. Februar 2004 07:04 schrieb Dave Barton:

...

<Q> Unable to create installation source from URL 'ftp://ftp.gwdg.de/pub/linux/suse/ftp.suse.com/suse/supplementary/'. Details: ERROR(InstSrc:E_no_instsrc_on_media) <Q/>

Can anyone suggest where I am going wrong?

I get the same thing.

For server name enter: ftp.gwdg.de

For the directory enter:

/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_8.2/yas t-source

or for SuSE 9.0:

/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.0/yas t-source

Even using this I have never been able to get YaST2 to accept a new installation source via ftp using SuSE 9.0 i386. In SLP 8.X this worked just great. Best Regards. -- _/_/_/ Bob Pearson gottadoit@mailsnare.net _/_/_/ "The best way to get information on Usenet is not to ask a _/_/_/ question, but to post the wrong information." - Aahz' Law

On Saturday 07 February 2004 18:56, Paul W. Abrahams wrote:

On Saturday 07 February 2004 4:15 am, Oliver Schwabedissen wrote:

For server name enter: ftp.gwdg.de

For the directory enter:

/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_8.2/yas t-source

or for SuSE 9.0:

/pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.0/yas t-source

the leading / will break it :/ Please simply use pub/linux/suse/ftp.suse.com/suse/i386/supplementary/KDE/update_for_9.0/yast-source as path. Yes, bugreport exists .... bye adrian ********************************************************************** Adrian Schroeter SuSE AG, Maxfeldstr. 5, 90409 Nuernberg, Germany email: adrian@suse.de (1175 mails already received today.)

I had to use rpm -Uvh --force --nodeps but it installed perfectly! and is running great now! Dave On Wed, 2004-02-04 at 20:07, Alistair Parsons wrote:

Hi

setting yast to point to an ftp server is fine if you have broadband but..

for those without

download all the rpms via someones broadband :-(

from the folder run rpm -Uvh *.rpm

now the problem i had was i had to uninstall kde3base-SUSE first, which i did through yast, i had kde running all the time and the only glitch it cause was my kicker crashed.

also on SUSEs ftp server are the rpms for rekall, a most excellent database program that i strongly recommend.

Alistair

I downloaded arts-1.2 from ftp.kde.org, but even after I installed it on my SuSE 8.2 / KDE 3.1.5 system, apt still refuses to upgrade: The following packages have unmet dependencies: kdebase3: Conflicts: kdebase3-SuSE (<= 9.0) but 8.2-112 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. I suspect the kdebase3 in the 8.2-repository depends on kdebase3-SuSE for 9.0. Is there anything I can do to work around it? (Even if the SuSE people will proably fix it eventually.) /Lennart onsdagen den 4 februari 2004 21.49 skrev Richard Bos:

Op woensdag 4 februari 2004 21:07, schreef Alistair Parsons:

...

download all the rpms via someones broadband :-(

from the folder run rpm -Uvh *.rpm

You know that now might be missing some required rpms that are only provided by the base part on the suse ftp server (or cd or dvd). So, don't complain afterwards that some things don't work as expected!

To get your pkg administration right check the following:

The following packages will be REPLACED: kdenetwork3-mail (by kdepim3) kgamma (by kdegraphics3) kopete (by kdenetwork3-chat) The following NEW packages will be installed: flac gnokii taglib

I might be missing many....

-- Richard Bos Without a home the journey is endless

-- !++ ! Lennart Börjeson ! Partner, Developer ! Cinnober Financial Technology AB ! Industrigatan 2A ! S-112 46 STOCKHOLM ! Sverige/Sweden/Schweden/Suède ! mailto:Lennart.Borjeson@cinnober.com ! phone:+46-8-50304700 ! fax:+46-8-50304701 ! http://www.cinnober.com !--

On Thursday 05 February 2004 7:07 am, Alistair Parsons wrote:

setting yast to point to an ftp server is fine if you have broadband but..

Even with broadband, it still took me a very long time to download those KDE3.2 base packages from ftp.suse.com. The problem being partially a lack of an Australian mirror (that I'm aware of), and no doubt partially that everyone wants them at the moment. Whether that would work nicelly depends on the way that YaST works. If it downloads them all before installing (which I assume it does), as opposed to installing each one as it downloads it, then it wouldn't matter if I had a YaST instal' take an hour.

now the problem i had was i had to uninstall kde3base-SUSE first, which i did through yast, i had kde running all the time and the only glitch it cause was my kicker crashed.

The first thing I did with my new SuSE system was grab a bunch of new KDE rpm's and install them with rpm, and then everything crashed. I think the main problem was me not realising that in needed to run suseConfig. But also having to uninstal kde3base-SUSE removed some eyecandy and made me think that more things were broken. (all fixed now).

also on SUSEs ftp server are the rpms for rekall, a most excellent database program that i strongly recommend.

Thanks for reminding me about rekall, I really must hae a look at it. I do a lot of work with MySql and PostgreSQL, so a nice KDE front end would make my day. :) Craig

* user_2 [02-05-04 14:22]:

hi alistair i've tried to install the suse rpm for rekall but it asks for the "rekall database backend" . any ideas

Please do not top post and leave the full qoute under. Did you look for _all_ the rekall packages on SUSE? Something there might catch your eye. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org

On Fri, 6 Feb 2004 23:46, user_2 wrote:

sorry patrick i'm not much for riddles. i've been up and down the suse site without finding anything. i've been to thr rekall site and for some reason you can't download anything there although it says you can.

You can download rekall from http://www.rekallrevealed.org/ but you have to create an account first. Make sure you type in their dam security codes. It took me a while to work it out. -- Regards, Graham Smith ---------------------------------------------------------

On Friday 2004 February 06 16:40, Patrick Shanahan wrote:

* user_2 [02-06-04 08:05]:

...

On Thursday 05 February 2004 23.39, Patrick Shanahan wrote:

...

* user_2 [02-05-04 14:22]:

Did you look for _all_ the rekall packages on SUSE? Something there might catch your eye.

sorry patrick i'm not much for riddles. i've been up and down the suse site without finding anything. i've been to thr rekall site and for some reason you can't download anything there although it says you can.

-rw-r--r-- 1 mirror susewww 3619121 Jan 27 07:46 rekall-2.2.0.beta1-5.i586.rpm -rw-r--r-- 1 mirror susewww 33294 Jan 22 17:45 rekall-mysql-2.2.0.beta1-0.i586.rpm -rw-r--r-- 1 mirror susewww 50355 Jan 22 17:45 rekall-postgresql-2.2.0.beta1-0.i586.rpm

-- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org

thank you for your reply, patrick. with suse8.2 the beta1-3 rpm is recommended. the mysql component is the same as you noted. for suse8.2 there seem to be 2 versions of this mysql file one is 33k and the other 29k (same name-different sites), neither of which register with yast2 as installable. installing either of them outside of yast2 doesn't solve the problem. rekall still asks for a db backend. so that's the problem. any ideas? - robert