I'm sorry but I can't test it anymore because my university switched to a
different VPN infrastructure.
I can't test it with my old setup.
Should we close this bug?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to plasma-widget-networkmanage
Possibly related bugs:
https://bugs.launchpad.net/ubuntu/+source/plasma-widget-networkmanagement/+bug/474698
and/or
http://bugs.kde.org/show_bug.cgi?id=188489
** Bug watch added: KDE Bug Tracking System #188489
http://bugs.kde.org/show_bug.cgi?id=188489
--
[karmic] vpnc connections not connec
I can confirm this.
Seems like there's no GUI for entering the user and group passwords upon
connecting to the VPN.
It works if both passwords are stored in kwallet.
--
vpnc doesn't connect with empty user password.
https://bugs.launchpad.net/bugs/474698
You received this bug notification becaus
javielillo, in order to help you we need more information about the problem.
Could you please:
1. Make sure that you have an internet connection so that the client can
connect to your university
2. Start the VPN connection in knetworkmanager
3. Wait 10 seconds
4. Open the file /var/log/daemon.log
Public bug reported:
Binary package hint: plasma-widget-networkmanagement
If I click on my configured vpnc connection in the knetworkmanager menu,
it connects to the vpn but doesn't show that it is connected. This also
means that there is no button for closing the connection which should be
shown
** Attachment added: "part of daemon.log that shows networkmanager connecting
with vpnc"
http://launchpadlibrarian.net/35331444/networkmanager-vpnc-connecting.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35331445/Dependencies.txt
** Attachment added: "Xsession
I had the same problem. Is the package "network-manager-vpnc" installed?
If not, install it and restart (!!!) Kubuntu. -> The vpnc connection should
work now.
My current problem is that knetworkmanager doesn't show that the connection is
established. I click on my VPN in the context menu of the t
This was a bug in my computer's BIOS, not in Grub 2.
** Changed in: grub2 (Ubuntu)
Status: New => Invalid
--
Grub2 can't boot Windows 7, doesn't even know NTFS
https://bugs.launchpad.net/bugs/448889
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Updating the BIOS worked.
Thank you very much, Felix.
--
Grub2 can't boot Windows 7, doesn't even know NTFS
https://bugs.launchpad.net/bugs/448889
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Public bug reported:
Binary package hint: grub2
I have a SATA drive with the following partitions:
sda1 - (hd0,1) - ext4 with /boot from Ubuntu 9.10 Beta
sda2 - (hd0,2) - encrypted (Luks) LVM with swap, / and /home (both ext4)
sda3 - (hd0,3) - NTFS with Windows 7 Professional
Grub2 is installed
** Attachment added: "/boot/grub/grub.cfg"
http://launchpadlibrarian.net/33456515/grub.cfg
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33456516/Dependencies.txt
--
Grub2 can't boot Windows 7, doesn't even know NTFS
https://bugs.launchpad.net/bugs/448889
You recei
11 matches
Mail list logo