** Tags added: noclick
** Summary changed:
- Regression: left mouse button stops working
+ Left mouse button gets stuck down (in software), usually after suspend/resume
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libinput (Ubuntu)
Importance:
Please also look in /var/crash for any crash files.
If you find some then:
1. Apply the workaround described in bug 994921.
2. Run: ubuntu-bug /var/crash/YOURFILE.crash
3. Tell us here the ID of the newly created bug(s).
--
You received this bug notification because you are a member of Ubu
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 1752431
When reporting bugs in the future please use apport by using 'ubuntu-
b
*** This bug is a duplicate of bug 1743812 ***
https://bugs.launchpad.net/bugs/1743812
user@server2:~$ tail /sys/devices/system/cpu/vulnerabilities/*
==> /sys/devices/system/cpu/vulnerabilities/meltdown <==
Mitigation: PTI
==> /sys/devices/system/cpu/vulnerabilities/spectre_v1 <==
Mitigation:
PPA containing a testfix for Xenial:
https://launchpad.net/~inaddy/+archive/ubuntu/lp1752683
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752683
Title:
race condition on rmm for module ldap (ldap
Public bug reported:
grub2 installation failed on /dev/mdo software RAID0 array
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Linux 4.13.0-21-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: am
I've seen a couple crashes on a ThunderX CRB1S system - though at this
point I don't have reason to believe it is related to KPTI. This system
happened to be installed with LVM + crypted home, and we haven't ran the
cert tests on such a config before. After the remaining tests complete,
I plan to r
I have found the cause of why the race condition happened and was able
to verify that apache2 upstream version (ldap module) also suffers from
the same issue. Instead of re-describing the problem here I'll give you
the URLs of where I'm working upstream:
This bug was already opened in 2015:
https
Public bug reported:
[Impact]
Description:
On a 4 socket server, when #lspci is run, it fails with output:
lspci: Error reading /sys/bus/pci/devices/:9a:00.0/label: Operation not
permitted
Version
pciutils-3.3.1-1.1ubuntu1.1
[Testcase]
Steps to Reproduce:
1. Install Ubuntu-Server-16.04.3
2
** Description changed:
+ READ ME FIRST
+ =
+ This is a cosmetic issue. The warning message is just that— a warning. Though
the message comes up, there is no problem with the install/upgrade happening
like normal. That said, feel free to ignore it. It will get fixed, but it's
nowher
I have updated the packages in my PPA at
https://launchpad.net/~nacc/+archive/ubuntu/nvdimm
Please test and report back.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752378
Title:
Please add User
** Attachment added: "sabre test results - all errors expected"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5066572/+files/submission_2018-03-01T15.11.01.312793.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thank you for showing up. Yes confirmed, this issue was sorted out in
further month updates.
** Changed in: lubuntu-meta (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Fixed in bionic.
https://launchpad.net/ubuntu/+source/berusky/1.7.1-1
** Changed in: berusky (Ubuntu)
Status: Confirmed => 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/1632104
T
This bug was fixed in the package cloud-init - 18.1-5-g40e77380-0ubuntu1
---
cloud-init (18.1-5-g40e77380-0ubuntu1) bionic; urgency=medium
* New upstream snapshot.
- GCE: fix reading of user-data that is not base64 encoded. (LP: #1752711)
- doc: fix chef install from apt pac
This bug was fixed in the package cloud-init - 18.1-5-g40e77380-0ubuntu1
---
cloud-init (18.1-5-g40e77380-0ubuntu1) bionic; urgency=medium
* New upstream snapshot.
- GCE: fix reading of user-data that is not base64 encoded. (LP: #1752711)
- doc: fix chef install from apt pac
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632104
Title:
berusky crashed with SIGSEGV
To manage notifications about this bug go to:
https://bu
Looking at the logs, I also see this:
2018-03-01 12:31:13 provisioningserver.rackdservices.tftp: [info] bootx64.efi
requested by a8:1e:84:f2:96:c5
2018-03-01 12:31:13 provisioningserver.rackdservices.tftp: [info] bootx64.efi
requested by a8:1e:84:f2:96:c5
2018-03-01 12:31:13 provisioningserver.r
So in that pcap when I look at it with vim, I see things like:
¤Û^V^Fj^B^L*Å^@^C^C<9a>ons^@feature_200_final^@feature_nativedisk_cmd^@feature_timeout_style^@^@Possible
commands are:^@Possible devices are:^@Possible files are:^@Possible partitions
are:^@Possible arguments are:^@Possible things are
This report pre-dates #1752053 and was submitted because the initial
NVIDIA driver installation failed. Bug #1752053 reports and already
installed NVIDIA driver being broken by a more recent update. Not
convinced these are duplicates.
--
You received this bug notification because you are a member
I installed the version of powerline from -proposed and no longer
received the crash with the version of the package in the release
pocket.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Same thing just happened to me, running UbuntuStudio 17.10 (installed 2 months
ago).
Please note I never actually tried to edit the menu -- it did it by itself.
Fixed it switching to 'alacarte' for menu editing and restoring system
configuration.
The 'Publishing' menu seems to be gone, however --
The verification of the Stable Release Update for net-snmp has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
I built a test kernel with commit 01c15e93a78c. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752061
Can you test this kernel and see if it resolves this bug?
Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb package
This bug was fixed in the package software-properties - 0.96.24.21
---
software-properties (0.96.24.21) bionic; urgency=medium
[ Julian Andres Klode ]
* add-apt-repository: Do not use absolute path to apt-get
[ Brian Murray ]
* software-properties-gtk: add a dependency on gno
This bug was fixed in the package net-snmp - 5.7.3+dfsg-1ubuntu4.1
---
net-snmp (5.7.3+dfsg-1ubuntu4.1) xenial; urgency=medium
* d/snmpd.init: also match start-stop-daemon against pidfile to avoid
killing extra snmpd processes for example in container (LP: #1720109)
-- Christi
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu19
---
zfs-linux (0.6.5.6-0ubuntu19) xenial; urgency=medium
* Add ZFS 0.7.0 kernel ioctl binary compat shim (LP: #1737761)
Detect ZFS kernel driver version and copy zfs ioctl command to the
newer ZFS 0.7.0 ioctl co
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/1752748
Title:
nouveau module can't be loaded
To manage n
This bug was fixed in the package linux-firmware - 1.172
---
linux-firmware (1.172) bionic; urgency=medium
* Rebase against
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
7344ec9e1df9e27d105ed48d2db99e22370236de
- nfp: update Agilio SmartNIC firmw
The verification of the Stable Release Update for fwupd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a re
This bug was fixed in the package gnome-themes-standard -
3.18.0-2ubuntu2
---
gnome-themes-standard (3.18.0-2ubuntu2) xenial; urgency=medium
* Use HighContrast icons for the HighContrast theme. (LP: #1644662)
-- Dariusz Gadomski Thu, 08 Feb 2018
07:55:43 +0100
** Changed in: gn
This bug was fixed in the package fwupd - 0.8.3-0ubuntu2
---
fwupd (0.8.3-0ubuntu2) xenial; urgency=medium
* Fix systemd unit for what is actually supported in
systemd 229 in xenial (LP: #1746114)
* This bug also fixes issues with USB devices being closed (LP: #1642812)
-- M
The verification of the Stable Release Update for fwupd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a re
This bug was fixed in the package fwupd - 0.8.3-0ubuntu2
---
fwupd (0.8.3-0ubuntu2) xenial; urgency=medium
* Fix systemd unit for what is actually supported in
systemd 229 in xenial (LP: #1746114)
* This bug also fixes issues with USB devices being closed (LP: #1642812)
-- M
This bug was fixed in the package bamf -
0.5.3~bzr0+16.04.20180209-0ubuntu1
---
bamf (0.5.3~bzr0+16.04.20180209-0ubuntu1) xenial; urgency=medium
* bamf-window: read snap and flatpak IDs and use it to guess desktop-
id (LP: #1747802)
-- Marco Trevisan (Treviño) Fri, 09 Feb 20
I didn't have a reliable way of reproducing exactly this scenario, so I
can't definitively say whether or not it's still present (I'm currently
running 17.10). I have experienced similar GUI hangs (but ssh still
responds) in 17.10, but not specifically while watching an embedded
youtube video in Ch
** Changed in: lttng-modules (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/1739591
Title:
lttng-modules-dkms failed to build with 4.14 Azure edg
** Tags removed: verification-done-xenial
** Tags added: verification-failed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747059
Title:
sru cloud-init (17.1.46-g7acc9e86-0ubuntu1) update to
This bug was fixed in the package lttng-modules - 2.8.0-1ubuntu1~16.04.4
---
lttng-modules (2.8.0-1ubuntu1~16.04.4) xenial; urgency=medium
* Fix builds on HWE 4.14 kernel (LP: #1739591)
Apply the following upstream commits:
0030-Fix-update-block-instrumentation-for-4.14-ker
Public bug reported:
Module nouveou can't be loaded. I get the following error message when I
try to load it manually:
# modprobe nouveau
modprobe: ERROR: ../libkmod/libkmod-module.c:832 kmod_module_insert_module()
could not find module by name='off'
modprobe: ERROR: could not insert 'off': Unkn
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
mousepad. This problem was most recently seen with package version
0.4.0-3ubuntu1, the problem page at
https://errors.ubuntu.com/problem/11b88a50048c8a6ecc034b1f22b6ca34341c0827
contains more de
The verification of the Stable Release Update for bamf has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
I have 17.10 and I do not see the bug. For 17.04 I had to recompile gr-
osmosdr (libgnuradio-osmosdr) to avoid crash, for 17.10 I run the
packaged version.
A terminaldump and ldd results below:
mjacek@mjacek-u1710:~$ gqrx
linux; GNU C++ version 6.2.0 20161027; Boost_106200; UHD_003.009.005-0-u
** Also affects: avahi via
https://github.com/lathiat/avahi/issues/169
Importance: Unknown
Status: Unknown
** Also affects: avahi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I see here that a fix was committed to Ubuntu Artful. Does this mean the
fix is specific for ubuntu distributions or there is a new kernel I will
be able to use with my ubuntu 16.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
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/1752742
Title:
Kernel deadlock when using cachefiles.
To
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** 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.
cachefilesd.conf:
dir /cache/fscache
tag mycache
brun 10%
bcull 7%
bstop 3%
frun 10%
fcull 7%
fstop 3%
secctx system_u:system_r:cachefiles_kernel_t:s0
/cache is a separate ext4 partition, currently only cachefiles using it.
the cifs mount was using the following options:
//htpc/rootfs/ on /smb/ht
** Bug watch added: Debian Bug tracker #883899
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883899
** Also affects: makedumpfile (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883899
Importance: Unknown
Status: Unknown
** Changed in: linux (Ubuntu Artful)
It is still an issue on 17.10 but I discovered it seemed to have been
triggered by a specific package in a local LAN repo I am using. Once I
removed the package from the repo it stopped crashing. However, I have
been unable to determine what exactly about the package was causing it
to crash which I
** Also affects: kexec-tools (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Artful)
Importance: Undecided
Status: New
** Changed in: kexec-tools (Ubuntu
Public bug reported:
Was using both a cifs share and a nfs share at the moment of the crash,
both network filesystems get mounted by automount, seems that the bug
happened at the cifs automatic umount. Machine froze and stopped
responding pings from the network, not even sysrq keys worked, needed
Public bug reported:
The "Show and configure virtual connections" option of plasma-nm's
Network Settings does not take effect for the plasmoid until after a
restart of plasmashell.
The ability to up/down and configure "virtual" connections like Bridge,
VLAN, etc. via GUI was removed in a previous
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/340255
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/340256
--
You received this bug notification because you are a member of Ubuntu
Bug
dino99, please don't recommend that users use Ubuntu 18.04 now. It's not
even officially in beta yet.
Also, there's no reason to recommend that users use the minimal install
option for this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
- On a clean install of Lubuntu Desktop 18.04, the default x-terminal-
- emulator is set to txiterm, which comes from the package xiterm+thai.
- With this terminal it's not possible to use characters with accents like
- í or Á.
+ STEPS TO REPRODUCE
+ ==
+ 1
*** This bug is a duplicate of bug 1752512 ***
https://bugs.launchpad.net/bugs/1752512
@Brian Launchpad did not list #1752512 as possible duplicate for me, so
I didn't notice. marked as a duplicate now
** This bug has been marked a duplicate of bug 1752512
Plugin download failes with check
Public bug reported:
I believe this issue is pretty well known, ex. here on optimus machine
sudo cat /sys/module/nvidia_drm/parameters/modeset
[sudo] password for doug:
Y
$ xrandr --prop | grep PRIME
PRIME Synchronization: 0 # this is the one needed to be 1
PRIME Synchronization:
** Tags removed: yakkety
** Tags added: artful bionic
** Tags removed: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522675
Title:
Warning messages about unsandboxed downloads
To manage not
The issue is still present in 17.10.
The "Network settings..." right-click-menu item is not present and,
thus, "virtual" connections like VLAN, Bridge, etc. cannot be seen,
activated, or configured via GUI.
On a separate (but related) note: checking the "Show and configure virtual
connections"
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/340252
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752711
Title:
cloud-init no longer proces
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu-dev-tools/+git/ubuntu-dev-tools/+merge/322863
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700846
Title:
src:texinfo fails
My desktop computer won't display the X desktop on my monitor after
installing the new driver with the Bionic-proposed packages. I get a
blank screen except for a tty cursor in the top left corner of the
screen. I can view the X desktop remotely using Teamviewer though,
which is really wierd. Ty
** Changed in: snapd (Ubuntu Bionic)
Status: In Progress => 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/1729867
Title:
confined snaps don't work on live images due to apparmor
I figured out why the simple test didn't work - when I first installed
Ubuntu 18.04, gnome-terminal wouldn't accept any keyboard input, I
assumed it was just a pre-alpha bug and installed terminator.
Installing terminator switched itself to the default including launching
with ctrl-alt-t , and term
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/340252
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751051
Title:
UnicodeEncodeError when cre
*** This bug is a duplicate of bug 1752512 ***
https://bugs.launchpad.net/bugs/1752512
You did read other recent bug reports, didn't you? How does yours differ
from #1752512, #1749690 and #1749573 or add new information?
Cheers,
Brian.
--
You received this bug notification because you are
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Triaged
** Summary changed:
- Default terminal emulator is set to txiterm, which causes problems with
certain characters
+ xiterm+thai is installed and set to x-terminal-emulator
--
You received this bug notification because you are a
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
Hi Achmad,
thank you for reporting this and for your help in making Ubuntu better.
Relevant lines are:
Mar 20 12:36:47 hostname mysqld_safe[22291]: [108B blob data]
Mar 20 12:36:47 hostname mysqld_safe[22291]: Fatal error in defaults handling.
Program aborted
Mar 20 12:36:47 hostname mysqld_safe[
Marking as Invalid because the release is EOL is not correct. Marking as
Incomplete. Also, 18.04 is (at the time of writing) still in development, and
you should expect some breakage.
https://wiki.ubuntu.com/Bugs/Responses#Release_has_reached_End_of_Life_.28EOL.29
Reporter, is this still present
ok i'll recreate the debdiffs and reupload.
** Tags removed: verification-needed verification-needed-artful
verification-needed-trusty verification-needed-xenial
** Changed in: isc-dhcp (Ubuntu Artful)
Status: Fix Committed => In Progress
** Changed in: isc-dhcp (Ubuntu Xenial)
Sta
** Changed in: cloud-init
Status: Confirmed => 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/1752711
Title:
cloud-init no longer processes user data on GCE in artful
To manage
** Changed in: mate-menus (Ubuntu)
Status: New => In Progress
** Changed in: mate-menus (Ubuntu)
Importance: Undecided => Medium
** Changed in: mate-menus (Ubuntu)
Assignee: (unassigned) => Martin Wimpress (flexiondotorg)
--
You received this bug notification because you are a me
** Changed in: Ubuntu Bionic
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1751459
Title:
[needs-packaging] kio-gdrive
To manage notifications ab
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1752722
Title:
sy
*sigh* my test case in
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1751667/comments/8
was flawed. With the PR, on a livecd the apparmor unit correctly doesn't
load the policy. snapd starts at some point, notices it is on an
overlay, adds the overlay snippet to /var/lib/snapd/apparmor/sn
101 - 200 of 1027 matches
Mail list logo
