Thanks !
Over the years we have opened these bugs reports on the same issue:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1947770
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1992439
All of them should be closed when Noble will be released.
--
You received this bug
The bug is still present in Kubuntu 22.04 :( :(
If someone could have a look at this bug. Again, it is a security issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1510731
Title:
Bug in
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799550 is related.
There is still no way to install 22.04 in dual boot with windows on an
encrypted partition without having to use the command line.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
No progress with 22.04.
It is not possbile to install 22.04 alongside windows in an encrypted
partitiono without have to use the command line to create/open the luks
container.
This bug is more that 3 years old.
It is a severe security isssue as many users will end up installing kubuntu on
a
I don't know if the new installer will be ready for 21.10.
If that is the case then I do hope it allows encrypted installation with dual
boot.
This lack of feature is a blocker.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Any chance to see some progress on this topic in 21.10?
It should be possible to encryt / without having to play with the command line,
no matter if we are in dual boot or if we are not.
It should be possible to /create/open a encrypted LUKS container and to install
(k)ubuntu on it without
Read "no progress" and not "one progress"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083038
Title:
Encrypted LVM in Ubiquity unavailable when installing alongside an
existing OS
To
Still one progress on this issue with 21.04.
It is not possible to install an encrypted kubuntu 21.04 alongside windows in
dual boot **without having to use the command line**.
This is a *security issue* because non expert users won't be able to install an
encrypted kubuntu.
--
You received
I gave the daily kubuntu 21.04 a try : there is no progress on this
issue :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799550
Title:
No way to encrypt at partition level (dual boot)
To manage
What's the meaning of this tag?
Le jeu. 7 janv. 2021 à 17:41, Brian Murray <1799...@bugs.launchpad.net> a
écrit :
> ** Tags removed: rls-hh-incoming
> ** Tags added: rls-hh-notfixing
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
Thank you so much for the feedback!
Le mer. 23 déc. 2020 à 00:20, Julian Andres Klode <
1799...@bugs.launchpad.net> a écrit :
> I think the answer there is fscrypt - native encryption at the
> filesystem level supported by ext4 and some other day - but I'm not sure
> what the plans are.
Right.
https://bugs.launchpad.net/bugs/1799550 has been opened in 2018 to track
the dual boot issue. This is the security issue I was referring to. Sorry
for the confusion.
Le mar. 22 déc. 2020 à 22:30, Julian Andres Klode <
1773...@bugs.launchpad.net> a écrit :
> The issue reported here is that
No it is not a grub issue. It's an issue with the installer which does not
provide this option anymore. Wishlist..kind of but I think it is much
closer to a big security issue than to a wishlist. The net result is that
people do install kubuntu without any encryption.
Le mar. 22 déc. 2020 à
Well it's an issue indeed but the fact that no encryption is possible
without having to deal with the command line is much worst.
Le lun. 21 déc. 2020 à 22:15, Nodøn <1773...@bugs.launchpad.net> a écrit
:
> Encryption should also be possible without LVM. LVM is very good, but if
> you are using
I might work with the ubuntu installer 20.10 (to be confirmed) but it does not
work with the kubuntu installer. By 'it does not work' I mean 'the option is
not given'.
One has to create the LUKS, open it, then launch the installer and eventually
use chroot to make it work.
--
You received
No progress on this topic :(
It is still not possible to install kubuntu 20.10 encrypted in dual boot with
windows without having to deal with the command line.
This is a security issue as it forces many beginners to go for a non encrypted
installation.
--
You received this bug notification
No progress on this issue in 20.04 beta :(
There is still no way to install an encrypted kubuntu in dual boot without
having to deal with the command line. That’s a no go for many users.
I’m not even asking for full encryption. The kubuntu installer should at
least be able to install an
oups, no progress on *20.10 beta* (of course 20.04 wasn't better).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799550
Title:
No way to encrypt at partition level (dual boot)
To manage
Sad story.
This bug should be critical as it has large security impact. Encryption should
be the norm.
It shall be possible to install an encrypted (k)ubuntu without being techy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I would argue that it is a security issue as it will prevent new users
(typical dual boot users) from encrypting the data.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869575
Title:
Ubiquity
Public bug reported:
This bug exists at leat with 19.04, 19.10 and 20.04 beta.
With the ubuntu installer one can click on "do something else" and
choose "physical volume for encryption" to create an encrypted
partition. The installer nicely ask for the password and creates and
then shows
Any chance to see a fix in 20.04?
We need to be able to encrypt (k)ubuntu data when ubuntu is installed alongside
windows.
/home encrytion was not perfect but it was better than nothing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: ubiquity (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799550
Title:
No way to encrypt at partition level (dual boot)
To manage
I thought that 18.04 still offers the option to encrypt /home but I was wrong :(
"Ubuntu 18.04 LTS and newer Ubuntu versions no longer include an option in the
installer to encrypt the home directory. This option was removed from the
Ubuntu installer because it uses eCryptfs, which is considered
The issue remains the unchanged with 19.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799550
Title:
No way to encrypt at partition level (dual boot)
To manage notifications about this bug go
The issue remains the same with 19.10 (beta I tried yesterday).
The 19.10 Kubuntu installer cannot install an encrypted kubuntu in dual boot
with e.g. windows10.
It is still possible to setup such an encrypted kubuntu but it requires
to chroot after the installer has finished its job and to
Agreed.
"Full-system encryption needs to be supported out-of-the-box" full system shall
mean 'the Linux partitions' an not 'the full disk'.
In 19.04 it is not possible to install an encrypted kubuntu in dual boot with
windows10 without playing with the command line.
It means that no users new
Any change to be able to install an encrypted Ubuntu 19.10 alongside of a win10?
I don't know if /boot should be encrypted but not being able to encrypt
anything out of the box in 19.04 is a security regression. Crypaetup may not be
perfect but it used to be good enough in many usecases.
--
Thanks!
https://blog.botux.fr/fr/2015/02/installation-ubuntu-utopic-14-10-encryption-manuelle-lvm-on-luks/
is wrong towards the end.
Nothing special is needed in /etc/default/grub and /etc/initramfs-
tools/conf.d/cryptroot shall not be created.
Simply put
CryptDisk UUID= none luks in
Because I followed an old and probably outdated documentation.
Should I remove the lines in /etc/default/grub and in
/etc/initramfs-tools/conf.d/cryptroot completely?
My current /etc/crypttab read:
CryptDisk UUID=c9deed35-610e-4328-b8e7-079e95d43f76 none
luks,retry=1,lvm=lvm-vg Is it correct?
/etc/crypttab
CryptDisk UUID=c9deed35-610e-4328-b8e7-079e95d43f76 none luks,retry=1,lvm=lvm-vg
/etc/default/grub
GRUB_CMDLINE_LINUX="cryptopts=target=CryptDisk,source=/dev/disk/by-uuid/c9deed35-610e-4328-b8e7-079e95d43f76,lvm=lvm-vg"
/etc/initramfs-tools/conf.d/cryptroot
"we are hoping the installer will support this out-of-the-box in the next
release."
That would be nice because it is a regression compared to 18.04 which was
(IIRC) the last version offering a simple way to encrypt /home in the
installer. As the swap should also be encrypted, the simplest way
It should be fairly simple to silence this warning. If cryptsetup is a script
it should even be possible to find a simple workaround before an official fix
is release.
The question is : which options are correct and which one should trigger a
warning??
In case of a lvm, are we supposed to
Ok it is a feature request but I see it more as a security regression.
It used to be possible to encrypt /home in one click in the installer. This
feature does not exist anymore and (I assume that) many users simply gave up
and installed an unencrypted (k)Ubuntu.
It is possible to install an
To Paddy Landau : Your link is a variant of
http://blog.botux.fr/en/2015/09/ubuntu-installation-manual-full-disk-encryption-lvm-on-luks/
This method does work with 19.04 with some mirror adaptation (e.g. swap is now
a file) even if I still have an issue this the grub menu not showing up during
The answer is no.
It is still impossible to install an encrypted kubuntu on a dual boot system.
What's the official way to encrypt /home with 19.04 ??
This hack written in 2015 ?? :
http://blog.botux.fr/en/2015/09/ubuntu-installation-manual-full-disk-encryption-lvm-on-luks/
--
You received
Will it be possible to install a fully encrypted dual boot system with
the 19.04 installer?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514120
Title:
Ubiquity needs to not disable the LVM and
Public bug reported:
I have installed kubuntu 18.10 on an encrypted partition.
I have written a /etc/crypttab
CryptDisk UUID=c9deed35-610e-4328-b8e7-079e95d43f76 none
luks,hash=sha256,tries=3
At each boot, I get this warning "cryptsetup: WARNING: Option 'hash' missing in
crypttab".
I tried
Public bug reported:
The F5/F6 keys used to work to set the keyboard backillumination level
with 18.04 but they do not work anymore with 18.10 4.18.0-10-generic
The back illumination can be turned on with : echo 255 >
/sys/class/leds/smc\:\:kbd_backlight/brightness but not anymore with the
Fn
Well actually I don't see how to achieve that with the *k*unbuntu installer.
I have created an encrypted partition
blkid /dev/sda7
/dev/sda7: UUID="c9deed35-610e-4328-b8e7-079e95d43f76" TYPE="crypto_LUKS"
PARTLABEL="Linux" PARTUUID="13aac430-9701-4323-810d-53231decca9c (on which I
installed
Ok I missed that point.
You can close it if you want,except if you intend to support resizing *and*
disk encryption.
Sorry for the noise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799550
Title:
Thanks for the answer but I'm not sure I fully understand.
If I do the setup manually the partitioning and launch the installer
once it is done, is there a way to perform the installation on this
encrypted partition without having to chroot the environment and to
create manually crypttab and
Public bug reported:
I'm using kubuntu alongside with windows in a dual boot, therefore I cannot use
the full disk partition option. There is no option in the installer to get an
encrypted kubuntu with windows (or any other OS) already installed on the same
disk. There used to be an option to
This is an old unresolved bug :
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1687637
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774720
Title:
Kubuntu installer crashes when toggling
Ok but what am I supposed to do on a dual boot machine??
I cannot use full disk encryption as I have other partitions for the other OS
(or can I??)
fscrypt ? where is it documented??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok thanks for the workaround but why did the default behavior change?
I can apply the workaround. However, I have no idea if it has side effect on
other packages which could rely on the gnugpg cache.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I don't know exactly which change triggers this behavior but now in 17.10,
gpg-agent is started automatically.
As gpg-agent --homedir /home/xavier/.gnupg --use-standard-socket --daemon is
running and it is not what I want. For some reasons, I want to type my password
each
It works with the kernel currently in -proposed.
Thank you!
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
Perfect example of excellent support! Thanks.
I hope the patch will find its way to the next zesty kernel update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
Title:
Dell Inspiron on
Here we go (except if it would be reverted before 4.12 but why would it?)
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/acpi/blacklist.c
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The patch is not getting much attention on the linux-acpi list :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
Title:
Dell Inspiron on kernel 4.10 : battery detected only after AC power
Mix of "fun" and "to be right sure it works" :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
Title:
Dell Inspiron on kernel 4.10 : battery detected only after AC power
adapter event
To
I think you mean this patch? It will probably take quite some time to
find its way to the package. I'm going to try to compile a patched
ubuntu kernel in the meantime. thanks.
diff --git a/drivers/acpi/blacklist.c b/drivers/acpi/blacklist.c
index 4421f7c9981c..bb542acc0574 100644
---
No such bug (The battery is correctly detected) with
linux-image-4.4.0-72-generic_4.4.0-72.93_amd64.deb
and
ro acpi_osi=Linux quiet splash vt.handoff=7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK do you have a patch?
On which basis do you want to set _REV to 2 instead of 5?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
Title:
Dell Inspiron on kernel 4.10 : battery detected only
Thanks!
Adding acpi_rev_override does the trick!
I set it to "fix released" even if "workaround documented" would be more
appropriate.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Exact same bug with kernel 4.11.0-041100rc5-generic
(still with acpi_osi=Linux in the kernel options)
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852656/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852658/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852655/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852652/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852660/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852657/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852659/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
Title:
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852650/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852653/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852654/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852651/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
Title:
apport information
** Tags added: apport-collected zesty
** Description changed:
Hi,
I already reported the bug here:
http://www.spinics.net/lists/linux-acpi/msg73101.html
When I boot a Dell 15" serie 7000 with or without it AC power adapter no
battery is detected:
acpi -i
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852648/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852649/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1678590/+attachment/4852647/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1678590
Title:
Dell
Public bug reported:
Hi,
I already reported the bug here:
http://www.spinics.net/lists/linux-acpi/msg73101.html
When I boot a Dell 15" serie 7000 with or without it AC power adapter no
battery is detected:
acpi -i -b -a
Adapter 0: off-line
As soon as I plug or unplug the AC adapter, the
#32 : It complains that spyder3.1.0 exists and that nbconvert,rope and
qtconsole are missing but it "works".
It seems that it is not yet in proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The version in Scott Howard's repository is fine but:
* One detail : It is missing a "depends python3-traitlets". Without this
package, spyder3 does not start.
* It would be cool to get a working spyder3 back in the mainline repository. It
feels wrong to add ppa on a freshly installed distrib to
On an up to date kubuntu, the bug it still there:
ssds see my laptop keyboard as a french one (which is correct) but the external
keyboard is still handeled as a qwerty. That's a bit of an issue for people who
are not used to foreign keyboard.
A workaround is presented here :
Bug #1448076
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458220
Title:
system keyboard layout not honored
To manage notifications about this bug go to:
Duplicate of Bug #1448076
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458220
Title:
system keyboard layout not honored
To manage notifications about this bug go to:
In Xenial, ssdm has been updated from 0.11.0 to 0.13.0 but this bug is still
there.
A workaround (at least) would be appreciated.
Maybe https://github.com/sddm/sddm/issues/202 also works for the old 0.11
version in 15.04. I have to check.
--
You received this bug notification because you are
This bug is still present in kubuntu 15.10.
The external keyboard settings are correct in the virtual terminal
(crtl+atl+fn).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448076
Title:
Wrong
** Package changed: kwallet-kf5 (Ubuntu) = audiocd-kio (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451021
Title:
kio-audiocd : no way to choose the format/bitrate
To manage
Public bug reported:
Hi,
On an up-to-date Kubuntu 15.04, I use a french keyboard layout set in the kde
settings. I have no issue with kde apps.
The issue is that the dead keys are not working correctly in gtk apps.
E.g. under firefox, I cannot type âêë. I get ^a^e¨e which is quite annoying.
It
Public bug reported:
Hi,
With kde4, it was easy to rip an audio cd and to select the format/bitrate in
the kde settings.
It is still possible to rip a cd using kio-audiocd /dolphin under kde5 but I'm
missing the tab in the kde settings to select the format/bitrate. Which package
should I
Public bug reported:
Each I time I switch the display (using System Settings) from my laptop screen
to my external screen (or reverve), konsole crashes.
I get that:
xavier@nano:~$ konsole
QCoreApplication::arguments: Please instantiate the QApplication object first
QDBusConnection: session D-Bus
Public bug reported:
Hi,
I'm using a fresh installation of kubuntu 15.04 on a laptop with an external
keyboard.
My system is installed in english but I'm using french keyboards.
When I enter my password in sddm with the laptop internal keyboard it works ok.
However, when I use the external
Public bug reported:
On my macbook air 6.1, the scrolling with the touchpad is not usable due to
this bug : https://bugs.kde.org/show_bug.cgi?id=331706
This bug have been solved upstream. I have compiled/tested the
git://anongit.kde.org/kcm-touchpad and it works (look at the last 3 or 4
It looks now ok on my box.
I cannot tell in which update the fix was.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291526
Title:
could not start ksmserver with nvidia-prime at next login
To
I also have 2 different sized displays but the bug is still there on my
up to date box today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291526
Title:
could not start ksmserver with
It makes nvidia-prime pretty much useless on my box.
I'm not an Xorg expert but if you have any idea/patch I would be happy to help
to test it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291526
Yes indeed : kubuntu saucy is now installable without any extra option.
All the other issues (sound and touchpad) are solved in 3.12-rc3 except the
libata.force=noncq story.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
My wifi router was configured in b+g+n mode.
It looks like the broadcom driver does not like the n mode (or my router does
not fully n compliant).
Anyway, it works in b+g mode. I haven't tried yet in a+n mode.
Is the n mode (much faster) supposed to be supported by the broadcom
driver?
Where is
Maybe we should setup a wiki but let me ask a side question here:
How do you get the wifi up and running on a 3.12-rc1??
I have tried to install bcmwl-kernel-source and/or to follow the instructions
of http://uli-heller.github.io/blog/2013/06/24/macbook-air/
Whatever I do, I see my wifi network
It looks like it will be too late to get in 13.10 :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197451
Title:
Ubuntu fails to properly boot on Macbook Air 2013 6,1 6,2
To manage notifications
** Changed in: linux (Ubuntu Saucy)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197451
Title:
Ubuntu fails to properly boot on Macbook Air 2013 6,1 6,2
Set to Fix Committed according to
http://marc.info/?l=linux-kernelm=137811791207884w=2 but I'm not sure if it
is correct : we have patch upstream to be committed in 3.12.
However, I not quite sure about the process to have this patch applied in
3.11.X Stable and in the ubuntu default kernel for
Do we have an open kernel bug on the audio issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197451
Title:
Ubuntu fails to properly boot on Macbook Air 2013 6,1 6,2
To manage notifications
To sum up for newcomers
The patch of #54 allows to boot in EFI mode without any special grub option
and it just works.
If you boot in legac bios mode, you still need the nosmp option to boot.
I'm not quite sure about the simplest way to install (k)ubuntu direclty in EFI
mode.
It would be nice
Great! I'm going to test that asap.
With this patch, is it suppose to boot without extra option? or do we still
need acpi=off or whatever else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197451
It works. Thanks.
This patch should find its way in 3.11.X or at least in the ubuntu kernel
before 13.10 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197451
Title:
Ubuntu fails to
I did the same with the current vanilla git (3.11-rc7) but it is still stuck at
loadig initial ramdisk.
I did a make odlconfig. could be that there is on option missing somewhere
and/or my EFI install is buggy.
Imre Kaloz is going to tell us what's going on :)
--
You received this bug
1 - 100 of 208 matches
Mail list logo
