To: John Gay

2001-05-29 Thread Robert Tilley



Regarding upgrading a Potato Debian to Woody, I 
beseech you for aid!
 
Given your hints that there is a point in the 
installation process where you can choose to install Woody instead of Potato, I 
wiped my disk for the third time and proceeded with a reinstall.
 
Failure.  I noticed no point which was an 
opportunity to install Woody and ended up with a Potato box again.  I 
quickly fixed LILO to let me get back to Windows 2000 so I could e-mail this 
message.
 
I read over the installation manual included on the 
Debian CD in both HTML and PDF format with no enlightenment 
occurring.
 
Mommy, make Debian give me Woody!  Bahahaha -- 
Yes, I'm almost at the point of tears, at least metaphorically 
speaking.
 
Robert
 
P.S.  Nor can I find a document entitled "How 
To Select Potato / Woody / Sid" on GNU/Debian.
 
P.P.S.  Could you please send me your e-mail 
address again as the previous mail is on my Linux 
partition.


Re: Pre-compiled Quanta available?

2001-05-29 Thread Hendrik Sattler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday, 29. May 2001 23:51, Chris Howells wrote:
> Due to the fact that I'm having trouble compiling Quanta (it can't find
> -lssl), I'm wondering if it's possible to get a binary version of Quanta
> from anywhere?

did you try "apt-get install quanta" with one of the KDE2 sources?

HS
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.5 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7FDK8zvr6q9zCwcERAp4EAJ9r2MQEWPFb9h246EX5MSs3EXeYYQCdEu0t
FbkJBmlWOzzWENWX1/I/dD8=
=98Fk
-END PGP SIGNATURE-




Pre-compiled Quanta available?

2001-05-29 Thread Chris Howells
Due to the fact that I'm having trouble compiling Quanta (it can't find
-lssl), I'm wondering if it's possible to get a binary version of Quanta
from anywhere?

-- 
Cheers,

Chris Howells -- [EMAIL PROTECTED]
http://www.chowells.uklinux.net




Re: KDM Failure + Kcontrol errors

2001-05-29 Thread John Gay



>So, I shall write what modules fail:
>
>look & feel : system notifications
>sound:midi
>sound:sound server

These are all sound related. I'm no expert with sound, especially since I've got
an ISA card and had to load the modules manually to get it to work. My MIDI
still isn't working properly. This is probably due to the wrong modules, but I
prefer timidity++ to my cheep sound card MIDI devices anyway. I know that my
artsd didn't start up automatically anymore after I did my last dist-upgrade,
but when I installed the kdebase-audiolibs it started working again. There might
be other problems causing your sound troubles but I'm no expert with sound so
hopefully someone else can offer better advice.


>system:   login manager kind of disabled..broken kdm?
>
This is probably due to your kdm problems. login manager IS kdm. As I said, I
found gdm to be better because they have a way of registering window managers
with gdm and just installing a new window manager will update gdm. kdm, on the
other hand needs to be manually updated, though there was talk of setting up
some auto-update for kdm, I'm not sure how far that got.

>odd...
>
>If you do know a valid potato mirror..please send it to me..
>I'm compiling kde form source now, and it takes a while...
>I started yesterdaynight :)

I'll include this again, for completeness. There are probably others and Ivan
has said that there will be a new master site soon.
Hello:

I am a mirror maintainer of two sites that are shown in:
http://www.google.com/search?q=cache:wO2peEYStdk:kde.tdyc.com/+kde+tdyc&hl=en ,
i.e.:
-http://sapi.vlsm.org
-http://kambing.vlsm.org


>
>Euhm, about the potato getting dated..I agree to that but as long
>woody isn't seen as stable, people should take care for it too
>
Yes, woody, I.E. testing is not fully stable, however it is supposed to be
fairly close. Packages in testing are supposed to be free of release critical
bugs for some time before they are accepted into testing. This does not
guarantee that you won't have problems with it, but the problems you do have
should not be disastrous. Also, if more people are working with testing then
Debian gets more bug reports and can get more fixed faster. So the general
guidelines I follow are:

If you know very little about Linux, computer internals or just want rock-solid
operation without too many headaches and are willing to use dated software for
stability, then stick with stable.

If you are familiar with Linux and the general configurations and such, are
looking for recent software but still want a system that won't completely break
from time to time, you might consider trying testing. You shouldn't need to be
an expert to keep testing working and you will get more recent versions of
software. Also, your feedback to problems you do see with help the project
immensely I would not run a mission critical system on testing, but I run my
home system on Progeny, which is testing with some additions.

If you are a Linux or UNIX expert, enjoy working with the latest and greatest
and can live with the occasional broken system then unstable is probably what
you want. Especially if you have good bug squashing skills and can track down
bizarre problems. By no means run your regular system on unstable unless your
are willing to live without it and re-build it from time to time.

These are just my suggestions. I'm sure many others have their own views. After
all, Ivan's kde for potato was beta anyway. This was my understanding when I
started using his kde deb's on my system. Granted they were more stable than
most beta software I've seen, but they did have their occasional breaks, though
short-lived. So most people here should be forewarned and might want to consider
trying testing. The sooner we can iron out the bugs in testing, the sooner
testing will freeze and potato will become history.
And thus the circle of life continues, sorry Disney ; )

>Greetz,
>
>hdcool
>

Cheers,

 John Gay





Re: Problems Upgrading To Woody

2001-05-29 Thread John Gay


I'm glad my advice worked better than your last attempt. Unfortunately upgrading
X can be very tricky. I've had quite a few issues trying to get X4.x.x working,
but I think it's just the completely new design of X.

