Your message dated Fri, 12 Jan 2007 11:23:19 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#385089: network-manager-kde: fails to use kwallet after
boot
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: network-manager-kde
Version: 0.09+0.1r560817-1
Severity: normal
Hi,
I now tried this several times and everytime the same result:
- knetworkmanager starts
- kwalletmanager gets started and the wallet is opened
- I correctly enter the wallet password
These two are optional but actually mark the error:
- I click on my WLAN entry
- knetworkmanager cannot retrieve the PSK :-(
These are the steps to success:
- I quit knetworkmanager
- I start knetworkmanager
- I click on my WLAN entry
- knetworkmanager successfully gets the PSK from the wallet
I would rather like to have it working without manually restarting it.
Possible?
HS
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.8-yavin
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages network-manager-kde depends on:
ii kdelibs4c2a 4:3.5.4-3 core libraries and binaries for
al
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libdbus-1-2 0.62-4 simple interprocess messaging
syst
ii libdbus-qt-1-1c2 0.62-4 simple interprocess messaging
syst
ii libgcc1 1:4.1.1-5 GCC support library
ii libglib2.0-0 2.10.3-3 The GLib library of C routines
ii libhal1 0.5.7-2 Hardware Abstraction Layer -
share
ii libnm-util0 0.6.3-2 network management framework
(shar
ii libstdc++6 4.1.1-5 The GNU Standard C++ Library v3
ii network-manager 0.6.4-1 network management framework
daemo
Versions of packages network-manager-kde recommends:
ii kwalletmanager 4:3.5.4-1 wallet manager for KDE
-- no debconf information
--- End Message ---
--- Begin Message ---
Hendrik Sattler wrote:
> Am Dienstag 09 Januar 2007 17:42 schrieben Sie:
>> could you please install
>> http://debs.michaelbiebl.de/knetworkmanager/network-manager-kde_0.1-3~test1
>> _i386.deb
>>
>> It contains a patch which avoids a race condition where knetworkmanager
>> is started from autostart and the session-management.
>> Maybe that fixes your problem.
>
> The problem shifted a bit since filing the bug report. I didn't see it in my
> home network but e.g. when visiting my parents or a friend of mine where
> acquiring the network ip takes awfully long (~30 seconds from network
> selection to IP).
> That usually works by now, so actually the bug report should have been
> closed.
> But sometimes (long delay like 40 hours uptime), knetworkmanager forgets that
> it knows about the wallet: the "new network" dialog alwayscomes up and you
> have to restart knm.
>
> It seems to have wrong usage of the wallet, too, because a forced closing of
> the wallet should make it _impossible_ for knm to reselect the network
> without asking for the wallet password. However, knetworkmanager seems to
> cache the network WPA passphrase which is not a valid use of kwallet.
>
> As I already wrote, I removed the second wallet and IIRC I do not have this
> problem since then. However, at that time I also remove the knetworkmanager
> configuration file, thus the situation is probably different now.
> I may try the second wallet later again and will try your patch if that makes
> problems.
>
> You may close the bug report if you feel that the two situations above do not
> match it any more and I'll file new ones when I have good test cases.
Doing so. The first problem you describe sounds indeed like a caching
problem, or maybe a stale kwallet connection. Never experienced
something like that, though.
The second problem, with multipile wallets, is also separate issue.
If you could provide a good test case, so that I'm able to reproduce
this behaviour, that would be great.
> Maybe you know of a good method to debug this _when_ it happens?
That's actually very hard, as KDED/DCOP communication is involved here,
which complicates things quite a bit.
> Do you have the source somewhere? I would be interested what race condition
> that may be in the code and how it was solved. Maybe I can find hint for my
> other problems...
>
I just uploaded -3, so best grab the sources from there.
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
