[Bug 2069835] Re: Search current folder ignores generic * outside home
Hello The search works very well in a partition formatted in NTFS. It does not work for a partition formatted in EXT4 whether there is the x-gvfs-show option or not. (ubuntu 22.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069835 Title: Search current folder ignores generic * outside home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2069835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069343] Re: can only attach to mirrors and top-level disks
So palliative was sudo zpool add -f MesDonneesPersonnelles raidz /dev/sdc12 /dev/sdc13 zpool status MesDonneesPersonnelles pool: MesDonneesPersonnelles state: ONLINE config: NAMESTATE READ WRITE CKSUM MesDonneesPersonnelles ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sda18 ONLINE 0 0 0 sdc11 ONLINE 0 0 0 raidz1-1 ONLINE 0 0 0 sdc12 ONLINE 0 0 0 sdc13 ONLINE 0 0 0 errors: No known data errors df -htzfs | grep -E "Taille|Mes" Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur MesDonneesPersonnelles 79G 31G 48G 40% /media/ZFS MesDonneesPersonnelles/sports 11G 11G 587M 95% /media/ZFS/sports MesDonneesPersonnelles/sports/Foot 4,6G4,1G 587M 88% /media/ZFS/sports/Foot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069343 Title: can only attach to mirrors and top-level disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2069343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069343] [NEW] can only attach to mirrors and top-level disks
Public bug reported: Hello There is something wrong somewhere. zfs version zfs-2.2.2-0ubuntu9 zfs-kmod-2.2.2-0ubuntu9 dpkg -l | grep zfs ii libzfs4linux zfs-zed 2.2.2-0ubuntu9 amd64OpenZFS filesystem library for Linux - general support ii zfs-initramfs 2.2.2-0ubuntu9 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii2.2.2-0ubuntu9 amd64OpenZFS Event Daemon ii zfsutils-linux2.2.2-0ubuntu9 amd64command-line tools to manage OpenZFS filesystems zpool status MesDonneesPersonnelles pool: MesDonneesPersonnelles state: ONLINE config: NAMESTATE READ WRITE CKSUM MesDonneesPersonnelles ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 sda18 ONLINE 0 0 0 sdc11 ONLINE 0 0 0 errors: No known data errors df -htzfs | grep -E "Taille|Mes" Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur MesDonneesPersonnelles 32G 31G 953M 98% /media/ZFS MesDonneesPersonnelles/sports 11G 11G 587M 95% /media/ZFS/sports MesDonneesPersonnelles/sports/Foot 4,6G4,1G 587M 88% /media/ZFS/sports/Foot So it's time to add disk space It looks like my order is correct. time sudo zpool attach -f MesDonneesPersonnelles raidz1-0 /dev/sdc12 cannot attach /dev/sdc12 to raidz1-0: can only attach to mirrors and top-level disks real0m6,073s ** Affects: subiquity (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/2069343 Title: can only attach to mirrors and top-level disks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2069343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067377] [NEW] unable to export pool
Public bug reported: I installed version 24.04 in a ZFS partition I noticed that the software used comes from the ZFS-ZED package. I now do another 24.04 installation in another EXT4 partition, I add the missing packages. I can then easily access the data contained in the ZFS partition. I now want to properly release the RPOOL so that it can be mounted without difficulty when I launch the ZFS partition (I reported a bug like this during the installation of zfs) But this is impossible. Despite some internet searching, I can't find the right procedure. zpool version zfs-2.2.2-0ubuntu9 zfs-kmod-2.2.2-0ubuntu9 zpool export rpool cannot export 'rpool': pool is busy zfs get mounted -r rpool NAME PROPERTY VALUESOURCE rpool mounted no - rpool/ROOTmounted no - rpool/ROOT/ubuntu_spel9m mounted no - rpool/ROOT/ubuntu_spel9m/srv mounted no - rpool/ROOT/ubuntu_spel9m/usr mounted no - rpool/ROOT/ubuntu_spel9m/usr/localmounted no - rpool/ROOT/ubuntu_spel9m/var mounted no - rpool/ROOT/ubuntu_spel9m/var/gamesmounted no - rpool/ROOT/ubuntu_spel9m/var/lib mounted no - rpool/ROOT/ubuntu_spel9m/var/lib/AccountsService mounted no - rpool/ROOT/ubuntu_spel9m/var/lib/NetworkManager mounted no - rpool/ROOT/ubuntu_spel9m/var/lib/apt mounted no - rpool/ROOT/ubuntu_spel9m/var/lib/dpkg mounted no - rpool/ROOT/ubuntu_spel9m/var/log mounted no - rpool/ROOT/ubuntu_spel9m/var/mail mounted no - rpool/ROOT/ubuntu_spel9m/var/snap mounted no - rpool/ROOT/ubuntu_spel9m/var/spoolmounted no - rpool/ROOT/ubuntu_spel9m/var/www mounted no - rpool/USERDATAmounted no - rpool/USERDATA/home_4903c3mounted no - rpool/USERDATA/root_4903c3mounted no - rpool/keystoremounted -- umount rpool/USERDATA umount: rpool/USERDATA: Aucun point de montage indiqué. umount rpool/keystore umount: rpool/keystore: Aucun point de montage indiqué. umount rpool/USERDATA/home_4903c3 umount: rpool/USERDATA/home_4903c3: Aucun point de montage indiqué. umount rpool/USERDATA/root_4903c3 umount: rpool/USERDATA/root_4903c3: Aucun point de montage indiqué. zpool export -f rpool cannot export 'rpool': pool is busy zpool export -a rpool too many arguments usage: export [-af] ... zpool export -af rpool too many arguments usage: export [-af] ... Do you have some ideas? THANKS ** Affects: zfs-linux (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/2067377 Title: unable to export pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2067377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065315] Re: NOBLE 24.04 Persistence is not enabled
Good morning. During the first try, I made a mistake in using it. I just started again under the same conditions and persistence works well. With my regrets. df -htext4 FilesystemSize Used Avail Use% Mounted on /dev/disk/by-label/casper-rw 636M 4.8M 585M 1% /var/log sudo lsblk /dev/sdd NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sdd 8:48 1 14.6G 0 disk ├─sdd1 8:49 18G 0 part ├─sdd2 8:50 16G 0 part /cdrom └─sdd3 8:51 1 663M 0 part /var/crash /var/log sudo blkid | grep sdd /dev/sdd1: LABEL="COW" UUID="1519dfcc-0e04-4290-9c39-590b4270305f" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c4d3df7d-01" /dev/sdd2: LABEL_FATBOOT="USBUNET" LABEL="USBUNET" UUID="72EE-4CCC" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="c4d3df7d-02" /dev/sdd3: LABEL="casper-rw" UUID="771a5628-7772-40d4-b5f3-929476b5a1b7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c4d3df7d-03" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065315 Title: NOBLE 24.04 Persistence is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2065315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065315] Re: NOBLE 24.04 Persistence is not enabled
Hello It is now good with this order. ubuntu@ubuntu:~$ sudo fdisk -l /dev/sdb Disk /dev/sdb: 14.65 GiB, 1572864 bytes, 3072 sectors Disk model: DataTraveler 3.0 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc4d3df7d Device BootStart End Sectors Size Id Type /dev/sdb1 2048 16779263 167772168G 83 Linux /dev/sdb2 *16779264 29362175 125829126G b W95 FAT32 /dev/sdb3 29362176 3071 1357824 663M 7 HPFS/NTFS/exFAT ubuntu@ubuntu:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065315 Title: NOBLE 24.04 Persistence is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2065315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065315] Re: NOBLE 24.04 Persistence is not enabled
Good morning I was worried because I read Unknown kernel command line parameters "persistent splash BOOT_IMAGE=/casper/vmlinuz", will be passed to user space. May 09 13:42:42 ubuntu kernel: persistent My live USB is like that a@b:~$ lsblk -fe7 /dev/sdd NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sdd ├─sdd1 vfat FAT32 USBUNET 72EE-4CCC 219,9M 96% /media/a/USBUNET ├─sdd2 ext4 1.0 casper-rw 06f20fd7-c411-4aa5-be02-7b11934f71b97,1G 4% /media/a/casper-rw └─sdd3 exfat 1.0 USBEXFAT F6BD-F745 660,9M 0% /media/a/USBEXFAT a@b:~$ I don't know if this partition should mount automatically or if it's up to me to mount it. If yes, how? The DF command did not list this partition as mounted. THANKS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065315 Title: NOBLE 24.04 Persistence is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2065315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065315] Re: NOBLE 20.04 Persistence is not enabled
** Attachment added: "journalctl -p err" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2065315/+attachment/5776699/+files/journal.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065315 Title: NOBLE 24.04 Persistence is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2065315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065315] Re: NOBLE 20.04 Persistence is not enabled
** Attachment added: "journalctl -g persis" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2065315/+attachment/5776698/+files/Persist.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065315 Title: NOBLE 24.04 Persistence is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2065315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065315] Re: NOBLE 20.04 Persistence is not enabled
** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2065315/+attachment/5776700/+files/Trace.log ** Summary changed: - NOBLE 20.04 Persistence is not enabled + NOBLE 24.04 Persistence is not enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065315 Title: NOBLE 24.04 Persistence is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2065315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065315] [NEW] NOBLE 24.04 Persistence is not enabled
Public bug reported: I'm trying to make persistence work in an installation boot without success. I suspect that the "persistence" parameter which is no longer recognized may be the cause. However, it is possible that with this version there is a new technique to enable persistence. But I can't find how to do it. Thank you for your reply May 09 13:42:42 ubuntu kernel: Kernel command line: BOOT_IMAGE=/casper/vmlinuz quiet persistent splash May 09 13:42:42 ubuntu kernel: Unknown kernel command line parameters "persistent splash BOOT_IMAGE=/casper/vmlinuz", will be passed to user space. May 09 13:42:42 ubuntu kernel: persistent ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CasperVersion: 1.498 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Thu May 9 14:31:58 2024 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065315 Title: NOBLE 24.04 Persistence is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2065315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063209] Re: FS-Cache: Duplicate cookie detected (NFS)
** Attachment added: "FS-Cache.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063209/+attachment/5769692/+files/FS-Cache.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063209 Title: FS-Cache: Duplicate cookie detected (NFS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063209] [NEW] FS-Cache: Duplicate cookie detected (NFS)
Public bug reported: Good morning I think it's the same problem as bug 19223670. But it's in NFS. I actually have two mounts in the fstab lsb_release -d Description:Ubuntu 22.04.4 LTS grep nfs /etc/fstab 192.168.1.22:/media/NosDonnees /media/NosDonneesBureau nfs defaults,user,auto,_netdev 192.168.1.22:/home/a /media/UbuntuBureau nfs defaults,user,auto,_netdev ** Affects: linux (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/2063209 Title: FS-Cache: Duplicate cookie detected (NFS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927807] Re: "https" address causes zsync download to fail with error 'could not read control file from URL'
Hello lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Noble Numbat (development branch) Release:24.04 Codename: noble sudo zsync https://cdimage.ubuntu.com/daily-live/current/noble-desktop-amd64.iso.zsync failed on url https://cdimage.ubuntu.com/daily-live/current/noble-desktop-amd64.iso.zsync could not read control file from URL https://cdimage.ubuntu.com/daily-live/current/noble-desktop-amd64.iso.zsync a@a:~$ sudo zsync http: failed on url http: could not read control file from URL http: and seems good with a@a:~$ sudo zsync http://cdimage.ubuntu.com/daily-live/current/noble-desktop-amd64.iso.zsync 100.0% 1223.2 kBps DONE No relevent local data found - I will be downloading the whole file. If that's not what you want, CTRL-C out. You should specify the local file is the old version of the file to download with -i (you might have to decompress it with gzip -d first). Or perhaps you just have no data that helps download the file downloading from http://cdimage.ubuntu.com/daily-live/current/noble-desktop-amd64.iso: #--- 5.2% 32.8 kBps ETA #--- 8.6% 1288.1 kBps 66:49 ETA ^C -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927807 Title: "https" address causes zsync download to fail with error 'could not read control file from URL' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1927807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059846] Re: The canary thread is apparently starving. Taking actiont
Hello My iPad can be used correctly with a live USB 24.04 and I systematically use it in 22.04 to ensure the internet connection in the absence of a box. For troubleshooting, I used an iPhone -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059846 Title: The canary thread is apparently starving. Taking actiont To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059846] Re: The canary thread is apparently starving. Taking actiont
** Attachment added: "journalctl" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059846/+attachment/5760867/+files/a.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059846 Title: The canary thread is apparently starving. Taking actiont To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059846] [NEW] The canary thread is apparently starving. Taking actiont
Public bug reported: Hello It is when i want connect mu iPAD ** Affects: linux (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/2059846 Title: The canary thread is apparently starving. Taking actiont To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049578] Re: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it.
a@localhost:~$ ubuntu-bug linux-base REDACTED config part /etc/cloud/cloud.cfg.d/90-installer-network.cfg, insufficient permissions a@localhost:~$ Gtk-Message: 19:31:45.720: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. a@localhost:~$ a@localhost:~$ ubuntu Noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049578 Title: Not loading module "atk-bridge": The functionality is provided by GTK natively. Please try to not load it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2049578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056575] [NEW] tracker-extract-3 crashed with SIGSYS in epoll_wait()
Public bug reported: Daily 20240308 ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: tracker-extract 3.4.6-3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.494 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Fri Mar 8 15:45:30 2024 ExecutablePath: /usr/libexec/tracker-extract-3 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306) ProcCmdline: /usr/libexec/tracker-extract-3 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 31 SignalName: SIGSYS SourcePackage: tracker-miners StacktraceTop: epoll_wait (epfd=7, events=0x71b7f6bff11c, maxevents=1, timeout=0) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 ?? () from /lib/x86_64-linux-gnu/libmount.so.1 mnt_monitor_get_fd () from /lib/x86_64-linux-gnu/libmount.so.1 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: tracker-extract-3 crashed with SIGSYS in epoll_wait() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: ** Affects: tracker-miners (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-crash noble ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056575 Title: tracker-extract-3 crashed with SIGSYS in epoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2056575/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056053] [NEW] tracker-extract-3 crashed with SIGSYS in epoll_wait()
Public bug reported: Hello it is Daily 2024/03/04 ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: tracker-extract 3.4.6-3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.494 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Mon Mar 4 16:34:01 2024 ExecutablePath: /usr/libexec/tracker-extract-3 LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240304) ProcCmdline: /usr/libexec/tracker-extract-3 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 31 SignalName: SIGSYS SourcePackage: tracker-miners StacktraceTop: epoll_wait (epfd=7, events=0x75adb13ff11c, maxevents=1, timeout=0) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30 ?? () from /lib/x86_64-linux-gnu/libmount.so.1 mnt_monitor_get_fd () from /lib/x86_64-linux-gnu/libmount.so.1 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: tracker-extract-3 crashed with SIGSYS in epoll_wait() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: ** Affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace noble third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056053 Title: tracker-extract-3 crashed with SIGSYS in epoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/2056053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973126] [NEW] crash ubiquity during installing Lubuntu 22.04
Public bug reported: option ubiquity -b is used because normal installation of grub want modify NVRAM and the computer does not accept. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.15 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470 Date: Thu May 12 08:19:27 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/lubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy lubuntu ubiquity-22.04.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973126 Title: crash ubiquity during installing Lubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1973126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972099] [NEW] computer startup crashes when NFS partition is inaccessible
Public bug reported: Hello. When the NFS partition described in the /etc/fstab file is not accessible (The server is down) starting the computer in version 22.04 is impossible. Message: "you are in emergency mode. After logging, type "journal -xb to view system log This was not the case in previous versions. The computer waited 90 seconds and booted without the NFS partition. I tried adding the nofail or nobootwait options but it didn't work. The line is coded this way: 192.168.0.31:/media/MyDatas /media/NFS defaults,user,auto,_netdev,bg What is the correct solution? Thank you for your reply ** Affects: util-linux (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/1972099 Title: computer startup crashes when NFS partition is inaccessible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1972099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969579] Re: Ubuntu Advantage is available only for Ubuntu 20.04 LTS, 18.04 LTS, 16.04 LTS, and 14.04 ESM.
you wrote Ubuntu LTSbut not Lubuntu LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969579 Title: Ubuntu Advantage is available only for Ubuntu 20.04 LTS, 18.04 LTS, 16.04 LTS, and 14.04 ESM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1969579] Re: Ubuntu Advantage is available only for Ubuntu 20.04 LTS, 18.04 LTS, 16.04 LTS, and 14.04 ESM.
Hello Thank you for your reply. In fact my real question is whether *L*ubuntu can also take advantage of ESM thank you Le 28/04/2022 à 17:16, Ivo Jansky a écrit : > Workaround: > Until the issue gets fixed, you should be able to use the "Buy now" button > instead of pressing the enter key in the third step. Please reply back, if > the workaround does not solve the issue for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969579 Title: Ubuntu Advantage is available only for Ubuntu 20.04 LTS, 18.04 LTS, 16.04 LTS, and 14.04 ESM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969579] [NEW] Ubuntu Advantage is available only for Ubuntu 20.04 LTS, 18.04 LTS, 16.04 LTS, and 14.04 ESM.
Public bug reported: Hello. I want to install "Extended Security Maintenance" in my computer which has a 20.04 version of ubuntu. He doesn't seem to recognize her. The error message is: "Other versions? Ubuntu Advantage is available only for Ubuntu 20.04 LTS, 18.04 LTS, 16.04 LTS, and 14.04 ESM. You can: Upgrade to a supported version Explore community support options" I proceed as follows: First connect to ubuntu one ( https://login.ubuntu.com/ ) 1) Connect to https://ubuntu.com/security/esm 2) Click on "get started with ubuntu advantage" ( https://ubuntu.com/advantage ) 3) Click on "buy new subscription" What are you setting up? ==> Desktops What Ubuntu version are you running? > Ubuntu 20.04 Do you also want tech support? ===> No, thanks Software and security updates only How many? ===> 1 Then "enter" for validate, and the above message is displayed. For information cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.4 LTS" uname -a Linux a 5.13.0-39-generic #44~20.04.1-Ubuntu SMP Thu Mar 24 16:43:35 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux cat /var/log/installer/media-info Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) I have the same problem with version 18.04. As well as another user for whom it is important because it cannot work in version 20.04.(https://forum.ubuntu-fr.org/edit.php?id=22554344 ) Thank you ** Affects: ubuntu-advantage-tools (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/1969579 Title: Ubuntu Advantage is available only for Ubuntu 20.04 LTS, 18.04 LTS, 16.04 LTS, and 14.04 ESM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1969579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728354] Re: ntfs: unsupported reparse point
Hello. I just found the reason. The receiving partition was formatted in FAT32 sorry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728354 Title: ntfs: unsupported reparse point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728354] Re: ntfs: unsupported reparse point
Hello there are at least all files ending with .mui getfattr -h -n system.ntfs_reparse_data -e hex "/media/a/W21H2B/Program Files/WindowsApps/Microsoft.LanguageExperiencePackfr-FR_19041.40.124.0_neutral__8wekyb3d8bbwe/Windows/System32/fr-FR/CompMgmtLauncher.exe.mui" getfattr : Suppression des « / » en tête des chemins absolus # file: media/a/W21H2B/Program Files/WindowsApps/Microsoft.LanguageExperiencePackfr-FR_19041.40.124.0_neutral__8wekyb3d8bbwe/Windows/System32/fr-FR/CompMgmtLauncher.exe.mui system.ntfs_reparse_data=0x17801100020001000200 $(which ntfs-3g) -help 2>&1 | grep ration ntfs-3g 2021.8.22 integrated FUSE 28 - Third Generation NTFS Driver Configuration type 7, XATTRS are on, POSIX ACLS are on file $(which ntfs-3g) /usr/bin/ntfs-3g: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=d6eead7b0c79cb65b47b4f8cb1c89108e3ffe0d5, for GNU/Linux 3.2.0, stripped md5sum $(which ntfs-3g) 0516ddcc6b804b856b606ac2ed6ceab6 /usr/bin/ntfs-3g ls -ld $(strings $(which ntfs-3g) | grep ntfs-plugin | sed -e 's/ntfs-plugin.*//') ls: impossible d'accéder à '/usr/lib/x86_64-linux-gnu/ntfs-3g/': Aucun fichier ou dossier de ce type ls /usr/lib/x86_64-linux-gnu/n* /usr/lib/x86_64-linux-gnu/nautilus: extensions-3.0 /usr/lib/x86_64-linux-gnu/nss: libfreebl3.chk libfreebl3.so libfreeblpriv3.chk libfreeblpriv3.so libnssckbi.so libnssdbm3.chk libnssdbm3.so libsoftokn3.chk libsoftokn3.so dpkg -l | grep ntfs ii libntfs-3g89 1:2021.8.22-3ubuntu1 amd64read/write NTFS driver for FUSE (runtime library) ii ntfs-3g1:2021.8.22-3ubuntu1 amd64read/write NTFS driver for FUSE 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/1728354 Title: ntfs: unsupported reparse point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728354] Re: ntfs: unsupported reparse point
Hello Same problème with 22.04 Beta Jammy "time sudo rsync -av --del --exclude=pagefile.sys --exclude=OneDrive --exclude=Edge* /media/$USER/$PART/* /media/$USER/$PART-SAVE >résultat-$PART" ** Attachment added: "list of errors" https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728354/+attachment/5577834/+files/r%C3%A9sultat-W21H2a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728354 Title: ntfs: unsupported reparse point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967748] [NEW] kswapd0 take 100% processor
Public bug reported:
Hello
I don't know if this is normal operation or if it is possible to configure
KSWAPD0.
I installed version 22.04 (jammy) choosing encrypted ZFS partitioning in an
external disk.
The installation chose to assign the swap partition to SDC2.
On reboot, this partition does not exist. Depending on how I reboot it is
either seen as SDA2 or SDB2. So I deactivated and opened a bug
(https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409)
However, this does not seem to block me.
So I decided to continue using ZFS.
My first decision was to copy the contents of my personal data partition to a
directory under rpool/USERDATA
with the RSYNC command
This action lasts several hours and requires a lot of inputs and
outputs. I noticed that firefox stopped responding. Every second, a
message asking if I want to wait is displayed.
I also saw that the KSWAPD0 process almost permanently consumes a
processor.
All this seems to me to be related to the copy. ( time sudo rsync -av
--exclude {'.Trash*','Downloads','$RECYCLE.BIN'} /media/Common /Common )
I know that ZFS wants to use the full RAM (6GB) to be able to maximally
compress the data.
So my question is whether this is completely normal. I would still like
to be able to consult the Internet while copying a directory.
I post under KSWAP0 without knowing if he is entirely responsible.
thank you
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-23-generic 5.15.0-23.23
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: a 3727 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 4 14:27:55 2022
HibernationDevice: RESUME=none
InstallationDate: Installed on 2022-04-01 (2 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
MachineType: TOSHIBA SATELLITE S70t-A
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_b4yff9@/vmlinuz-5.15.0-23-generic
root=ZFS=rpool/ROOT/ubuntu_b4yff9 ro
RelatedPackageVersions:
linux-restricted-modules-5.15.0-23-generic N/A
linux-backports-modules-5.15.0-23-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2014
dmi.bios.release: 1.30
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.30
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Type2 - Board Product Name1
dmi.board.vendor: Type2 - Board Vendor Name1
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.ec.firmware.release: 1.30
dmi.modalias:
dmi:bvnInsydeCorp.:bvr1.30:bd04/18/2014:br1.30:efr1.30:svnTOSHIBA:pnSATELLITES70t-A:pvrPSKN6E-01C00KFR:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:skuPSKN6E:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE S70t-A
dmi.product.sku: PSKN6E
dmi.product.version: PSKN6E-01C00KFR
dmi.sys.vendor: TOSHIBA
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
** Attachment added: "TOP -N 1"
https://bugs.launchpad.net/bugs/1967748/+attachment/5576841/+files/KSWAPD0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967748
Title:
kswapd0 take 100% processor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967748/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962409] Re: ZFS: The content of the /etc/crypttab file is bad
Hello Same problem withe beta jammy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962409 Title: ZFS: The content of the /etc/crypttab file is bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859899] Re: Please add a ZFS gui
Hello Hello With the arrival of version 22.04, it is now certain that ZFS is a way to do an installation. It seems abnormal to me that gnome-disks keeps saying that ZFS is an unknown system and doesn't know how to mount it. Please do the needful quickly. Do not forget that the partition can be encrypted. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859899 Title: Please add a ZFS gui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1859899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965961] Re: gjs and mount.ntfs loop together with 150 processeor and errors
lines 68-111 a@a:~$ journalctl -b -p err mars 22 16:11:38 a kernel: Bluetooth: Patch file not found ar3k/AthrBT_0x3101.dfu mars 22 16:11:38 a kernel: Bluetooth: Loading patch file failed mars 22 16:11:49 a gpod[1414]: No device found with uuid bd21926a45c292c575869dffe91ae2b1458bfb40, is it plugged in? mars 22 16:12:14 a gnome-session-binary[2712]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed mars 22 16:12:14 a gnome-session-binary[2712]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed mars 22 16:12:40 a gdm-password][3399]: gkr-pam: unable to locate daemon control file mars 22 16:12:41 a kernel: nouveau :01:00.0: bus: MMIO read of FAULT at 002140 [ !ENGINE ] mars 22 16:12:43 a systemd[3449]: Failed to start Application launched by gnome-session-binary. mars 22 16:12:43 a systemd[3449]: Failed to start Application launched by gnome-session-binary. mars 22 16:12:43 a systemd[3449]: Failed to start Application launched by gnome-session-binary. mars 22 16:12:46 a systemd[3449]: Failed to start Application launched by gnome-session-binary. mars 22 16:12:46 a systemd[3449]: Failed to start Application launched by gnome-session-binary. mars 22 16:12:48 a gdm-launch-environment][2539]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed** a@a:~$ journalctl -b -g finalize | head mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af71f8cb0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7157540 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7157620 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7157620 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7157620 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7151740 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7141020 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af71574d0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af7157700 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:14:04 a gnome-shell[3636]: Object 0x564af71f8cb0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. a@a:~$ journalctl -b -g finalize | wc -l 635 a@a:~$ journalctl -b -g finalize | tail mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c41bb270 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c40ad140 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f568000aa20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f568000aa20 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c427ce00 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c41e1cc0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c40ad290 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x564af56b74a0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x564af53ef4c0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. mars 22 16:54:50 a gnome-shell[3636]: Object 0x7f56c427cd90 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management. a@a:~$ -- You received
[Bug 1965961] [NEW] gjs and mount.ntfs loop together with 150 processeor and errors
Public bug reported: a@a:~$ journalctl -g finalized mars 22 15:27:05 a gnome-shell[4162]: Object 0x5574e1359b30 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:05 a gnome-shell[4162]: Object 0x7ff0e0025d70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:05 a gnome-shell[4162]: Object 0x7ff0dc0134d0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:36 a gnome-shell[4162]: Object 0x5574dfdfb6f0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:36 a gnome-shell[4162]: Object 0x5574e1bbb050 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:36 a gnome-shell[4162]: Object 0x5574e1359b30 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:36 a gnome-shell[4162]: Object 0x7ff0e0025e50 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:27:52 a gnome-shell[4162]: Object 0x5574e062b4d0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:28:02 a gnome-shell[4162]: Object 0x5574e17f1770 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:28:02 a gnome-shell[4162]: Object 0x7ff0e0027cb0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:28:02 a gnome-shell[4162]: Object 0x5574e256ab70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 15:28:02 a gnome-shell[4162]: Object 0x5574e256a940 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:34 a gnome-shell[4162]: Object 0x5574e3642250 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:34 a gnome-shell[4162]: Object 0x7ff0e02c8ec0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:34 a gnome-shell[4162]: Object 0x7ff0e02d9830 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff090003f40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e3642250 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e0be0910 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e0026f70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e062b5b0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e02c8ec0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e0be09f0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e0be0a60 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e0215530 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x5574e2f1f490 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e02d9910 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e02d9830 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e01fa190 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory manageme> mars 22 14:29:44 a gnome-shell[4162]: Object 0x7ff0e02d9830 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid
[Bug 1962409] Re: ZFS: The content of the /etc/crypttab file is bad
Hello Same problem with this version jammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962409 Title: ZFS: The content of the /etc/crypttab file is bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
Hello This version is now good. jammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962387] Re: EFI is not on the drive
Hello Same problem with this version jammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962387 Title: EFI is not on the drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960083] Re: dirname applet missing from initramfs
Hello This version is goodjammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961055] Re: Key load error: Failed to open key material file: No such file or directory
Hello This version in now goodjammy-desktop-amd64.iso 2022-03-21 08:38 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961055 Title: Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1961055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927071] Re: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot)
Hello. with Daily ubuntu. with snap firefox_1%3a The message is. still unable to contact the Store. Trying for another 20 minutes. after a message for continue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927071 Title: Fresh install of chromium-browser during installer-like process, in a chroot fails (when preparing machines prior to first boot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1927071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963902] [NEW] xdg-user-dirs-gtk-update not working properly
Public bug reported: Hello. It seems to me that the xdg-user-dirs-gtk-update command does nothing at all. I want to change the location of the download directory. So I move the directory with this command: "mv -v /media/Common/a/Downloads /media/Common/a/BisDownloads" Then I update my reference file with this command: "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/DownloadsBis" Then I think to inform the software that the directory has changed by doing this command: "xdg-user-dirs-gtk-update" But when initiating a download, it cannot be done with the error message "...unable to save because an unknown error has occurred" Also, the "files" application continues to reference the old directory as if no update had been made. I have to log out and log back in to get everything working properly again. On the other hand, would it be possible to modify the contents of the file "user-dirs.dirs" to clearly say if the modification carried out by the command "xdg-user-dirs-update --set DOWNLOAD /media/Commun/a/TéléchargementsBis" is immediately carried out wherever necessary or if it is necessary to make another additional command or if it is necessary to wait for the next session launch because the message is not very understandable by saying only that the modifications are not lost. UBUNTU version 20.04 Thank you. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 41.3-3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 7 13:09:20 2022 InstallationDate: Installed on 2022-02-16 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220216) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963902 Title: xdg-user-dirs-gtk-update not working properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1963902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962409] Re: ZFS: The content of the /etc/crypttab file is bad
** Description changed: Hello I just installed the zfs 22.04 encrypted version on an external drive. When I launch the installed software, there is a loss of time of 90 seconds looking for the partition containing the swap. Would it be possible to replace the device name with a UUID name in the /etc/crypttab? - Indeed at the time of installation the disk is SDC but it becomes SDA during startup... - + Indeed at the time of installation the disk is SDC but it becomes SDA or SDB during startup... + cat /etc/crypttab cryptoswap/dev/sdc2 /dev/urandomswap,initramfs blkid | grep LUKS /dev/sda2: UUID="6897cf48-5e28-4163-9de5-056b1385063c" TYPE="crypto_LUKS" PARTUUID="a8a79383-adb6-eb4c-95b6-fd40affd90d0" /dev/zd0: UUID="e516377f-ee45-46e2-a3b0-03869113269a" TYPE="crypto_LUKS" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962409 Title: ZFS: The content of the /etc/crypttab file is bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962409] [NEW] ZFS: The content of the /etc/crypttab file is bad
Public bug reported: Hello I just installed the zfs 22.04 encrypted version on an external drive. When I launch the installed software, there is a loss of time of 90 seconds looking for the partition containing the swap. Would it be possible to replace the device name with a UUID name in the /etc/crypttab? Indeed at the time of installation the disk is SDC but it becomes SDA during startup... cat /etc/crypttab cryptoswap /dev/sdc2 /dev/urandomswap,initramfs blkid | grep LUKS /dev/sda2: UUID="6897cf48-5e28-4163-9de5-056b1385063c" TYPE="crypto_LUKS" PARTUUID="a8a79383-adb6-eb4c-95b6-fd40affd90d0" /dev/zd0: UUID="e516377f-ee45-46e2-a3b0-03869113269a" TYPE="crypto_LUKS" ** Affects: systemd (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/1962409 Title: ZFS: The content of the /etc/crypttab file is bad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
Hello SOLVED with new Daily jammy-desktop-amd64.iso 2022-02-26 08:21 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962387] [NEW] EFI is not on the drive
Public bug reported: Hello I just installed the latest release jammy made on Feb 26 in an ZFS external hard drive. I would have liked the part of BOOT EFI to also go to the external hard drive and not to the internal hard drive. It is true that it is an error which certainly dates from the creation of the EFI ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "some commands" https://bugs.launchpad.net/bugs/1962387/+attachment/5563988/+files/EFI.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962387 Title: EFI is not on the drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
The little script that makes ZFS booting impossible. sudo -i #1) Montage des partitions contenant le logiciel rmdir /ZFS zpool import -N -R /ZFS rpool && sleep 5 zfs set canmount=on rpool && zfs mount -v rpool for var in $(zfs list | grep ROOT/ubuntu|cut -d" " -f1) do echo $var zfs set canmount=on $var && zfs mount -v $var sleep 1 done #2) On récupère la séquence de boot. Mais c'est celle obtenue en mode recovery et pas la dernière !!! journalctl -b -p err -D /ZFS/var/log/journal >/home/a/boot-ERR.txt journalctl -b-D /ZFS/var/log/journal >/home/a/boot-TOT.txt #3) On démonte le root for var in $(zfs list | tac | grep ROOT/ubuntu|cut -d" " -f1) do echo $var zfs unmount $var && zfs set canmount=off $var && sleep 1 done zfs unmount rpool && zfs set canmount=off rpool && sleep 1 umount -v --recursive /ZFS zpool export rpool zpool list ** Attachment added: "The little script that makes ZFS booting impossible." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+attachment/5563870/+files/CHROOTnormal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
Hello. To advance this problem, I decided to redo a brand new installation without using encryption. I can also boot several times without any difficulty. With another O.S. in version 22.04 installed in an EXT4 partition, I launched the script to access this ZFS partition. The problem is reproduced in a simpler way. The boot does not finish despite waiting about an hour. I took a screenshot which I am attaching. I know the problem is systematic. Using the quoted script, I can access the log. But I see that the log has not yet been created. I am only allowed to boot into recovery mode. It's a little better. The boot hangs less I am attaching the errors encountered and the entire trace of the log. All this is obtained by the aforementioned script. I'm willing to admit that my script isn't up to snuff. however this should absolutely not prevent ZFS from booting. I don't know whether to do another bug report or if it can stay in this one. Good research and good editing. ** Attachment added: "photograph of unencrypted ZFS boot hang" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+attachment/5563868/+files/boot.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
The little script that makes ZFS booting impossible. ** Attachment added: "The little script that makes ZFS booting impossible." https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+attachment/5563869/+files/CHROOTchiffr%C3%A9.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961910] Re: Ubuntu 22 crash when updating, broken network manager and cannot report bug
Hello. Hello Not exactly the same. it processes a few files and the toshiba boot screen is offered. I can only press the restart button on the lap -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961910 Title: Ubuntu 22 crash when updating, broken network manager and cannot report bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1961910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962061] Re: ZFS Key load error: Failed to open key material file: No such file or directory
Helle Hello Here is the access sequence to the encrypted partition from another O.S. zpool import -N -R /ZFS rpool && sleep 10 if [ -e /dev/zvol/rpool/keystore ] ; then cryptsetup -v open /dev/zvol/rpool/keystore keystore-rpool && sleep 10 mkdir -p /run/keystore/rpool mount -v /dev/mapper/keystore-rpool /run/keystore/rpool && sleep 10 fi Here is an encrypted partition release sequence from another O.S. which prevents the boot of the encrypted partition shutdown or crash of O.S. Another zpool export rpool && shutdown Antoher umount -v /run/keystore/rpool && sleep 5 cryptsetup -v close /dev/mapper/keystore-rpool && sleep 5 zpool export rpool shutdown Here is the correct sequence of freeing encrypted partition from another O.S. which allows the boot of the encrypted partition. But first you have to go through the recovery option. There's probably a better solution. umount -v /run/keystore/rpool && sleep 5 cryptsetup -v luksClose /dev/mapper/keystore-rpool && sleep 5 zpool export rpool && zpool list shutdown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962061] [NEW] ZFS Key load error: Failed to open key material file: No such file or directory
Public bug reported: Hello The message is Key load error: Failed to open key material file: No such file or directory Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied Hello I recently installed an encrypted ZFS 22.04 version. She boots well. I can do the updates and reboot except that now the reboot is impossible because of the message above. I suspect that access to the encryption keys has become impossible. The reason could be a borrowing of these keys by another O.S. with poor quality playback. For example forget to free the key file because the incident is systematic have a good day ** Affects: systemd (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/1962061 Title: ZFS Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1962061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959194] Re: zfs mount is error free but no directory is present
Hello. i have solved the problem by writing zfs mount -v $(zfs list | grep ROOT/ubuntu | head -1 |cut -d" " -f1) zfs mount -v $(zfs list | grep BOOT/ubuntu | head -1 |cut -d" " -f1) But i don't kwnow if it is the goodQ- solution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959194 Title: zfs mount is error free but no directory is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1959194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961055] Re: Key load error: Failed to open key material file: No such file or directory
Hello I worked around the problem by removing the words quiet splash from the entry menus of the /boot/grub/grub.cfg file so that I could enter the password. But the swap partition is not mounted. Probably because is name is now SDA2 and not SDC2 which was the name during installation on a external drive. sudo blkid | grep sda2 /dev/sda2: UUID="99ce927e-67ae-4e9a-93f1-ac637af7f34f" TYPE="crypto_LUKS" PARTUUID="caada0e6-030f-5143-93f8-8534629af79c" a@a:~$ df -h Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur tmpfs 583M2,1M 581M 1% /run /dev/mapper/keystore-rpool 437M 28K 404M 1% /run/keystore/rpool rpool/ROOT/ubuntu_trj428 444G3,1G 441G 1% / tmpfs 2,9G3,3M 2,9G 1% /dev/shm tmpfs 5,0M4,0K 5,0M 1% /run/lock rpool/USERDATA/root_77w87m 441G384K 441G 1% /root rpool/ROOT/ubuntu_trj428/var/mail 441G256K 441G 1% /var/mail rpool/ROOT/ubuntu_trj428/var/snap 441G1,9M 441G 1% /var/snap rpool/ROOT/ubuntu_trj428/var/www 441G256K 441G 1% /var/www rpool/ROOT/ubuntu_trj428/srv 441G256K 441G 1% /srv rpool/USERDATA/a_77w87m441G102M 441G 1% /home/a rpool/ROOT/ubuntu_trj428/var/spool 441G384K 441G 1% /var/spool rpool/ROOT/ubuntu_trj428/var/games 441G256K 441G 1% /var/games rpool/ROOT/ubuntu_trj428/usr/local 441G512K 441G 1% /usr/local rpool/ROOT/ubuntu_trj428/var/lib 442G1,3G 441G 1% /var/lib rpool/ROOT/ubuntu_trj428/var/lib/AccountsService 441G256K 441G 1% /var/lib/AccountsService rpool/ROOT/ubuntu_trj428/var/lib/NetworkManager441G256K 441G 1% /var/lib/NetworkManager rpool/ROOT/ubuntu_trj428/var/lib/apt 441G 96M 441G 1% /var/lib/apt rpool/ROOT/ubuntu_trj428/var/lib/dpkg 441G 51M 441G 1% /var/lib/dpkg rpool/ROOT/ubuntu_trj428/var/log 441G3,2M 441G 1% /var/log bpool/BOOT/ubuntu_trj428 1,8G 85M 1,7G 5% /boot /dev/sdb1 98M 32M 67M 32% /boot/efi tmpfs 583M 11M 573M 2% /run/user/1000 note The goog name seems /run/keystore/rpool journalctl -b -p err févr. 17 00:33:23 a systemd[1]: Timed out waiting for device /dev/sdc2 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961055 Title: Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1961055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961055] Re: Key load error: Failed to open key material file: No such file or directory
** Description changed: Hello This morning I downloaded the UBUNTU JAMMY version which had just been made an hour earlier. I installed it asking for encryption. When I boot, the password is asked. He is accepted. But root mount is denied. ... find: /dev/zvol: No such file or directory key load error: Failed to open key matéral file No such file or directory Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted: permission denied - - Picture will come + Picture is here https://zupimages.net/viewer.php?id=22/07/v372.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961055 Title: Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1961055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961055] [NEW] Key load error: Failed to open key material file: No such file or directory
Public bug reported: Hello This morning I downloaded the UBUNTU JAMMY version which had just been made an hour earlier. I installed it asking for encryption. When I boot, the password is asked. He is accepted. But root mount is denied. ... find: /dev/zvol: No such file or directory key load error: Failed to open key matéral file No such file or directory Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted: permission denied Picture will come ** Affects: systemd (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/1961055 Title: Key load error: Failed to open key material file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1961055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960083] Re: dirname applet missing from initramfs
Hello Oh!!! jammy-desktop-amd64.iso 2022-02-16 08:353.1GDesktop image for 64-bit PC (AMD64) computers (standard download) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960083] Re: dirname applet missing from initramfs
I just downloaded the iso today, then I redid an installation But it's still the version minus one I don't know how to update the ISO I just downloaded before installing it -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960083] Re: dirname applet missing from initramfs
Hello Are you sure? https://zupimages.net/viewer.php?id=22/07/fxcb.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960083 Title: dirname applet missing from initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1960083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959194] [NEW] zfs mount is error free but no directory is present
Public bug reported: Hello In a 22.04 version installed in an EXT4 partition, I am trying to watch the contents of a 22.04 version installed in a ZFS partition. I can't. However, I can easily access the "duplicate" of this partition which was created under ZFS. I think it certainly needs an additional option that I can't find. But maybe this is a bug??? Can you help me. Thank you. sudo blkid | grep zfs_member /dev/sdb4: LABEL="rpool" UUID="3705767347231228268" UUID_SUB="17088151264315178202" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="4c7ee6a4-46e4-a244-83ad-744047de9184" /dev/sdb3: LABEL="bpool" UUID="2280493683547443963" UUID_SUB="6738067129089399524" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="ab89c3ca-8125-dc40-83f9-2d1050c1251c" /dev/sdc6: LABEL="poolSORTIE" UUID="10752972542097428173" UUID_SUB="3388036065267144189" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="2be01f36-25c3-463c-9ba2-fbbe0b0b9a45" On a duplicate partition of rpool all is good sudo zpool import -f -N poolSORTIE Sortie; zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT Sortie 19.5G 10.1G 9.36G- - 0%51% 1.00xONLINE - sudo zfs set mountpoint=/mnt/Sortie Sortie sudo zfs set canmount=on Sortie sudo zfs mount Sortie ls /mnt/Sortie bin boot cdrom dev etc home lib lib32 lib64 libx32 media mnt opt proc sudo zpool export Sortie ; zpool list no pools available ls /mnt/Sortie -- On the rpool partition, No directory is visible. sudo zpool import -f -N rpool Root; zpool list NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT Root 920G 5.00G 915G- - 0% 0% 1.00xONLINE - sudo zfs set mountpoint=/mnt/Root Root sudo zfs set canmount=on Root sudo zfs mount Root ls /mnt/Root However no error on the mount action janv. 27 09:43:51 b sudo[8050]:a : TTY=pts/1 ; PWD=/home/a ; USER=root ; COMMAND=/usr/sbin/zpool import -f -N rpool Root janv. 27 09:43:51 b sudo[8050]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) janv. 27 09:43:55 b zed[8214]: eid=37 class=config_sync pool='Root' janv. 27 09:43:55 b zed[8216]: eid=38 class=pool_import pool='Root' janv. 27 09:43:55 b zed[8238]: eid=40 class=config_sync pool='Root' janv. 27 09:43:55 b sudo[8050]: pam_unix(sudo:session): session closed for user root janv. 27 09:44:59 b sudo[8360]:a : TTY=pts/1 ; PWD=/home/a ; USER=root ; COMMAND=/usr/sbin/zfs set mountpoint=/mnt/Root Root janv. 27 09:44:59 b sudo[8360]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) janv. 27 09:45:00 b sudo[8360]: pam_unix(sudo:session): session closed for user root janv. 27 09:45:00 b sudo[8376]:a : TTY=pts/1 ; PWD=/home/a ; USER=root ; COMMAND=/usr/sbin/zfs set canmount=on Root janv. 27 09:45:00 b sudo[8376]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) janv. 27 09:45:00 b sudo[8376]: pam_unix(sudo:session): session closed for user root janv. 27 09:45:00 b sudo[8387]:a : TTY=pts/1 ; PWD=/home/a ; USER=root ; COMMAND=/usr/sbin/zfs mount Root janv. 27 09:45:00 b sudo[8387]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000) janv. 27 09:45:00 b sudo[8387]: pam_unix(sudo:session): session closed for user root sudo zpool export Root ; zpool list ls /mnt/Root ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 27 10:33:07 2022 InstallationDate: Installed on 2021-11-01 (86 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211031) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission non accordée: '/etc/sudoers.d/zfs'] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959194 Title: zfs mount is error free but no directory is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1959194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956160] Re: resize btrfs partition too much
** Attachment added: "gparted_BTRFS1.htm" https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1956160/+attachment/5550581/+files/gparted_BTRFS1.htm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956160 Title: resize btrfs partition too much To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1956160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956160] Re: resize btrfs partition too much
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1956160/+attachment/5550582/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956160 Title: resize btrfs partition too much To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1956160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956160] Re: resize btrfs partition too much
** Attachment added: "gparted_BTRFS.htm" https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1956160/+attachment/5550580/+files/gparted_BTRFS.htm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956160 Title: resize btrfs partition too much To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1956160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956160] [NEW] resize btrfs partition too much
Public bug reported: it is possible to decrease the size of a btrfs partition. But not too much. It seems that there should be a minimum of 4 GB of free space? Is it possible to take it into account in the calculation of the reduction proposal? Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gparted 1.2.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Jan 1 19:32:18 2022 InstallationDate: Installed on 2021-11-01 (60 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211031) SourcePackage: gparted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gparted (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/1956160 Title: resize btrfs partition too much To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1956160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951578] Re: unable to install apt-offline
hello sudo apt update has bigs errors... => it was an error in the file/etc/apt/sources.list sorry -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951578 Title: unable to install apt-offline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-offline/+bug/1951578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951634] Re: package iotop missing
hello sudo apt update has bigs errors... => it was an error in the file/etc/apt/sources.list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951634 Title: package iotop missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iotop/+bug/1951634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951634] [NEW] package iotop missing
Public bug reported: Hello sudo apt full-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" iotop Command 'iotop' not found, but can be installed with: sudo apt install iotop sudo apt install iotop Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package iotop Thanks ** Affects: linux (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/1951634 Title: package iotop missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951578] [NEW] unable to install apt-offline
Public bug reported: hello Installation off apt-offline impossible in ubuntu 20.04 apt-offline --help Command 'apt-offline' not found, but can be installed with: sudo apt install apt-offline sudo apt install apt-offline Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package apt-offline cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.3 LTS" ** Affects: apt-offline (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/1951578 Title: unable to install apt-offline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-offline/+bug/1951578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951416] [NEW] gparted fat32 mtools
Public bug reported: hello. gparted incorrectly indicates that all fat32 partitions are in trouble only because the mtools package is missing. Can you rectify in the right place: In the O.S. main or during the installation of gparted Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 41.2-1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 18 13:28:36 2021 InstallationDate: Installed on 2021-11-01 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211031) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951416 Title: gparted fat32 mtools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1951416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949355] [NEW] unity-tweak-tool
Public bug reported:
Hello
it seems to me that the installation of unity-tweak-tool is going wrong
Paramétrage de unity-tweak-tool (0.0.7+-0ubuntu9) ...
/usr/lib/python3/dist-packages/UnityTweakTool/__init__.py:136: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
assert id is not -1
/usr/lib/python3/dist-packages/UnityTweakTool/section/spaghetti/theme.py:155:
SyntaxWarning: "is" with a literal. Did you mean "=="?
self.ui['check_cursor_size'].set_active(True if
gsettings.interface.get_int('cursor-size') is 48 else False)
a@a:~$
thank you
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 40.4-2
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 1 12:33:30 2021
InstallationDate: Installed on 2021-10-24 (8 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
KernLog:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2021-10-29 (2 days ago)
** Affects: unity-tweak-tool (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949355
Title:
unity-tweak-tool
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1949355/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945974] Re: systemctl hibernate not write the contents of the RAM into swap partition or swapfile. le
However sudo hibernate work correctly! ** Attachment added: "The journalct trace of sudo hibernate command" https://bugs.launchpad.net/ubuntu/+source/hibernate/+bug/1945974/+attachment/5530464/+files/s2disk.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945974 Title: systemctl hibernate not write the contents of the RAM into swap partition or swapfile. le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hibernate/+bug/1945974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945974] [NEW] systemctl hibernate not write the contents of the RAM into swap partition or swapfile. le
Public bug reported: Hello I see that the systemctl hibernate command does not write the contents of the nvram in the swap partition (or in the swap file). This is also true in version 21.04 There is therefore no restart with the recovered data. Worse, when restarting, the partition is not in good condition. The FSCK command automatically repairs the partition structure. I work around the problem with the sudo hibernate command which calls the S2DISK process, but it doesn't work if using a swap file and is only present for LTS versions! Please tell me the correct method to use. File systemctl.txt contains the traces of systemctl hibernate => you will see just ONE LINE for the hibernation action. oct. 03 19:47:52 a kernel: PM: hibernation entry File s2disk.txt contains the traces of sudo hiberntate == you will see the copy of the ram oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x-0x0fff] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x00088000-0x000f] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x2000-0x201f] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x40004000-0x40004fff] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x94a13000-0x94a13fff] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x94a23000-0x94a24fff] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x94a32000-0x94a32fff] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x959b-0x961a] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x961b1000-0x961b1fff] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x961bd000-0x961bdfff] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x97d3c000-0x97db6fff] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x9a7bf000-0x9affefff] oct. 04 12:17:20 a kernel: PM: Marking nosave pages: [mem 0x9b00-0x] oct. 04 12:17:20 a kernel: PM: Basic memory bitmaps created oct. 04 12:17:20 a kernel: PM: Preallocating image memory... done (allocated 666109 pages) oct. 04 12:17:20 a kernel: PM: Allocated 2664436 kbytes in 0.64 seconds (4163.18 MB/s) oct. 04 12:17:20 a kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done Thinks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hibernate 2.0+15+g88d54a8-1 ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140 Uname: Linux 5.4.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Oct 4 12:56:25 2021 InstallationDate: Installed on 2021-06-05 (120 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) PackageArchitecture: all SourcePackage: hibernate UpgradeStatus: Upgraded to focal on 2021-06-06 (119 days ago) ** Affects: hibernate (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "journal trace of systemctl hibernate" https://bugs.launchpad.net/bugs/1945974/+attachment/5530460/+files/systemctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945974 Title: systemctl hibernate not write the contents of the RAM into swap partition or swapfile. le To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hibernate/+bug/1945974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
hello a completely lost user => https://forum.ubuntu-fr.org/viewtopic.php?id=2066473 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Hello I still say that the action proposed by these lines " dev/XXX: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/ requires a manual fsck" Is not easy to understand. So I suggested a change of presentation that could become this one: "busybox allows you to manually repair the software partition if you hit 'fsck /dev/xx' to its command "(initramfs)". When the repair is complete, type the word 'exit' in order to continue the boot sequence." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Hello "It asks me to do an fsk manually if I read between the lines, and I don't understand what that means or what to do." => https://forum.ubuntu-fr.org/viewtopic.php?pid=22480277#p22480277 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Hello Thanks for your answer but 99.999% of basic users are unable to answer repair software English questions other than "YES". However the sentence can become "EXECUTE THIS COMMAND 'fsck /dev/xx' to do a manual fsck on the root file system." If the answer "yes" completely destroys the software, just reinstall it! NOTE: A competent user does not store his personal data in the partition containing the software. He stores them elsewhere! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
https://forum.ubuntu-fr.org/viewtopic.php?id=2066134 https://forum.ubuntu-fr.org/viewtopic.php?id=2066096 https://forum.ubuntu-fr.org/viewtopic.php?id=2066153 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1939238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939238] [NEW] UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Public bug reported: Hello This problem did not occur on my computer. https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png It occurs in users who are not competent. This week, the French forum collapsed over this incident. I think changing the advice phrase might improve understanding of the action to be taken. Can these lines " ( i.e.. without -a or -p options) fsck existed with status code 4 The root file system on /dev/ requires a manual fsck" become "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root file system." ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-terminal 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Aug 8 15:16:28 2021 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-08-02 (370 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939238 Title: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1939238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926624] Re: failed to start commit a transient machine-id on disk
The journal log ** Attachment added: "T" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926624/+attachment/5493340/+files/T -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926624 Title: failed to start commit a transient machine-id on disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926624] [NEW] failed to start commit a transient machine-id on disk
Public bug reported: Hello. I installed the Hirsute Hippo version (21.04) in a partition of a USB stick. The boot is slow. This is certainly normal. But a lot of "time-out" messages are reported in the log. The first one met is "failed to start commit a transient machine-id on disk". I do not know that they will be the consequences. Is it possible to configure the waiting time? ** Affects: systemd (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/1926624 Title: failed to start commit a transient machine-id on disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1926624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922780] Re: refind in secure mode forget to look in ext4 partitions
Hello I solved the problem by not downloading the file "refind_0.13.2-1_amd64.deb" But the file "refind-bin-0.13.2.zip" Installation commands are now wget https://sourceforge.net/projects/refind/files/0.13.2/refind-bin-0.13.2.zip unzip refind-bin-0.13.2.zip 1>/dev/null ./refind-bin-0.13.2/refind-install --shim /usr/lib/shim/shimx64.efi.signed --alldrivers --yes And everything works perfectly fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922780 Title: refind in secure mode forget to look in ext4 partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/refind/+bug/1922780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922780] Re: refind in secure mode forget to look in ext4 partitions
the actual script ** Attachment added: "installation script" https://bugs.launchpad.net/ubuntu/+source/refind/+bug/1922780/+attachment/5487778/+files/refind2104-v3.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922780 Title: refind in secure mode forget to look in ext4 partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/refind/+bug/1922780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922780] Re: refind in secure mode forget to look in ext4 partitions
Hello With debug trace level 4 ... --Next loader-- 17:12:46 - Starting ext4_x64.efi 17:12:46 - Using load options '' 17:12:46 - Note: ext4_x64.efi is a driver 17:12:46 - 'EFI\refind\drivers_x64\ext4_x64.efi' is a valid loader 17:12:47 - Getting EFI variable 'SecureBoot' from NVRAM 17:12:47 - Getting EFI variable 'SetupMode' from NVRAM 17:12:47 - Employing Shim LoadImage() hack 17:12:47 - Secure boot error while loading 'ext4_x64.efi'; Status = 15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922780 Title: refind in secure mode forget to look in ext4 partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/refind/+bug/1922780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913576] Re: Fsck with recovery mode
Remenber ubuntu@ubuntu:~$ Temp=$(diskutil list | grep -i '0FC63DAF-8483-4772-8E79-3D69D8477DE4\|BC13C2FF-59E6-4262-A352-B275FD6F7172\|933AC7E1-2EB4-4F13-B844-0E14E2AEF915\|E6D6D379-F507-44C2-A23C-238F2A3DF928\|A19D880F-05FC-4D3B-A006-743F0F84911E\|0657FD6D-A4AB-43C4-84E5-0933C84B4F4F\|Linux') diskutil : commande introuvable ubuntu@ubuntu:~$ diskutil diskutil : commande introuvable ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=21.04 DISTRIB_CODENAME=hirsute DISTRIB_DESCRIPTION="Ubuntu Hirsute Hippo (development branch)" ubuntu@ubuntu:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913576 Title: Fsck with recovery mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1913576/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922780] Re: refind in secure mode forget to look in ext4 partitions
Hello Same problem in Legacy version It is necessary to tinker with the installation of what is missing! My script is as follows PDM="/boot/efi" # définir le point de montage echo Refind est absent. Installation de refind fourni par UBUNTU lancée. add-apt-repository universe && apt update echo -ne "\nveuillez valider la réponse \e[1mOUI\e[0m prépositionnée dans la grille d'installation de refind qui va s'afficher en cours d'installation.\n $ERR continuer l'installation." read apt install --reinstall refind rmdir $PDM/EFI/tools 2>/dev/null Stock=$PDM/EFI/refind cp -r /usr/share/refind/banners $Stock cp -r /usr/share/refind/fonts $Stock cp -r /usr/share/refind/refind/drivers_x64$Stock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922780 Title: refind in secure mode forget to look in ext4 partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/refind/+bug/1922780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922780] Re: refind in secure mode forget to look in ext4 partitions
Hello My script of installation under ubuntu 21..04. The ubuntu are still not detected at the time of the reboot. PDM="/boot/efi" # définir le point de montage Shim="shimx64.efi" ## Le fichier de boot sécurisé à utiliser sachant que shimx64.efi.dual.signed est actuellement refusé par le script et que shimx64.efi n'est pas signé Stock=$PDM/EFI/refind ### Le lieu de stockage. mkdir $Stock cp -r /usr/lib/shim/* $Stock if [ ! -f $Stock/$Shim.REF ]; then cp -v $Stock/$Shim $Stock/$Shim.REF cp -v $Stock/$Shim.dualsigned $Stock/$Shim fi wget https://sourceforge.net/projects/refind/files/0.13.2/refind_0.13.2-1_amd64.deb dpkg --install refind_0.13.2-1_amd64.deb echo sbverify --list $Stock/shimx64.efi && sbverify --list $Stock/shimx64.efi echo sbverify --list $PDM/EFI/refind/grubx64.efi && sbverify --list $PDM/EFI/refind/grubx64.efi cp/usr/share/refind-0.13.2/refind-install$Stock ### Mais ne fonctionne que sous /usr cp -r /usr/share/refind-0.13.2/banners $Stock cp -r /usr/share/refind-0.13.2/fonts $Stock cp -r /usr/share/refind-0.13.2/refind/tools_x64 $Stock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922780 Title: refind in secure mode forget to look in ext4 partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/refind/+bug/1922780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922780] Re: refind in secure mode forget to look in ext4 partitions
Hello I started again, staying very close to the documentation I am enclosing all the excerpts for you. The ubuntu are still not detected at the time of the reboot. I specify that I am running from a so-called "live-usb" session. I want to clarify that in the command line, the two signed files (shimx64.efi.dualsigned and shimx64.efi.signed) are rejected by the name control of the process /usr/share/refind-0.13.2/refind-install --shim /boot/efi/EFI/refind/shimx64.efi.signed /usr/share/refind-0.13.2/refind-install --shim /boot/efi/EFI/refind/shimx64.efi.dualsigned ** Attachment added: "Traces of exécution" https://bugs.launchpad.net/ubuntu/+source/refind/+bug/1922780/+attachment/5485209/+files/bug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922780 Title: refind in secure mode forget to look in ext4 partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/refind/+bug/1922780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922780] [NEW] refind in secure mode forget to look in ext4 partitions
Public bug reported: Hello I have been using refind in insecure mode for many years. I just decided to put a computer in secure mode. Apart from the difficulty of booting, I can no longer directly choose the various ubuntu on ext4 partitions, it just displays the grub present in the boot partition !!! Tested with ubuntu version 20.04 Tested with ubuntu version 21.04 Also tested with https://sourceforge.net/projects/refind/files/0.12.0/refind_0.12.0-1_amd64.deb/download When I return to non-secure mode, all ubuntu are visible again. There is however an ubunty specially installed in secure mode. Is it an error in installing the ext4 drivers which are not secure? Thanks. ** Affects: refind (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/1922780 Title: refind in secure mode forget to look in ext4 partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/refind/+bug/1922780/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922380] Re: remove shim-signed very difficult
Hello. I'm confused. When I type the words correctly, it works. Traitement des actions différées (« triggers ») pour man-db (2.9.4-2) ... root@a:~# apt purge shim-signed Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Veuillez utiliser « apt autoremove » pour les supprimer. Les paquets suivants seront ENLEVÉS : shim-signed* ATTENTION : Les paquets essentiels suivants vont être enlevés. Vous NE devez PAS faire ceci, à moins de savoir exactement ce que vous êtes en train de faire. shim-signed 0 mis à jour, 0 nouvellement installés, 1 à enlever et 41 non mis à jour. Après cette opération, 2 734 ko d'espace disque seront libérés. Vous êtes sur le point de faire quelque chose de potentiellement dangereux Pour continuer, tapez la phrase « Oui, faites ce que je vous dis ! » ?]Oui, faites ce que je vous dis ! dpkg: avertissement: problème contourné par utilisation de --force : dpkg: avertissement: this is a protected package; it should not be removed (Lecture de la base de données... 153953 fichiers et répertoires déjà installés.) Suppression de shim-signed (1.45+15+1552672080.a4a1fbe-0ubuntu2) ... (Lecture de la base de données... 153940 fichiers et répertoires déjà installés.) Purge des fichiers de configuration de shim-signed (1.45+15+1552672080.a4a1fbe-0ubuntu2) ... root@a:~# however root@a:~# apt purge shim-signed --force E: L'option --force de la ligne de commande n'est pas reconnue quand elle est utilisée avec d'autres options. root@a:~# apt purge --force shim-signed E: L'option --force de la ligne de commande n'est pas reconnue quand elle est utilisée avec d'autres options. root@a:~# -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922380 Title: remove shim-signed very difficult To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1922380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922380] [NEW] remove shim-signed very difficult
Public bug reported:
Hello
I don't want the shim-signed anymore, but I need an additional password to
remove it.
This error is for all version of ubuntu.
I am sure I am entering the correct one because I entered it using a
copy paste technique.
Have pity on those who do not know English well !!
apt purge shim-signed
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus
nécessaires :
mokutil shim
Veuillez utiliser « apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
shim-signed*
ATTENTION : Les paquets essentiels suivants vont être enlevés.
Vous NE devez PAS faire ceci, à moins de savoir exactement ce
que vous êtes en train de faire.
shim-signed
0 mis à jour, 0 nouvellement installés, 1 à enlever et 0 non mis à jour.
Après cette opération, 2 734 ko d'espace disque seront libérés.
Vous êtes sur le point de faire quelque chose de potentiellement dangereux
Pour continuer, tapez la phrase « Oui, faites ce que je vous dis ! »
?]Oui, faites ce que je vous dis !
Annulation.
root@a:~# export LANG=us
root@a:~# apt purge shim-signed
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
mokutil shim
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
shim-signed*
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
shim-signed
0 upgraded, 0 newly installed, 1 to remove and 171 not upgraded.
After this operation, 2734 kB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
?] Yes, do as I say!
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "fr_FR:fr_CA",
LC_ALL = (unset),
LC_TIME = "fr_FR.UTF-8",
LC_MONETARY = "fr_FR.UTF-8",
LC_ADDRESS = "fr_FR.UTF-8",
LC_TELEPHONE = "fr_FR.UTF-8",
LC_NAME = "fr_FR.UTF-8",
LC_MEASUREMENT = "fr_FR.UTF-8",
LC_IDENTIFICATION = "fr_FR.UTF-8",
LC_NUMERIC = "fr_FR.UTF-8",
LC_PAPER = "fr_FR.UTF-8",
LANG = "us"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
dpkg: warning: overriding problem because --force enabled:
dpkg: warning: this is a protected package; it should not be removed
(Reading database ... 211327 files and directories currently installed.)
Removing shim-signed (1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
(Reading database ... 211314 files and directories currently installed.)
Purging configuration files for shim-signed
(1.45+15+1552672080.a4a1fbe-0ubuntu2) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
root@a:~#
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: evince 3.38.0-1
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 2 15:07:48 2021
InstallationDate: Installed on 2020-10-25 (159 days ago)
InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64
(20201022)
KernLog:
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: evince (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug groovy uec-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922380
Title:
remove shim-signed very difficult
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1922380/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917174] Re: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit stat
Hello It seeems that it is the same thing with hirsute! https://forum.ubuntu-fr.org/viewtopic.php?pid=22427092#p22427092 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917174 Title: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1917174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917174] Re: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit stat
Under liveusb and during installation ubuntu@ubuntu:journalctl -g attention -- Logs begin at Tue 2021-03-02 19:51:25 CET, end at Wed 2021-03-03 10:34:34 CET. -- mars 03 00:41:32 ubuntu ubiquity[59340]: grub-install : attention : Cannot read EFI Boot* variables. mars 03 00:41:32 ubuntu ubiquity[59340]: grub-install : attention : mars 03 00:41:32 ubuntu ubiquity[59340]: grub-install : attention : vars_get_variable: read_file(/sys/firmware/efi/vars/Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c/r> mars 03 00:41:32 ubuntu ubiquity[59340]: grub-install : attention : efi_get_variable: ops->get_variable failed: Erreur d'entrée/sortie. lines 1-5/5 (END) ubuntu@ubuntu:/target/sys/firmware/efi/vars/Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c$ ls -ls total 0 0 -r 1 root root 4096 mars 3 10:30 attributes 0 -r 1 root root 4096 mars 3 10:30 data 0 -r 1 root root 4096 mars 3 10:30 guid 0 -rw--- 1 root root 4096 mars 3 10:30 raw_var 0 -r 1 root root 4096 mars 3 10:30 size ubuntu@ubuntu:/target/sys/firmware/efi/vars/Boot0004-8be4df61-93ca-11d2-aa0d-00e098032b8c$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917174 Title: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1917174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917174] Re: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit stat
Hello So, in chroot mode root@ubuntu:/# grub-install - Installation pour la plate-forme x86_64-efi. grub-install : attention : Cannot read EFI Boot* variables. grub-install : attention : read_file: could not read from file: Erreur d'entrée/sortie. grub-install : attention : vars_get_variable: read_file(/sys/firmware/efi/vars/Boot002A-8be4df61-93ca-11d2-aa0d-00e098032b8c/raw_var) failed: Erreur d'entrée/sortie. grub-install : attention : efi_get_variable: ops->get_variable failed: Erreur d'entrée/sortie. grub-install : erreur : failed to register the EFI boot entry: Erreur d'entrée/sortie. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917174 Title: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1917174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916019] [NEW] speed of execution of reshape and chunk.
Public bug reported: Hello speed of execution of reshape and chunk under Ubuntu version 20.04.2. The execution speed of the "reshape" and "chunk" actions of the MDADM command is much too slow :(speed = 288K / sec). The IOTOP command also indicates that the flow is very low. There is nothing visible with the journalctl command. It will take more than six hours to process a raid of 30 GB. So probably a month if the raid is 4 TB! In addition these commands have no effect sudo sysctl -w dev.raid.speed_limit_min=5 && sudo sysctl -w dev.raid.speed_limit_max=50 && cat /proc/sys/dev/raid/speed_limit* 50 5 The problem is also visible in this french discussion: https://forum .ubuntu-fr.org/viewtopic.php?pid=22416407#p22416407 Please provide a solution. ** Affects: mdadm (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/1916019 Title: speed of execution of reshape and chunk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1916019/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915860] [NEW] The function 'bd_md_examine' called, but not implemented
Public bug reported: Hello Under ubuntu 20.04 version, I am reorganizing some RAIDS I come across a message that I cannot understand. Is something missing in the software? It seems to be written every second journalctl -b -g "The function 'bd_md_examine' called, but not implemented" >T.txt && wc T.txt -l 524 T.txt ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Trace of the bug" https://bugs.launchpad.net/bugs/1915860/+attachment/5464177/+files/T.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915860 Title: The function 'bd_md_examine' called, but not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1915860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826703] Re: Could not prepare Boot variable: Function not implemented
Hello I encounter a similar incident a@a:~$ sudo efibootmgr --create --disk /dev/sdb --part 7 --label "grububuntu" --loader "\efi\ubuntu\grubx64.efi" --verbose Could not prepare Boot variable: Function not implemented a@a:~$ a@a:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS" a@a:~$ a@a:~$ sudo fdisk -l /dev/sdb Disque /dev/sdb : 3,75 GiB, 4009754624 octets, 7831552 secteurs Disk model: DT 100 G2 Unités : secteur de 1 × 512 = 512 octets Taille de secteur (logique / physique) : 512 octets / 512 octets taille d'E/S (minimale / optimale) : 512 octets / 512 octets Type d'étiquette de disque : dos Identifiant de disque : 0xa935e60d Périphérique Amorçage Début Fin Secteurs Taille Id Type /dev/sdb12048 1050623 1048576 512M 83 Linux /dev/sdb2 1050624 2099199 1048576 512M 83 Linux /dev/sdb3 2099200 3147775 1048576 512M 83 Linux /dev/sdb4 3147776 7831551 4683776 2,2G 5 Étendue /dev/sdb5 3149824 4198399 1048576 512M 83 Linux /dev/sdb6 4200448 5249023 1048576 512M 83 Linux /dev/sdb7*5251072 6299647 1048576 512M ef EFI (FAT-12/16/32) I ran this command thinking it might work and give a result similar to this one I found in a thread.. efibootmgr -v BootCurrent: 0005 Timeout: 0 seconds BootOrder: 0005,,0001,0003 Boot* Optical Disk Drive BBS(CDROM,ÿ,0x0)... Boot0001* Notebook Hard Drive BBS(HD,ÿ,0x0)... Boot0002* Notebook Ethernet BBS(128,ÿ,0x0)>.. Boot0003* Notebook Ethernet BBS(128,ÿ,0x0)>.. Boot0004* USB Hard Drive BBS(HD,ÿ,0x900)... Boot0005* ubuntu HD(4,MBR,0xde2df8d4,0xd4217fe,0x7c5f942)/HD(3,MBR,0x0,0x12867800,0x19000)/File(\EFI\ubuntu\shimx64.efi) what could be the correct coding to install in a logical partition? 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/1826703 Title: Could not prepare Boot variable: Function not implemented To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1826703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912044] Re: invalid arch-independant ELF magic
So under grub rescue, with four commands lines set root=(hd0,gpt3) set prefix=(hd0,gpt3)/usr/lib/grub insmod nornal normal then under grub, with three commands lines linux /boot/vmlinuz root=/dev/sdd3 ro initrd /boot/initrd.img boot This troubleshooting works but it is not normal to have to use it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912044 Title: invalid arch-independant ELF magic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1912044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912044] Re: invalid arch-independant ELF magic
Hello Today I downloaded the new DAILY version again I see the same problem again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912044 Title: invalid arch-independant ELF magic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1912044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914599] Re: efi: Froze efi_rts_wq and disabled EFI Runtime Services
Hello I remind you that at startup, the EFI computer is not in SECURE mode. There is therefore no reason to require that the secure mode be installed. There is an installation option --n0-nvram Use it! It is easy to do a read command of the NVRAM to see that it is refused in reading. This implies that writing will probably not be possible! You could even set the noefi option in the options of the /etc/default/grub file !!! Thank you for improving the situation. This attached file contains the boot-repair trace with the content of dmesg trace ** Attachment added: "Page fault caused by firmware at PA: 0x660591d0" https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1914599/+attachment/5459956/+files/Boot-Repair.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914599 Title: efi: Froze efi_rts_wq and disabled EFI Runtime Services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1914599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914599] [NEW] efi: Froze efi_rts_wq and disabled EFI Runtime Services
Public bug reported: Hello I think this problem has been around for many years. For ubuntu, I only found this bug (https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1777228) which was closed. I chose to open a new one. The context is an ubuntu 20.04 installation ": Ign: 1 cdrom: // Ubuntu 20.04.1 LTS _Focal Fossa_ - Release amd64 (20200731) focal InRelease" The incident noted in the DMESG is as follows efi: Froze efi_rts_wq and disabled EFI Runtime Services The contents of the Boot-install.txt file show the details. In such an environment, I suggest you do the following development: - Tell the user that the EFI variables cannot be read and that the secure mode will not be activated. - Write the grubx64.efi file in the boot directory instead of the shimx64.efi file, renaming it also bootx64.efi. probably write the grub.cfg file there as well. It seems to me the minimum. - Eventually if the microsoft boot structure is not present, create it and transfer the corrected standard boot structure to it and rename the bootx64.efi file to bootmgfw.efi It also seems possible to me. For more details, please watch this French discussion carefully: https://forum.ubuntu-fr.org/viewtopic.php?id=2061619 -If the windows boot structure is present and the BKbootmgfw.efi file is missing and if you are brave, you can ask for permission to change the way you boot. If it is granted to you, you must then duplicate the bootmgfw.efi file in BKbootmgfw.efi before starting the transfer of the files from ubuntu. You will also find the attempt to repair "boot-repair" with a very large trace which encounters the same problem. Thank you for improving the situation. ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Trace of the bug" https://bugs.launchpad.net/bugs/1914599/+attachment/5459948/+files/Boot-install.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914599 Title: efi: Froze efi_rts_wq and disabled EFI Runtime Services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1914599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914264] [NEW] Unlisted SSD Partitions
Public bug reported: Hello I did an install of ubuntu 20.04 in legacy mode in an SSD. Everything works perfectly fine. For the sake of helping people, I decided to make an error in the /boot directory.( mv grub burg) Unsurprisingly, the boot does not work. The error indicated is: ERROR: file "/boot/grub/i386-pc/normal.mode not found". It is therefore theoretically repairable. The documentation says to do these commands ls set root=(hd0,msdos1) set prefix=(hd0,msdos1)/usr/lib/grub normal insmod normal But the ls command does not list the partitions contained in the SSD but only those present in the hard disks It seems abnormal to me ** Affects: grub2 (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/1914264 Title: Unlisted SSD Partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1914264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912044] Re: invalid arch-independant ELF magic
Hello This "legacy only" computer is old. It now contains an SSD disk composed of four partitions including windows 10 and ubuntu 20.04. Another disk containing windows XP and windows 7. A third larger disc containing the duplications of the two preceding discs. I know the ubuntu boots fairly well since I participate in an important way in the EFI part with another computer in the following documentations, https://doc.ubuntu-fr.org/refind https://doc.ubuntu-fr.org/tutoriel/installation_sur_disque_usb I noticed that the installation of ubuntu has changed a lot with version 20.04. So I want to see how version 21.04 will behave. So I decided to use this 64-bit computer which only knows the LEGACY mode to install the future version 21.04 on an external hard drive by choosing to overwrite the entire drive. (I often used the option something else.) The installer therefore overwrote the ms-dos partition table to install a GPT partition table. Everything is going well. The boot is done well with this external drive. But I get the quoted message which is the subject of my correction request. I don't quite know how to understand it. I saw that it was cited a lot several years ago and that it seemed to be a mix between 32 bit mods and 64 bit mods. Subsequently I have the following tests: Boot the ubuntu from the SSD (20.04.1). Make him discover the O.S. Installed. He forgets to look at the contents of the external disks !!! So I duplicated by gparted the root partition 21.01 in the big disk and restarted the detection. At the next boot, I can choose version 21.04 (the duplication of the external disk in the large 3 TB disk formatted GPT). It works. I even updated it yesterday. I also plugged the external drive into my laptop which is in efi. The boot works perfectly well! It is possible that installing version 20.04 or version 20.10 will give the same result. I did not try. Hope this can be of help to you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912044 Title: invalid arch-independant ELF magic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1912044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
