[Bug 2056548] Re: fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories
@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. (This doesn't affect all updates, and so it affects only some machines depending on the hardware being supported.) EXAMPLE: $ fwupdmgr refresh Failed to update metadata for lvfs: checksum failure: failed to verify data, expected 0a5a850327f8e8b196b2d79e79ce347cb86037f1 This has been discussed in the GitHub for fwupd: https://github.com/fwupd/fwupd/issues/6888 This problem was solved in the newest version of fwupd. - The snap store currently has the latest version of fwupd, version - 1.9.14. - LONG-TERM SOLUTION - Therefore, the Ubuntu repositories for 22.04 must be updated either to - have the latest version of fwupd, or to replace it with the snap version - (in the same way as Firefox does). + Therefore, the Ubuntu repositories for 22.04 must be updated to have the + latest version of fwupd. + + It's not appropriate to use snap or flatpak, because they can be development versions rather than stable: + https://github.com/fwupd/fwupd?tab=readme-ov-file#compiling WORKAROUND For people currently having this problem, the current solution is to - uninstall the apt version fwupd (this is important) and then install the - snap version of fwupd. + uninstall the apt version fwupd (this is important) and then install + either the snap or flatpak version of fwupd. However, this should be a + temporary solution as the snap and flatpak versions are for development + rather than stable. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: fwupd 1.7.9-1~22.04.3 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 12:14:03 2024 InstallationDate: Installed on 2022-08-28 (558 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.fwupd.remotes.d.lvfs-testing.conf: [modified] modified.conffile..etc.fwupd.remotes.d.lvfs.conf: [modified] mtime.conffile..etc.fwupd.remotes.d.lvfs-testing.conf: 2022-11-23T08:07:53.266347 mtime.conffile..etc.fwupd.remotes.d.lvfs.conf: 2022-11-23T08:07:53.358347 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056548 Title: fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2056548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056548] Re: fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories
@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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056548 Title: fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2056548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056548] [NEW] fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories
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 refresh Failed to update metadata for lvfs: checksum failure: failed to verify data, expected 0a5a850327f8e8b196b2d79e79ce347cb86037f1 This has been discussed in the GitHub for fwupd: https://github.com/fwupd/fwupd/issues/6888 This problem was solved in the newest version of fwupd. The snap store currently has the latest version of fwupd, version 1.9.14. LONG-TERM SOLUTION Therefore, the Ubuntu repositories for 22.04 must be updated either to have the latest version of fwupd, or to replace it with the snap version (in the same way as Firefox does). WORKAROUND For people currently having this problem, the current solution is to uninstall the apt version fwupd (this is important) and then install the snap version of fwupd. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: fwupd 1.7.9-1~22.04.3 ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 12:14:03 2024 InstallationDate: Installed on 2022-08-28 (558 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: fwupd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.fwupd.remotes.d.lvfs-testing.conf: [modified] modified.conffile..etc.fwupd.remotes.d.lvfs.conf: [modified] mtime.conffile..etc.fwupd.remotes.d.lvfs-testing.conf: 2022-11-23T08:07:53.266347 mtime.conffile..etc.fwupd.remotes.d.lvfs.conf: 2022-11-23T08:07:53.358347 ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056548 Title: fwupd metadata bug due to outdated version in Ubuntu 22.04 repositories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2056548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1216969] Re: man page names the same file twice -- are there really 2?
> "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/1216969 Title: man page names the same file twice -- are there really 2? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1216969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968313] [NEW] Bash manual contains an error in the "Invocation" section
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
penultimate paragraph has this phrase:
"… it reads and executes commands from ~/.bashrc and ~/.bashrc"
The file ~/.bashrc should be stated just once, because it's confusing
having it mentioned twice.
This needs correcting at the Debian level, so that all Debian-based
distributions will inherit the fix.
• Ubuntu 20.04.4 LTS, Lubuntu 20.04, Ubuntu 21.10
• apt-cache policy bash: 5.0-6ubuntu1.1
• bash --version: GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bash 5.0-6ubuntu1.1
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 8 11:18:38 2022
InstallationDate: Installed on 2020-09-05 (579 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: bash
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: bash (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968313
Title:
Bash manual contains an error in the "Invocation" section
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1968313/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 996454] Re: Recovery Mode starts in read-only, does not mount home folder, and hangs when trying to do something
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 starts in read-only, does not mount home folder, and hangs when trying to do something To manage notifications about this bug go to: https://bugs.launchpad.net/friendly-recovery/+bug/996454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790468] Re: system-summary shows wrong physical volume state
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 manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1790468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884726] Re: [TTM] Buffer eviction failed
Hello I like to help but not sure what to do. I could not use the workaround to install the proprietary driver because it does not work https://bugs.launchpad.net/ubuntu/+source/nvidia- graphics-drivers-440/+bug/1878946. What must I do for the test of the Please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ ? Sorry I have not done such things before, so I need more advise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884726 Title: [TTM] Buffer eviction failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878946] Re: Cannot install proprietary NVIDIA driver
I have the same problem and need it because the bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884726 freeze my PC very often. I would be happy to get this fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878946 Title: Cannot install proprietary NVIDIA driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1878946/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906420] Re: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)
> 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 Wayland. Does this restriction exist because some Ubuntu derivatives use Wayland? Mind you, Ubuntu 22.04 is close, so Ubuntu 20.04 is probably low priority. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906420 Title: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1906420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] Re: Lubuntu OEM install doesn't work; it simply starts Lubuntu
@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 Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend
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.launchpad.net/bugs/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917512] Re: Add support for AVIF images
*** 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 bug 1946567 AVIF Support (feature request) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917512 Title: Add support for AVIF images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/viewnior/+bug/1917512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917518] Re: Add support for AVIF images
*** 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 bug 1946567 AVIF Support (feature request) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917518 Title: Add support for AVIF images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwenview/+bug/1917518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend
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/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend
> 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839380] Re: Nautilus freezes when restoring files and a copy already exists
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 files and a copy already exists To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1839380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
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 (VirtualBox) inside Ubuntu, so that LUKS also protects it. It's a good solution provided that your hardware is powerful enough. If your hardware isn't up to it, you don't have much choice. -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906420] Re: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)
@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 trying to solve another problem with Desktop Icons (it shows a permanent error that cannot be fixed). In any case, even if Desktop Icons is maintained, it lacks the features that NG has, so it would be much easier to just use the latter than to try to fix the former. I would hate to return to Desktop Icons, having used Desktop Icons NG (DING) for some time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906420 Title: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1906420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901150] Re: No "Are you sure?" question when deleting something from Desktop
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901150 Title: No "Are you sure?" question when deleting something from Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1901150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906420] [NEW] Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author)
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 continues to maintain, the far superior "Desktop Icons NG (DING)" [2]. It solves a number of problems including the two aforementioned bugs. It's possible to disable, but not uninstall, "Desktop Icons", and then to install "Desktop Icons NG (DING)". I did this a while ago with great results. If Canonical replaces the former with the latter, not only will Ubuntu be using a better desktop manager, but also it will be able clear all related bugs at a stroke. This is a simple, cheap, quick and effective solution that will let the devs concentrate on more important tasks. Please give this serious consideration. More information: Ubuntu 20.04.1 LTS 64-bit Gnome version 3.36.3 [1] https://extensions.gnome.org/extension/1465/desktop-icons/ [2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ ** Affects: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided Status: New ** Tags: desktop-file -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906420 Title: Please replace default Gnome extension "Desktop Icons" with "Desktop Icons NG (DING)" (by the same author) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1906420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897562] Re: gedit snap fails to save or open files in miscellaneous directories including dot-folders, ~/bin, and system folders.
** 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 to Ubuntu. https://bugs.launchpad.net/bugs/1897562 Title: gedit snap fails to save or open files in miscellaneous directories including dot-folders, ~/bin, and system folders. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897562] Re: gedit needs classic confinement
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 needs classic confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] ProcCpuinfoMinimal.txt
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/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.welcome.conf.txt
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 Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] ProcEnviron.txt
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 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] Dependencies.txt
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 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.before_bootloader_context.conf.txt
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.bootloader.conf.txt
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.locale.conf.txt
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 Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] Re: Lubuntu OEM install doesn't work; it simply starts Lubuntu
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 manufacturers)" in Lubuntu 20.04 doesn't do as promised. It simply starts Lubuntu as if you'd chosen the first option, "Start Lubuntu". This is tested on Lubuntu release 20.04.1 (lubuntu-20.04.1-desktop- amd64.iso). Please fix this to allow for OEM installation for Lubuntu. (It already works correctly in Ubuntu.) I understand that the following task is relevant: https://phab.lubuntu.me/T16 + --- + ProblemType: Bug + .etc.calamares.modules.finished.conf: + --- + restartNowMode: user-checked + restartNowCommand: "systemctl -i reboot" + .etc.calamares.modules.partition.conf: + efiSystemPartition: "/boot/efi" + enableLuksAutomatedPartitioning: true + userSwapChoices: none + drawNestedPartitions: true + defaultFileSystemType: "ext4" + .etc.calamares.modules.shellprocess_logs.conf: + --- + dontChroot: true + timeout: 30 + script: + - calamares-logs-helper @@ROOT@@ + .etc.calamares.modules.unpackfs.conf: + --- + unpack: + - source: "/cdrom/casper/filesystem.squashfs" + sourcefs: "squashfs" + destination: "" + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + CasperMD5CheckResult: pass + CasperVersion: 1.445.1 + CurrentDesktop: LXQt + DistroRelease: Ubuntu 20.04 + LiveMediaBuild: Lubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + Package: calamares 3.2.20-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 + RelatedPackageVersions: + calamares-settings-ubuntu-common 1:20.04.2 + calamares-settings-lubuntu 1:20.04.2 + xfsprogs 5.3.0-1ubuntu2 + btrfs-progs 5.4.1-2 + Tags: focal + Uname: Linux 5.4.0-42-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: ".etc.calamares.modules.after_bootloader_context.conf.txt" https://bugs.launchpad.net/bugs/1901056/+attachment/5425919/+files/.etc.calamares.modules.after_bootloader_context.conf.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 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.machineid.conf.txt
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 to Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.packages.conf.txt
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 Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.automirror.conf.txt
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.mount.conf.txt
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 Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.settings.conf.txt
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://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.users.conf.txt
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 Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.fstab.conf.txt
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 Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.before_bootloader_mkdirs_context.conf.txt
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 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 Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] .etc.calamares.modules.displaymanager.conf.txt
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901056 Title: Lubuntu OEM install doesn't work; it simply starts Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901150] Re: No "Are you sure?" question when deleting something from Desktop
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 used to control the desktop. In Ubuntu, the default is the broken "Desktop Icons" [1], which should be replaced with the fixed "Desktop Icons NG (DING)" [2] (by the same author). I have uninstalled Desktop Icons and installed Desktop Icons NG (DING). Thus, my desktop's behaviour might differ from the standard. See Bug #1813441 comment 24 [1] https://extensions.gnome.org/extension/1465/desktop-icons/ [2] https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901150 Title: No "Are you sure?" question when deleting something from Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1901150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901056] [NEW] Lubuntu OEM install doesn't work; it simply starts Lubuntu
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 Lubuntu as if you'd chosen the first option, "Start Lubuntu". This is tested on Lubuntu release 20.04.1 (lubuntu-20.04.1-desktop- amd64.iso). Please fix this to allow for OEM installation for Lubuntu. (It already works correctly in Ubuntu.) I understand that the following task is relevant: https://phab.lubuntu.me/T16 ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: install lubuntu oem ** Attachment added: "Screenshot of Lubuntu 20.04.1 Live USB boot options" https://bugs.launchpad.net/bugs/1901056/+attachment/5425557/+files/OEM%20install%20%28for%20manufacturers%29.png -- 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 Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1901056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900275] [NEW] sshguard unit file always initializes for iptables
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 sshguard: 2.3.1-1ubuntu1.1 Even when using a different firewall like nftables(sshguard.conf -> BACKEND="/usr/lib/x86_64-linux-gnu/sshg-fw-nft-sets"), sshguard always initializes for iptables. [Unit] Description=SSHGuard Documentation=man:sshguard(8) After=network.target Before=sshd.service [Service] PIDFile=/run/sshguard.pid ExecStartPre=-/usr/sbin/iptables -N sshguard ExecStartPre=-/usr/sbin/ip6tables -N sshguard ExecStopPost=-/usr/sbin/iptables -X sshguard ExecStopPost=-/usr/sbin/ip6tables -X sshguard ExecStart=/usr/sbin/sshguard [Install] WantedBy=multi-user.target Sure, I can create an override file for the unit (which I did), but to me it just does not feel right. Looks like something that deserves a more elegant solution? ** Affects: sshguard (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900275 Title: sshguard unit file always initializes for iptables To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshguard/+bug/1900275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
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 Icons NB (DING): https://extensions.gnome.org/extension/2087/desktop-icons-ng-ding/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897562] Re: gedit needs classic confinement
@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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897562] Re: gedit needs classic confinement
@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 true for others such as ~/.local/ or ~/.bashrc, and for system files loaded with "sudo -H gedit". ** Attachment added: "Screenshot of error when trying to save" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+attachment/5414989/+files/Save%20to%20bin%20error.png -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897562] Re: gedit needs classic confinement
** 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 ~/bin or ~/.local or ~/.config, or standard files such + as ~/.bashrc. Even "sudo -H gedit /etc/fstab" doesn't work. As there is a bug in the non-snap versions [1], the snap version is important, but sadly it is unusable for a certain number of cases. I understand that the only solution is to make gedit available in classic confinement. Please would you do this. Thank you [1] https://gitlab.gnome.org/GNOME/gedit/-/issues/361 ** 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 ~/.local or ~/.config, or standard files such - as ~/.bashrc. Even "sudo -H gedit /etc/fstab" doesn't work. + standard folders ~/bin or ~/.local or ~/.config, or standard files such + as ~/.bashrc or ~/.profile. Even "sudo -H gedit /etc/fstab" doesn't + work. As there is a bug in the non-snap versions [1], the snap version is important, but sadly it is unusable for a certain number of cases. I understand that the only solution is to make gedit available in classic confinement. Please would you do this. Thank you [1] https://gitlab.gnome.org/GNOME/gedit/-/issues/361 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897562] [NEW] gedit needs classic confinement
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 non-snap versions [1], the snap version is important, but sadly it is unusable for a certain number of cases. I understand that the only solution is to make gedit available in classic confinement. Please would you do this. Thank you [1] https://gitlab.gnome.org/GNOME/gedit/-/issues/361 ** Affects: gedit (Ubuntu) Importance: Undecided Status: 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 needs classic confinement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1897562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894878] Re: gedit has lost the ability to specify the max-recents value
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/-/issues #357 https://gitlab.gnome.org/GNOME/gedit/-/issues/357 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894878 Title: gedit has lost the ability to specify the max-recents value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1894878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894878] [NEW] gedit has lost the ability to specify the max-recents value
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 30, because I need a lot in my history): gsettings set org.gnome.gedit.preferences.ui max-recents 30 Unfortunately, even that has been taken away now, so there is no way to increase (or decrease, which some people say they need for confidentiality) the number of recent files listed. Please could this option be reinstated, because the current limit is too restrictive. Thank you ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: gedit max-recents -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894878 Title: gedit has lost the ability to specify the max-recents value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1894878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712698] Re: Uninstalling Dash To Dock does not restore Ubuntu Dock
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712698 Title: Uninstalling Dash To Dock does not restore Ubuntu Dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1712698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 640418] Re: Please add support for bash highlight in gedit
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/640418 Title: Please add support for bash highlight in gedit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/640418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 640418] Re: Please add support for bash highlight in gedit
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' )
FILENAME="$( readlink "${ARG}" )"
;;
esac
CONFUSING_LINE="case esac"
Starting from the line with the command substitution, gedit thinks that
the rest of the file is within quotes — except those that are parts that
are actually within quotes! This makes it confusing to edit a large
script.
Thank you
** Changed in: gedit (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/640418
Title:
Please add support for bash highlight in gedit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/640418/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
** 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 that wouldn't be encrypted are the EFI partition and the initial Grub bootloader, for obvious reasons. It should also not delete other installed systems unless explicitly requested. On top of this, the previous method of encrypting data (ecryptfs) is now considered buggy, and full-disk encryption is recommended as an alternative. Unfortunately, the current implementation of full-disk encryption wipes any existing OS such as Windows, making the implementation unusable for most users. Now, using LUKS and LVM, it is already possible to have full-disk encryption (strictly, full-partition encryption because it leaves any existing OS alone), while encrypting /boot. Reference: https://help.ubuntu.com/community/ManualFullSystemEncryption ... but with one major limitation: Grub is incorrectly changed after an update affecting the kernel or Grub, so that a manual Grub update is required each time this happens (this is fully covered in the linked instructions). If the incorrect Grub change is fixed, it should be (relatively) simple to support full-system encryption in the installer. Further information (2018-08-17): The NCSC recommends, "Use LUKS/dm-crypt to provide full volume encryption." References: • https://blog.ubuntu.com/2018/07/30/national-cyber-security-centre-publish-ubuntu-18-04-lts-security-guide • https://www.ncsc.gov.uk/guidance/eud-security-guidance-ubuntu-1804-lts + + **EDIT** + Refer to comment #47 for an alternative version. -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
@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 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
@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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514120] Re: Ubiquity needs to not disable the LVM and encryption options for dual boot
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514120 Title: Ubiquity needs to not disable the LVM and encryption options for dual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1514120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565950] Re: Grub 2 fails to boot a kernel on a luks encrypted volume with Secure Boot enabled
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 enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1565950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401532] Re: GRUB's Secure Boot implementation loads unsigned kernel without warning
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1401532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514120] Re: Ubiquity needs to not disable the LVM and encryption options for dual 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 of this, for which refer to bug #1773457 • Reference for full-system encryption including /boot and without wiping any other OS: https://help.ubuntu.com/community/ManualFullSystemEncryption -- 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 encryption options for dual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1514120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
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 that /boot shouldn't be encrypted, this is a direct contradiction of what you wrote earlier that malware can be loaded into the ESP; so why couldn't malware be loaded into /boot? Please would you explain why you think that we should NOT encrypt /boot? The rest of us here are mystified; we should encrypt as much as possible in order to increase the barriers to black hats. -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
@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 needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
@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.net/ubuntu/+source/grub2/+bug/1062623 2. As you rightly say, the need to properly sign the Ubuntu kernel and initrd files. I think that this should be raised as a bug report if Ubuntu is to be taken seriously in corporate, government and other fields. So, on that note, how specifically should this bug be raised? I'll be happy to raise it if I know the specifics of what needs to be reported. Alternatively, if you know the details, perhaps you could please raise it and post the link here? 3. Implementing this process in the standard Ubuntu installer, which is what this bug request is about. -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785850] [NEW] Grub installation crashes on Ubuntu installation
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 3. Create a LUKS partition, which includes: — partition for root — partition for /boot After installing Ubuntu, the installation fails with this error message. I have tried this on various systems, including (but not limited to): • Ubuntu 16.04 • Lubuntu 16.04 • Xubuntu 16.04 • Kubuntu 16.04 • Mint 16.04 • Ubuntu 18.04 • Lubuntu 18.04 All 64-bit and all using UEFI. It is possible to complete the installation by manually fixing Grub; in other words, everything else is correctly installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Tue Aug 7 17:04:25 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785850 Title: Grub installation crashes on Ubuntu installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1785850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
** 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 that wouldn't be encrypted are the EFI partition and the initial Grub bootloader, for obvious reasons. It should also not delete other installed systems unless explicitly requested. On top of this, the previous method of encrypting data (ecryptfs) is now considered buggy, and full-disk encryption is recommended as an alternative. Unfortunately, the current implementation of full-disk encryption wipes any existing OS such as Windows, making the implementation unusable for most users. Now, using LUKS and LVM, it is already possible to have full-disk encryption (strictly, full-partition encryption because it leaves any existing OS alone), while encrypting /boot. Reference: https://help.ubuntu.com/community/ManualFullSystemEncryption ... but with one major limitation: Grub is incorrectly changed after an update affecting the kernel or Grub, so that a manual Grub update is required each time this happens (this is fully covered in the linked instructions). If the incorrect Grub change is fixed, it should be (relatively) simple to support full-system encryption in the installer. + + Further information (2018-08-17): + + The NCSC recommends, "Use LUKS/dm-crypt to provide full volume encryption." + References: + • https://blog.ubuntu.com/2018/07/30/national-cyber-security-centre-publish-ubuntu-18-04-lts-security-guide + • https://www.ncsc.gov.uk/guidance/eud-security-guidance-ubuntu-1804-lts -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785573] [NEW] incrontab changes its contents, and fails, under certain conditions
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 aren't a problem, even though it would be far preferable not to do this: • Remove blank lines. • Change multiple spaces after the path to a single space. • Change the order of masks, e.g. IN_NO_LOOP,IN_MODIFY to IN_MODIFY,IN_NO_LOOP. But other cases are not so good. • When using a tab for whitespace in a line, incron doesn't understand it — but there is no error message. • When adding a comment (i.e. a line beginning with a hash): — If the comment is just a hash or has exactly one word after the has line is removed. — If the comment has more than one word, the first word is replaced with a zero. Example: # This is a comment. is changed to # 0 is a comment. (It gets more complicated when tabs are involved.) What incrontab should do instead: • Do not automatically change the contents. Both whitespace and comments are used to document the purpose entries, and are important to the long- term maintenance of a running system. • Accept whitespace (multiple spaces and tabs) between the path and the mask set, and between the mask set and the command. • If there is a syntax error in the edits, reject the edits with a meaningful error message when saving incrontab, and give the option of re-editing (in the same way that crontab does). Finally, the documentation should mention the bugs (until they're fixed) so that people understand why their incron is not working and how to fix it. Thank you ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: incron 0.5.10-3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Aug 6 08:47:54 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-17 (414 days ago) InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: incron UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.incron.allow: [inaccessible: [Errno 13] Permission denied: '/etc/incron.allow'] modified.conffile..etc.incron.deny: [inaccessible: [Errno 13] Permission denied: '/etc/incron.deny'] ** Affects: incron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Summary changed: - incrontab changes its contents under certain conditions + incrontab changes its contents, and fails to work, under certain conditions ** Summary changed: - incrontab changes its contents, and fails to work, under certain conditions + incrontab changes its contents, and fails, under certain conditions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785573 Title: incrontab changes its contents, and fails, under certain conditions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/incron/+bug/1785573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
@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 messing around with "install this, then install that, then fix this other thing" especially as it's neither documented nor supported by Canonical. That's just life. While technical people love messing around — it's their job, after all! — your average "human being" hates it. (I also dislike it; I put together the method simply because I needed it. I documented the process publicly because I know that there are many, many people like me who need it.) Also, I have never had good results from installing a desktop environment over an existing system, even something as simple as Lubuntu desktop over an Ubuntu installation. That, too, is just life. This request is something that Ubuntu should support. It's not a "nice to have" feature. In today's world, it's a a "got to have" feature, whether for business, government, professionals, salespeople, scientific research, and even personal use. (If I could program, I'd amend the installer myself to implement this — it is open source, after all). This is made even more urgent by the fact that Ubuntu 18.04 no longer supports encryption at all. Even the recommended workaround, fscrypt, is broken. I cannot understand the antagonism to this request — it's a proven method; it's not particularly difficult; it's easy enough to modify the existing installer to do this; it's significantly better than the existing options; it uses only proven technology; and it would prove hugely popular, helping to tip the balance to switch to Ubuntu in organisations that are currently uncertain. I know that I were an internal sysadmin, or a consultant to a professional (I used to be both, decades ago), up to version 16.04 I would have recommended Ubuntu every time without hesitation. But, from 18.04, I absolutely would not, because it's too problematic to install with encryption and then keep it reliably up to date. -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768340] Re: fscrypt does not work for home directory encryption
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 users, because it wipes any other OS such as Windows. (There is an alternative — https://goo.gl/KtsLMk — that doesn't do this, but it has two important flaws.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768340 Title: fscrypt does not work for home directory encryption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1768340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756840] Re: Buggy, under-maintained, not fit for main anymore; alternatives exist
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 make a far better option than asking users to manually install fscrypt. There is a bug with Grub that prevents wide scale adoption of this, for which I have raised a bug: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457 Reference for full-disk encryption without wiping any other OS: https://help.ubuntu.com/community/ManualFullSystemEncryption Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756840 Title: Buggy, under-maintained, not fit for main anymore; alternatives exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1756840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
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 already know, full-disk encryption wipes any existing OS such as Windows. Therefore, this gives extra impetus to this bug report. Phillip, I posted the message on the board as you requested, but as there has been no reply, I consider this request to be fully valid. ** 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 that wouldn't be encrypted are the EFI partition and the initial Grub bootloader, for obvious reasons. It should also not delete other installed systems unless explicitly requested. - Using LUKS and LVM, it is already possible... + On top of this, the previous method of encrypting data (ecryptfs) is now + considered buggy, and full-disk encryption is recommended as an + alternative. Unfortunately, the current implementation of full-disk + encryption wipes any existing OS such as Windows, making the + implementation unusable for most users. + + Now, using LUKS and LVM, it is already possible to have full-disk + encryption (strictly, full-partition encryption because it leaves any + existing OS alone), while encrypting /boot. Reference: https://help.ubuntu.com/community/ManualFullSystemEncryption ... but with one major limitation: Grub is incorrectly changed after an update affecting the kernel or Grub, so that a manual Grub update is required each time this happens (this is fully covered in the linked instructions). If the incorrect Grub change is fixed, it should be (relatively) simple to support full-system encryption in the installer. -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
> 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 weekend), and loading malware in order to either modify or steal your data. This type of espionage does actually happen. Full disk encryption prevents this, because I really don't think that you can load a virtual machine into the (at most) 400Kb of free space in the ESP and somehow transfer control to the ESP after you've done that. The alternative, leaving a USB stick in the machine and hoping that you won't notice a strange stick in your machine, is far too obvious to be effective. Please, if you wish to continue this conversation further, please start something on the Ubuntu Forums and post the link here. I'll be happy to discuss it at length there, because this is taking it way off track on this bug report. The bug report is about converting the current halfway encryption method to a full encryption method, for all the right reasons. Just because someone "might" be able to load a virtual machine into the 400Kb of free ESP is hardly a reason to stick with the halfway method where someone definitely can load malware into the system. Thank you -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
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 approach violates, among others, the EU's GDPR. We do need to encrypt our computers, and encrypting absolutely everything to help prevent malware is the best possible way forward. Full-system encryption is possible (there is already a how-to for this), and it should be implemented as there is very little to do to make it available in the default installer. We shall have to beg to differ on this, as your argument is unsuitable given the current technical, social and especially legal environment. -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252255] Re: The 'grub-efi-amd64-signed' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot.
@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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252255 Title: The 'grub-efi-amd64-signed' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1252255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
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't add, modify or delete anything whatsoever anywhere else. Not root. Not the kernel. Not /boot. Not /home. Nothing. There's no access even to the file system. You can't even see what type of file system it is, e.g. ext4 or BTRFS. There's no access even to the partitioning. All you can see when you boot with your malware USB is two physical partitions: 1. The ESP. 2. A single partition filled with apparently random data with a LUKS header. Not even a file system. Not even the partitioning details. That's it. It's not like ecryptfs, where you can see (and modify) the files in root and /boot, and where you can see (and corrupt) the files in /home even though the file names and contents are encrypted. With LUKS, you can't see anything. At all. Literally everything is encrypted apart from the ESP. Everything. Seriously. The only way to add malware is to somehow mess with the ESP. It's a pretty tall order. I suppose that it could be done, theoretically, but I've yet to see anything along these lines being done. And, when booting from the hard drive (not the malware USB), once you are past the EFI stage, Grub (which is encrypted and therefore cannot be replaced with malware) takes over, thereafter moving into Linux, which is encrypted and therefore cannot be replaced with malware. I hope that you understand what I'm saying. As you can see, it is a robust system that puts both Windows and the existing Ubuntu method to shame. I can't comment on Mac, because I haven't worked with it in decades. So, can you see that I don't understand what you are getting at? I'm trying to understand your objection, but I am lost. I just cannot see it. -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
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 needs to be supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems
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 play nicely, and leave the other existing systems alone. I've amended the title to reflect this need. ** Summary changed: - Full-system encryption needs to be supported out-of-the-box including /boot + Full-system encryption needs to be supported out-of-the-box including /boot and should not delete other installed systems ** 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 that wouldn't be encrypted are the EFI partition and the initial Grub bootloader, for obvious reasons. + + It should also not delete other installed systems unless explicitly + requested. Using LUKS and LVM, it is already possible... https://help.ubuntu.com/community/ManualFullSystemEncryption ... but with one major limitation: Grub is incorrectly changed after an update affecting the kernel or Grub, so that a manual Grub update is required each time this happens (this is fully covered in the linked instructions). If the incorrect Grub change is fixed, it should be (relatively) simple to support full-system encryption in the installer. -- 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 supported out-of-the-box including /boot and should not delete other installed systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box including /boot
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-system encryption needs to be supported out-of-the-box + Full-system encryption needs to be supported out-of-the-box including /boot -- 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 supported out-of-the-box including /boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] Re: Full-system encryption needs to be supported out-of-the-box
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773457 Title: Full-system encryption needs to be supported out-of-the-box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773457] [NEW] Full-system encryption needs to be supported out-of-the-box
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 encrypted are the EFI partition and the initial Grub bootloader, for obvious reasons. Using LUKS and LVM, it is already possible... https://help.ubuntu.com/community/ManualFullSystemEncryption ... but with one major limitation: Grub is incorrectly changed after an update affecting the kernel or Grub, so that a manual Grub update is required each time this happens (this is fully covered in the linked instructions). If the incorrect Grub change is fixed, it should be (relatively) simple to support full-system encryption in the installer. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: encryption installer luks -- 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 supported out-of-the-box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1773457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773224] [NEW] Installation of Lubuntu crashes near the end of the installation
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 (usually) can be manually fixed with quite a bit of expert knowledge, but I don't know why it fails. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 Date: Thu May 24 18:16:27 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/lubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic lubuntu ubiquity-18.04.14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773224 Title: Installation of Lubuntu crashes near the end of the installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1773224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769423] [NEW] Xbox One S Bluetooth Controller Won't Connect
Public bug reported: When attempting to connect a bluetooth xbox controller the controller would fail to connect. Either, an error message saying "This device could not be connected" or the controller would connect, then disconnect constantly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-21-lowlatency 4.15.0-21.22 ProcVersionSignature: Ubuntu 4.15.0-21.22-lowlatency 4.15.17 Uname: Linux 4.15.0-21-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Sun May 6 13:52:05 2018 InstallationDate: Installed on 2018-04-17 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769423 Title: Xbox One S Bluetooth Controller Won't Connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1769423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769423] Re: Xbox One S Bluetooth Controller Won't Connect
Solution: https://bbs.archlinux.org/viewtopic.php?id=219471 The problem seems to be with ertm. Disabling this works fantastically. echo 1 > /sys/module/bluetooth/parameters/disable_ertm works on a single session If you want a better solution to disable bluetooth ertm, then edit /etc/default/grub and add the kernel flag 'bluetooth.disable_ertm=1' to the GRUB_CMDLINE_LINUX line. Then run 'sudo grub-mkconfig -o /boot/grub/grub.cfg' and reboot. works even on multiple reboots. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769423 Title: Xbox One S Bluetooth Controller Won't Connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1769423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1706701] [NEW] Default Keyring is not unlocked for the user in Lubuntu
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 not have to be retyped. But in Lubuntu, the Default Keyring is locked, and the user has to enter the account password to unlock it before it can be used by the system. • This must be done every time when attempting reconnection after reboot or after logging out and in again. • When this happens, even though the correct account password is entered, the first time, the FTP password is not retrieved. • If the Default Keyring is manually unlocked beforehand (e.g. via seahorse), the connection proceeds without hindrance. Anything that requires access to the Default Keyring within Lubuntu would be affected. This has been tested on Lubuntu 16.04 including a vanilla installation, on both PCManFM and Nautilus. Note that if Lubuntu is used by installing lubuntu-desktop over an Ubuntu 16.04 installation, this problem does not occur. Ubuntu Forums discussion: https://ubuntuforums.org/showthread.php?t=2367062 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnupg 1.4.20-1ubuntu3.1 ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-27-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Jul 26 16:39:16 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-17 (38 days ago) InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnupg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnupg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1706701 Title: Default Keyring is not unlocked for the user in Lubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1706701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 891029] Re: keepass2 (2.16+dfsg-2) crashes switching tabs
@jtaylor I followed your instructions in comment #5 but using +=10 instead of +=5, and this worked for me! I can even use customised tab colours. It seems that the value needs to be rather larger than originally anticipated. BTW, do you think that the KeePass PPA will be updated any time soon to the latest version? Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891029 Title: keepass2 (2.16+dfsg-2) crashes switching tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepass2/+bug/891029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677150] Re: keepass2 (2.35+dfsg-1~ubuntu16.04~ppa1) crashes switching tabs
There is a solution. Please see comment #5 and comment #18 in bug #891029 Also refer https://sourceforge.net/p/keepass/bugs/1634/ KeePass2 needs a minor patch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677150 Title: keepass2 (2.35+dfsg-1~ubuntu16.04~ppa1) crashes switching tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepass2/+bug/1677150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 891029] Re: keepass2 (2.16+dfsg-2) crashes switching tabs
Unfortunately, I still get this error — no custom colours used. Reference https://sourceforge.net/p/keepass/bugs/1634/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/891029 Title: keepass2 (2.16+dfsg-2) crashes switching tabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepass2/+bug/891029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 998546] Re: 0408:3003 [Packard Bell oneTwo (PW.U6C)] Touch-screen did work on 11.04 but no longer works on 12.04
This appears to have been silently fixed as from the 16.04 HWE linux kernel. I have tested this on: • 16.04 64-bit, kernel 4.8.0-45 installed with linux-generic-hwe-16.04 • 16.10 using a Live CD • Today's 17.04 daily build using a Live CD I suppose that this can be marked as solved. Pity it took so long :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/998546 Title: 0408:3003 [Packard Bell oneTwo (PW.U6C)] Touch-screen did work on 11.04 but no longer works on 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/998546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252255] Re: The 'grub-efi-amd64-signed' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot.
@Dr_SE thank you, but my EFI has been many-times checked, and Boot Repair crashes for me :( This bug really does need fixing, especially for newbies to Ubuntu, who would probably give up and go back to Windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252255 Title: The 'grub-efi-amd64-signed' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1252255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1252255] Re: The 'grub-efi-amd64-signed' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot.
Still getting this problem, installing 16.04 or 16.10 on VirtualBox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1252255 Title: The 'grub-efi-amd64-signed' package failed to install into /target/. Without the GRUB boot loader, the installed system will not boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1252255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585592] Re: Ubuntu 16.04 - grub-efi-amd64-signed failed to install into /target/
I am getting this error as well, but the message that @Phillip Susi describes did not happen with me. The disk is correctly partitioned for UEFI. I am a bit lost as to how to diagnose and fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585592 Title: Ubuntu 16.04 - grub-efi-amd64-signed failed to install into /target/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1585592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665329] Re: Installer fails to create startup.nsh for EFI system on VirtualBox
@Phillip Susi Is this something should be filed as a bug on VirtualBox? If so, I have nowhere near sufficient knowledge to file a bug report that makes any sense. Would you be willing to file such a bug report? I found these two bug reports, but I don't know if they are relevant (as I say, I'm not technically expert): https://www.virtualbox.org/ticket/14279 https://www.virtualbox.org/ticket/16373 ** Bug watch added: Virtualbox Trac #14279 http://www.virtualbox.org/ticket/14279 ** Bug watch added: Virtualbox Trac #16373 http://www.virtualbox.org/ticket/16373 -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1665329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665329] Re: Installer fails to create startup.nsh for EFI system on VirtualBox
@Phillip Susi Forgive me if I'm wrong on this — unfortunately, I'm not technically expert. As far as I could tell, the ESP should have startup.nsh. If it's a bug with VirtualBox, I should post a bug report there, but I'd need to know details about how it's wrong. If you could explain, please, or point me to a suitable link online, I'll take it from there. I have been Googling but I'm not finding what I need to find. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1665329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665329] Re: Installer fails to create startup.nsh for EFI system on VirtualBox
** Package changed: ubuntu => ubiquity (Ubuntu) -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1665329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665329] [NEW] Installer fails to create startup.nsh for EFI system on VirtualBox
Public bug reported: Summary: When installing Ubuntu using LUKS & LVM onto a VirtualBox system, it creates a non-bootable system because it fails to create the file startup.nsh on the EFI partition. How to duplicate: 1. Create a new virtual machine on VirtualBox with a sufficiently large disk drive. Ensure that "Enable EFI" is ticked in Settings > System > Motherboard. 2. Run the Ubuntu installer from a Live CD. Chose the default "Erase disk and install Ubuntu". Also tick "Encrypt the new Ubuntu installation for security", which automatically selects "Use LVM with the new Ubuntu installation". 3. Allow the installation to finish. What should happen: 1. On rebooting the virtual machine, it should boot into Ubuntu. What does happen: 1. On rebooting the virtual machine, it boots into the UEFI Interactive Shell and cannot proceed. Workaround: 1. Create a file named startup.nsh on the FS0: drive (either using the UEFI Interactive Shell or by booting into the Live CD). The file should contain the following single line: \EFI\ubuntu\grubx64.efi 2. Reboot the virtual machine. It will boot into Ubuntu. Proposed solution: 1. The Ubuntu installer should create the startup.nsh file when creating the EFI partition. Further information: • Tested on VirtualBox 5.1.14 • Tested with both Ubuntu 16.04.1 64-bit and Lubuntu 16.04.1 64-bit ** Affects: ubuntu Importance: Undecided Status: New ** Tags: bot-comment efi installer uefi ** Attachment added: "Screenshot of the UEFI Interactive Shell where startup.nsh is missing" https://bugs.launchpad.net/bugs/1665329/+attachment/4820123/+files/VirtualBox%20LUKS%20%26%20LVM%20installation%20error.png -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1665329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1186676] Re: gksu handles quoted strings wrongly
Bug still present in 16.04 and 16.10. More information: http://askubuntu.com/questions/21033/what-is-the-difference-between- gksudo-and-gksu/288506#288506 https://ubuntuforums.org/showthread.php?t=1819589 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1186676 Title: gksu handles quoted strings wrongly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1186676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659519] [NEW] System reports error but nothing crashes. libxrender1:i386 has been installed to allow HMRC.'s Basic PAYE. Tools to be run. Tis was apparently successful.
Public bug reported: HMRC.'s Basic PAYE. Tools is a 32bit program being run on a 64bit machine. A whole slug of 32bit library files were installed to satisfy dependencies. I thought this had been successful until I got a recurrent error message. Nothing crashes ! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libxrender1 1:0.9.9-2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 26 09:57:48 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G73 [GeForce 7300 GT] [10de:0393] (rev a1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. G73 [GeForce 7300 GT] [1682:4006] InstallationDate: Installed on 2017-01-22 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Gigabyte Technology Co., Ltd. P35-DS3L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=fa15041b-3491-4d64-b5bb-00b677ef833c ro quiet splash SourcePackage: libxrender UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 11/29/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: P35-DS3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd11/29/2007:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Thu Jan 26 09:37:00 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-I-1TV-1 VGA-1 xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: nouveau ** Affects: libxrender (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659519 Title: System reports error but nothing crashes. libxrender1:i386 has been installed to allow HMRC.'s Basic PAYE. Tools to be run. Tis was apparently successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxrender/+bug/1659519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