As I said, the Debian site should have installation instructions for each
version available. I don't have URL's at the moment because I'm at work and
don't have Internet access. Any version-update can be problematic. Debian seems
to be better behaved than most, though.

If the dist-upgrade to woody directly still gave problems, I would think the
next thing to try would be a fresh installation of testing directly. Again,
check for instalation instructions on Debians main site. Another option is to
try Progeny, which is Debian-based and headed by Debians founder. This is
testing with some really nice installation GUI's and fairly good autodetection
tools. The only down-side to Progeny is their latest KDE is 2.0.0-final. I
overcame this by pointing to Ivan's site and upgrading KDE from there, but with
that site gone, you will have to use one of the mirrors.

I hope this is of some use to you and good luck with the upgrade to testing.
It's not completely stable but it's supposed to be better than unstable had been
in the past. Feel free to ask me directly for any other help I can give. I've
also got a home address at:

[EMAIL PROTECTED]

They are both on this list so I can keep up with developments from work and at
home.

Cheers,

 John Gay





Problems Upgrading To Woody

2001-05-29 Thread Robert Tilley
Given that KDE is now a part of Woody and active development (or 
re-development by the illustrious Mr. Moore II has ceased) I have sought to 
upgrade my Potato platform to Testing.

Problem?

The first assay I did in these untested waters was to simply change all 
occurrences of "stable" in my sources.list file to "testing".  This led to 
multiple dependency problems when I did an apt-get upgrade.  There was too 
much work to do to correct my machine, so I wiped and reloaded.

The second time I followed some advice I had received and changed "stable" to 
"woody" then proceeded with an apt-get dist-upgrade.  This was better and I 
actually began the process of changing to XFree86 4.0.3 (which was my main 
goal, aside from KDE).  Problems arose again and given my frustration level 
at this and the lateness of the hour, I wiped and reloaded Potato.

This morning I decided to ask for help from the group.  Where are some 
instructions on safely and cleanly upgrading to Woody?  I know I can play 
around with my sources.list and apt-get but I would like to read some 
documentation that tells where to point apt-get and what procedure to follow.

Thank you for any information!

Robert "The Meticulous"
[EMAIL PROTECTED]




Re: Audio problems w/es1371

2001-05-29 Thread Casper Gielen
On Mon, May 28, 2001 at 09:36:31PM -0700, [EMAIL PROTECTED] wrote:
> 
> > > First, the freezing problem.  This primarly happens with the console
> > > beep in KDE2's 'konsole' program.  I can make the beep in konsole as
> > > many times as I like with no problems, but after a beep has been
> > > played in konsole, the sound driver goes into a weird state for around
> > > 30 seconds or more, where if any other program is loaded that tries to
> > > play sounds (xmms, snes9x, rocknes, and so forth) there will either be
> > > an error (rocknes says "Cannot find sound card"), or more commonly,
> > > the program will simply freeze hard for 30 seconds or so, and then
> > > start executing normally as soon as the driver decides it wants to
> > > work again.
> > >  

KDE has a special daemon to handle sound. When a KDE programm wants to
use the sound, the daemon locks the device and allows the programm to
play. Other programms can't play sound during this time and have to wait
until KDE is ready. When it is the sound deamon (artsd) goes to sleep
and another application can play sound.

-- 
Casper Gielen
[EMAIL PROTECTED], [EMAIL PROTECTED]
--
People just generally like to disagree. 
Bill Joy




Re: WM (KDE) themes - current plan

2001-05-29 Thread Junichi Uekawa
Ben Burton <[EMAIL PROTECTED]> immo vero scripsit

> John Galt raises an important point here.  I've posted small shots of all the 
> themes at http://people.debian.org/~bab/themes/ and I would love if people 
> could take a glance and point out any obvious copyright violations.  Some 
> themes are original, some are based on IceWM themes according to the author's 
> comments.


Your ITP only says they are GPL. It's not quite clear where things are taken 
from.

Reading the documentation this guy seems to have gotten a screenshot and 
changed color (MacBlue).
Matthe looks like an Aqua theme to me, and microGUI seems strikingly
similar to QNX.

However, "is looking similar to one" a big problem ? If so, sawmill
seems to contain a theme that resembles QNX, for example.


regards,
junichi

-- 
[EMAIL PROTECTED]  http://www.netfort.gr.jp/~dancer
-BEGIN GEEK CODE BLOCK-
Version: 3.12
GE d+ s:- a-- C+ UL P- L+++ E W++ N o-- K- w++ 
O- M- V-- PS+ PE-- Y+ PGP+ t-- 5 X-- R* tv- b+ DI- D++ 
G e h* r% !y+ 
--END GEEK CODE BLOCK--






Re: KDE and crypto

2001-05-29 Thread Christian Mayrhuber
Am Tuesday 29 May 2001 00:02 schrieb Ivan E. Moore II:
> JAVA SSL support requires a seperate JAVA package..or rather a "non-free"
> (I believe) .jar file from SUN's site...I don't remember the url off the
> top of my head...
You need the Java secure socket extensions from Sun if you are running
jdk 1.3.
The URL is: http://java.sun.com/products/jsse/
Extract the zip file, copy jcert.jar, jnet.jar and jsse.jar
to /usr/share/apps/kjava and restart Konqueror.

The good news is that these extensions are integrated in Java 1.4,
so hopefully SSL problems with Java applets in Konqueror will be a non
issue in autumn, when Java 1.4 is released.

-- 
WfG, Chris