I just received update and virtualbox started working! Thanks if someone
did something.
But I don't understand how the update system works. Since nothing changed in
all the sources I know:
1. https://packages.ubuntu.com/focal/virtualbox shows the same stuff.
2. https://launchpad.net/ubuntu/+sourc
It is because virtualbox versions <6.1.18 do not support kernel 5.11
Changelog:
https://www.virtualbox.org/wiki/Changelog
VirtualBox 6.1.20 (released April 20 2021)
Linux host and guest: Support kernel versions 5.11 (bug #20198) and 5.12
Bug:
https://www.virtualbox.org/ticket/20198
** Bug watc
Same error for me. Attached txt. How to fix it?
Similar issue was few months ago with virtualbox, but it affected more people
and was fixed faster. What is the cause this does not effect everybody? What
could be workaround?
** Attachment added: "make log.txt"
https://bugs.launchpad.net/ubunt
Though solved by using a workaround, this was and still is a bug - 18.04
installer do not work on an old computer, which do not have option to
choose booting mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Finally!:) Workaround - it actually did work, if plug it with SATA
connection instead of eSATA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786003
Title:
How to install 18.04 in Legacy mode?
To
Nope, this workaround does not work either. Installed on another
computer successfully (almost), but does not boot on mine. Forever black
screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786003
Thanks, though your suggestion did not work.
But I got an idea - found another computer with a lot of bios options,
thus I will be able to choose Legacy mode and install there, then move
the HDD back to my computer and it might work:)
--
You received this bug notification because you are a membe
Public bug reported:
After installation I get this error:
“The ‘grub-efi-amd64-signed’ package failed to install into /target/ . Without
the GRUB boot loader, the installed system will not boot.
My computer is old, my bios is very simple and has no option to choose
anything mentioning UEFI, secu
OK, finished testing all the situations with all the channels and all
the radios. Final conclusion - GPS works well.
Made an instruction how to use GPS on Nexus 4:
http://askubuntu.com/a/760031/514318
Issues I described previously was caused by this bug:
https://bugs.launchpad.net/ubuntu/+source
Position does not only freeze as I described in previous message, but if
there is other GPS apps running, then uNav app, for example, does not
only looses position, but it works very strangely, it is very choppy,
and does not know the direction (map swings in many directions
constantly), and finall
I can confirm I experience exactly the same problem as described in #6
comment, and filled a duplicate bug lately #1573140. But I cannot
confirm information in other comments #1, #2, because GPS always starts
working again if I switch apps, but GPS stops again after a minute and
apps have to be swi
Yay, it works finally!:) (Almost)
I tried all kinds of posibilities many times, and it works only then:
1. Flashing bq-aquaris.en channel
2. Turn on GPS with Nokia HERE setting.
3. Restart.
Tests show, that it works independent of radio version, it can be old or new,
does not matter (It always w
Some people flashed "ubuntu-touch/stable/bq-aquaris.en" channel in
addition with latest nexus 4 radio and it works.
Reference: http://askubuntu.com/questions/691468/how-to-use-gps-on-
nexus-4
On my it does not work :( Since all nexus 4 should be the same, I wonder
why it works on some nexus 4, bu
13 matches
Mail list logo
