Public bug reported:
This is a bug in the init script of the nagios4 daemon,
/etc/init.d/nagios4, part of the nagios4-common package. I found this
bug in version 4.3.4-3 of that package, on Ubuntu server 20.04.3 LTS.
The nagios4 deamon is always stopped by 'kill -9'. Because this happens after a
Public bug reported:
After installing twine (apt install twine), running "twine upload" causes the
error:
Traceback (most recent call last):
File "/usr/bin/twine", line 11, in
load_entry_point('twine==3.1.1', 'console_scripts', 'twine')()
File
From: nore...@launchpad.net on behalf of Lucas
Albuquerque Medeiros de Moura <1939...@bugs.launchpad.net>
Sent: Monday, August 16, 2021 08:17
To: MICHAEL JEFFREY GERARD
Subject: [Bug 1939951] Re: package ubuntu-advantage-tools 17 failed to
install/upgrade: new ubuntu-advantage
Public bug reported:
I backed up my Ubuntu 18.04 system on an HDD, installed Ubuntu 20.04 on
a new computer and then attempted to restore my file system from my
backup. After rsyinc-ing, I attempted to give "sude apt-get update &&
apt-get upgrade -y", which failed on both accounts.
ProblemType:
next scan. It may even become worse.
The noise become part of the actual scan too!
You will have to stop the app and reconnect the scanner.
I've noticed this problem to be reproducable.
See attached screen output.
Kind regards,
Gerard van Drielen
** Affects: ubuntu
Importance: Undecided
Public bug reported:
Voici ce que le terminal dit pendant une tentative d'upgrader vers
Ubuntu 21.04;
les données compressées sont corrompues
dpkg-deb: erreur: subprocess returned error exit status 2
dpkg: erreur de traitement de l'archive /var/cache/apt/archives/ubuntu-release-u
Public bug reported:
Attempting to start the cachefiles service when /etc/default/cachefilesd
has #RUN=yes commented out:
systemctl start cachefilesd.service
Leaves service "active" even though the daemon fails:
systemctl status cachefilesd.service
● cachefilesd.service - LSB: CacheFiles
The proposed solution fixes the bug I filed when joining against older
Windows Active Directory servers.
(https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1906673) i.e. The
domain join works without the --use-ldaps.
We do not currently have the correct certificate set up to use --use-
ldaps,
Public bug reported:
Following update sssd/bionic-updates,bionic-security,now
1.16.1-1ubuntu1.7 to the sssd et. al. packages, our realm joins not
longer work. They hang at the step:
root@dec03daily:~# realm join ourdomain.net -U admin-acct -v
* Resolving: _ldap._tcp.ourdomain.net
* Performing
Public bug reported:
Je n'y connais rien...
Donc je ne parviens pas à effectuer la mise à jour vers 20
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.40
ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18
Uname: Linux 4.15.0-124-generic x86_64
A nicer error message would be nice. Or use /tmp for tempfiles instead
of current working directory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/673438
Title:
update-grub: cannot restore the
Public bug reported:
Please see https://bugs.launchpad.net/ubuntu/+source/python-
pip/+bug/1833229 . I have no idea why it was marked "fixed" in May,
because it still active in bionic.
** Affects: python-pip (Ubuntu)
Importance: Undecided
Status: New
** Tags: bionic python3
--
Yesterday's (10-13) update of the PPA has broken the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833229
Title:
`--extra-index-url` not working for PIP
To manage notifications about this
To stop automatic updates from overwriting the bug fix version of python3-pip,
create file
/etc/apt/preferences.d/citrain-pin-700 with the following content:
Package: python3-pip
Pin: origin "ppa.launchpad.net"
Pin-Priority: 700
--
You received this bug notification because you are a member
It appears the ppa is no longer "just working" because the mainline
bionic Ubuntu version of python3-pip has incremented. That is to say,
even after adding the ppa and doing apt update, apt-get install pulls
the buggy one from the mainline repo.
I was able to get the right version by using:
apt
Yes, please; let's get back to the core issue. The Firefox print
function does not save functioning hyperlinks when the output is PDF. I
dislike having to switch to Chromium (I use Linux) to create a PDF with
functioning hyperlinks. Can we please get Firefox to create a PDF with
hyperlinks that
** Changed in: alsa-driver (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720693
Title:
[10MVCTO1WW, Realtek ALC294, Black Headphone Out,
To make this copy-and-paste obvious for the next person to come by:
add-apt-repository ppa:ci-train-ppa-service/3690
apt update
apt install python3-pip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Additional note: the kernel is 5.5.8 from the kernel-ppa.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867195
Title:
vlc crashed with SIGSEGV playing music from SMB share
To manage notifications
Public bug reported:
using Xubuntu 20.04 preview, vlc crashed when playing music from a SMB
share via gvfs - it just did this twice in a row
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: vlc-bin 3.0.8-4
Uname: Linux 5.5.8-050508-generic x86_64
NonfreeKernelModules: 8723bu
Disregard. Looks like 4.15.0.1048 is installed but running uname -a
shows 4.15.0.1047 so the box just hasn't been rebooted since the update
and since it's an AWS ASG it's just reverting back to the 1047 version
from the AMI every time it panics and AWS re-creates the instance. Time
to rebuild
I'm seeing the same kernel panic on linux-aws 4.15.0.1048.47 as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842447
Title:
Kernel Panic with linux-image-4.15.0-60-generic when specifying
Public bug reported:
Attempting to access the property raised the exception 'SystemError: error
return without exception set'
The error occurs when version._records.hashes.file_size == 0.
The package occurred on (cups=2.2.7-1ubuntu2.5) on an Ubnuntu 18.04.2 LTS
system ; attempting to download
gerard@ASUS-HP-UB:~$ sudo ubuntu-bug ubuntu-release-upgrader-core
(apport-gtk:15348): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
(firefox:15645): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
ProblemType
Thanks for the solution, this was no fun to debug on multiple servers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774645
Title:
mount.cifs with sec=krb5 fails with No such file or directory
To
Public bug reported:
First time upgrade, fresh Bionic Beaver instance
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: uuid-runtime 2.31.1-0.4ubuntu3.2
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.5
Public bug reported:
I cannot update becuase of some problem with tird party programs, howeve
I deleted all of them an it is still occurring. It also appears a new
user called LibvirtQuemu.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libdrm-intel1 2.4.83-1~16.04.1
Hi, I am also affected by this bug but not on a Lenovo or Thinkpad
laptop. Mine is an Asus Zenbook UX301L running Ubuntu 17.10. Latest
working kernel version is 4.13.0-36-generic. Patches 37 and 38 cause the
freeze on boot. Adding option noibpb solves the issue (at least with
4.13.0-38-generic).
Proposed update fixed the issue, thanks.
product: Mobile 4 Series Chipset Integrated Graphics Controller
vendor: Intel Corporation
$ apt policy libgl1-mesa-dri
libgl1-mesa-dri:
Installed: 17.2.4-0ubuntu1~16.04.4
Candidate: 17.2.4-0ubuntu1~16.04.4
Version table:
*** 17.2.4-0ubuntu1~16.04.4
Public bug reported:
cant install anything
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: manpages 3.65-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Fri Dec 29 08:34:18
Also, if you're so inclined, I now have CouchDB 1.7.0 test packages for
Artful here:
https://launchpad.net/~jderose/+archive/ubuntu/couchdb-1.7.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729305
Devin,
Thanks for the bug report!
CouchDB 1.6.x doesn't work with the Erlang 20.0.4 packages in Artful.
I've been working on CouchDB 2.1 packages for Artful for internal use at
System76, but it's a much different beast in many ways and also has
upstream packaging changes that make it very
First of all thank you very much for your quickly response.
I am glad to say you we fixed that issue thanks to your post :)
The problem was we formatted the disk (sb5) using some tool from newer Ubuntu
version which put metadata_csum feature on it. And because using on Ubuntu
14.04 it had some
We have an error quiet similar to this one reported.
We are using Ubuntu 14.04 .. but I really think it's not a matter of version
though.
We are getting randomly the following errors:
--
[97030.025645] EXT4-fs error (device sdb5): ext4_iget:4156: inode #26351669:
comm apache2: checksum
Sorry I attached a wrong file, this one is the correct one!
** Attachment added: "e2fsck_output_ok"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1637779/+attachment/4920266/+files/error_32_1.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs,
-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gerard 2014 F pulseaudio
Date: Fri May 19 23:35:25 2017
ErrorMessage: subprocess new pre-installation
Public bug reported:
Received this error after login after a new install of ubuntu 17.04
ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: shim-signed 1.28+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
Public bug reported:
SE BLOQUEA MI MAQUINA, AL INSTALAR CROSSOVER
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libwebkit2gtk-4.0-37:amd64 2.16.1-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion:
sorry, I just realize I did not post w/ the same Id.
In order not to raise confusion
winux = gerard
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565106
Title:
Wifi works on W10 but not on Ub
Hi Christopher
As I already said, but surprising not stated here:
- I've installed 17.04 beta one week ago
- wifi works beautifully
I could say
- solved on the "17.04 non LTS"
- BUT not solved on the "16.04 LTS" which I would like to use till the end of
support (another 4 years)
What is the
*** This bug is a duplicate of bug 1667085 ***
https://bugs.launchpad.net/bugs/1667085
Public bug reported:
Je suis français. Je ne comprends RIEN à ce qui est écrit.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libsane 1.0.25+git20150528-1ubuntu2 [modified:
Public bug reported:
Steps to reproduce:
1) Fresh UEFI install using 20170209 16.04.2 daily ISO (sha1sum:
93378778ba193f6fbcac222a8d60a4bae52c94e8)
2) Reboot into install and run `sudo apt-get autoremove`
Thanks!
** Affects: debian-installer (Ubuntu)
Importance: Undecided
Hello.
I Still have this problem with Thunderbird on Ubuntu 16.10 :
- with 1 gmail account, Thunderbird is ok
- with 2 gmail accounts, Thunderbird crashes.
However my Thunderbird package is 1:45.5.1+build1-0ubuntu0.16.10.1.
I have the same bug on Ubuntu 14.04.
So the bug hasn't been fixed...
Mathieu,
Okay, just finished testing with xenial-proposed, no issues found.
Things are working as expected for my use-case (with no adjustments on
my end), so at least for the corners that my particular use-cases
covers, this proposed package seems regression free.
I tested PXE booting into a
Steve,
I'm not sure whether it was a truly representative test, but it works
fine with latest Xenial daily desktop ISO under QEMU + OVMF, and these
dailies do have xenial-proposed enabled.
(I'm testing the 2016 ISO, sha1sum
0ed4db8dad7142837ce9175e2b9617c4dd93a326.)
I recall that d-i needed
Mathieu,
I tested your PPA package with Xenial: with no config changes on my end,
it's working as expected from my use case.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
FYI, same thing is happening with the latest Zesty server ISO (see
attached).
** Attachment added: "Screenshot from 2016-10-31 14-32-09.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1637985/+attachment/4770253/+files/Screenshot%20from%202016-10-31%2014-32-09.png
--
You
Attaching tarbal of /var/log from lp:1638086
** Attachment added: "log.tgz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1637985/+attachment/4770249/+files/log.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1637985 ***
https://bugs.launchpad.net/bugs/1637985
Attaching tarball of /var/log
** Attachment added: "log.tgz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1638086/+attachment/4770250/+files/log.tgz
--
You received this bug notification
Public bug reported:
The current Zesty daily desktop ISO can't be installed, fails with error
message in bug title.
Please see attached screenshot.
I tried both "Install Ubuntu" and an OEM install, both fail.
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
**
And still present in version 5.1.4.2, under Linux version 4.4.0-36-generic
(buildd@lcy01-01) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) )
#55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016
Very annoying, had a similar problem with jEdit, which I could solve. It is a
very annoying
Public bug reported:
Zip files might include symbolic links which could be abused by an
attacker to escape from restricted directories and/or from restricted
environments. The attached patch includes a command line option -g which
does not apply the symbolic links when zip file is extracted. In
Okay, tested 0.122ubuntu8.5 from xenial-proposed, and it fixes the issue
for my use-case.
But I'm not changing verification-needed to verification-done yet as I
don't know if it fixes the use case of the original reporter.
@scotte - can you please confirm whether this fixes things for you?
--
@jbicha hmm, I didn't experience this with the final Ubuntu desktop
16.10 ISOs... what was your experience with the final 16.10 Ubuntu GNOME
ISOs?
But I also don't think this is happening with perfect determinism
either.
--
You received this bug notification because you are a member of Ubuntu
Oh, and to be clear, I have no problem with this change in Yakkety. It's
just starting to feel a bit too invasive in my opinion for Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
@martin - I tested the proposed package, and it's workable, but there
are behavior changes still compared to prior to when this regression was
introduced (in particular, the boot is a lot slower when there are
mulitple NICs but only one will be configured, even when I use
"ip=:eth0:dhcp").
Attaching a tarbal of everything i have in /var/log, not sure it's
useful (not my "ephemeral" environment is read-only with /var/log on a
tmpfs, so it's mostly empty).
Also here's my exact /proc/cmdline from within the booted ephemeral
environment:
BOOT_IMAGE=vmlinuz-4.4.0-42-generic
@chiluk - I tested the latest package in your PPA, but something seems
slightly wonky for my use case.
Networking seems to come up correctly, but it takes longer than it
should and I see warnings like this repeated several times:
ip: ether "dev" is duplicate, or "permanent" is garbage
--
You
Public bug reported:
The 20161012.1 yakkety desktop ISO fails to reboot after the install
completes (see attached screenshot).
Tested on QEMU in BIOS and UEFI mode, which is where the screenshot is
from. Same thing is seemingly happening on hardware (reboot hangs),
although I don't see this
@chiluk - the package in your PPA fixes it from my use case, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
As asked by chiluk on IRC, here's my PXE boot configuration (well,
representative one anyway, the exact kernel version will obviously
change):
DEFAULT ubuntu
LABEL ubuntu
LINUX vmlinuz-4.4.0-36-generic
APPEND initrd=initrd.img-4.4.0-36-generic root=/dev/nfs
So far I haven't encountered this again... so might have been a fluke
with the state of Yakkety for a brief period, phase of the moon, or
whatever. But if I do encounter it again, I'll collect as many details
as I can.
--
You received this bug notification because you are a member of Ubuntu
I'm back to testing u-s-d started under systemd, and I found some
serious wackiness observing `sudo journalctl -f` when I use the
brigtness up/down hotkeys.
The attached "wacky-journalctl.txt" file has the output of `sudo
journalctl -f` during which I used the brightness hotkeys *twice*, and
`sudo forkstat -D 4` when u-s-d is started under systemd and I press the
brightness up hotkey.
** Attachment added: "with-systemd.txt"
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756099/+files/with-systemd.txt
--
You received this bug
Okay, an interesting hint is that this problem seems to be fixed if
u-s-d is started under the Upstart user session instead of the systemd
user session.
If anyone wants to try this, just comment out these three lines in
/etc/X11/Xsession.d/00upstart:
if [ "${1#*.target}" != "$1" ]; then
And I sanity checked the server ISO on the same slew of UEFI hardware...
no issues found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624096
Title:
yakkety: backport (or rebase to) fix
Okay, the 20161005.1 ISOs seem to have done the trick. Tested the
desktop and server ISOs under QEMU+OVMF, plus tested the desktop ISO on
a slew of UEFI hardware. No issues encountered shim-wise.
I'll test the server ISO on UEFI hardware shortly, but there are a few
other things I need to finish
Oops, I attached the wrong screenshot, here's the correct one.
** Attachment added: "Screenshot from 2016-10-05 12-06-26.png"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+attachment/4755346/+files/Screenshot%20from%202016-10-05%2012-06-26.png
--
You received this bug
** Attachment removed: "Screenshot from 2013-11-11 11:45:50.png"
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+attachment/4755311/+files/Screenshot%20from%202013-11-11%2011%3A45%3A50.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yeah, I can do this, assuming I can reproduce it again. This is on my
work machine, so I had to just kill `fwupd` so I could get on with my
work in the meantime :D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
One other useful detail. There are actually 2 fwupd processes running,
both started by PID 1:
ps -ef | grep fwupd
root 2823 1 99 11:41 ?01:35:03
/usr/lib/x86_64-linux-gnu/fwupd/fwupd
root 4712 1 0 11:44 ?00:00:00
/usr/lib/x86_64-linux-gnu/fwupd/fwupd
But it's
Public bug reported:
Just hit this, haven't yet dug into details or tried to reproduce it.
I booted up a nearly up-to-date Yakkety desktop, noticed my fans were
running like crazy, and looking at top shows `fwupd` is the culprit (see
attached screenshot).
I don't know much about fwupd, but I'm
Thanks for the feedback, Robie! I believe the underlying problem was this
kernel bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628336
The /dev/nbd0p1, etc, partition devices were never getting creating
automatically after connecting the device, no matter how long you
waited. So you
Hmmm, today's yakkety-desktop-amd64.iso
(sha1:494bc027be3d29c494eb17d057dcc51cdfc6f50b) is seemingly still using
the broken shim package?
I'm guessing there's something special about how the shim package gets
onto the ISO as it doesn't seem to be listed in yakkety-desktop-
amd64.manifest?
But
Public bug reported:
On Ubuntu 12.10 through Ubuntu 16.04, something like this worked with
100% reliability in my experience:
sudo modprobe nbd
sudo qemu-nbd -c /dev/nbd0 /my/vm/image.qcow2
sudo mount /dev/nbd0p1 /mnt
But on Yakkety, this *almost* always fails because the /dev/nbd0p1
device
Ah, sorry, I forgot to follow up on this. Yes, the bug has been fixed
for about a week now (but I was on vacation).
Is it better to mark this as Fix Released instead?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Mathieu - I was on vacation last week, so I wasn't in the loop on IRC.
What's the current status of this? Does it seem feasible that the fixed
shim package can be signed (and FFE'd) in time for 16.10? Or are we
already at the point where reverting to the shim 0.8-0ubuntu2 package
from Xenial
** Summary changed:
- yakkety server: fails to detect and mount CD-ROM (QEMU, BIOS mode)
+ yakkety server: fails to detect and mount CD-ROM
** Description changed:
The latest yakkety server amd64 daily (20160921.1, sha1sum
b3e9f59397389bf23390f4869d3aef46de5d105c) fails to detect and mount
Public bug reported:
The latest yakkety server amd64 daily (20160921.1, sha1sum
b3e9f59397389bf23390f4869d3aef46de5d105c) fails to detect and mount the
CD-ROM.
Please see attached screenshot.
I found this testing under QEMU (BIOS mode), not yet sure whether it
effects hardware. But I'll be
@@Mathieu yeah, if you can get me a custom ISO with an updated shim
package (doesn't need to be signed, I'm not using secure boot), then
I'll giving a thorough testing under QEMU and on all the UEFI hardware I
have access too (6 different laptops, 3 different desktops).
Thanks!
--
You received
@Laszlo - darn, no luck. Following your recommendations, PXE booting is
no longer attempted, but I still end up at Shell> and the installer
doesn't launch.
I'm attaching the isolated test script I'm using ATM. If I try it with
the latest Yakkety desktop daily ISO, I hit the above hardware
Oops, forgot to attach my test script :P
** Attachment added: "test-yakkety-guest.sh"
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1624096/+attachment/4745643/+files/test-yakkety-guest.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Laszlo - thank you very much for the detailed explanation!
Sounds like your tips, plus /EFI/BOOT/fallback.efi being present on the
ISO, should be enough for me to work-around this issue. I'll let you
know how it goes.
Thanks again!
--
You received this bug notification because you are a
@Mathieu - I've been doing some quick experiments with fallback.efi on
the ISO, and I'm not sure that alone will fix things.
The problem is that when fallback.efi is present, the installer isn't
launching. Instead, OVMF tries to PXE boot (which in my test environment
fails because I don't have
@Laszlo - awesome, thanks! Do you happen to know what version introduced
the bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624096
Title:
yakkety: desktop and server ISOs wont boot under QEMU
@Laszlo - thanks for the debugging tips! I'm getting the same result
that you are.
I found a possibly related opensuse bug:
https://lists.opensuse.org/opensuse-bugs/2016-01/msg00965.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Sometime after August 25th (or so) something changed in the Yakkety ISOs
that make them no longer boot under QEMU in UEFI mode. However, the ISOs
do work fine still on the physical UEFI hardware I've tested (3
different systems). I'm not sure about other VM solutions like
Brain,
Strange. So I just tried the upgrade again, and after the upgrade
completed, I:
1) Clicked "Reboot Now" (which did nothing, same as yesterday)
2) Ran `sudo reboot` - it worked, but seemed to hang for some time
before doing anything (it hung for maybe 20 seconds or so)
I'm not sure how
Public bug reported:
After doing a 14.04 to 16.04 upgrade, clicking "Reboot Now" has no
effect. update-manager simply closes. However, I could then reboot fine
using the indicator or the power button, which kinda suggests the
problem is in update-manager rather than in the general state of such
FYI, I seem to be hitting this same bug (under qemu) with the xenial
daily ISO as well (which have xenial-proposed enabled by default).
Will this be fixed in Xenial also?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Marco: thanks for the FYI!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1598770
Title:
Unity in low-graphics mode has animations and unneeded redraws
To manage notifications about this bug go
Here's another screenshot that shows the SegvAnalysis.
In my testing thus far, this failure (assuming it's related to this
unity/nux change) only seems to happen when trying to install under
qemu. I tried -vga qxl, -vga std, and -vga virtio... none of them yield
a working installation. Compiz
Possibly as a result of this change, unity/compiz is failing to start
when trying to install from the latest 16.04.1 daily ISO under qemu
(xenial-desktop-amd64.iso 20160713, sha1sum
c9b1ad9b1044c4e68684395daa3f85e016491c3a).
I attached a screenshot as I couldn't file a bug from within the qemu VM
Also attaching a screenshot, just so folks don't think I'm making this
up :P
** Attachment added: "screenshot.png"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876/+attachment/4692953/+files/screenshot.png
--
You received this bug notification because you are a member of
Public bug reported:
This is an extremely odd bug that requires a very specific scenario to
reproduce:
1) You need to be using an ecryptfs-style cryptoswap partition (as would
be setup when you choose "Encrypt my home directory" during the
installation)
2) The underlying physical swap partition
@diwic - I agree, there have been problems in multiple places causing
this.
Yesterday I sorted out one of them. If you have swap on a GPT
partitioned NVMe or MMC drive, ecryptfs-setup-swap isn't correctly
marking the partition as non-auto-mounting, which leads the the user
erroneously being
after installing new kernel 4.7, RJ45 connected
I rebooted a first time (on 4.7)
took RJ45 out
no wifi
I connected RJ45 to install Chromium
rebooted a 2nd time, RJ45 out, no wifi
I rebooted a 3rd time, RJ45 out, wifi was visible (see the picture below)
http://i68.tinypic.com/29479ly.jpg
I did
Christopher
in order to bring you as much info as I can, I did the following tests and the
result is very strange!!
after installing new kernel 4.7, RJ45 connected
I rebooted a firt time (on 4.7)
took RJ45 out
no wifi
I connected RJ45 to install Chromium
rebooted a 2nd time, RJ45 out, no wifi
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565106
Title:
Wifi works on W10 but not on Ub 16.04 nor 14.04
To manage
Hi Christopher
I followed your recommendations
as far as I understood
- I reinstalled a brand new clean version with the current kernel
- I declared the bug following your user guide link
Here is the bug address
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1595960
Hope you
1 - 100 of 1534 matches
Mail list logo
