--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068738
Title:
AMD GPUs fail with null pointer dereference when IOMMU enabled,
leading to black screen
To manage notifications about this bug go to:
h
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068738
Title:
AMD GPUs fail with null pointer dereference when IOMMU enabled,
leading to black screen
To manage notifications about this bug go to:
h
Public bug reported:
Kernel 5.15.113 does not load graphic drivers during booting
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
#1930573 usrmerge error after upgrading from 21.10 to 22.04 LTS
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: usrmerge 25ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
NonfreeKernelModules: zfs zuni
Public bug reported:
The version of libsystemd0 Ubuntu 20.04 has the following issue present
in the package:
https://github.com/systemd/systemd/issues/15528
https://github.com/ledbettj/systemd-journal/issues/88
It was fixed here:
https://github.com/systemd/systemd/commit/2b6df46d21abe8a8b7481e4
Public bug reported:
doing a fresh install on HP15 laptop with a clean reformat of hard drive
during grub install to sda1 receive fatal errror message
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname
** Changed in: unetbootin (Ubuntu)
Assignee: (unassigned) => blake kinley (bl8k3)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965791
Title:
unetbootin crashed with SIGSEGV in QThreadPriv
** Changed in: unetbootin (Ubuntu)
Assignee: Gerhard Pirretti (gerhard272) => blake kinley (bl8k3)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1620628
Title:
Only get a grey window
Hi there,
I'm afraid I haven't had much time to look properly into this recently,
but it remains on my list.
In the meantime, I've submitted an enhancement request upstream:
https://bugzilla.mindrot.org/show_bug.cgi?id=3203
Cheers
Toby
** Bug watch added: OpenSSH Portable Bugzilla #3203
ht
Hi Christian,
Again, thanks for the above.
https://bugzilla.mindrot.org/show_bug.cgi?id=2775, in particular, looks
interesting, as it seems to be an attempt to bring the relevant ccache
patches up to date for version 8. e.g. we have been patching our SL
systems additionally for
https://bugzilla.
Hi Christian,
Thanks for your reply (and for the links). I agree that a configurable
option coming from upstream would be the preferred option. I'll submit
a bug upstream accordingly and note the ID here.
I note there's a patch referenced in the openssh mailing list link,
unfortunately the link
set KRB5CCNAME at all, so the system
default is used.
Many thanks
Toby Blake
School of Informatics
University of Edinburgh
** Affects: openssh (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Confirmed, I get the message in #1 every boot. 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873614
Title:
Definition of add_mountroot_fail_hook doesnt match lvm2's usage
To manage notificat
Public bug reported:
not sure it's a bug
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.23
Architecture
I tried it by comparing the same VM with and without that setting. Here
is what I found:
With "Use Host I/O Cache" disabled, booting took 40 seconds.
With "Use Host I/O Cache" enabled, booting took 12 seconds.
With "Use Host I/O Cache" disabled, doing a mini update took a few minutes.
With "Us
Public bug reported:
Working find on Ubuntu 19.10, started having a cracking sound in the
audio immediately after upgrading to 20.04. Tested in Firefox and
Chrome playing video/audio.
AMD x570 chipset
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersi
Public bug reported:
I found the 'Dell Premium Active Pen (PN579X)' that I just received and
as presently sold by Dell elicits the problem described at
https://github.com/linuxwacom/xf86-input-wacom/issues/39. I generated a
patch file from https://github.com/linuxwacom/xf86-input-
wacom/commit/3b
Release 2.4.3 debdiff.
** Description changed:
- Am running an HA MAAS, but every few days named gets stuck on one of the
- region controllers.
+ [Impact]
- systemd thinks the service is running, but it doe not respond to any
+ * systemd thinks the service is running, but it does not respond
** Changed in: maas (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: maas (Ubuntu Bionic)
Assignee: (unassigned) => Blake Rouse (blake-rouse)
** Also affects: maas/2.4
Importance: Undecided
Status: New
** Changed in: maas/2.4
Status: New
Public bug reported:
NVIDIA binary driver VER 340.17 is crashing steam. If I purge all NVIDIA
drivers Steam runs successfully from Nouveau, but seems to have
performance issues in game. Steam support was unhelpful and referred me
to anyone else.
Steam output from terminal is:
Running Steam on ub
Are you re-initializing or on fresh install you hit this issue?
>From the description of the bug I cannot tell.
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Changed in: maas
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/1847058
Title:
MAAS deployment failed with vgchange command
To manage notifications about this bug go
We are current working on getting this backported to 2.4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710278
Title:
[2.3a1] named stuck on reload, DNS broken
To manage notifications about this b
** Changed in: maas
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/1743595
Title:
modprobing mlx5_core doesn't bring the interface up
To manage notifications about this
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594317
Title:
Cannot start lxd-bridge.service wh
This seems to be an issue with the kernel and not an issue with MAAS
directly. Which Ubuntu release is set as the commissioning release on
the Global Settings page? If you can provide the full console log of the
boot that would be helpful as well.
** Also affects: linux (Ubuntu)
Importance: Und
** Merge proposal linked:
https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/371218
** Changed in: maas/2.7
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
Last resolution update:
The bind9 source package should be modified to generate 2 binary
versions of bind9.
bind9 -> standard multi-threaded bind9 (main)
bind9-single -> single-threaded bind9 (universe)
This will allow security updates to still be handled with the source
bind9 package generating
** Changed in: maas/2.7
Status: Fix Released => New
** Changed in: maas/2.6
Assignee: (unassigned) => Blake Rouse (blake-rouse)
** Changed in: maas/2.6
Milestone: None => 2.6.1
** Changed in: maas/2.7
Milestone: 2.3.0alpha2 => 2.7.0alpha1
** Changed in: b
No we do not ensure that. We leave that up to the user to define a
proper over-commit ratio for their systems.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831134
Title:
Pods Cannot allocate memor
** Changed in: maas (Ubuntu)
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/1804861
Title:
MTU size defined on /etc/netplan/50-cloud-init.yaml not applied
To mana
Attached is the packet capture.
** Attachment added: "GRUB2 EFI HTTP Boot Packet Capture"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1822007/+attachment/5254210/+files/grub2-efi.pcap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I have verified that the proposed package in cosmic works as expected. I
performed the following steps with MAAS.
0) Provide kernel and initrd on an HTTP server on the network.
1) Boot from the network in UEFI mode using grub's grubnet.efi binary.
2) Provided the following config:
linuxefi http:/
Seems that SUSE supports this in their grub because its well documented
on their site:
https://en.opensuse.org/UEFI_HTTPBoot_Server_Setup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822007
Title:
This bug blocks the progress of completion of bug:
https://bugs.launchpad.net/maas/+bug/1820983
** Changed in: grub2 (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/b
Public bug reported:
While implementing the complete UEFI HTTP booting path for MAAS I have
hit a roadblock. Grub2 is loaded but then fails to request the
/grub/grub.cfg as it does when booting with UEFI PXE (aka. TFTP).
The dhcpd.conf has the following in it to tell the UEFI firmware to load
the
I have verified that the proposed package in bionic works as expected. I
performed the following steps with MAAS.
0) Provide kernel and initrd on an HTTP server on the network.
1) Boot from the network in UEFI mode using grub's grubnet.efi binary.
2) Provided the following config:
linuxefi http:/
Public bug reported:
no boot just red squar on screan
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.2
Architectur
Sorry I am no longer using Ubuntu so I cannot say if the bug still
exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316648
Title:
gedit hangs on start
To manage notifications about this bug g
** Changed in: maas
Milestone: next => 2.5.0rc1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801899
Title:
cannot install with python3.7 as default async is a reserved keyword
To manage notif
** Changed in: maas
Assignee: (unassigned) => Blake Rouse (blake-rouse)
** Changed in: maas
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1801899
Urgency is high, this slows down every booting machine of MAAS by 1:30
seconds, that is a long boot time just to get the OS to install or to
commission the machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
Here is the output log:
http://paste.ubuntu.com/p/KfTWC5ghwR/
You can't really see the iSCSI error in the console log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792905
Title:
[2.5] iSCSI syst
** Also affects: open-iscsi
Importance: Undecided
Status: New
** No longer affects: open-iscsi
** Also affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
See title.
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
CurrentDesktop: ubuntu:GN
Public bug reported:
On boot up I get a message alot are getting ,, Graphics need
reconfigured booting in Low Graphics Mode, After log in I get a message
about a system error referencing the file usr/lib/xorg/xorg
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVers
** Merge proposal linked:
https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/341132
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743249
Title:
High IO on the system prevents MAAS to
I experienced this issue twice in the last 24 hours on 16.04. Both
times, I waited over an hour after the computer froze before performing
a hard reset on the machine. (The expected time for the operation to
complete was under 10 minutes.) In my case, the computer goes directly
from working as expe
** Changed in: maas
Status: In Progress => Invalid
** Changed in: maas
Assignee: LaMont Jones (lamont) => (unassigned)
** Changed in: maas
Milestone: 2.1.3 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Merge proposal linked:
https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/337233
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743249
Title:
High IO on the system prevents MAAS to
Andres did the testing of the changes and has logs to prove the
improvement.
On Tue, Feb 6, 2018 at 4:43 PM, Jason Hobbs
wrote:
> Blake, that's great. Do you have before and after numbers showing the
> improvement this change made?
>
> Do you have any data or logs that led yo
Actually caching does make a difference. That method is not just caching
the reading of a file, it caches the searching of the file based on the
purpose, the reading of that file from disk (sure can be in kernel
cache), the parsing of the template by tempita.
All of that is redudant work that is b
** Changed in: maas
Status: New => Triaged
** Changed in: maas
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1743966
Title:
Trusty deployments fail when
Jon,
Does armbian-config work on ubuntu 16.04?Does that command freeze all
SW or allow you to specify?
THX
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691729
Title:
linux-firmware-raspi
although the "diversion" workaround results in a nice-looking upgrade
output. The system fails to reboot for me 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/1691729
Title:
linux-firmware
This kernel is PXE booting from MAAS. We might be able to modify the
kernel on disk that pxelinux.0 pulls to get you more information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1742324
Title:
Bi
** Changed in: systemd (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/1739672
Title:
Regression in getaddrinfo(): calls block for much longer on Bionic
(com
The issue is with the systemd resolver not with glibc.
With systemd-resolve IP in /etc/resolv.conf:
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
n
$ systemd-resolve --status
Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
$ time ./test not-a-real-hostname
Trying to resolve: not-a-real-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)
real0m10.007s
user0m0.001s
sys 0m0.001s
--
You received this bug notification because you are a mem
** Tags added: packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729925
Title:
Update to upstream 2.3.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sourc
I have verified that smoser changes do work with MAAS.
Testing steps:
1. Generated xenial amd64 image stream using smosers PPA.
2. Installed MAAS.
3. Removed the workaround in MAAS.
4. Imported the xenial amd64 image with smosers PPA.
5. Entered rescue mode.
6. Pinged google.com. (Worked)
7. Exit
Public bug reported:
after an extended time with no hdmi plugged in i plug in the hdmi and i
receive no signal
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-core 2:1.19.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
I have submitted the patch upstream:
https://github.com/ipxe/ipxe/pull/66
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707999
Title:
pod VM fails to PXE boot after receiving multiple DHCP offers,
Rod,
I moved my comment to the other bug. But to respond to your comments.
I think your point about #1 is something that should be solved during
installation. There is no reason the Ubuntu installation cannot be smart
enough to re-order the boot order. I think on fresh install that makes
perfect
Comment I made on https://bugs.launchpad.net/maas/+bug/1642298. Was
requested to direct it here.
I think this is more of a GRUB issue overall instead of a MAAS issue
directly. True it affects MAAS and we can do the debconf selections to
work around this issue but overall for quality of Ubuntu I do
I think this is more of a GRUB issue overall instead of a MAAS issue
directly. True it affects MAAS and we can do the debconf selections to
work around this issue but overall for quality of Ubuntu I do not
believe this is the proper fix.
I will give an example without MAAS.
1. First the user inst
Scott,
Since we are no longer using iscsi and using the squashfs over HTTP,
would open-iscsi even be used?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set
I noticed that the repo now has kernel 4.4.0-93 available- i tried that
but it did not work either - it also seemed to set SMT to 8 which caused
me a few problems until i realized what it did.
I rebooted with kernel 4.4.0.94 and all is well again (after I set SMT
to off)
Hopefully the new kernel
Added kernel 4.4.0-94-117 to the nova node
I am now able to create VMs on it.
Fix is successful
ubuntu@rcsnode03:~$ uname -a
Linux rcsnode03 4.4.0-94-generic #117~lp1709784 SMP Wed Aug 23 20:28:29 UTC
2017 ppc64le ppc64le ppc64le GNU/Linux
ubuntu@rcsnode03:~$ virsh list
IdName
I will look into testing it on our nova host.
I tested it on a vm just to ensure it booted ok- no issues. I will try it on
the nova host as soon as i can and see if i am able to launch a virtual
instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Also see Bug 1709784 -- seems to be the same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1712626
Title:
Cannot launch virtual instance on nova host after upgrading to kernel
4.4.0.92- wo
not able to run apport-collect
It appears that the latest upstream stable kernel is v4.4.83 -- I have that
installed and it is ok- no issues- the problem does not exist in this kernel.
However, a apt update installed 4.4.0-92 - this one did have issues. I
have 9 more systems to update- it woul
Public bug reported:
Host -- IBM Power 8 822L
OS- Ubuntu 14.04 ppc64el
previous kernel 3.19.0.68
Nova Compute host using kvm - Openstack Liberty
HWE was out of date so needed to update
Steps:
sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
sudo init 6
sudo apt upda
te open_flags after ->inactivate() callback"
>
>
> I'll prep a build with that and test as well
Here's what is brewing for my pull request, although if you can
successfully test things, I'm happy to add a Tested-by: tag before
actually sending the pull request:
gi
** Changed in: maas/2.2
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710278
Title:
[2.3a1] named stuck on reload, DNS broken
To manage notifications about this b
** Changed in: maas
Status: Triaged => In Progress
** Changed in: maas
Assignee: (unassigned) => Blake Rouse (blake-rouse)
** Changed in: maas
Milestone: None => 2.3.0
** Also affects: maas/2.2
Importance: Undecided
Status: New
** Changed in: maas/2.2
I
On Wed, Aug 2, 2017 at 9:49 AM, Ryan Harper <1642...@bugs.launchpad.net>
wrote:
> On Wed, Aug 2, 2017 at 8:12 AM, Blake Rouse
> wrote:
>
> > update_nvram is now default for curtin and re-ordering is also default
> >
>
> MAAS send update_nvram as True ? or False
update_nvram is now default for curtin and re-ordering is also default
for UEFI installs. I don't think setting grub2/update_nvram in debconf
should be a default. To me MAAS should tell curtin to set that debconf
as that is overriding a package default.
--
You received this bug notification becau
dann,
I think you are correct that 'grub2/update_nvram' is still not set by
curtin and an upgrade of grub could break the machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642298
Title:
UEFI
I think having MAAS tell curtin to set the grub2/update_nvram to False,
works fine. Since the path to the EFI loader should not change this is
acceptable.
Having grub adjust the EFI vars because of an upgrade is really bad in
MAAS case because a following re-deploy will no longer work.
--
You re
** Changed in: maasrsd
Status: Triaged => Fix Committed
** Changed in: maasrsd
Status: Fix Committed => Invalid
** Changed in: maas
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
More info: Host is Server 2016. Guest is Generation 2 type. Dynamic
memory is not enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676209
Title:
VM crashes after saving and restoring with lat
Hi, I know this isn't my thread but I'm trying to help. I am seeing the
crash of the VM during a Windows Server Backup with the latest kernel
4.4.0-67. I installed the kernel from comment 42 referenced in the other
thread. It did make a difference. I will post screenshots of the
results.
Side note
** Attachment added: "Linux4.4.0-71jsalisburyNoCrash.gif"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676209/+attachment/4848321/+files/Linux4.4.0-71jsalisburyNoCrash.gif
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
Running on Ubuntu 14.04 LTS, running mhonarc prints to stderr:
defined(%hash) is deprecated at /usr/share/mhonarc/mhamain.pl line 1564.
(Maybe you should just omit the defined()?)
defined(%hash) is deprecated at /usr/share/mhonarc/mhopt.pl line 867.
(Maybe you
I have the same problem with Gigabyte Aero 14.
NVidia gtx 1060
Kabylake i7 7700HQ
16GB RAM
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1637733
Title:
freeze on login with prime-select intel
To ma
Bob,
This is fixed in MAAS the issue is still in the Xenial images. That is
why cloud-init is still marked Confirmed for Xenial as it has not been
SRU'd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Attachment added: "dmesg output"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659430/+attachment/4809132/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659430
Title:
Public bug reported:
I previously reported a X freeze and screen powering off bug over here
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1655803. I had
hoped that some of the fixes in newer mesa releases would fix it, but
alas I having the same problem on the latest x-staging mesa. After
Public bug reported:
I added the x-staging ppa and upgraded my 16.04 system (equipped with
AMD W9000) to use the mesa drivers in the upcoming release. After about
15 minutes of emacs, terminal, and chrome usage the screen blanks to
grey with blue squares, then to grey, then powers off. I'm loggi
t *r, ppc_avr_t *b,
> uint32_t ps)
> }
>
> for (i = 0; i < 16; i++) {
> -zone_digit = (i * 2) ? b->u8[BCD_DIG_BYTE(i * 2)] >> 4 : zone_lead;
> +zone_digit = (i) ? b->u8[BCD_DIG_BYTE(i * 2)] >> 4 : zone_lead;
Extra (); I'd g
** Changed in: maas/2.1
Importance: Undecided => Critical
** Changed in: maas/2.1
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas/trunk
Assignee: (unassigned) => Andres Rodriguez (andreserl)
--
You received this bug notification because you are a member o
Yes this fix should be SRU to Xenial as anyone with lots of MAAS images
comes across this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1389811
Title:
tgtadm: out of memory crash
To manage n
** Also affects: maas/1.9
Importance: Undecided
Status: New
** Changed in: maas/1.9
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1574113
Title:
curtin/maa
** Changed in: maas
Milestone: 2.1.1 => 2.1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621901
Title:
impitool lacks support for ipv6 addresses
To manage notifications about this bug go to
** Changed in: maas
Milestone: 2.1.1 => 2.1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To manage notifications abo
** Changed in: maas
Milestone: 2.1.1 => 2.1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1629972
Title:
networking stop incorrectly disconnects from (network) root filesystem
To manage notif
** Changed in: maas
Milestone: 2.1.1 => 2.1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628535
Title:
AH00493: SIGUSR1 received. Doing graceful restart - Apache2 crashes -
Can't access m
Public bug reported:
When I start my system I get this error message. I am not personally
trying to install or upgrade tex-common, so I'm not sure why this is
happening.
I recently upgraded to Ubuntu 16.04.1 LTS, which is when I noticed this
(though I am not 100% confident that it had never occur
1 - 100 of 409 matches
Mail list logo
