Tim,
Jaunty comes out in about 2 weeks now, and I'm not sure what the
process is going to be for us 3.5 users. What is involved for us in
the upgrade. I don't currently have KDE4 installed. When I upgrade
will it get installed or does it stay away. Do I have to edit my
sources.list file, or does it automatically get pointed to the 3.5
jaunty repo?
Can you tell us what to expect?
Thanks,
Michael
I've got another question. Again, my home system works well and my
laptop has trouble. Both run kde 3.5 on Ubuntu. The desktop is 64
bit and the laptop 32 bit.
When kopete starts on my laptop is can't connect to kwallet. It
prompts for passwords, then says that it can't save them securely.
This happens every time I log in.
On my desktop, kopete connects to kwallet fine. I get prompted once
for the kwallet password, and never again.
I don't even know where to start looking for the problem.
Michael
Another vote here for giving up on knetworkmanager - it doesn't work properly in 4.2 either, or not for me anyway, so I don't think there's much change of a working backport to 3.5!
I use wicd for jumping on and off wireless networks, but that is flaky too. At least it works, and if it doesn't you can see what command lines it tried to use which helps you troubleshoot.
regards
Zack
-----Original Message-----
From: B. Buchli [mailto:bbuchli@gmail.com]
Sent: Wed 3/11/2009 13:11
To: kubuntu-kde3.5-users(a)pearsoncomputing.net
Subject: Re: [kubuntu-kde3.5-users] knetworkmanager problem
Stefan Endrullis wrote:
> Hello KDE3.5 users,
>
> I'm very happy about the KDE3 PPA of Tim Pearson. All my KDE
> programs work, except the knetworkmanager.
> Therefore I wanted to ask you if you know a good solution for
> the knetworkmanager problem?
>
> My current workaround is to use knetworkmanager in combination
> with a shell script. First I tell knetworkmanager to connect to
> a specific WLAN, then I start my shell which does the same. By
> this procedure knetworkmanager recognizes the connection and
> all KDE programs are cheerful.
>
> Do you know an easier solution?
>
> Regards,
> Stefan
>
Knetworkmanager has been buggy for quite a while and only has caused me
troubles. My workaround is using nm-applet which works like a charm...
Hope that helps.
Ben
Hello KDE3.5 users,
I'm very happy about the KDE3 PPA of Tim Pearson. All my KDE
programs work, except the knetworkmanager.
Therefore I wanted to ask you if you know a good solution for
the knetworkmanager problem?
My current workaround is to use knetworkmanager in combination
with a shell script. First I tell knetworkmanager to connect to
a specific WLAN, then I start my shell which does the same. By
this procedure knetworkmanager recognizes the connection and
all KDE programs are cheerful.
Do you know an easier solution?
Regards,
Stefan
I have two systems, both running kubuntu 8.10 with the KDE 3.5
packages installed and no KDE 4.2. I'm very happy with this
combination.
On my desktop, I can use konqueror to browze info pages. If I enter
"info:grub" I'll see the grub manual.
On my desktop that doesn't work. Konqueror doesn't seem to know about
info:. Does anyone know what package I need to install to get this
working on my laptop, too?
Thanks,
Michael
