** Changed in: linux (Ubuntu)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Bionic)
Assignee:
Public bug reported:
With the proposed openjdk-7 7u181-2.6.14-0ubuntu0.1 update, eclipse
crashes when starting up using the zero vm, as invoked by:
eclipse -vm /usr/lib/jvm/java-7-openjdk-
amd64/jre/lib/amd64/zero/libjvm.so
after the 'choose a workspace directory' dialog is answered. This
Would like to have this submittal closed. In further testing, the
problem did not exist when VLC was run by a totally new user. Thus the
problem must lie within my old and possibly corrupt /home
configuration(s). I have since rebuilt the entire /home.
--
You received this bug notification
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777907
Title:
oss4 4.2-build2010-5ubuntu1~14.04.1 ADT test failure with linux-hwe-
edge 4.15.0-23.25~16.04.1
To manage
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777913
Title:
v4l2loopback 0.9.1-4 ADT test failure with linux-hwe-edge
4.15.0-23.25~16.04.1
To manage notifications about
Thank you, sir, for your reply and advices.
15 minutes of research on internet helped me to solve the problem and
install xubuntu flawless. I just wanted to send you the report to help
improving this fantastic OS.
Great regards,
Dragos
Den ons 20 juni 2018 17:11Phillip Susi skrev:
> Your
Public bug reported:
I was trying to install gparted when this happed
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpam-runtime 1.1.8-3.2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-31.50-powerpc-smp 4.4.13
Uname: Linux 4.4.0-31-powerpc-smp ppc
ApportVersion: 2.20.1-0ubuntu2.1
Ouch - If you wanted to get clever, you could add your own puppet package
provider that extends the default gem one to use that altered path - it's
probably not as hard as it sounds.
On Thu, Jun 21, 2018 at 3:10 AM Philip Davies <1777...@bugs.launchpad.net>
wrote:
> Hey Nick,
>
> Ah ok, so thats
Yes, this is still a bug, and still unfixed. My new HP duplex printer
works fine from lpr on the command line with the right options for
double-sided, and qpdfview can also print both sides, but because the
printer default for duplex is Off, Evince's drop-down is stuck on One-
Sided and refuses to
Public bug reported:
error to install it
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: android-androresolvd 1.3-1
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Thu
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759723
Title:
Public bug reported:
No big changes, mostly to keep in sync:
bind9 (1:9.11.3+dfsg-2) unstable; urgency=medium
* [CVE-2018-5738]: Add upstream fix to close the default open recursion
(Closes: #901483)
* Change the maintainer address (Closes: #899959)
-- Ondřej Surý Thu, 14 Jun 2018
Public bug reported:
No big changes, mostly to keep in sync:
bind9 (1:9.11.3+dfsg-2) unstable; urgency=medium
* [CVE-2018-5738]: Add upstream fix to close the default open recursion
(Closes: #901483)
* Change the maintainer address (Closes: #899959)
-- Ondřej Surý Thu, 14 Jun 2018
Public bug reported:
I started a new nemo instance after nemo -q. Then I opened a SFTP
connection to an other device and another tab with my home folder. There
I was somehow not able to rename a file but it was no problem in the
SFTP tab. After more failed tries with copying and renaming a file
** Also affects: linux-kvm (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-kvm (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug
** Also affects: linux-kvm (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-kvm (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug
** Also affects: linux-kvm (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux-kvm (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug
Where is this fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521173
Title:
AER: Corrected error received: id=00e0
To manage notifications about this bug go to:
Please do NOT support more javascript features.
Javascript is one of the most aweful things to put in pdf and an exellent
target for malware.
There would be a lot of new security issues coming along with it.
In case one day there will be javascript inside poppler beyond formular
filling, please
So here's the reference manual:
https://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/js_api_reference.pdf
There are interesting use cases for javascript in pdf files. The gnome
desktop would benefit if supported!
Maybe consider offering this as part of GSoC or something?
--
You
See also: https://gitlab.gnome.org/GNOME/evince/issues/379
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/371618
Title:
evince does not calculate total sum in application form
To manage
Actaully I think we should close this bug.
We already export the Javascript from the poppler side and for example
Okular supports it partially https://www.youtube.com/watch?v=S-zmHc3WUhs
I don't think we could actually do that from within the core of poppler
since it needs to know things as
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777949
Title:
package android-androresolvd 1.3-1 failed to install/upgrade:
subproses skrip post-installation
Hello
Also in xenial but in the apache log I found
Jun 20 10:44:05 localhost apache2: DIGEST-MD5 common mech free
Jun 20 10:44:53 localhost apache2: message repeated 22 times: [ DIGEST-MD5
common mech free]
dpkg -l libsasl2-modules
Desired=Unknown/Install/Remove/Purge/Hold
|
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include
Public bug reported:
Never werks.
Breken since youbuntu 14.04.
Every (flaveur letter)ubuntu installer is breken due to this shiet.
Boot iso into UEFI mode under my laptop == :( no I not install grub
Boot iso into UEFI mode under my desktop ==:( no I not install grub
Boot iso into BIOS
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776667
Title:
lttng-modules 2.10.5-1ubuntu1 ADT test failure with linux 4.17.0-2.3
To manage notifications about this bug go to:
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777894
Title:
xtables-addons 2.12-0.1~16.04.2 ADT test failure with linux-hwe-edge
4.15.0-23.25~16.04.1
To manage
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
Problem does not happen on a new install from Ubuntu 18.10 "Cosmic Cuttlefish"
- Alpha amd64 (20180620) on same PC
corrado@corrado-p13-cc-0620:~$ apt policy snapd
snapd:
Installed: 2.33+18.10ubuntu3
Candidate: 2.33+18.10ubuntu3
Version table:
*** 2.33+18.10ubuntu3 500
There used to be a prompt that while worded poorly, did give you the
ability to switch to a bios mode install even though you booted the
installer in UEFI mode, but it was removed in 18.04. Unfortunately,
instead of making it switch to a bios mode install by default, it keeps
with the UEFI
Hello Joseph,
I have tested the kernel you kindly provide in #5 but this not resolves
the issue on all laptop which have trouble.
What I said in #4 is partial and not resolves the issue on all test
cases. Sorry for this wrong interpretation, but the cases are quite
complicated.
I have hidden
*** This bug is a duplicate of bug 1466150 ***
https://bugs.launchpad.net/bugs/1466150
Yes; the errors in your log are exactly like that one. The one subtle
difference I just noticed though is that that was dealing with software
raid, but it sounds like you are using bios fakeraid. I would
This bug was fixed in the package apt - 1.7.0~alpha0ubuntu2
---
apt (1.7.0~alpha0ubuntu2) cosmic; urgency=medium
[ David Kalnischkies ]
* Add boilerplate plural form to po/apt-all.pot
* don't try SRV requests based on IP addresses
* use 127.0.0.1 instead of localhost as
This bug was fixed in the package apt - 1.7.0~alpha0ubuntu2
---
apt (1.7.0~alpha0ubuntu2) cosmic; urgency=medium
[ David Kalnischkies ]
* Add boilerplate plural form to po/apt-all.pot
* don't try SRV requests based on IP addresses
* use 127.0.0.1 instead of localhost as
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775764
I'm not sure what you mean by "can I install grub on boot drive?"; I
have never seen such a prompt. What I see is after choosing to
partition manually ( "something else" ), on the partitioning screen you
can choose where to install grub to. One of the automatic choices
however, just installs it
I have similar big problem with kernel and latest nvidia drivers but i
do not secure boot in my machine. When Ubuntu install new kernel and
boot. nvidia drivers not loaded in kernel. And system crashing.
Error! Could not locate dkms.conf file.
File: does not exist.
using nvidia 390 drivers.
Any response on this? It is affecting a lot of servers where we are
attempting to use it.
I believe this would be remedied, as well as #1772098, by simply
providing a newer version of PCS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777942
Title:
package libpam-runtime 1.1.8-3.2ubuntu2 failed to install/upgrade:
package libpam-runtime is not
** Changed in: vlc (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764032
Title:
VLC does not play dvd's properly or at all
To manage notifications about this
** Description changed:
With the proposed openjdk-7 7u181-2.6.14-0ubuntu0.1 update, eclipse
crashes when starting up using the zero vm, as invoked by:
- eclipse -vm /usr/lib/jvm/java-7-openjdk-
+ eclipse -vm /usr/lib/jvm/java-7-openjdk-
amd64/jre/lib/amd64/zero/libjvm.so
after
--- Comment From cdead...@us.ibm.com 2018-06-20 17:20 EDT---
@pridhiviraj Hello Pridhiviraj, can this issue be closed now?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770849
Title:
Public bug reported:
grub-installer failed
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
Date: Wed Jun
** Bug watch added: Debian Bug tracker #901001
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901001
** Also affects: python3-defaults (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901001
Importance: Unknown
Status: Unknown
--
You received this bug
--- Comment From cdead...@us.ibm.com 2018-06-20 17:50 EDT---
Ubuntu issue. Removing IBM FW tag.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767927
Title:
ISST-LTE:pKVM:Ubuntu1804:
For giggles I downloaded the latest kernel available today. 4.18.RC1
to try. And it too exhibits the same thing. No change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777586
Title:
Ubuntu
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Triaged
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
*** This bug is a duplicate of bug 1768230 ***
https://bugs.launchpad.net/bugs/1768230
** This bug has been marked a duplicate of bug 1768230
Long time booting : Failed to connect to lvmetad. Falling back to device
scanning.
--
You received this bug notification because you are a member
Generating a new keypair and exporting only the subkey and then
importing it into 18.04 seems to work. There must be something
particular about my existing keychain. I guess I'll have to start git
bisecting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777900
Title:
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New => Fix
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
Outside of freeipa, I can get it to crash with multiple different
assertion errors, just not yet the one we get when using it with
freeipa. It doesn't look like a very robust system.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a
This bug is believed to be fixed in cloud-init in version 18.3. If this
is still a problem for you, please make a comment and set the state back
to New
Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ion]
Manual verification artifacts will also be hosted in the folllowing
repository:
https://github.com/cloud-init/ubuntu-sru/tree/master/20180620
== End SRU Template ==
== Changelog ==
- - release 18.3
- - docs: represent sudo:false in docs for user_groups config mod
Your EFI system partition is corrupt; you will need to repair it with
either dosfsck or Windows' chkdsk/scandisk.
** Changed in: grub-installer (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777901
Title:
ucarp not working with ubuntu server 18.04
To manage notifications about this bug go to:
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
--- Comment From jos...@br.ibm.com 2018-06-20 15:22 EDT---
Hello,
>From the the development side it looks very good: both hotplug and hot
unplug are working good.
Thank you very much,
Ziviani
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Xenial)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1674273
I an using Ubuntu Server as a KVM-host, relying on multiple anonymous
bridges, and am suffering from this bug under 18.04.
For others needing a workaround: I do configure the bridges with
netplan.io as usual and bring up the bridges by defining in file
Weird... Ubiquity seems to have somehow stopped running as root:
Jun 18 19:36:23 ubuntu ubiquity: dpkg: warning: failed to open configuration
file '/root/.dpkg.cfg' for reading: Permission denied
Jun 18 19:36:24 ubuntu /plugininstall.py: log-output -t ubiquity chroot /target
py3compile -p
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fdroidserver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762183
** Summary changed:
- Sync fdroidserver 1.0.3-1 (universe) from Debian unstable (main)
+ Sync fdroidserver 1.0.6-1 (universe) from Debian/testing (main)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The link to the duplicate bug does not exists anymore. It was
https://bugs.launchpad.net/bugs/1761784. I removed the link so this bug
can be worked on.
** This bug is no longer a duplicate of private bug 1761784
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
I spent days trying unsuccessfully to do a clean install of 18.04 onto a
system with an existing version of Linux. Each time the installer would
appear to be working properly, only to bomb out with an error after half
an hour.
Eventually I gave up, REFORMATTED MY HARD DRIVE and was able to get
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
*** This bug is a duplicate of bug 1772374 ***
https://bugs.launchpad.net/bugs/1772374
** This bug has been marked a duplicate of bug 1772374
ubiquity need mount point /sys/firmware/efi/efivars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1768230
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Your disk is currently partitioned to boot in bios mode, but you booted
the installer in EFI mode. You either need to boot the installer in bios
mode, or partition the disk using GPT and set up an EFI system partition
to install in EFI mode. This will be done for you if you choose the "use
entire
Strange. I wonder if the entries have changed since you initially tried
to install. Can you try the install again and see if it works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772407
Title:
And if it does not, then before you reboot, run efibootmgr -vv ( double
v ) and post the output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772407
Title:
ubuntu bionic "grub-efi-amd64-signed"
Could you please try the latest meld package from Cosmic?
** Changed in: meld (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769869
Title:
Crash
Hi Christopher.
Answering your questions in turn:
1) All I can say for the moment is that it was OK in Ubuntu 17.10 and
not OK in 18.04.
2) The monitor is actually a Samsung television, model no. UE40EH5000.
However, I want to be clear that the issue is with the screen in the
laptop itself, not
For more information, I am now regressing on kernels. I tried 4.14.50
and it too errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777586
Title:
Ubuntu Server 18.04 LTS aacraid error
To
I linked the wrong bug; sorry.
https://bugs.launchpad.net/bugs/1767703 is the one to view the carnage
in the aftermath of this change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668148
Title:
Your installation medium is corrupt; you will need to recreate it and
may want to verify it using the check disc option at the boot menu.
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1 - 100 of 631 matches
Mail list logo
