Version: (using KDE 4.3.0) Compiler: gcc ver. 4.3.3 OS: Linux Installed from: Debian stable Packages KDE 64 bit 4.2.2 (4.3 not a stable option in 64) - new updates made wlan inoperable, plasma crashes, persistent request for WEP key and crashes again soon after entry. plasma crash causing signal ?? error.
Wireless works fine from windows side - not a hardware issue. I am using a broadcom FW cutter on the linux side.
Would you specify the exact bug you're reporting? You're talking about both plasma crashes and the problem on the password dialog. I've changed the summary to the "persistent password dialog" (wich I've just had one hours ago on a notebook). If you want to report specific crashes too, you should report them separately specifying how reproduce them and providing a complete backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
One small note about the persistent password dialog: knetworkmanager ask for the wireless (WEP) password, and it doesn't connect, after some secods (about 20 or so) it ask the password again and again. I've had this problem using networkmanager-plasmoid-svn package from Archlinux AUR (trunk r1007572) and networkmanager 0.7.? Could the problem be the old version of networkmanager daemon?
Maybe. The correct thing to do would be try it with a different client that works and let me compare the connections on dbus as described at userbase.kde.org/NetworkManagement.
Ping
I have the same problem as FiNeX on Kubuntu Karmic. I tried to follow instructions on userbase and here is the difference between plasma-networkmanager and nm-applet (which works fine): nm-applet: qdbusfornm --system org.freedesktop.NetworkManagerUserSettings /org/freedesktop/NetworkManagerSettings/2 org.freedesktop.NetworkManagerSettings.Connection.GetSettings a{sa{sv}}(==802-11-wireless== mode: infrastructure security: 802-11-wireless-security seen-bssids: 00:12:0e:33:e0:58 ssid: WRT-311 ==802-11-wireless-security== auth-alg: open key-mgmt: none wep-key-type: 1 ==connection== id: Auto WRT-311 timestamp: 1256829592 type: 802-11-wireless uuid: 9b2a3fd5-8284-4fbd-945c-2d2314ba3b9a ) plasma: a{sa{sv}}(==802-11-wireless== mode: infrastructure security: 802-11-wireless-security ssid: WRT-311 ==802-11-wireless-security== key-mgmt: none wep-tx-keyidx: 0 ==connection== autoconnect: true id: WRT-311 type: 802-11-wireless uuid: 06edb630-e6ca-4178-809b-1a52bbccf31b ) It does not look too informative to me. Is there any other info I can get?
I'm re-purposing this bug since the original reporter never provided information and the later report shows a new bug introduced by NM 0.8 changing its interface. The setting that is missing in KDE's dbus: wep-key-type: 1 shows that unreleased NetworkManager 0.8pre changed interface and since I develop on openSUSE with 0.7.1 I was not aware of this until now. http://projects.gnome.org/NetworkManager/developers/settings-spec-08.html says that it means that the client can tell NM whether the key is hex or passphrase so NM itself can hash a passphrase.
I am also facing this same problem. I am on Kubuntu 9.10 , KDE 4.3.2 and the output of running the qdbus command is : knetworkmanager : (not working) [Argument: a{sa{sv}} {"802-11-wireless" = [Argument: a{sv} {"mode" = [Variant(QString): "infrastructure"], "seciant(QString): "802-11-wireless-security"], "ssid" = [Variant(QByteArray): {49, 57, 51, 52, 32, 35, 50}]}], "80-security" = [Argument: a{sv} {"key-mgmt" = [Variant(QString): "none"], "wep-tx-keyidx" = [Variant(uint): 0]}], = [Argument: a{sv} {"autoconnect" = [Variant(bool): false], "id" = [Variant(QString): "1934 #2"], "type" = [Va): "802-11-wireless"], "uuid" = [Variant(QString): "5bdd3f49-fee8-4c21-9e86-1ff7a7ddb288"]}]}] nm-applet (GNOME) (working): [Argument: a{sa{sv}} {"802-11-wireless" = [Argument: a{sv} {"mode" = [Variant(QString): "infrastructure"], "seen-bssids" = [Variant(QStringList): {"00:14:6c:50:8b:ae"}], "ssid" = [Variant(QByteArray): {49, 57, 51, 52, 32, 35, 50}], "security" = [Variant(QString): "802-11-wireless-security"]}], "802-11-wireless-security" = [Argument: a{sv} {"key-mgmt" = [Variant(QString): "none"], "auth-alg" = [Variant(QString): "open"], "wep-key-type" = [Variant(uint): 1]}], "connection" = [Argument: a{sv} {"uuid" = [Variant(QString): "0bf03017-c1f8-4246-8227-8dad48b2cdc8"], "id" = [Variant(QString): "Auto 1934 #2"], "type" = [Variant(QString): "802-11-wireless"], "timestamp" = [Variant(qulonglong): 1265228180]}]}]
Is this still happening?
(In reply to comment #9) > Is this still happening? No, and I am sorry I was too busy to produce a bug report. About that time I switched to Ubuntu desktop for some time. Several months later I tried Kubuntu again and the network worked fine. You folks do a nice job and Ubuntu/Kubuntu is the greatest OS I have ever experienced.