KDE
Best regards to all on the list.
I'm new to Debian but not new to Linux. I installed "Sarge" on this
AMD Duron 1595 MHz Mem: 2567 system and was using KDE. Everything was
working nicely.
I had OpenOffice 1.1.3 but wanted to upgrade to 2.0.3 and assumed the
best way would be to use the package manager, (probably my first
mistake in this case). This was about 2 weeks ago.
I asked advice on irc.freenode.net #debian and was told that I'd need
to add backports.org to my sources.list and so I did, (probably my
second mistake).
I eventually did get OpenOffice 2.0.3, (after having issues with
dependencies such as java, but there were other libraries as well.
IL found that KDE had somehow lost all application entries from it's
Kmenu and was told I might be able to fix that by just updating KDE,
which I did.
So, the bottom line is that I updated a lot of stuff and at some
point, it seemed as if I was fixing things, but things took a downward
turn and lost KDE functionality.
I removed backports entry from my sources.list and installed gnome so
I'd have a working GUI again, and, well, that's pretty much where I am
at now.
I'd like to fix KDE and get back to the nice system I had before,
(even if I loose my OpenOffice upgrade). Not that Gnome isn't nice,
it's just that I prefer KDE.
SO, basically what I need to know is how is the best / easiest way to fix KDE.
Also, I don't mind having both Gnome and KDE on here, I'll probably
mostly use KDE, but may find the urge or need to run Gnome from time
to time as well. Hard drive space is not an issue.
I'm going to forward queries/answers as was sent/received from a LUG
that is also helping/trying to help, so you can get a better idea of
where I am at with this issue.
As a new Debain user, I have marveled at the ease with which I've
installed and upgraded applications - UNTIL, I upgraded OpenOffice
1.1.3 to 2.0.3
Not only did I have to manually enter a line in /etc/apt/sources.list
to use backports.org but ended up adding "contrib non-free" to all
lines that began with "deb ftp://...."; and "deb http://...."; (this
was to solve uninstallable dependency for java). I should note that
the "contrib non-free" additions need to be removed afterward for
apt-get to work properly for future updates and new application
installs.
It took several days for me to figure all this out and get
OpenOffice.org updated. I would have saved a lot of time by just
installing manually but was determined to use the package manager,
(for everything).
Part of the problem is that I had to cross version lines to get this
one application upgraded, (OpenOffice 1.1.3 is in sarge/stable while
OpenOffice 2.0.3 is in testing/unstable).
And the second problem was OpenOffice's requirement for java, and not
sure why that was such a problem, but I assume it is because can not
be kept in the normal repositories and can not be part of OpenOffice,
(because it belongs to Sun). If it hadn't been for that, things would
have been much easier I'm sure.
There may have been an easier way of doing what I just did, and being
new to Debian and it's idiosyncrasies was mostly what confounded me
and caused me to take so long to get the job done and maybe someone
else can shed some light on this subject so as to make it a bit easier
for the next new user that encounters this delima.
As far as I can tell, just upgrading OpenOffice manually is the best
or easiest route.
--------- Forwarded message ----------
From: Wayne Walker <wwalker@bybent.com>
Date: Aug 25, 2006 8:38 AM
Subject: Re: [NTLUG:Discuss] OpenOffice 2.0.3 upgrade - Debian
To: trryhend@gmail.com, NTLUG Discussion List <Discuss@ntlug.org>
You should complain LOUDLY to the debian folks. OpenOffice should Not
require java to install. As you saw, that causes lots of nightmares.
Lots of other distros install OpenOffice without Java. It works fine
without Java.
Wayne
On Fri, Aug 25, 2006 at 07:36:52AM -0500, Terry Henderson wrote:
As a new Debain user, I have marveled at the ease with which I've
installed and upgraded applications - UNTIL, I upgraded OpenOffice
1.1.3 to 2.0.3
Not only did I have to manually enter a line in /etc/apt/sources.list
to use backports.org but ended up adding "contrib non-free" to all
lines that began with "deb ftp://...."; and "deb http://...."; (this
was to solve uninstallable dependency for java). I should note that
the "contrib non-free" additions need to be removed afterward for
apt-get to work properly for future updates and new application
installs.
It took several days for me to figure all this out and get
OpenOffice.org updated. I would have saved a lot of time by just
installing manually but was determined to use the package manager,
(for everything).
Part of the problem is that I had to cross version lines to get this
one application upgraded, (OpenOffice 1.1.3 is in sarge/stable while
OpenOffice 2.0.3 is in testing/unstable).
And the second problem was OpenOffice's requirement for java, and not
sure why that was such a problem, but I assume it is because can not
be kept in the normal repositories and can not be part of OpenOffice,
(because it belongs to Sun). If it hadn't been for that, things would
have been much easier I'm sure.
There may have been an easier way of doing what I just did, and being
new to Debian and it's idiosyncrasies was mostly what confounded me
and caused me to take so long to get the job done and maybe someone
else can shed some light on this subject so as to make it a bit easier
for the next new user that encounters this delima.
As far as I can tell, just upgrading OpenOffice manually is the best
or easiest route.
--
Registered Linux User 188099
<><
_______________________________________________
http://www.ntlug.org/mailman/listinfo/discuss
--
Wayne Walker
- Hide quoted text -
On 8/25/06, Stuart Johnston <saj@thecommune.net> wrote:
According to the Debian bug reports, this is no longer the case with the version currently in
Testing. Keep in mind that when you install packages from backports.org, you are installing
unofficial, development versions.
Why is OpenOffice 2.0.3 in unstable/testing in the first place?
(Sholdn't it be in stable?)
On 8/25/06, Stuart Johnston <saj@thecommune.net> wrote:
According to the Debian bug reports, this is no longer the case
with the version currently in
Testing. Keep in mind that when you install packages from
backports.org, you are installing
unofficial, development versions.
Why is OpenOffice 2.0.3 in unstable/testing in the first place?
(Sholdn't it be in stable?)
That's not what 'stable' means (well... not exactly).
See:
http://www.debian.org/releases/
OpenOffice 2.0.3 is new.. thus only in the development side
of Debian.. which is called 'unstable'.
Now.. .if it finds its way into 'testing'... that's a
different story! (is it in 'testing'?... if so.. that's
a good thing).
On 8/26/06, Chris Cox <cjcox@acm.org> wrote:
Terry Henderson wrote:
> On 8/25/06, Stuart Johnston <saj@thecommune.net> wrote:
>> According to the Debian bug reports, this is no longer the case with the version currently in
>> Testing. Keep in mind that when you install packages from backports.org, you are installing
>> unofficial, development versions.
>
> Why is OpenOffice 2.0.3 in unstable/testing in the first place?
> (Sholdn't it be in stable?)
That's not what 'stable' means (well... not exactly).
See:
http://www.debian.org/releases/
OpenOffice 2.0.3 is new.. thus only in the development side
of Debian.. which is called 'unstable'.
Now.. .if it finds its way into 'testing'... that's a
different story! (is it in 'testing'?... if so.. that's
a good thing).
Yet another erroneous assumption on my part. I thought stable and
testing were just two names for the same category. Ok, now I realize
that stable and testing are two separate categories.
Reply to:
- Follow-Ups:
- KDE
- From: "Terry Henderson" <trryhend@gmail.com>