[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 299863] Network connections crashed when added wireless profile with wpa enterprise
From:       Anton Samsonov <avsco () mail ! ru>
Date:       2012-10-01 10:17:44
Message-ID: bug-299863-17878-DkGwakRuvu () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=299863

--- Comment #21 from Anton Samsonov <avsco@mail.ru> ---
(In reply to comment #0)
> Open network connections window, create a new wireless profile with WPA/WPA2 \
> Enterprise and save it. Crashes every time.

Artur, did you try to fill-in the "Identity" field, setting it to certificate's
Common Name (the body to which the certificate was issued to)? I have a similar
problem with NetworkManager 0.9.0.2 and found such a workaround.


(In reply to comment #18)
> Your new crash is still related to a problem in dbus library. You setup is probably \
> messed up or NetworkManager is crashing at some point.

Lamarque, in both our crash dumps (Artur's in comment 17 and mine from bug
307496) there are a couple of lines near the top of the call stack:
> 0x... in _dbus_abort () at dbus-sysdeps.c:94
> 0x... in _dbus_warn_check_failed (format=0x... "arguments to %s() were incorrect, \
> assertion \"%s\" failed in file %s line %d.\nThis is normally a bug in some \
> application using the D-Bus library.\n") at dbus-internals.c:290
I am not a skilled crash dump parser, but this message looks more like a
deliberate argument checking and early halting on encountered error, rather
than passing obviously incorrect parameters further to lower-level functions.
Although the presence of "%s" and "%d" placeholders introduces some doubts
about dbus' own sanity, I still suppose that dbus is not the one to blame,
since it really receives bad arguments. Isn't it the caller's responsibility to
provide a valid "Identity" parameter, whether explicitly defined by user or
implicitly looked up in the certificate?

-- 
You are receiving this mail because:
You are watching all bug changes.


[prev in list] [next in list] [prev in thread] [next in thread]