Don't get me wrong, I'm not saying there aren't issues with the 2.2 release, because there are. I had konqueror crashing on me in the beginning, for example, and I've also experienced the sound server problem I've seen others talk about. It's just that he was saying that the packages were compiled 'without ssl support', which is clearly wrong, because if they were, there's no way it could function on my machine. Another person wrote in saying how he had fixed his problem with missing ssl support by changing a setting, yet Tim ignored all this, and kept insisting the packages were compiled wrongly. Anders On Friday 17 August 2001 00:23, Ben Rosenberg wrote:
Well, then there was a problem with SuSE's RPM's f**king up the configuration of an existing install of 2.2 Beta1 because it happened on my machine..worked with 2.2 Beta1..went to 2.2 Final and things changed. So clearly there was a problem. I downloaded the kde.org rpm's and over wrote the ones from the suse ftp site..doesn't matter who made them. It fixed the issue with out opening the kcontrol panel an mucking with settings that were already there. Just because one doesn't have doesn't mean another will not have an issue. Quite a few people have had issues. We can't all be having a mass delusion? *grin*
Cheers! It's fixed either way :)
* Anders Johansson (andjoh@cicada.linux-site.net) [010816 14:36]: ->Repeating a falsehood won't make it true. There has never been a problem in ->the suse packages with ssl on my machine. They have always worked on my ->machine. This is clearly a configuration problem. -> ->Anders -> ->On Thursday 16 August 2001 23:33, Timothy R.Butler wrote: ->> It looks like SuSE has updated the KDE RPM's today on their FTP site. I ->> wonder if SSL works now? ->> ->> -Tim -> ->-- ->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com ->For additional commands send e-mail to suse-linux-e-help@suse.com ->Also check the FAQ at http://www.suse.com/support/faq and the ->archives at http://lists.suse.com ->