@burger.ga — This looks like a different problem, as far as I can tell.
I suggest asking on Ubuntu Discourse for some help to diagnose and fix
this.
https://discourse.ubuntu.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Update for me: I have kernel 6.8.0-48.
Hardware: Dell OptiPlex 5480 AIO All-In-One with a touchscreen monitor.
When I use both "intel_iommu=igfx_off" and "acpi_backlight=native", this
solves both this bug and bug #2049248. Without those extras, I continue
to have problems.
--
You received this
I have kernel 6.8.0-48, and unfortunately my screen still blanks.
Hardware: Dell OptiPlex 5480 AIO All-In-One with a touchscreen monitor
As reported in bug #2078054 (marked as a duplicate of this one).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
@rebbel — You haven't told us what error you received. My guess is that
you need to use sudo.
Do this:
1. Enter "sudo su" (without the quotation marks). It'll ask you for your
password.
2. Enter the entire "cat" command again.
3. Enter "exit" (without the quotation marks).
Then you can continu
Update: One of the devs from Zabbly has advised me, and his workaround
has helped me.
Add "acpi_backlight=native" to the kernel command line.
To do this, edit /etc/default/grub, locate GRUB_CMDLINE_LINUX_DEFAULT,
and add "acpi_backlight=native". Finish with "sudo update-grub".
This isn't a solut
@andresmp
> After upgrade from 24.0 to 24.1 …
Do you mean from 24.04 to the daily build of 24.10?
Which kernel does your upgrade have?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2025523
Title:
If a dev looks at this bug, please note that a possible solution is
posted in GitHub Zabbly bug 26 [1].
https://github.com/zabbly/linux/issues/26
I have contacted that dev directly, and I hope to get a response.
** Bug watch added: github.com/zabbly/linux/issues #26
https://github.com/zabbly/
I've updated to kernel 6.8.0-44 on Ubuntu 22.04, via Pre-released
updates (jammy-proposed), and unfortunately it doesn't solve the
blanking problem, nor does it solve bug #2049248.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Update:
This is still broken on kernel 6.8.0-44.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049248
Title:
Kernel 6.5 breaks display brightness controls and sets it to 100% all
the time
To ma
Alas, the latest update from the Zabbly line no longer works after the
last update :(
** Description changed:
Since kernel 6.5, monitor brightness is set to 100%, and cannot be
changed: The brightness controls have disappeared from Settings, and
brightness doesn't respond to the keypad cont
Further to my comment #75, the workaround no longer works after the
latest update.
It worked with kernel linux-image-6.10.6-zabbly+ but no longer works
with kernel linux-image-6.10.7-zabbly+
This is incredibly frustrating and upsetting.
--
You received this bug notification because you are a me
To add some useful information to this, a workaround (explained in
duplicate bug #2078054) is to install the Zabbly mainline kernel [1].
This also seems to be related to bug #2049248 (but not a duplicate).
As far as I can tell, this affects certain Intel displays, though I
could be wrong.
[1] ht
** Description changed:
Since kernel 6.5, monitor brightness is set to 100%, and cannot be
changed: The brightness controls have disappeared from Settings, and
brightness doesn't respond to the keypad controls.
See the attached screenshot, showing the difference between the settings
i
Public bug reported:
Since kernel 6.8, the screen has been going black intermittently and
unpredictably for several seconds. Sometimes it happens several times in
a row over half a minute or so, and other times just once. It happens
regularly.
dmesg shows this type of error every time:
[ 7912.26
There is a solution to this, albeit not the greatest. However, it does
point to how the devs can fix this.
Apparently, for reasons known only to itself, Canonical removes some of
the drivers from the kernels when releasing them.
A maintainer, Zabbly, maintains the mainline kernel but including th
> The problem came to me a week ago with the latest kernel update. If I
try an older kernel it is still ok!
That's curious. This started when I was on kernel 5.19.0, so I wonder
what's going on?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Xiscu — That's one of the solutions that I have tried (I tried again
today after re-enabling tracker3), and unfortunately it doesn't work for
me. It bizarrely said that it had completed the indexing, but still ran
at 100% CPU.
--
You received this bug notification because you are a member of Ubu
I've just tested 24.04, and it works correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665329
Title:
Installer fails to create startup.nsh for EFI system on VirtualBox
To manage notificatio
@afunix — Thank you for that information about snap and flatpak, which I
had missed. I'll update the bug report accordingly.
** Description changed:
The Ubuntu 22.04 repositories have fwupd version 1.7.9. This is a badly
outdated version that cannot cope with some of the newer updates.
(
@superm1 — Thank you. I missed those when I was searching for the
problem.
Bug #2028548 would solve this bug; it's not quite a duplicate, but it
has the same solution.
It would also solve bug #1979963 — again, not a duplicate, but the same
solution.
--
You received this bug notification because
Public bug reported:
The Ubuntu 22.04 repositories have fwupd version 1.7.9. This is a badly
outdated version that cannot cope with some of the newer updates.
(This doesn't affect all updates, and so it affects only some machines
depending on the hardware being supported.)
EXAMPLE:
$ fwupdmgr r
> "I unfortunately don't know what the first ~/.bashrc should be
replaced with."
The author has confirmed that it should just be removed, not replaced.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/12
Public bug reported:
This is a minor error in the Bash manual, which I have confirmed with
one of the authors (Chet Ramey). The error appears to have been created
in Debian, and therefore Ubuntu has inherited it.
DETAIL
In the Bash manual ("man bash"), in the "Invocation" section, the
penultimat
I don't know when it happened, but this seems to have been fixed.
It works correctly on Ubuntu 20.04 and Lubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/996454
Title:
Recovery Mode sta
I have just come across this. It happens on both Ubuntu 20.04 and
Lubuntu 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790468
Title:
system-summary shows wrong physical volume state
To man
> Note also that we can't consider DING for inclusion in Ubuntu 20.04
focal because to render in Wayland sessions it requires mutter 3.38 or
later.
DING works perfectly for me:
Ubuntu 20.04
Mutter 3.36.9
Gnome 3.36.8
DING version 17 (according to the metadata.json file)
Ubuntu 20.04 doesn't use
@chesedprather — It's not a feature request. It's a bug, specifically a
regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901056
Title:
Lubuntu OEM install doesn't work; it simply starts Lu
My computer is now running kernel 5.13.0-25, which works correctly.
Marking as Fix Released.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
*** This bug is a duplicate of bug 1946567 ***
https://bugs.launchpad.net/bugs/1946567
This bug report is about a specific app, Viewnior, but AVIF support
should be generic to all of Ubuntu. For that reason, I'll mark this as a
duplicate of #1946567.
** This bug has been marked a duplicate of
*** This bug is a duplicate of bug 1946567 ***
https://bugs.launchpad.net/bugs/1946567
This bug report is about a specific app, gwenview, but AVIF support
should be generic to all of Ubuntu. For that reason, I'll mark this as a
duplicate of #1946567.
** This bug has been marked a duplicate of
This has been marked as expired, but it is still a valid bug.
Remarking as Confirmed.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
> Maybe upgrade to Hirsute? It uses 5.11 kernel.
Unfortunately, the bug is still present in kernel version 5.11.0-25.
In any case, for those who (like me) use the LTS versions, upgrading to
21.04 wouldn't be a solution.
--
You received this bug notification because you are a member of Ubuntu
Bu
The status is "Fix Released" October 2020, but it's still happening.
Ubuntu 20.04
Nautilus 3.36.3-stable
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1839380
Title:
Nautilus freezes when restoring
This doesn't look like it'll ever be done. Based on past experience, I
don't think that Canonical takes encryption seriously.
So, I've thrown in the towel. Since buying a new computer, I haven't
used dual-boot. Instead, I installed Ubuntu using its full-disk LUKS
encryption. I run Windows in a VM
@seb128 — Hmm, maybe I'm wrong about it being maintained. It's just that
it shows a lower level of compatibility in its Extensions listing. Sorry
if I was wrong.
I don't recall where specifically I have came across the recommendation
for NG, but I found it referenced in several places when I was t
I have created Bug #1906420 which, if implemented, will solve this and
other bugs.
Please visit and "star" it (the green writing at the top) if you agree
with it.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1906420
--
You received this bug notification be
I have created Bug #1906420 which, if implemented, will solve this and
other bugs.
Please visit and "star" it (the green writing at the top) if you agree
with it.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1906420
--
You received this bug notification be
Public bug reported:
By default, Ubuntu installs the Gnome extension "Desktop Icons" [1] (by
rastersoft).
Unfortunately, this extension is now unmaintained, is problematic, and
leads to several bugs, including but not limited to Bug #1901150 and Bug
#1813441.
The same author has created, and con
** Summary changed:
- gedit snap fails to open fails in user dot directories
+ gedit snap fails to save or open files in miscellaneous directories including
dot-folders, ~/bin, and system folders.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Please don't expire this request.
The problem still exists in full.
** Changed in: gedit (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897562
Title:
gedit n
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425934/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425935/+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/1901056
apport information
** Attachment added: ".etc.calamares.modules.welcome.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425931/+files/.etc.calamares.modules.welcome.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425933/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901056
apport information
** Attachment added: ".etc.calamares.modules.before_bootloader_context.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425921/+files/.etc.calamares.modules.before_bootloader_context.conf.txt
--
You received this bug notification because you are a member of U
apport information
** Attachment added: ".etc.calamares.modules.bootloader.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425923/+files/.etc.calamares.modules.bootloader.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
apport information
** Attachment added: ".etc.calamares.modules.locale.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425926/+files/.etc.calamares.modules.locale.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
apport information
** Tags added: apport-collected focal
** Description changed:
Booting Ubuntu or its flavours from a Live USB gives five options,
including an OEM installation.
Lubuntu 20.04 provides the same options (see screenshot).
Unfortunately, choosing "OEM install (for man
apport information
** Attachment added: ".etc.calamares.modules.machineid.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425927/+files/.etc.calamares.modules.machineid.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: ".etc.calamares.modules.packages.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425929/+files/.etc.calamares.modules.packages.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: ".etc.calamares.modules.automirror.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425920/+files/.etc.calamares.modules.automirror.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
apport information
** Attachment added: ".etc.calamares.modules.mount.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425928/+files/.etc.calamares.modules.mount.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
apport information
** Attachment added: ".etc.calamares.settings.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425932/+files/.etc.calamares.settings.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
apport information
** Attachment added: ".etc.calamares.modules.users.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425930/+files/.etc.calamares.modules.users.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
apport information
** Attachment added:
".etc.calamares.modules.before_bootloader_mkdirs_context.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425922/+files/.etc.calamares.modules.before_bootloader_mkdirs_context.conf.txt
--
You received this bug notification because you ar
apport information
** Attachment added: ".etc.calamares.modules.fstab.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425925/+files/.etc.calamares.modules.fstab.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
apport information
** Attachment added: ".etc.calamares.modules.displaymanager.conf.txt"
https://bugs.launchpad.net/bugs/1901056/+attachment/5425924/+files/.etc.calamares.modules.displaymanager.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I'm using Ubuntu 20.04.
On my desktop, Delete (which moves the item to the Recycling bin) just deletes
it.
Shift+Delete (which deletes the item permanently) does ask.
To me, this is correct behaviour and shouldn't change.
But...
I don't know if this has anything to do with the extension that is
Public bug reported:
Booting Ubuntu or its flavours from a Live USB gives five options,
including an OEM installation.
Lubuntu 20.04 provides the same options (see screenshot).
Unfortunately, choosing "OEM install (for manufacturers)" in Lubuntu
20.04 doesn't do as promised. It simply starts Lub
The updated Desktop Icons, "Desktop Icons NG (DING)" (by the same
author), fixes these problems.
Canonical could make its life easier by simply replacing the old Desktop
Icons with the new Desktop Icons NG (DING).
Desktop Icons:
https://extensions.gnome.org/extension/1465/desktop-icons/
Desktop
@seb128 — Correction to my previous post: For system folders, I cannot
even load files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897562
Title:
gedit needs classic confinement
To manage notifi
@seb128 — I can load files from ~/bin, but when I try to save, I get
this error (screenshot attached):
Could not save the file "/home/paddy/bin/myscript".
You do not have the permissions necessary to save the file. Please check that
you typed the location correctly and try again.
The same is tru
** Description changed:
The snap version of gedit prevents viewing and editing files outside a
strictly limited set of folders. For example, it cannot change files in
- standard folder ~/bin, or standard files such as ~/.bashrc. Even "sudo
- -H gedit /etc/fstab" doesn't work.
+ standard folder
Public bug reported:
The snap version of gedit prevents viewing and editing files outside a
strictly limited set of folders. For example, it cannot change files in
standard folder ~/bin, or standard files such as ~/.bashrc. Even "sudo
-H gedit /etc/fstab" doesn't work.
As there is a bug in the no
Thank you for the links, Sebastian and Daniel.
I've resubmitted a bug report, because the one that was turned down was
specifically about max-recents in dconf, rather than about the
functionality.
https://gitlab.gnome.org/GNOME/gedit/-/issues/357
** Bug watch added: gitlab.gnome.org/GNOME/gedit/
Public bug reported:
• Ubuntu 20.04.1 LTS 64-bit
• gedit 3.36.2-0ubuntu1
gedit used to have an option to change the number of recently-opened
files in the Open dropdown button.
Later, that option was removed (I don't know why), but we could still set it as
follows (in this case, I've set it to
I don't know why this bug is marked as fixed, because it has just happened to
me.
Ubuntu 18.04
Gnome 3.28.2
The workaround mentioned, to reset the entire dconf settings, is not a
good idea for me, having made a number of personalisations there.
--
You received this bug notification because you
I have since discovered that sh.lang has been corrected for the problem
that I reported in comment #9 and so this can probably be re-closed.
Source:
https://gitlab.gnome.org/GNOME/gtksourceview/tree/master/data/language-specs
--
You received this bug notification because you are a member of Ubun
Could we reopen this, please?
gedit has highlighting for sh, but not for bash.
Most of the time, this works fine for bash, but sometimes it goes wrong.
For example, use a command substitution that contains a quote within
case-esac as follows.
#!/bin/bash
case ${SOMETHING} in
( 'a' )
** Description changed:
In today's world, especially with the likes of the EU's GDPR and the
many security fails, Ubuntu installer needs to support full-system
encryption out of the box.
This means encrypting not only /home but also both root and /boot. The
only parts of the system th
@tomreyn — Tom, thank you for posting this. I have added it to these three
documents:
https://help.ubuntu.com/community/ManualFullSystemEncryption
https://ubuntuforums.org/showthread.php?t=2399092
https://help.ubuntu.com/community/FullDiskEncryptionHowto
--
You received this bug notification bec
@jjakob — Jernej, thank you for this useful and important information. I have
included your link in the instructions:
https://help.ubuntu.com/community/ManualFullSystemEncryption
https://ubuntuforums.org/showthread.php?t=2399092
--
You received this bug notification because you are a member of U
Definitely, /boot should be encrypted. It has been proven possible, so
there's every reason to do so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773457
Title:
Full-system encryption needs to be
In answer to Xavier Gnata…
Have you tried this method?
https://help.ubuntu.com/community/ManualFullSystemEncryption
Be aware that it is designed for 18.04 and so it might not work with 19.04
unless modified.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I believe that bug #1565950 is related (but not a duplicate).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401532
Title:
GRUB's Secure Boot implementation loads unsigned kernel without
warning
I believe that bug #1401532 is related (but not a duplicate).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565950
Title:
Grub 2 fails to boot a kernel on a luks encrypted volume with Secure
Boot
I notice that bug #1773457 has been marked as a duplicate of this one.
It is a duplicate, but with one important difference: /boot should also
be encrypted.
As per comment #5 by @spm2011, I repeat the key points here for
convenience:
• There is a bug with Grub that prevents wide scale adoption o
Phillip, the goal is BOTH secure boot AND encryption. This bug report
specifically deals with the latter, not the former. Why are you so
against encryption? I don't understand!
In the EU, GDPR is law, and in the rest of the world, encryption is
pretty much already de rigueur.
If you are arguing t
@psusi Yes, that's correct, and should be done in addition to this
request. In other words, both are necessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773457
Title:
Full-system encryption ne
@Jonathan Polom (s0nic0nslaught)
Thank you for the extra information.
The full-system encryption linked in the OP solves the part about /boot
being accessed, which is a good thing.
That leaves only three parts to be solved.
1. The error with Grub, which has been reported:
https://bugs.launchpad
Public bug reported:
Description:Ubuntu 18.04.1 LTS
Release:18.04
Installing Ubuntu onto a fresh installation from a Live CD. Prior to
initiating the installation:
1. Create a gpt partition table (thereby clearing the entire disk)
2. Create a FAT32 partition for EFI System Partition
** Description changed:
In today's world, especially with the likes of the EU's GDPR and the
many security fails, Ubuntu installer needs to support full-system
encryption out of the box.
This means encrypting not only /home but also both root and /boot. The
only parts of the system th
Public bug reported:
Description:Ubuntu 16.04.5 LTS
Release:16.04
incron version 0.5.10-3
—
It seems that incrontab has some problems, especially with comments and
whitespace. Additionally, incrontab modifies edits.
In some cases, automatic modifications are
@Dimitri Thanks for your comments. I understand where you are coming
from.
I do think, however, that as Ubuntu is intended (and was intended right
from day 1) to be "for human beings", it would make hugely more sense to
support full-system encryption from the installer. People don't want to
be mes
This bug needs to be assigned a high priority, because right now there is no
working encryption method that is considered reliable.
• ecryptfs is considered buggy and insufficiently maintained.
• fscrypt is unusable as described in this bug report.
• Full-system encryption is unsuitable for most u
Would people please note that full-disk encryption is already possible,
where everything on a new installation is encrypted even including
/boot, but without wiping any existing OS such as Windows. (This is why
the existing full-disk encryption is not useful for the majority of
users.)
This would
I have just discovered that home-folder encryption has been removed from
Ubuntu because, it seems, it is considered buggy and under-maintained.
Full-disk encryption is recommended as an alternative.
Reference:
https://www.linuxuprising.com/2018/04/how-to-encrypt-home-folder-in-ubuntu.html
As you
Sorry, Phillip, yes, you're right about the ESP space — more like
100Mb. I was typing incorrectly; what I meant was at most 400Mb.
I'll look at the ubuntu-devel mailing list and post there. But that
still doesn't obviate this request.
--
You received this bug notification because you are a memb
> The point is to prevent people from getting your data if they steal
your computer, not to prevent them from modifying the computer.
Sorry, no, that's not why I raised this bug report, Phillip. There
definitely *is* a point in preventing someone from sneaking into your
office (say, over the weeke
Phillip, I think that you need to take this discussion to somewhere like
Ubuntu Forums.
If we were to accept your argument, we would say that there is no point
whatsoever in encrypting anything, and we should eliminate the current
option to encrypt the home folder when installing Ubuntu.
This app
@Phillip Susi
This was not the case for me. I have had this multiple times, never with a mix
of two different versions, and always with a completely fresh installation on a
blank slate.
Therefore, this should not be marked as Invalid.
--
You received this bug notification because you are a mem
Yes, I know this, Philip, but unlike with the current setup (where you
can add malware to root and the kernel), with this method, the only
thing that they can change is the ESP (EFI System Partition), because
everything else is fully encrypted in a single partition using LVM
within LUKS.
They can'
Phillip, you are correct only if the software partitions are unencrypted
(as is the case with the existing default method). This bug report is
about fully encrypting the entire system — that's everything, including
swap and both root and /boot.
--
You received this bug notification because you ar
Phillip, do you feel that malware cannot be loaded onto /boot? If you
are right, that would take me by surprise!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773457
Title:
Full-system encryption n
Oliver, another point that I missed in my previous comments is that the
full-disk encryption that Ubuntu uses does not play nicely with other
systems. E.g., if you have Windows (true of most users), it will delete
the entire Windows system plus its data.
The instructions given in the above report
Oliver, I've amended the title (the body of the report already says so).
I don't know how to change it to "wishlist", although really, as I say,
in today's world, it is nearly approaching a legal requirement (at least
in the EU because of GDPR) than merely a wish.
** Summary changed:
- Full-syste
Thank you, Oliver. That link was in fact one of the (many) reference
pages used in creating the instructions. Unfortunately, it isn't
actually full system encryption: /boot isn't encrypted, which allows for
a clear attack vector.
--
You received this bug notification because you are a member of U
Public bug reported:
In today's world, especially with the likes of the EU's GDPR and the
many security fails, Ubuntu installer needs to support full-system
encryption out of the box.
This means encrypting not only /home but also both root and /boot. The
only parts of the system that wouldn't be
Public bug reported:
Installing Lubuntu 18.04 64-bit. I've seen this also with 16.04, with
Ubuntu, Lubuntu and some other Ubuntu-flavours.
Message:
The 'grub-efi-amd64-signed-' package failed to install into /target/. Without
the GRUB bootloader, the installed system will not boot.
This (usuall
Public bug reported:
Example scenario:
1. Go to the file manager (e.g. Nautilus, PCManFM)
2. Connect to a server via FTP
3. Enter the password and select "Remember forever"
In Ubuntu, this is correctly placed into the Default Keyring, and
remembered (even after a reboot) so that the password does
1 - 100 of 359 matches
Mail list logo
