You should also check what's going on with this error:
Could not resolve 'archive.getdeb.net'
That domain doesn't seem to exist anymore, maybe you added that a long
time ago to your sources list?
--
You received this bug notification because you are a member of Ubuntu
Server, which is
Hi,
my keyboard has changed from azerty to qwerty yesterday, i was with the 14.04
LTS ubuntu version. Today after a upgrade in 16.04 LTS, i have still the same
problem.
how to fix it ?
Dell Latitude E6430
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Tue, 09 Oct 2018, pragyansri.pa...@intel.com wrote:
> Confirmed information from microcode team:
>
> 206F2 – Westmere-EX Rev 0x3B shows as OK for OS load. The prior one marked
> as Production was 0x39 and mark as NOT_FOR_OS.
> 206C2 – Westmere-EP Rev 0x1F and 0x1E shows as OK for OS load
Resetting to verification-done for bionic; using netplan.io
0.40.1~18.04.1:
I have run more tests and I can verify that renames at boot are behaving
correctly with netplan -- netplan follows exactly the configuration
provided on the system:
network:
version: 2
ethernets:
ens6:
The activity in the upstream bug seems to have stalled. Last report
seems to indicate that http://bugs.squid-
cache.org/attachment.cgi?id=3549 "works around the problem", but it's
not clear what the consequences are of the workaround versus a proper
committed fix.
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: isc-dhcp (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/1781699
Title:
To re enable the network after suspended mode I found that this works:
22:07:23-root@Seth:~$ rmmod r8169
22:11:22-root@Seth:~$ modprobe r8169
Unloading the driver and then reloading it brings the interface back up.
unplugging the cable did not, nor did any network manager commands that
I tried.
Tested.
Works OK
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794923
Title:
Corrupt sreen in CIV VI
To manage notifications about this bug go to:
The activity in the upstream bug seems to have stalled. Last report
seems to indicate that http://bugs.squid-
cache.org/attachment.cgi?id=3549 "works around the problem", but it's
not clear what the consequences are of the workaround versus a proper
committed fix.
--
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We noticed that you were installing the LTS version of
Ubuntu using an older version of the installation media. The latest
point release of 16.04 is 16.04.3. Please try installing from that
version of the
Public bug reported:
our vmtest proposed tests failed here
https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64-proposed/16/console
those essentially get run like
+ ./tools/jenkins-runner -p4
CURTIN_VMTEST_ADD_REPOS=proposed
CURTIN_VMTEST_CURTIN_EXE_VERSION=18.1-56-g3aafe77d
Booting in recovery mode and resuming normal start works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796730
Title:
Ubuntu 18.10 regression: nvidia driver does not work
To manage notifications
Removing packages from cosmic:
smokeqt 4:4.14.3-1.2ubuntu3 in cosmic
libsmokeqt4-dbg 4:4.14.3-1.2ubuntu3 in cosmic amd64
libsmokeqt4-dbg 4:4.14.3-1.2ubuntu3 in cosmic arm64
libsmokeqt4-dbg 4:4.14.3-1.2ubuntu3 in cosmic armhf
Excellent! Thank you...
--
Cristian Aravena Romero (caravena)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796743
Title:
Ubuntu 18.10 - Alienware 17 R5 crashes on sleep
To manage notifications
Same here, touchpad not working in Ubuntu 18.04... on every kernel i
tried
curious facts:
sudo acpidump | grep -C3 ELAN
5B10: 39 5F 48 49 44 00 A0 13 93 54 43 50 44 0A 02 A4 9_HIDTCPD...
5B20: 0D 53 59 4E 41 33 32 35 35 00 A0 13 93 54 43 50 .SYNA3255TCP
5B30: 44 0A 03 A4 0D 41 4C
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: akonadi (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/1782558
Title:
Yay this is in fact fixed in 4.19-rc7! Thanks very much this was a real
show stopper :)
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
installation log of nvidia-driver-390
** Attachment added: "Nvidia-driver-installation.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796730/+attachment/5199235/+files/Nvidia-driver-installation.log
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have a very similar issue after upgrade to 18.10 (the system hangs
after gdm login).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796730
Title:
Ubuntu 18.10 regression: nvidia driver does not
I was able to fix it with the comment by nschmelzle here:
https://gist.github.com/tsrivishnu/5b467f07374ce42ad6d97b6a3fdf0ea5
The problem was that the touchpad was using the synaptics driver, while the
trackpoint used libinput. The solution was to uninstall the synaptics driver:
apt remove
Removing packages from cosmic:
perlqt 4:4.14.1-0ubuntu11 in cosmic
libqtcore4-perl 4:4.14.1-0ubuntu11 in cosmic amd64
libqtcore4-perl 4:4.14.1-0ubuntu11 in cosmic arm64
libqtcore4-perl 4:4.14.1-0ubuntu11 in cosmic armhf
** Also affects: grub2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: grub2 (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: grub2 (Ubuntu Bionic)
Importance: Critical => High
** Changed in: grub2 (Ubuntu Bionic)
Status: New => Triaged
Verification-done with shim 15+1533136590.3beb971-0ubuntu1 / shim-signed
1.37~18.04.2:
I have verified that the system boots correctly, can chainload to
Windows 10, and that common tasks for mokutil (setting timeout,
enrolling a key, toggling validation) are working as expected.
Marking
Upstream bug report: http://gnats.netbsd.org/cgi-bin/query-pr-
single.pl?number=53646
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1793028
Title:
NetBSD CVE Patch Regression
To manage
Upstream bug report: http://gnats.netbsd.org/cgi-bin/query-pr-
single.pl?number=53646
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793028
Title:
NetBSD CVE Patch Regression
To manage
Thanks for all the testing. If this bug is fixed in -proposed, then the
fix is already applied to the Ubuntu kernel and will be released in the
next round of updates on November 12th.
The fix will be in the 4.15.0-37 or newer kernel.
Can others affected by this bug confirm that the proposed
I built the next test kernel, up to the following commit:
34cc0aa2545603560c79aaea3340d8ff3a71bd10
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1783957
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
** Changed in: ipsec-tools (Ubuntu)
Status: Incomplete => Triaged
** Changed in: ipsec-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793028
This was erroneously marked as released. Verification is not yet done.
** Changed in: linux (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1792044
Do you have the full logs of "/var/log/unattended-upgrades" and
"/var/log/apt" handy ?
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796376
Title:
Bug #1739107 fix causes
** Changed in: ipsec-tools (Ubuntu)
Status: Incomplete => Triaged
** Changed in: ipsec-tools (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to ipsec-tools in Ubuntu.
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri
(mhcerri)
** Changed in: kernel-sru-workflow/prepare-package-meta
Tested the first bisected version, on commit
003ae88ae88d48643e71dc69c18d4eda598339d5, problem still present.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796895
Title:
Kernel 4.15.0-36 network
Did you install it from somewhere other than the Ubuntu archive?
What is the output of:
apt-cache policy multipath-tools
FWIW, I can run "ubuntu-bug multipath-tools" just fine on trusty.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to
Did you install it from somewhere other than the Ubuntu archive?
What is the output of:
apt-cache policy multipath-tools
FWIW, I can run "ubuntu-bug multipath-tools" just fine on trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Via code inspection, it looks like this affects cosmic as well:
/**
* Release a mysql connection
*/
static void conn_release(private_mysql_database_t *this, conn_t *conn)
{
this->mutex->lock(this->mutex);
conn->in_use = FALSE;
this->mutex->unlock(this->mutex);
}
The diff that was
Via code inspection, it looks like this affects cosmic as well:
/**
* Release a mysql connection
*/
static void conn_release(private_mysql_database_t *this, conn_t *conn)
{
this->mutex->lock(this->mutex);
conn->in_use = FALSE;
this->mutex->unlock(this->mutex);
}
The diff that was
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1796949
and then change the status of the bug to 'Confirmed'.
If, due to the
The patch seems to work. Dovecot now displays the correct quota.
Also the command doveadm quota get -u user shows correct values.
What I'm unable to verify is the quota-status-service for postfix.
I have it configured in dovecot.conf as follows:
plugin {
quota_grace = 10%%
# 10% is the
I agree with the above analysis.
There is something else I have noticed... the openscap community
consists of several components, one of them implements security-guides
(scap content (checklists) to pass to oscap). xenial did not ship any
security-guide component. However, bionic does. Bionic
I confirmed it, xenial is fine, so just bionic still needs fixing.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1791139
Title:
postfix-mysql package upgrade results in server
I confirmed it, xenial is fine, so just bionic still needs fixing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791139
Title:
postfix-mysql package upgrade results in server configuration error
Public bug reported:
[Impact]
[Fix]
[Test]
[Regression Potential]
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: cavium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This is quite often reproducible. Both on Ubuntu and latest Mint. Seems
like the USB is getting disconnected, but it is still staying on the USB
port.
Installation is done in legacy mode on disk with MBR and the old
partitioning schema.
ProblemType: Bug
DistroRelease:
Retested with 2.02-2ubuntu8.6:
dannf@mdraid:~$ sudo grub-reboot 0
WARNING: Detected GRUB environment block on diskfilter device
0 will remain the default boot entry until manually cleared with:
grub-editenv /boot/grub/grubenv unset next_entry
--
You received this bug notification because
@at-fresh, please try the ISO from http://cdimage.ubuntu.com/ubuntu-
server/bionic/daily-live/current/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783129
Title:
Only "main" component enabled
Is there something still to be done in the "subiquity" task of this bug?
Sorry if I missed it in the comments above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783129
Title:
Only "main"
Do you happen to know which commits are also needed in Bionic?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794110
Title:
MPS (Max Payload Size) is not correctly programmed upon Hot Insertion
Does this workaround also work with the current 4.15.0-36 kernel
available in updates: modprobe rtl8723be ant_sel=1
Are does it only work with the test kernel I posed in comment #41?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is a more detailed explanation of the bug:
Linux kernel defines /proc/vmstat::pgpgin as type unsigned long, so it is
uint32 on 32 bit Linux, uint64 on 64 bit Linux.
VMware Tools reads /proc/vmstat::pgpgin and saves it as uint64 type on both 32
& 64 bit Linux.
When 64 bit kernel
Thanks for testing. I'll submit a Bionic SRU request to include that
commit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795653
Title:
87cdf3148b11 was never backported to 4.15
To manage
We may have to test some prior kernel to have a starting version for a
bisect. Before starting a bisect, would it be possible for you to test
the proposed kernel and post back if it resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use
@~chrisccoulson
What's the Status?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786951
Title:
Update to 60.0
To manage notifications about this bug go to:
Just tested with the proposed build, the problem is fixed with the
proposed kernel 4.15.0-37 on my server.
Does this mean the problem is Ubuntu specific? When will the proposed
version be released? Do you still think it's necessary to test against
the mainline?
--
You received this bug
Public bug reported:
Any printing attempt to any printer is quitted with "filter failed" by
cups. Even for test pages.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18
Uname: Linux 4.15.0-37-generic x86_64
I started a kernel bisect between 4.15.0-34 and 4.15.0-36. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
003ae88ae88d48643e71dc69c18d4eda598339d5
The test kernel can be downloaded from:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug is for tracking the 4.18.0-1002.3 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the
Verification done with netplan.io 0.40.1~18.04.1:
I have verified that when using ip=dhcp / ip6=dhcp on the kernel cmdline
to boot to a remote filesystem; initramfs's scripts correctly write
"critical: true" in /run/netplan/.yaml, and that config is
correctly interpreted by netplan as being
This bug was fixed in the package nova - 2:18.0.1-0ubuntu1~cloud0
---
nova (2:18.0.1-0ubuntu1~cloud0) bionic-rocky; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
nova (2:18.0.1-0ubuntu1) cosmic; urgency=medium
.
* New stable point release for
This bug was fixed in the package nova - 2:18.0.1-0ubuntu1~cloud0
---
nova (2:18.0.1-0ubuntu1~cloud0) bionic-rocky; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
nova (2:18.0.1-0ubuntu1) cosmic; urgency=medium
.
* New stable point release for
** Attachment added: "plymouth-debug-bad.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/+attachment/5199164/+files/plymouth-debug-bad.log
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Attachment added: "plymouth-debug-good.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/+attachment/5199163/+files/plymouth-debug-good.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think the dupe indicated in comment #12 is probably correct.
I didn't manage to make this happen when not using plymouth (removing
"splash" from the kernel commandline). I also installed bionic-release's
version of plymouth, to eliminate whether or not the patches applied
there are bad. The bug
** Attachment added: "journal-bad.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1795637/+attachment/5199162/+files/journal-bad.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795637
My understanding of the issue after an IRC conversation with sforshee is
that the modules were intentionally dropped from the kernel packages,
but the corresponding Provides of virtualbox-guest-modules was _not_
dropped from the kernel packaging. This means that when we install
Help Joseph!
:)
--
Cristian Aravena Romero (caravena)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796720
Title:
High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
To manage
Public bug reported:
Cups tells changing a printer the user would have to authenticate with
username and password, but never asks for username and password in tune
cups denys access to printer configurations and no changes are possible
using the web interface.
ProblemType: Bug
DistroRelease:
@dannf, can you please confirm which version of grub you were using for
the tests?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788298
Title:
grub-reboot changes boot default permanently on Lucid
Verification was done earlier by dannf; this is the same SRU with more
patches included for a different issue.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Could you please download and install
https://launchpad.net/ubuntu/+source/finalrd/3/+build/15227702/+files/finalrd_3_all.deb
(this is a link from
https://launchpad.net/ubuntu/+source/finalrd/3/+build/15227702 )
And check if that helps with reboots? This should perform pivot-root
from rootfs to
This issue was fixed in the openstack/oslo.config 6.6.0 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796163
Title:
py3 failure cfg.py - dictionary changed size during iteration
To
I've done a fresh upgrade to 18.04 and had a "no sound" problem that I
haven't found a solution to. I found this and have been using it to get
the sound connected. Can't find the source again, unfortunately. Thought
it might help to point to the problem. Reinstalling Alsa and Pulse;
starting and
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The error that you are a reporting is a conflict between
packages from the official Ubuntu archive and packages from a PPA. To
resolve this situation please deactivate PPAs using the tool 'ppa-purge'
which is
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The error that you are a reporting is a conflict between
packages from the official Ubuntu archive and packages from a PPA. To
resolve this situation please deactivate PPAs using the tool 'ppa-purge'
which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2-signed (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/1796770
Balint, I wrote in comment #4 that changing the nvidia stack is expected
on upgrades, and that we should special-case this in shim-signed to
suppress the error. Why are you proposing to change unattended-upgrades
instead?
** Changed in: unattended-upgrades (Ubuntu Bionic)
Status: New =>
I'm seeing this on my Lenovo Thinkpad X1 Carbon. The window resizes very
strangely, like it's zoomed in at the top left corner and then a normal
size along the rest of the screen. Definitely happens with nautilus and
default document viewer. Happens when I close the lid and reopen it. I
attached a
This bug was fixed in the package mesa - 18.2.2-0ubuntu1
---
mesa (18.2.2-0ubuntu1) cosmic; urgency=medium
* New upstream bugfix release. (LP: #1796367, #1794923)
-- Timo Aaltonen Mon, 08 Oct 2018 14:23:09 +0300
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
Looks good to me here; I was able to have Windows 10 chainload from
grub2 2.02-2ubuntu8.6 / grub2-signed 1.93.7.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package mesa - 18.2.2-0ubuntu1
---
mesa (18.2.2-0ubuntu1) cosmic; urgency=medium
* New upstream bugfix release. (LP: #1796367, #1794923)
-- Timo Aaltonen Mon, 08 Oct 2018 14:23:09 +0300
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix
https://bugzilla.kernel.org/show_bug.cgi?id=201297
--
Cristian Aravena Romero (caravena)
** Bug watch added: Linux Kernel Bug Tracker #201297
https://bugzilla.kernel.org/show_bug.cgi?id=201297
** Changed in: linux
Remote watch: Linux Kernel Bug Tracker #201355 => Linux Kernel Bug Tracker
Public bug reported:
This bug is for tracking the 4.18.0-1002.3 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
This change was made by a bot.
** Changed in: linux (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/1794074
Title:
xhci_hcd :25:00.0: ERROR unknown
@Cristian
thank you for the heads up...so this the upstream mainline kernel bug?
>From the link you have posted I can see that the latest 4.19-rc doesn't seem
>to affected!
Do you still need me to install the latest kernel and confirm whether
this fixed or not using the following instruction
Seth,
I've installed your kernel in an image that wasn't booting on the
instance type and validated that the test kernel from comment #12 does
fix boot.
$ sudo ethtool -i ens3
driver: bnxt_en
version: 1.9.1
firmware-version: 20.8.172.0/pkg 20.8.29.0
expansion-rom-version:
bus-info: :00:03.0
Hi, I don't know how to find them, I used make, so I suppose the things
you are looking for are inside some makefile in the Linux kernel source.
If you want to solve the issue, please give instructions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
--- Comment From mranw...@us.ibm.com 2018-10-09 13:31 EDT---
We can recreate this without GPFS using a modified version of the tests here:
https://github.com/NVIDIA/gdrcopy
Working on the DD1 removal backport.
--
You received this bug notification because you are a member of Ubuntu
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/356356
** Changed in: samba (Ubuntu)
Assignee: Karl Stenerud (kstenerud) => Andreas Hasenack (ahasenack)
** Changed in: samba (Ubuntu Bionic)
Assignee: Karl Stenerud (kstenerud)
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/samba/+git/samba/+merge/356356
** Changed in: samba (Ubuntu)
Assignee: Karl Stenerud (kstenerud) => Andreas Hasenack (ahasenack)
** Changed in: samba (Ubuntu Bionic)
Assignee: Karl Stenerud (kstenerud)
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => 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/1796542
Title:
Silent data corruption in Linux kernel 4.15
To manage
I just discovered this the hard way. I happened to have speedtest.net
opened in an unfocused Chromium tab on an inactive workspace and spent
quite a bit of time going through a wild goose chase trying to figure
out why my previously reliable DPMS/screen-locking setup suddenly flat-
out refused to
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794074
Title:
xhci_hcd :25:00.0: ERROR unknown event type 15
To manage
I am having the same issues. I had no problems with my sound on my HP
15-ay041wm in 18.04, however now that I have upgraded to 18.10 I have no
sound whatever. Additionally,
sudo alsa force-reload
does nothing for me.
--
You received this bug notification because you are a member of Ubuntu
Verification-done on bionic, using netplan.io 0.40.1~18.04.1:
"""
parameters (mapping)
Customization parameters for special bridging options. Unless
otherwise specified, parameter values for
time intervals should be expressed in milliseconds, but can also
be
Public bug reported:
Test Case
-
1) Install ubuntu-release-upgrader-core on an 18.04 system
2) Edit /etc/update-manager/release-upgrades set Prompt=normal
3) Run 'do-release-upgrade -d'
4) Observe the following
(bionic-amd64)root@impulse:~# do-release-upgrade -d
Checking for a new Ubuntu
Hi Guillaume, would it be possible to provide step-by-step instructions
to reproduce 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/1796376
Title:
Bug #1739107 fix causes
Hi,
Can you please attach the .tar.gz file created by
cloud-init collect-logs
in success and failure cases.
Also, please include the open-vm-tools version in both.
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
when you've provided that input, set the status back to 'New'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796875
Title:
cloud-init and cloud-init-local services boot sequence does not obey
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796580
Title:
Touchscreen breaks after suspend on Acer Aspire Switch 11
To manage
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796574
Title:
Black
201 - 300 of 706 matches
Mail list logo
