Re: [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

2015-01-14 Thread Nick B.
I tried that and it didn't work. This machine was upgraded and it only started after upgrading to 14.10 with no changes made to the network settings. Prior it was working as expected. On Wednesday, January 14, 2015 06:24:34 PM Søren Holm wrote: As state in a previous post: You can change

[Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

2015-01-14 Thread Nico R.
Same problem here on Kubuntu 14.10 on a Dell Latitude E6410 (Intel 5 Series Chipset). Everything worked flawlessly before the upgrade from 14.04 to 14.10. I also tried the supposed fix from #51, but that didn't help. -- You received this bug notification because you are a member of Kubuntu

[Bug 1317449]

2015-01-14 Thread Caulier-gilles-9
*** Bug 342802 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to digikam in Ubuntu. https://bugs.launchpad.net/bugs/1317449 Title: sqlite3 version 3.8.2 breaks digikam To manage notifications

[Bug 1397674] Re: Kubuntu 14.10 installation crashes

2015-01-14 Thread Wim
*** This bug is a duplicate of bug 1303790 *** https://bugs.launchpad.net/bugs/1303790 Hi, I had the same issue, my SSD was configured on the motherboard as the 3rd device. Trying several times to install Kubuntu 14.10 each time it failed as described above. I changed on the motherboard

[Bug 1410914] [NEW] When installing from liveCD, crashing on Keyboard Layout

2015-01-14 Thread EXL
CurrentDesktop: KDE Date: Wed Jan 14 13:03:56 2015 InstallCmdLine: file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Kubuntu 15.04 Vivid Vervet - Alpha amd64 (20150114) SourcePackage: ubiquity UpgradeStatus: No upgrade

[Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

2015-01-14 Thread Søren Holm
As state in a previous post: You can change whatever setting you'd like. It does not have to be the auto-connection setting. You can even change the IP-allocation policy from DHCP to Manual. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to

[Bug 1325801] Re: failed to boot from USB disk with error: gfxboot.c32: not a COM32R Image boot:

2015-01-14 Thread Yu Ning
Hi guys, attached is a patch which will sync the *.c32 files from host system to the target. With this patch I create a 14.10 usb stick on a 14.04 machine, and the usb stick can boot with Legacy BIOS successfully without any error. BTW, I wonder if we could fix this issue in a different way. Per