[Bug 604252] Re: system freeze before entering suspend
Same issue on my e6400. I had no troubles suspending with 2.6.35-20, with 2.6.35-21 it happened one but worked correctly afterwards. Now, with 2.6.35-22 suspend is definitely broken. Interesting enough, when I try to run 2.6.35-21 or 2.6.35-22 now, I can suspend/resume correctly when logged out of X, however running suspend from X/KDE session hangs. Logs from pm-suspend attached. The main difference I see is different initial parameters. ** Attachment added: successful suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/604252/+attachment/1626228/+files/s1 -- system freeze before entering suspend https://bugs.launchpad.net/bugs/604252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 604252] Re: system freeze before entering suspend
** Attachment added: hanged suspend https://bugs.launchpad.net/ubuntu/+source/linux/+bug/604252/+attachment/1626230/+files/s2 -- system freeze before entering suspend https://bugs.launchpad.net/bugs/604252 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 633568] Re: dhclient3 not recognize -4 option sent by network manager
I can confirm that the message Usage: dhcp... is no longer appearing in logs. With the latest package network-manager 0.8.1+git.20100810t184654.ab580f4-0ubun It is replaced by time out: Sep 20 20:06:15 note381 NetworkManager[991]: info (wlan0): DHCPv4 state changed nbi - preinit Sep 20 20:06:16 note381 dhclient: Listening on LPF/wlan0/00:22:fb:18:11:3a Sep 20 20:06:16 note381 dhclient: Sending on LPF/wlan0/00:22:fb:18:11:3a Sep 20 20:06:16 note381 dhclient: Sending on Socket/fallback Sep 20 20:06:16 note381 dhclient: DHCPREQUEST of 192.168.2.51 on wlan0 to 255.255.255.255 port 67 Sep 20 20:06:30 note381 dhclient: last message repeated 2 times Sep 20 20:06:30 note381 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 Sep 20 20:06:33 note381 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 Sep 20 20:06:37 note381 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 Sep 20 20:06:47 note381 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16 Sep 20 20:07:01 note381 NetworkManager[991]: warn (wlan0): DHCPv4 request timed out. Sep 20 20:07:01 note381 NetworkManager[991]: info (wlan0): canceled DHCP transaction, DHCP client pid 20840 Manual setup via iwconfig essid my_essid dhcp wlan0 still works without any problem. Should I file another bug report? -- dhclient3 not recognize -4 option sent by network manager https://bugs.launchpad.net/bugs/633568 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 633568] Re: dhclient3 not recognize -4 option sent by network manager
Thanks for your answer Serge. Are there any other dhcp clients available in maverick then? I though that dhcp3 is the only one. In that case, there is no need to detect it at runtime, right? -- dhclient3 not recognize -4 option sent by network manager https://bugs.launchpad.net/bugs/633568 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 633568] Re: dhclient3 not recognize -4 option sent by network manager
Probably related to Bug #527313, the -4 option was mentioned in one of the comments there. However, the workarounds mentioned there do not work for me. I have to stop NM and do iwconfig and dhcpclient manually. -- dhclient3 not recognize -4 option sent by network manager https://bugs.launchpad.net/bugs/633568 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 633568] [NEW] dhclient3 not recognize -4 option sent by network manager
Public bug reported: Binary package hint: dhcp3-client This is about interaction of nentowrk-manager and dhclient3 in current maverick. My wifi AP does not support IPv6, so the nm is trying to instruct dhclient not to use it. And apparently fails. Described in: http://pugio.net/2010/08/fix-dhcp-problems-in-networkmager.html My current syslog is: Sep 8 22:50:54 note381 kernel: [ 154.330060] wlan0: no IPv6 routers present Sep 8 22:51:27 note381 kernel: [ 187.330684] lo: Disabled Privacy Extensions Sep 8 22:54:55 note381 dhclient: Internet Systems Consortium DHCP Client V3.1.3 Sep 8 22:54:55 note381 dhclient: Copyright 2004-2009 Internet Systems Consortium. Sep 8 22:54:55 note381 dhclient: All rights reserved. Sep 8 22:54:55 note381 dhclient: For info, please visit https://www.isc.org/software/dhcp/ Sep 8 22:54:55 note381 dhclient: Usage: dhclient [-1dqrx] [-nw] [-p port] [-s server] Sep 8 22:54:55 note381 dhclient: [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val] Sep 8 22:54:55 note381 dhclient: [-sf script-file] [interface] ** Affects: dhcp3 (Ubuntu) Importance: Undecided Status: New -- dhclient3 not recognize -4 option sent by network manager https://bugs.launchpad.net/bugs/633568 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 329221] Re: valgrind --db-attach /proc/$PID/fd permission problem
This may not be valgrind specific. I see something similar with gdb itself: $ gdb (gdb) attach 1766 Attaching to process 1766 ptrace: Operation not permitted. Process 1766 is owned by the same user as gdb. -- valgrind --db-attach /proc/$PID/fd permission problem https://bugs.launchpad.net/bugs/329221 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 633568] [NEW] dhclient3 not recognize -4 option sent by network manager
Public bug reported: Binary package hint: dhcp3-client This is about interaction of nentowrk-manager and dhclient3 in current maverick. My wifi AP does not support IPv6, so the nm is trying to instruct dhclient not to use it. And apparently fails. Described in: http://pugio.net/2010/08/fix-dhcp-problems-in-networkmager.html My current syslog is: Sep 8 22:50:54 note381 kernel: [ 154.330060] wlan0: no IPv6 routers present Sep 8 22:51:27 note381 kernel: [ 187.330684] lo: Disabled Privacy Extensions Sep 8 22:54:55 note381 dhclient: Internet Systems Consortium DHCP Client V3.1.3 Sep 8 22:54:55 note381 dhclient: Copyright 2004-2009 Internet Systems Consortium. Sep 8 22:54:55 note381 dhclient: All rights reserved. Sep 8 22:54:55 note381 dhclient: For info, please visit https://www.isc.org/software/dhcp/ Sep 8 22:54:55 note381 dhclient: Usage: dhclient [-1dqrx] [-nw] [-p port] [-s server] Sep 8 22:54:55 note381 dhclient: [-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val] Sep 8 22:54:55 note381 dhclient: [-sf script-file] [interface] ** Affects: dhcp3 (Ubuntu) Importance: Undecided Status: New -- dhclient3 not recognize -4 option sent by network manager https://bugs.launchpad.net/bugs/633568 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357073] Re: doesn't resume from suspend, black screen and no response
I am getting the same behavior on Dell E6400, however only when the system suspends on its own (via power management). When I suspend it manually, it wakes up as expected. -- doesn't resume from suspend, black screen and no response https://bugs.launchpad.net/bugs/357073 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 446303] Re: Can't connect to network with WEP encryption
This is probably upstream bug 203266, https://bugs.kde.org/show_bug.cgi?id=203266 The cause of this behavior is change of dbus api between versions of nm. The main developer knows about the problem. ** Bug watch added: KDE Bug Tracking System #203266 http://bugs.kde.org/show_bug.cgi?id=203266 -- Can't connect to network with WEP encryption https://bugs.launchpad.net/bugs/446303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 446303] Re: [Karmic] [Jaunty] kubuntu network manager can't connect to network with WEP encryption
I can confirm that this bug still exists with plasma-widget-networkmanagement_0.9~svn1029786-0ubuntu1_amd64.deb nm-applet works without any problems. The difference is in the way they launch dhclient. I remember having similar problems in debian, where the issue was related to calling dhclient for ipv6 interface rather than ipv4. Relevant parts of daemon.log for plasma -network-manager: Oct 26 20:11:39 note381 NetworkManager: info Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Oct 26 20:11:39 note381 NetworkManager: info Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Oct 26 20:11:39 note381 NetworkManager: info (wlan0): device state change: 5 - 7 (reason 0) Oct 26 20:11:39 note381 NetworkManager: info Activation (wlan0) Beginning DHCP transaction (timeout in 45 seconds) Oct 26 20:11:39 note381 dhclient: Internet Systems Consortium DHCP Client V3.1.2 Oct 26 20:11:39 note381 dhclient: Copyright 2004-2008 Internet Systems Consortium. Oct 26 20:11:39 note381 dhclient: All rights reserved. Oct 26 20:11:39 note381 dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Oct 26 20:11:39 note381 dhclient: Oct 26 20:11:39 note381 NetworkManager: info dhclient started with pid 10355 Oct 26 20:11:39 note381 NetworkManager: info Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) scheduled... Oct 26 20:11:39 note381 NetworkManager: info Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Oct 26 20:11:39 note381 NetworkManager: info DHCP: device wlan0 state changed normal exit - preinit Oct 26 20:11:39 note381 NetworkManager: info Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) started... Oct 26 20:11:39 note381 NetworkManager: info Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete. Oct 26 20:11:39 note381 dhclient: Listening on LPF/wlan0/00:22:fb:18:11:3a Oct 26 20:11:39 note381 dhclient: Sending on LPF/wlan0/00:22:fb:18:11:3a Oct 26 20:11:39 note381 dhclient: Sending on Socket/fallback Oct 26 20:11:39 note381 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 Oct 26 20:11:43 note381 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 Oct 26 20:11:47 note381 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11 Oct 26 20:11:58 note381 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19 Oct 26 20:11:59 note381 wpa_supplicant[1313]: CTRL-EVENT-SCAN-RESULTS Oct 26 20:12:17 note381 dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 Oct 26 20:12:24 note381 NetworkManager: info (wlan0): DHCP transaction took too long, stopping it. The same for nm-applet: Oct 26 20:15:24 note381 NetworkManager: info Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. Oct 26 20:15:24 note381 NetworkManager: info Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... Oct 26 20:15:24 note381 NetworkManager: info (wlan0): device state change: 5 - 7 (reason 0) Oct 26 20:15:24 note381 NetworkManager: info Activation (wlan0) Beginning DHCP transaction (timeout in 45 seconds) Oct 26 20:15:24 note381 dhclient: Internet Systems Consortium DHCP Client V3.1.2 Oct 26 20:15:24 note381 dhclient: Copyright 2004-2008 Internet Systems Consortium. Oct 26 20:15:24 note381 dhclient: All rights reserved. Oct 26 20:15:24 note381 dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Oct 26 20:15:24 note381 dhclient: Oct 26 20:15:24 note381 NetworkManager: info dhclient started with pid 10486 Oct 26 20:15:24 note381 NetworkManager: info Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) scheduled... Oct 26 20:15:24 note381 NetworkManager: info Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. Oct 26 20:15:24 note381 NetworkManager: info Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) started... Oct 26 20:15:24 note381 NetworkManager: info Activation (wlan0) Stage 4 of 5 (IP6 Configure Get) complete. Oct 26 20:15:24 note381 NetworkManager: info DHCP: device wlan0 state changed normal exit - preinit Oct 26 20:15:24 note381 dhclient: Listening on LPF/wlan0/00:22:fb:18:11:3a Oct 26 20:15:24 note381 dhclient: Sending on LPF/wlan0/00:22:fb:18:11:3a Oct 26 20:15:24 note381 dhclient: Sending on Socket/fallback Oct 26 20:15:24 note381 dhclient: DHCPREQUEST of 192.168.2.51 on wlan0 to 255.255.255.255 port 67 Oct 26 20:15:24 note381 dhclient: DHCPACK of 192.168.2.51 from 192.168.2.1 Oct 26 20:15:24 note381 dhclient: bound to 192.168.2.51 -- renewal in 12667691 seconds. Oct 26 20:15:24 note381 NetworkManager: info DHCP: device wlan0 state changed preinit - reboot Oct 26 20:15:24 note381 NetworkManager: info Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled... Oct 26 20:15:24 note381 NetworkManager: info Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started... Oct 26 20:15:24 note381 NetworkManager: infoaddress 192.168.2.51 Oct 26 20:15:24 note381 NetworkManager: infoprefix 24
[Bug 426827] [NEW] krusader crashes on startup
Public bug reported: Binary package hint: krusader Krusader-dbg 1:2.0.0-1ubuntu2(amd64) crashes on startup with the following backtrace: Program received signal SIGSEGV, Segmentation fault. 0x00453cda in PanelManager::slotChangePanel (this=0xc34ca0, p=0x0) at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71 71 in /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp (gdb) bt #0 0x00453cda in PanelManager::slotChangePanel (this=0xc34ca0, p=0x0) at /build/buildd/krusader-2.0.0/krusader/panelmanager.cpp:71 #1 0x0045eb7a in KrusaderView::start (this=0xb2a7c0, leftTabs=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece. ) at /build/buildd/krusader-2.0.0/krusader/krusaderview.cpp:141 #2 0x0046e03d in Krusader (this=0x7fffcf50, __in_chrg=value optimized out, __vtt_parm=value optimized out) at /build/buildd/krusader-2.0.0/krusader/krusader.cpp:376 #3 0x0045baea in main (argc=value optimized out, argv=value optimized out) at /build/buildd/krusader-2.0.0/krusader/main.cpp:240 ** Affects: krusader (Ubuntu) Importance: Undecided Status: New -- krusader crashes on startup https://bugs.launchpad.net/bugs/426827 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 93062] Re: network-manager regularly loses connection
Hi Alexander, thanks for suggestion. I hope I understand it correctly... When the connection was lost, I manually changed essid and tried to reconnect to the correct network using network-manager. It was successfull. So far, no other loss of connection. Does it help? Vasek On 8/14/07, Alexander Sack [EMAIL PROTECTED] wrote: please try if unsetting essid with iwconfig manually before attempting to connect using network-manager helps. Thanks, - Alexander ** Changed in: network-manager (Ubuntu) Status: New = Incomplete -- network-manager regularly loses connection https://bugs.launchpad.net/bugs/93062 You received this bug notification because you are a direct subscriber of the bug. -- network-manager regularly loses connection https://bugs.launchpad.net/bugs/93062 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 93062] Re: network-manager regularly loses connection
Same behaviour here. It worked fine for the first time, but when I lost connection again it did not work anymore... In fact, I have about 1MB syslog file with most entries from NetworManager. Is it worth submitting somewhere? Or is there any specific message I should look for? There are quite a few lines containing keywords: Error, DISCONNECTED, timeout, etc. On 8/15/07, Mario Vukelic [EMAIL PROTECTED] wrote: I did a quick try too, when it lost connection (which, BTW, still happens every 2nd day or so, in Gutsy), but I didn't have enough time yet to be sure how much it helped. I ran sudo iwconfig eth2 essid off after losing connection, then tried to reconnected by picking my WLAN from the nm-applet list. At first I was happy since it seemed to reconnect immediately, but it re-lost connection just as quickly. I ran the cmd line again, but now reconnecting did not work. I tried a few more times, and it happened again that it reconnected but lost connection again immediately. I will try some more when I have time. -- network-manager regularly loses connection https://bugs.launchpad.net/bugs/93062 You received this bug notification because you are a direct subscriber of the bug. -- network-manager regularly loses connection https://bugs.launchpad.net/bugs/93062 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93062] Re: network-manager regularly loses connection
I also see this problem. The NetworkManager daemon tries to reconnect but somehow it fails. In order to recover, I must manually restart the daemon. Sometimes it takes two manual stop/start cycles to get my connection back. After that it runs fine. Daemon log attached. Note the last line: CTRL-EVENT-TERMINATING - signal 15 received ** Attachment added: d.log http://launchpadlibrarian.net/8141000/d.log -- network-manager regularly loses connection https://bugs.launchpad.net/bugs/93062 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90138] Re: knetworkmanager does not save password for WPA enterprise
The new package works all right for me. Many thanks gentlemen. Vasek -- knetworkmanager does not save password for WPA enterprise https://bugs.launchpad.net/bugs/90138 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for knetworkmanager in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 88400] Re: [Feisty] Sound card (HDA) no more detected after switching from -8 to -9
I am not sure if this is related, but many bugs were marked as duplicates of this one, so I am posting it here. My I82801DBICH4 does not work properly as well. More accurately, it works just fine on a fresh boot, however, after hibernate, or even soft-reboot (!) it breaks and no sound is produced. Following the guide at DebuggingSoundProblems, I generated all the files and tried to find differences. The only difference is different order of lines in lsmod and, of course, different dmesg. It is worth posting it here? Please advice me what else to try and report. -- [Feisty] Sound card (HDA) no more detected after switching from -8 to -9 https://launchpad.net/bugs/88400 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 90138] Re: knetworkmanager does not save password for WPA enterprise
Same behaviour here. Password is written into kwallet but it is not retrieved correctly. On 4/4/07, dystopianray [EMAIL PROTECTED] wrote: I tested the package with the fix and can confirm that it isn't working properly. The password is saved into kwallet correctly when you initially connect to the network. However, on subsequent attempts to connect it is not retrieving the password from kwallet. -- knetworkmanager does not save password for WPA enterprise https://bugs.launchpad.net/bugs/90138 You received this bug notification because you are a direct subscriber of the bug. -- knetworkmanager does not save password for WPA enterprise https://bugs.launchpad.net/bugs/90138 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 88965] Re: intel hda audio much too soft
I have the same problem with I82801DBICH4, though it doesn't work in 2.6.20-8 either. It was discussed on kernel mailing list: http://www.mail-archive.com/linux-kernel%40vger.kernel.org/msg107583.html and the recommended suggestion http://www.mail-archive.com/linux-kernel%40vger.kernel.org/msg107686.html was reported to work. Could this be related? -- intel hda audio much too soft https://launchpad.net/bugs/88965 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 90138] Re: knetworkmanager does not save password for WPA enterprise
I am running the latest update (1 hour ago) from Feisty repositories and the problem remains. I guess it has different cause. WEP keys do appear in kwalletmanager immediatelly after log in to the network. However, WAP Enterprise never appears in kwalletmanager. Is there any log I should provide? On 3/7/07, Anthony Mercatante [EMAIL PROTECTED] wrote: That's a well known issue between kwallet and kdeinit. It is fixed in feisty, since kwallet now writes all entries immediatly instead of on logout. ** Changed in: knetworkmanager (Ubuntu) Status: Unconfirmed = Fix Released -- knetworkmanager does not save password for WPA enterprise https://launchpad.net/bugs/90138 -- knetworkmanager does not save password for WPA enterprise https://launchpad.net/bugs/90138 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 90138] knetworkmanager does not save password for WPA enterprise
Public bug reported: Binary package hint: knetworkmanager Typically, knetworkmanager uses kwallet to store passwords. It works very well for WEP keys but it doesn't for WAP Enterprise. When I connect to WAP Enterprise, knm remembers the network (in OptionsShow Networks) but it does not create an entry in kwallet (Kwalletmanager does not show it in knetworkmanager branch). So, when knm attempts to connect to the network next time, it goes to infinite loop (or Very long timeout?). Workaround: 1) Delete the saved network in OptionsShow Networks 2) Switch to offline 3) Switch to online 4) connect to the same network this time the dialog for entering the password pups-up. ** Affects: knetworkmanager (Ubuntu) Importance: Undecided Status: Unconfirmed -- knetworkmanager does not save password for WPA enterprise https://launchpad.net/bugs/90138 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
