@corrado venturini
Thanks for reporting this bug as i was about to do the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953052
Title:
In Jammy sound level reset after reboot
To manage notif
@ Thomas Schmitt
Thanks for explaining , it was just a thought as i noticed in the diff
text there was some numbers on there own such as the one at the top so i
wasn't sure if there was something else going on.
>21,22c21
--
You received this bug notification because you are a member of Ubuntu
B
@ José Marinho
>>As I said yesterday, this changes only work at first boot but in the
following boots the >>behaviour is the same again.
If you look at post #16 i had the issue with hirsute where the USB stick
would no longer boot and i had to go to Gnome Disks and untick legacy
bios and then ena
Thanks José for confirming that and trying Thomas instructions on GPT.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
HIrsute live session takes ages to boot on BIOS systems
To manage
>>Thomas Schmitt , Let's try to find out which of the two suspects does
the trick:
Sorry Thomas i tried to read through the instructions but i just simply
don't have any type of command or development skills and i find it
confusing. :(
I'm just a point and click Ubuntu user...
--
You received t
I've just built a new ISO with xorriso but this time i never removed
grub_platform and left it all untouched and now the USB stick boots
without any grub_platform error and after 20 to 30 seconds of a black
screen it boots as normal so it's the way the new ISO is being written
to the USB stick as L
You might need to hold my hand through this as my technical skills are
limited.
Before i attempt what you ask i've just built a new ISO with
grub_platform removed and it now boots up in the same manner as the
Gnome disk option , after the grub menu it gives a black screen for
about 20 to 30 secon
@Thomas Schmitt
run1.txt = Standard ISO unmodified
run2.txt = Gnome disks - first partition legacy bios enable.
I'll post the difference between the logs , if you want the full logs
posted let me know and i will paste them up.
diff run1.txt run2.txt
21,22c21
< MBR partition : 1 0x00 0x
My bad , I've got it working with /dev/sdc instead of $/dev/sdc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
HIrsute live session takes ages to boot on BIOS systems
To manage notif
@José Marinho
I don't mean to put this on you but as the Gnome disks options also
worked for you i might be better if you run the report_system_area scan
between the normal ISO and the Gnome disk edited version so it gets done
correctly as i'm getting out of my depth here as a point and click user
Amazing how we can all get different results doing the same thing. :)
For me a freshly written ubuntu ISO to a USB regardless if i use Ubuntu
USB creator or DD refuses to boot my old legacy gear that is the last
generation phoenix bios just before EFI was released.
It shows an error just before t
Thanks :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342
Title:
HIrsute live session takes ages to boot on BIOS systems
To manage notifications about this bug go to:
https://bugs.launchpad.n
Yeah it is complicated , when you look at a freshly written USB stick
with gnome disks there is a box you can tick that says Legacy BIOS
bootable , I'm not sure if gnome disks is doing as described below with
the "bios_grub" flag as the link talks about a hardrive so i'm not sure
if it would apply
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1922342/comments/12
Yeah, if you do as post 12 it cuts the black screen boot time of Hirsute
and Impish down to about 20 seconds , not tried it with Lubuntu...
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Well i don't hold much confidence if it's not considered important...
I wouldn't be the best person to start a new bug as i don't know what
package this is supposed to be put against , how best to articulate it
or how best to provide any extra information needed as i'm just a point
and click user.
https://cdimage.ubuntu.com/daily-live/current/
@José Marinho
Don't know if you have tried the latest 21.10 development build but it's
still exactly the same as before as you still have to enable legacy bios
in gnome disks to get it to boot and there's still a long freeze before
it starts.
--
Yo
How far into the ‘Impish Indri’ Development should we start reporting
that the live image doesn't boot on legacy computers and do we report it
here or start a new bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
bilibop-lockfs can be used instead of Fsprotect as it uses overlayfs (if
aufs is not available) and all you have to do is install it and add
lockfs to ubuntu grub to activate it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
@Seth Forshee
>Similar functionality is available from systemd
Is there a simple install script then for non-technical users as i'm
currently stuck without either fsprotect or systemd overlay?
fsprotect you just installed it and added a command to grub , systemd
overlay is more complex and needs
@Chris Guiver
>>>I dispute that 'they' don't care.
>>>thus bugs with low rating being ignored is to be expected.
Bad choice of words , i should have used i guess it's not considered important.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@José Marinho
I've removed the other bug report as i see that you've been trying to
get this resolved for ages with no luck so i'm guessing they just don't
care so it was pointless starting a new one.
I've given up to be honest as there is some really odd stuff going on
with regards to the live i
** Tags removed: bot-comment hirsute live
** Changed in: ubuntu
Status: Confirmed => Invalid
** Description changed:
- I've noticed lots of people around the web posting that they are not
- able to boot legacy computers with the live disk as they get a grub
- command error followed by a b
https://bugs.launchpad.net/ubuntu/+bug/1926260
Thanks Jose, i've opened a bug thread above and the work around , can
you click that This bug affects you too near the top and post in the
thread to confirm the work around?
Thanks
--
You received this bug notification because you are a member of U
Public bug reported:
I've noticed lots of people around the web posting that they are not
able to boot legacy computers with the live disk as they get a grub
command error followed by a black screen and a blinking cursor , i've
just confirmed this issue when trying to boot legacy computers with
Ub
If you look at the freshly written image with Gnome disks , 1st ubuntu
partition , click the cog wheel and choose edit partition you'll notice
that the build team have not enabled the Legacy BIOS bootable option?
If you enable it and click change the drive will now boot , there is
still a really l
If you look at the freshly written image with Gnome disks , 1st ubuntu
partition , click the cog wheel and choose edit partition you'll notice
that the build team have not enabled the Legacy BIOS bootable option?
If you enable it and click change the drive will now boot , there is
still a really l
** Summary changed:
- Ubuntu 19.10 unorthodox format?
+ User Error , Please Delete.
** Description changed:
- Any media i format to NTFS with gnome-disk can't be used in either my
- Hisense or Netgear Mediaplayers as it says no disks attached yet the
- same media formatted to NTFS with either G
Public bug reported:
Any media i format to NTFS with gnome-disk can't be used in either my
Hisense or Netgear Mediaplayers as it says no disks attached yet the
same media formatted to NTFS with either Gparted or Windows works
perfectly.
gnome-disks seems to name EXT4 disks differently as instead
> 19.10 network install
> sudo apt-get install ubuntu-restricted-extras
exe fails from sourceforge.net the same as Schröshire Cat said above.
Apart from confirming this issue i have to ask do we need mscorefonts in
this day and age?
--
You received this bug notification because you are a membe
Public bug reported:
==
During fsprotect 1.7 install
==
Created symlink /etc/systemd/system/sysinit.target.wants/fsprotect.service →
/lib/systemd/system/fsprotect.service.
update-rc.d: warning: start and stop actions are no longer supporte
30 matches
Mail list logo
