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
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
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
**
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
Same result when I use "Try Ubuntu without installing" and "Install
Ubuntu". Happens with both UEFI and BIOS installs.
A quick glance at `JournalErrors.txt` confirms that the crash is
happening during "Configure time zone...":
Jun 01 15:59:03 hostname /plugininstall.py[6642]: Exception during
For me the installer is crashing when the status beneath the progress
bar says, "Configuring time zone...".
(See attached screenshot.)
Note this was a UEFI install in OEM mode. I know this crash is likewise
occurring with BIOS installs in OEM mode. Will try a normal install
next.
** Attachment
Any chance this can get fixed in Xenial in time for 16.04.1?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447282
Title:
Does not use encrypted swap when using GPT partitioning + encrypted
home
On a whim, I just checked in on this with the 20160601 Xenial daily
amd64 ISO (sha1sum e07c8b4df1fc71a487fafb309bd318041a65774f), and
everything works great:
http://cdimages.ubuntu.com/xenial/daily-live/pending/
So seems things are on track for this not being a problem in the 16.04.1
release.
Public bug reported:
No other details at this time, will add more as I have more info.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: ubiquity 16.10.1
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture:
Also, the graphical Ubuntu Software Updater is likewise hanging
indefinitely.
And I've confirmed this on 3 different systems so far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583879
Title:
Public bug reported:
Just ran `sudo apt-get update`, which is hanging indefinitely after the
downloads complete, the last CLI output from which is:
Fetched 733 kB in 1s (399 kB/s)
Looking at `top` suggests `appstreamcli` is the culprit as it's pegged
at near 100% CPU usage:
100 0.1 18:29.02
** Description changed:
Ubiquity (as shipped on the 16.04 amd64 desktop ISO) does not download
updates while installing when you've checked "Download updates while
installing".
Same result with both BIOS and UEFI installs (although UEFI installs
- aways download the latest kernel,
Okay, seems that "Download updates while installing" has no effect with
the Ubiquity version on the 16.04 ISOs.
I filed a bug against Ubiquity for this, would appreciate if someone
could confirm my findings:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1580232
--
You received this
Public bug reported:
Ubiquity (as shipped on the 16.04 amd64 desktop ISO) does not download
updates while installing when you've checked "Download updates while
installing".
Same result with both BIOS and UEFI installs (although UEFI installs
aways download the latest kernel, whether or not
@seb128... I'll try to get some better debug info soon. Interestingly,
it only seem to happen with Intel 7260 WiFi cards (and not, for example,
with Intel 8260 WiFi cards).
So I'm not sure whether what we're seeing is actually a problem with
network-manager. I'm now kinda thinking it's more
With this proposed package, System76 is seeing network-manager crash
upon the first resume from suspend. Anyone else experiencing this?
I'll be looking into this more today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed this fix in the proposed packaged, everything seems shiny.
I confirmed that after an OEM install, enabling proposed, updating, and
finally clicking "Prepare for shipping to user", Ubiquity behaves as
expected during the first-run user config:
1) When not connected to Ethernet and you
** Description changed:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to
Hmm, I just tried this on Skylake hardware, and "Download updates while
installing" isn't doing the trick.
Could be that "Download updates while installing" is broken on the 16.04
ISOs, or this could be a result of the phased updates done by the Ubuntu
Software Updater and related components that
** Description changed:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to
Abhinav,
Sounds like you're encountering a different bug, or perhaps your ISO
file is corrupted. Have you verified the checksum of your download?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
** Description changed:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to
** Description changed:
- Currently it's impossible to install from xenial-desktop-amd64.iso on a
- wide range of hardware with Nvidia GPUs.
+ [Description updated to reflect state of 16.04 release ISO]
- The problem is invalid opcode(s) when using llvmpipe (the software
- opengl fallback,
Just confirmed on Skylake hardware that llvm-toolchain-3.8 from proposed
fixes this issue on Skylake hardware using llvmpipe.
Thanks!
** Changed in: system76
Status: Triaged => Fix Committed
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
After further investigating, it seems this bug doesn't effect Haswell-E
after all, sorry about the confusion.
Will continue to report back as we learn more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that tjaalton's above test packages fix the problem on a
Skylake laptop with an i7-6700 CPU and an Nvidia 970m GPU when using the
nouveau driver.
I installed libllvm3.8_3.8-2ubuntu1.1_amd64.deb from a VT then rebooted,
and now I have working Unity again.
--
You received this bug
*** This bug is a duplicate of bug 1572436 ***
https://bugs.launchpad.net/bugs/1572436
Public bug reported:
The `oem-config-gtk` package is not installed after doing an OEM install
from the Xenial 20160419 daily desktop ISO (sha1sum
8965fb3673631e1161b4656f2c95b593ac302eb2). This is true on
Oh, and another bit of information: our laptops all use embedded Display
Port for their connection to the internal screen, and in this case, this
bug always manifests.
So at least in our testing so far, both eDP and DP seem to be effected.
--
You received this bug notification because you are a
So there seems to be a curious pattern with this bug (which might
provide an important hint): on desktop systems with 970 GTX or 980 GTX
cards, this bug always seems to happen when connected to a monitor over
DisplayPort, but does *not* seem to happen when connected to a monitor
over HDMI.
We'll
** Changed in: xorg-server (Ubuntu)
Status: New => 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/1561685
Title:
x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
Correction: this is fixed as of 1.18.3-1ubuntu2.
1.18.3-1ubuntu1 still had this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561685
Title:
x-staging: 1.18.2-2ubuntu0.1 host breaks arrow
I'm no longer having this problem as of 1.18.3-1ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1561685
Title:
x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
To manage
David, thanks for providing more information!
In terms of looking for issues related to the NVMe driver, this is
probably the best approach:
dmesg | grep -i nvme
And then see if there is anything suspicious in the resulting output.
In term of the CPU performance being dramatically different
** Description changed:
Currently Unity on Xenial is unusable when the llvmpipe software
fallback is used, at least on certain hardware.
For example, from dmesg:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4
sp:7ffccd914ea0 error:0
[ 2093.109485] traps:
m76
Status: New => Triaged
** Changed in: system76
Assignee: (unassigned) => Jason Gerard DeRose (jderose)
** Changed in: system76
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
Currently Unity on Xenial is unusable when the llvmpipe software
fallback is used, at least on certain hardware.
For example, from dmesg:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4
sp:7ffccd914ea0 error:0
[ 2093.109485] traps: compiz[10192]
Mathieu,
Everything seems solid with this fix. I confirmed that:
1. When plugged into Ethernet, the NM applet is show, networking is
enabled, and ubi-timezone correctly guesses your timezone
2. When *not* plugged into Ethernet but you have WiFi hardware, the NM
applet is shown, oem-config
One other thing... in the future if you encounter any issues, please use
the System76 support system.
Log into your System76 account, then go to support and created a ticket.
You'll tend to get a much quicker response there.
Our engineers do their best to keep tabs on System76 related bugs on
Thanks for the bug report, sorry to hear you're having issues!
Sounds like you're having multiple (and perhaps unrelated issues), so
let's first focus on the keyboard and mouse not working.
If you could please provide a bit more information to help us narrow
this down:
(1) You used the word
** Changed in: system76
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563505
Title:
unresponsive lemu6 . . . NVMe SSD ( samsung SSD 950 PRO )
To manage
Mathieu, thanks a million for fixing this! I'll test it ASAP!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508865
Title:
oem-config: networking not enabled during user config
To manage
Okay, I just tried this on an Intel GPU system, and it has the same
problem.
Arrow keys are broken with 1.18.2-2ubuntu0.1, but work fine with
1.18.1-1ubuntu4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This is an odd one. 1.18.2-2ubuntu0.1 (on the host) breaks the arrow
keys on qemu guests.
Actually, I'm not sure it breaks the arrow keys on the guest in all
scenarios, but it at least breaks them in the pre-boot menu when trying
to install a qemu VM from an ISO.
For
Yup, I can also confirm that it seems fixed in the 20160323 daily ISO.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554099
Title:
Changing what action for security updates unusable
To manage
Yup, I can also confirm that it seems fixed in the 20160323 daily ISO
(tested yesterday). Will test today's shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554099
Title:
Changing what
I'm still seeing this bug on a fresh install from today's daily ISO
(20160321, sha1sum 4773a2328eb4470761e1c37174d5d3cad5b6219d).
But I'm no longer seeing it on my upgraded existing install from a few
months back.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Same is happening with latest Ubuntu (Unity) Xenial daily ISO (sha1sum
8e06dd499bfe357ebbad44c827d8428d70baacf4).
I attached a screenshot of the same problem under Unity.
This bug has been around for a few weeks or so, although I'm not exactly
sure when it was introduced.
** Attachment added:
Public bug reported:
Sometime recently during Xenial development, oem-config has become quite
broken.
It seems the underlying problem is that the "oem" user and the
"/home/oem" folder aren't getting removed by oem-config-firstboot.
Steps to reproduce:
1) Do an OEM-mode install from the latest
This problem seems to exist currently on both 15.10 and Xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085766
Title:
/var/log/upstart/ureadahead.log contains garbage
To manage notifications
Just to clarify what the behaviour is with 14.04.4, what the behaviour
used to be up till 15.10.
After an OEM install and clicking "Prepare for shipping to end user", on
the next boot 14.04.4 will:
1. Automatically enabled wired networking when connected over Ethernet,
or
2. When not connected
1 - 100 of 804 matches
Mail list logo
