[Bug 378145] Re: plasma widget networkmanager couldn't connect wpa
Yes, that version works (for the record I'm using an amd64 system). The next step would be to build and test different subversion revision to find where things start to break. -- plasma widget networkmanager couldn't connect wpa https://bugs.launchpad.net/bugs/378145 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 378145] Re: plasma widget networkmanager couldn't connect wpa
Great new (sort of). I've now installed Karmic and tested WPA-PSK and I'm now experiencing the same problem as you guys. Since the same version works for me in Jaunty the problem most be in combination with a new version of some other component. My guess is either wpa_supplicant or KWallet manager (since it kept asking me for a correct wpa key) is to blame, but I'll investigate this further. -- plasma widget networkmanager couldn't connect wpa https://bugs.launchpad.net/bugs/378145 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 378145] Re: plasma widget networkmanager couldn't connect wpa
Hi, would it be possible to test the new version again and attach your /var/log/daemon.log (only lines starting with Network Manager are interesting for me). (Between those two revisions I've got some patches committed that was supposed to get WPA to work, so I would be happy to see why it now fails for you) -- plasma widget networkmanager couldn't connect wpa https://bugs.launchpad.net/bugs/378145 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 378145] Re: plasma widget networkmanager couldn't connect wpa
I've looked at the log but Network Manger doesn't seem to report any problems. Only the same line about Association request to the driver failed makes me think this is not related to plasma-widget-network-manager. I've build the 0.0+svn966653-0ubuntu1 version from Karmic and it works without problems for me under Jaunty with WPA-PSK. Are all of you testing this on Karmic or Jaunty? -- plasma widget networkmanager couldn't connect wpa https://bugs.launchpad.net/bugs/378145 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 377399] Re: Latest update of plasma-widget-network-manager causes it to fail to connect to WPA2 network
Michael, would it be possible to test the new version in Karmic and attach your /var/log/daemon.log (only lines starting with Network Manager are interesting for me) since I've created some patches in the Karmic version that was suppose to help connecting to WPA2 networks. -- Latest update of plasma-widget-network-manager causes it to fail to connect to WPA2 network https://bugs.launchpad.net/bugs/377399 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 334052] Re: Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty
Brice: Acording to the connection log the settings seems to have been set correctly and accepted by Network Manager. Since other people have reported problems with the Intel wireless 3945 I don't think the reason that you fail to connect is related to this bug. It could be an issue with Network Manager or the driver. -- Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty https://bugs.launchpad.net/bugs/334052 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 334052] Re: Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty
I've changed the properties that the application sends to Network Manager so WPA-EAP with TTLS should now work. Can anyone experience problems using TTLS try version ppa3 in my PPA and report if it works. Also the changes also apply to WPA-EAP with PEAP so I would like if those who got PEAP to work with my previous versions also tested the new version to ensure it still works. I'm attaching a debdiff over the changes I made. ** Attachment added: Make the widget work with TTLS http://launchpadlibrarian.net/26630960/phase2auth.debdiff -- Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty https://bugs.launchpad.net/bugs/334052 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 334052] Re: Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty
Great news, both my patches has been commited upstream. But no new news on the ttls issues yet. -- Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty https://bugs.launchpad.net/bugs/334052 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 334052] Re: Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty
Hi, thanks for trying my fix with TTLS. In helping the troubleshooting can you provide parts of your /var/log/daemon.log log that shows all lines starting with NetworkManager when you try to connect. Also can you tell a little bit about your wireless connection like if your are using certificates. -- Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty https://bugs.launchpad.net/bugs/334052 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 334052] Re: Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty
I'm no expert on wireless security so perhaps someone else can answer on this but from looking at the man page of wpa_supplicant.conf (http://linux.die.net/man/5/wpa_supplicant.conf) and the knetworkmanager program there seems to be a difference between using security with WPA- EAP (as you do on plasmoid) and IEEE8021X (used on NM-APPLET). I don't think there are any support in plasmoid to configure the connection to use IEEE8021X so that may be the reason why it doesn't work for you. -- Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty https://bugs.launchpad.net/bugs/334052 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 334052] Re: Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty
Charles good catch! I've found that the widget stores the PEAP version settings as a string (one and zero) but tried to load it as numbers so the loading always failed and the default value 0 was always used. I've created a patched and updated my PPA (version 0.0+svn930811-0ubuntu3~ppa2) but testing this is not easy for me so if anybody could confirm that the patch works for peap version 1 would be great. ** Attachment added: peapver-parsing.debdiff http://launchpadlibrarian.net/24909444/peapver-parsing.debdiff -- Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty https://bugs.launchpad.net/bugs/334052 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 224220] Re: slow boot and network racecondition
I'm not sure since I reported this some time ago, but since then I've set dynroot to true and I think the slow boot symptom haven't appeared after that. So enabling that is a good workaround. -- slow boot and network racecondition https://bugs.launchpad.net/bugs/224220 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 334052] Re: Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty
I've created a patch which don't set the peaplabel setting when using peap version 0 and also don't set it when not configured (which currently is not possible using the GUI). I've patched plasma-widget-network-manager and uploaded it to my PPA. It works for me when using WPA-EAP with PEAP and MSCHAPv2 but I haven't tested it with any other configuration. ** Attachment added: phaselabel-fix.debdiff http://launchpadlibrarian.net/24301956/phaselabel-fix.debdiff -- Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty https://bugs.launchpad.net/bugs/334052 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 334052] Re: Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty
Details of how to use it here: https://launchpad.net/~hermansson- per/+archive/ppa -- Network Manager Plasmoid won't connect to WPA Enterprise AP's in Jaunty https://bugs.launchpad.net/bugs/334052 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to plasma-widget-network-manager in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 291263] Re: kvpnc: needs ability to add --script-security 2 to openvpn args
I've patched kvpnc to always start openvpn with script-security 2. Not sure if it's the best solution but at least kvpnc now works for me. I'm attaching a debdiff with the modifications I've made. The new version is also available in my ppa. ** Attachment added: script-security.debdiff http://launchpadlibrarian.net/23628464/script-security.debdiff -- kvpnc: needs ability to add --script-security 2 to openvpn args https://bugs.launchpad.net/bugs/291263 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 339014] Re: missing usplash screen in kubuntu jaunty
This also happens to me. But is a lite bit more serious since I use encryption and I never see it prompting for a password. My only option is too boot using recovery mode and enter the boot password that way. Since the usplash update is about the boot image I can mention that my monitor has a native resolution of 1400x900. If that is any help. I use Kubuntu and amd64. -- missing usplash screen in kubuntu jaunty https://bugs.launchpad.net/bugs/339014 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 339014] Re: missing usplash screen in kubuntu jaunty
Thanks, that worked! My native resolution was actually 1440x900 so entering that in /etc/usplash.conf worked. But the boot splash image looked really funny like a TV test image, is that normal? -- missing usplash screen in kubuntu jaunty https://bugs.launchpad.net/bugs/339014 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 325690] Re: udev has wrong name for devmapper devices, cryptsetup initramfs hook fails
I've installed the 138-1 version using the rescue mode from the install cd, but the system still fails to detect the luks partition. Any ideas on how can I troubleshoot this? -- udev has wrong name for devmapper devices, cryptsetup initramfs hook fails https://bugs.launchpad.net/bugs/325690 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 325690] Re: udev has wrong name for devmapper devices, cryptsetup initramfs hook fails
I've build and installed udev-137-3 from bzr but the boot still fails to detect my luks partition. -- udev has wrong name for devmapper devices, cryptsetup initramfs hook fails https://bugs.launchpad.net/bugs/325690 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 224220] [NEW] slow boot and network racecondition
Public bug reported: On rare ocation Ubuntu boots really slowly and after awhile the usplash boot screen disapears. Instead the terminal is shown and, amongst others, the following lines: Starting AFS service: openafs afsd. ADVISEADDR: Error in specifying interface addresses: No existing IP interface found. Since this problem isn't occurring every time one explanation might be some kind of race condition with starting my network interfaces. I'm attaching my 'messages' log file during the boot if it might help. Although the afs error doesn't seems to be specified in any log file (only in the terminal). ** Affects: openafs (Ubuntu) Importance: Undecided Status: New -- slow boot and network racecondition https://bugs.launchpad.net/bugs/224220 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 224220] Re: slow boot and network racecondition
** Attachment added: Boot log http://launchpadlibrarian.net/14014951/messages -- slow boot and network racecondition https://bugs.launchpad.net/bugs/224220 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 188380] Re: [Hardy] Eclipse applications show error Could not initialize the application's security component
This also happened for me each time I exited Rssowl using openjdk-6 in Hardy. Creating the ~/.mozilla/eclipse fixed the error. -- [Hardy] Eclipse applications show error Could not initialize the application's security component https://bugs.launchpad.net/bugs/188380 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 208267] Re: openjdk-6 path should be added to java_home
I can't start Eclipse 3.2.2 using openjdk-6 in Hardy since I get this message: A Java Runtime Environment (JRE) or Java Development Kit (JDK) must be available in order to run Eclipse. No Java virtual machine was found after searching the following locations: /usr/lib/j2sdk1.4-sun/bin/java Adding '/usr/lib/jvm/java-6-openjdk' to /etc/eclipse/java_home solved the issue. -- openjdk-6 path should be added to java_home https://bugs.launchpad.net/bugs/208267 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 122043] Re: backslash+pipe key \| misbehaving on english layouts if english not primary
I can confirm this for Swedish (default) + English in Gutsy. The bug appears only when the default (Swedish) is at the top of the list and English is below. When I switch keyboard to English the two keys \ and | behaves as the Swedish keyboard layout. The suggested workaround, with swapping the layout order, works for me. -- backslash+pipe key \| misbehaving on english layouts if english not primary https://bugs.launchpad.net/bugs/122043 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 117859] Re: Gutsy kernel 2.6.22 fails to mount /boot
How was this bug fixed? I'm having exactly this problem ever since upgrading to Gutsy. Purging evms didn't solve it for me. Any of my non lvm partitions fails to be mounted since the UUID links points to partitions in /dev/ and not in /dev/mapper. See my post: http://ubuntuforums.org/showthread.php?t=588474highlight=lvm+gutsy for further information of my system. I'm asking the same question as in the forum post: How do I update my uuid links to use the new path required by lvm? -- Gutsy kernel 2.6.22 fails to mount /boot https://bugs.launchpad.net/bugs/117859 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 153950] upgrade feisty to gutsy broken packages
Public bug reported: Binary package hint: update-manager I'm upgrading to gutsy trough the alternate CD. I have some dependency errors and the update step aborts. I've look in the apt.log and the only problem I see is dependency with ttf-dejavu-core (but I can be wrong): Starting 2 Investigating ubuntu-desktop Package ubuntu-desktop has broken dep on ttf-dejavu-core Considering ttf-dejavu-core 1 as a solution to ubuntu-desktop 0 Re-Instated ttf-dejavu-core Re-Instated ubuntu-desktop Investigating ttf-dejavu-core Package ttf-dejavu-core has broken dep on ttf-dejavu Considering ttf-dejavu 4 as a solution to ttf-dejavu-core 1 Holding Back ttf-dejavu-core rather than change ttf-dejavu Investigating ubuntu-desktop Package ubuntu-desktop has broken dep on ttf-dejavu-core Considering ttf-dejavu-core 1 as a solution to ubuntu-desktop 0 Removing ubuntu-desktop rather than change ttf-dejavu-core Done Installing ttf-dejavu-core as dep of ubuntu-desktop Setting NOT as auto-installed because its a direct dep of a package in section metapackages ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- upgrade feisty to gutsy broken packages https://bugs.launchpad.net/bugs/153950 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 153950] Re: upgrade feisty to gutsy broken packages
My upgrade log files. ** Attachment added: dist-upgrade.tar.gz http://launchpadlibrarian.net/10058424/dist-upgrade.tar.gz -- upgrade feisty to gutsy broken packages https://bugs.launchpad.net/bugs/153950 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 139713] planes spawn at different altitude
Public bug reported: Binary package hint: airstrike The red (left) plane spawns in the air, while the blue (right) plane starts on the ground. This gives an unfair advantage for the red player when playing player vs player matches. ** Affects: airstrike (Ubuntu) Importance: Undecided Status: New -- planes spawn at different altitude https://bugs.launchpad.net/bugs/139713 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 139713] Re: planes spawn at different altitude
The following patch fixes the hard coded spawn values so that player spawn at the same height above the ground. ** Attachment added: spawnfix.patch http://launchpadlibrarian.net/9284801/spawnfix.patch -- planes spawn at different altitude https://bugs.launchpad.net/bugs/139713 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 139329] Red plane has unlimited amount of bombs.
Public bug reported: Binary package hint: airstrike The red plane always has an unlimited amount of bombs. This can be tested when setting the left player to keyboard and repeatedly pressing the bomb button (default Tab). ** Affects: airstrike (Ubuntu) Importance: Undecided Status: New -- Red plane has unlimited amount of bombs. https://bugs.launchpad.net/bugs/139329 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 139329] Re: Red plane has unlimited amount of bombs.
The following patch fixes the bug by decrementing the bomb amount as done in src/sprite_types/blueplane.c. ** Attachment added: proposed solution http://launchpadlibrarian.net/9268661/airstrike.patch -- Red plane has unlimited amount of bombs. https://bugs.launchpad.net/bugs/139329 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 103148] Re: kinit: No resume image
It seems my swap partition has lost its UUID after upgrading to feisty. Both my swap, root and home partition are stored on a lvm partition. After my upgrade to feisty I get the same error at boot and freeze for a minute. When my computer later boots the mount command doesn't report any swap being mounted. Tried to check my UUIDs as suggested above: [EMAIL PROTECTED]:~$ sudo vol_id -u /dev/mapper/Ubuntu-Root d1cd2492-6b03-4476-96a9-c764c1770eff [EMAIL PROTECTED]:~$ sudo vol_id -u /dev/mapper/Ubuntu-Swap which returns nothing. -- kinit: No resume image https://bugs.launchpad.net/bugs/103148 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
