Public bug reported:
Hello
A USB key to install ubuntu 19.04 has been created.
The first decision is to install REFIND in the ESP boot partition.
As the computer is not very standard with the EFI, REFIND had to be duplicated
in the EFI/BOOT structure then in the EFI/Microsoft/Boot structure
Public bug reported:
Hello
Initially the EFI partition numbered 2 was on disk 0 and the ubuntu partition
numbered 22 was on the same disk.
I duplicated the EFI partition on an external drive. At boot there is
the following error
Error: No such partition
entering rescue mode
grub rescue>
The
hello
the problem is not solved in ubuntu. See this return for an EFI partition
fsck.fat 4.1 (2017-01-24)
Checking we can access the last sector of the filesystem
Seek to 536870400:Argument invalide
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello
I discovered this problem after trying to duplicate the contents of the windows
partition
with the RSYNC command
rsync -a --delete --filter "- .tmp" --filter "- lost+found/" --filter
"- .Trash/"/Windows1 /mnt/sdc14 2>ERROR.txt
All files come from the "Program Files/WindowsApps"
The same repository Under windows
** Attachment added: "DIR command"
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728354/+attachment/5295467/+files/ERROR3.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For example under "Ubuntu 18.04.3 LTS"
ls -als "/Windows1/Program
Files/WindowsApps/microsoft.windowscommunicationsapps_16005.11629.20316.0_x64__8wekyb3d8bbwe"
>$HOME/ERROR1.txt
** Attachment added: "contents of LS command"
$ journalctl -f
-- Logs begin at Wed 2020-01-08 00:43:00 CET. --
févr. 10 22:51:35 a pkexec[3203]: a: Executing command [USER=root]
[TTY=unknown] [CWD=/home/a]
[COMMAND=/usr/lib/update-notifier/package-system-locked]
févr. 10 22:51:38 a gnome-shell[2176]: Window manager warning: Overwriting
a@a:~$ journalctl -f
-- Logs begin at Wed 2020-01-08 00:43:00 CET. --
févr. 10 22:53:30 a rtkit-daemon[1441]: Supervising 7 threads of 3 processes of
2 users.
févr. 10 22:54:14 a PackageKit[1669]: daemon quit
févr. 10 22:54:14 a systemd[1]: packagekit.service: Main process exited,
code=killed,
Public bug reported:
greubefi amd signed cant be installed
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.4
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Public bug reported:
Hello
It seems to me that extundete should easily find some accidentally
deleted files
Versions
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.10
DISTRIB_CODENAME=eoan
DISTRIB_DESCRIPTION="Ubuntu 19.10"
extundelete -v
extundelete version 0.2.4
libext2fs
Hello
The incident is always present with the most recent ubuntu version.
a@a:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu Focal Fossa (development branch)"
a@a:~$
a@a:~$
a@a:~$ sudo apt update
Atteint :1
** Attachment added: "Trace of execution"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5331562/+files/Bug1857914-102-176-8192Mo-SDB10bis.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When installing ubuntu 20.04 on an USB drive, the installation crash
with message saying that it is not possible to find grub-efi-amd-signed
package.
In fact, the cause is because UAS module does not work correcty!
In the trace, we see theses lines
[ 1258.552259] sd
** Attachment added: "commands executed"
https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914/+attachment/5322582/+files/BUGUSB-d.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857914
Hello
I progressed in the reproduction of the incident which I know how to do
systematically.
It seems to me that resize2fs is part of the incident by forgetting to control
something.
I can raise with a debugging option.
Which advise me you?
In attachment you will find the script of the four
Something strange in journalctl
janv. 24 09:02:03 a sudo[2658]: root : TTY=pts/0 ; PWD=/root ; USER=root ;
COMMAND=/usr/sbin/e2fsck -f -y -v /dev/sdb4
janv. 24 09:02:04 a sudo[2667]: root : TTY=pts/0 ; PWD=/root ; USER=root ;
COMMAND=/usr/sbin/resize2fs -P /dev/sdb4
janv. 24 09:02:04 a
maybe a link with this option that i never used
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857914
Title:
resize2fs destroy the
Public bug reported:
591/5000
Hello
To try to understand this incident (
https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914 ) which
systematically occurs in version 19.10 and which I cannot (yet?) reproduce in
version 18.04.03, I made a test game.
Using this test game consisting
** Attachment added: "Bug with SDB6 only"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323755/+files/Bug1857914-sdb6.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Bug with only SDB5 partition"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323754/+files/Bug1857914-sdb5.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "Bug with only SDB2 partition"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5323763/+files/Bug1857914-sdb2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello.
When I decide to reduce the size of a partition stored in an external drive and
formatted in EXT4 after booting with ubuntu 19.10, this partition is destroyed.
it seems abnormal to me.
This is systematic for the twelve partitions and twelve boots in the
prepared context.
If several
** Package changed: ubuntu => e2fsprogs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860917
Title:
uas_eh_abort_handler uas-tag inflight OUT
To manage notifications about this bug go
** Attachment added: "File contains three scripts to make the bug"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5324759/+files/BUG13.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello.
Thank you for your involvement in this problem.
My goal is to make ubuntu better.
I accidentally encountered this incident in a real context.
I knew that changing partition size is risky and impossible with a partition in
use. That's why I duplicated it on an external disk.
I found that
ATTENTION
This error is new. and it is because of use of logical device not un good
order!!!
Feb 02 10:59:19 a systemd[1315]: mnt-USBsdb3.mount: Succeeded.
Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op
0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Feb 02
Hello
I discovered that if I gradually decrease the partition size by 250 MiB
at a time (not tested with 500 MiB), I can shrink the file system to the
minimum value indicated without it being broken.
But the end result is very surprising: The partition cannot be reduced.
There is a message that
Screen of gparted refuse to reduce https://doc.ubuntu-
fr.org/_media/captures/gparted/gpartedtreduce.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857914
Title:
resize2fs destroy the content
Me also
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860544
Title:
package uuid-runtime 2.34-0.1ubuntu2.1 failed to install/upgrade:
installed uuid-runtime package post-installation script
Hello
I cannot reproduce the incident with this method
export LC_ALL=POSIX
sudo mke2fs -t ext4 /USB1910bis/fs.img 30G
mke2fs 1.45.3 (14-Jul-2019)
Creating regular file /mnt/USB1910bis/fs.img
Creating filesystem with 7864320 4k blocks and 1966080 inodes
Filesystem UUID:
Public bug reported:
Hello
The used version of ubuntu is 19.10
So the used version of ubuntu is GParted 0.32.0
and the used of resize2fs is 1.45.3 (14-Jul-2019)
I wanted to shrink by 20 GB the size of an old partition created with
ubuntu 18.04 and stored on an external hard drive
Hello
You suggested that I use a file to simulate a partition. I could not highlight
the incident.
However, the commands you offer can also be used with a partition. So I no
longer need to use gparted.
This highlights that it is the resize command that destroys the partition. Here
is the trace
** Attachment added: "result of some commands executed in version 18.04.3"
https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914/+attachment/5318230/+files/Resize.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "list of all orders"
https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914/+attachment/5318229/+files/BUG5.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857914
** Attachment added: "details of actions performed with gparted in version
19.10"
https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914/+attachment/5318231/+files/gparted_1.htm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "result of some commands executed in version 19.10"
https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914/+attachment/5318232/+files/Resize2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello
It took me a little while to reproduce the incident.
I only wanted to put what seemed to me the minimum necessary.
But I couldn't reproduce the incident.
So I replayed the initial scenario. I also couldn't rebuild.
So I destroyed the inaccessible partition to make a new one now called SDB1
** Attachment added: "result of some commands executed in version 19.10 to
repair the partition."
https://bugs.launchpad.net/ubuntu/+source/gpart/+bug/1857914/+attachment/5318233/+files/Resize3.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hello.
The problem is more complicated or simpler than I thought.
I tried again.
A) With version 18.04.3
Formatting SDB1, SDB2 and SDB3
Creation of the P1, P2, P3 and P4 directories in the 3 partitions.
B) Reboot with version 19.10.
Deletion of the P1 directories in the three partitions.
Public bug reported:
sudo apt upgrade on 20.04 BETA
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: shim-signed 1.40+15+1533136590.3beb971-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error:
Contents of journalctl
** Attachment added: "Contents of journalctl"
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1875647/+attachment/5362493/+files/Trace.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hello
I just installed version 20.04. I note that the wifi no longer works using the
iPad in relay mode.
I note that the French service FREEWIFI serving as a backup is not
offered as a breakdown service.
Not currently having a wired connection, I am forced to steal an
And extract for lines contains network
** Attachment added: "Some lines of journalctl"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875647/+attachment/5362530/+files/Network.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362525/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362522/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362527/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362523/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362521/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
Title:
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362528/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362524/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362529/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362526/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362515/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362518/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362520/+files/Lsusb-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/1875647
Title:
apport information
** Tags added: apport-collected
** Description changed:
Hello
I just installed version 20.04. I note that the wifi no longer works using
the iPad in relay mode.
I note that the French service FREEWIFI serving as a backup is not
offered as a breakdown service.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362516/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362519/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362517/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
Title:
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1875647/+attachment/5362496/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
Title:
** Attachment added: "A French trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875647/+attachment/5364544/+files/wificheck.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875647
Hello
I found a way to update the kernel of version 20.04-lts
I start with vmlinuz-5.4.0-28-generic
Again the iPad is perfectly recognized as a network device in WIFI technique.
This first problem therefore seems to be resolved by the software update.
However it is still impossible to connect
Contents of NetworkManager
** Attachment added: "Contents of NetworkManager"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+attachment/5398250/+files/NetworkManager.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The Ubuntu version
** Attachment added: "The Ubuntu version"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+attachment/5398253/+files/Version.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Contents of Journalctl
** Attachment added: "Contents of Journalctl"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+attachment/5398248/+files/Journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hello.
I know how to solve some connection problems. I can't find enough explanation
to understand the cause of this problem!
It seems to loop forever on the user login and network acquisition sequences.
First stage
"try ubuntu before installing it"
This step goes
Contents Of dpkg
** Attachment added: "Contents Of dpkg"
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1890133/+attachment/5398249/+files/dpkg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello
today the correction is not yet available
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"
sudo apt update
Atteint :1 http://fr.archive.ubuntu.com/ubuntu focal InRelease
Réception de :2
Hello
If the operation of smartctl should be the same between version 18.04 and
version 20.04, it seems to me that this is not the case,
In version 18.04, it is possible to test that everything is functional with
this command.
sudo sh -c 'echo test de message | smart-notifier --notify'
This
sudo apt install --reinstall smart-notifier
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 :
libfprint-2-tod1 libpython2-stdlib
False alarm
You just have to reboot the computer after installing smart-notifier for the
test message to appear on the screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875498
Title:
Hello
Five years latter, the problem is back!
a@a:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS"
a@a:~$ sudo apt update
Atteint :1 http://fr.archive.ubuntu.com/ubuntu focal InRelease
Réception de :2
Hello
sudo apt install --reinstall smart-notifier
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 1 réinstallés, 0 à enlever et 0 non mis
à jour.
Il est nécessaire de prendre 0
Public bug reported:
Hello
I am a user who updates the documentation from time to time.
In the old French version of smartmontools, it was specified that the
verification of the operation of the disk destruction alerts was
possible to verify by making this command
sudo sh -c 'echo test de
Public bug reported:
Hello
I am a user who updates the documentation from time to time.
In the old French version of smartmontools, it was specified that the
verification of the operation of the disk destruction alerts was
possible to verify by making this command
sudo sh -c 'echo test de
** Summary changed:
- The boot_delay parameter is not interpreted by the correct boot modude
+ The boot_delay parameter is not interpreted by the correct boot module.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Hello.
Normal computer booting is no longer possible. However, this computer boots up
without any difficulty using recovery mode.
A first research shows that the normal boot does not reach the phase of
delivery of the trace in the file /var/log/journal.
If he did that, it
Hello
See these return
$ sudo apt update
Atteint :1 http://fr.archive.ubuntu.com/ubuntu groovy InRelease
Atteint :2 http://fr.archive.ubuntu.com/ubuntu groovy-updates InRelease
Atteint :3 http://security.ubuntu.com/ubuntu groovy-security InRelease
Atteint :4 http://fr.archive.ubuntu.com/ubuntu
Public bug reported:
Hello
I decide to install the DAILY version of Hirsute Hippo using a "legacy only"
computer.
I choose to install on the whole disk. As a result:
The msdos partition table is destroyed and replaced with a GPT partition table.
A 32 MiB bios_grub partition is created,
A 512
** Also affects: grub-installer (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/1912044
Title:
invalid arch-independant ELF magic
To manage
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
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: //
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
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
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:
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
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
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
Public bug reported:
Hello
Today, to please myself, I decided to boot in recovery mode.
A nice grid of choices is displayed.
I choose the fourth line titled:
fsck check all filesystems
The following warning message is displayed:
Continuing will remount your filesystem / in read/write mode and
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
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
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
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
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:
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
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
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
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.
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
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')
1 - 100 of 170 matches
Mail list logo
