putting 'radeon.modeset=0' to kernel options is what disables all hw
acceleration
if it doesn't boot properly without that, you need to test a newer
kernel, so try installing 'linux-generic-hwe-16.04'
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug
Attached is a patch (generated on 16.04) that activates volume groups
when root=UUID=... is on the kernel command-line.
** Patch added: "activate VGs when root=UUID="
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1573982/+attachment/5038702/+files/lvm2_local_top.patch
--
You received
The log in the last comment shows an error from the kernel driver for
the disk, which is either a hardware or kernel bug. It is unrelated to
the issue reported in this launchpad bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
--- Comment (attachment only) From sthou...@in.ibm.com 2018-01-18 02:00
EDT---
** Attachment added: "syslog"
https://bugs.launchpad.net/bugs/1737662/+attachment/5038672/+files/boslcp4g5-25-2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
--- Comment From sthou...@in.ibm.com 2018-01-18 01:58 EDT---
*** Bug 163644 has been marked as a duplicate of this bug. ***
--- Comment From sthou...@in.ibm.com 2018-01-18 01:59 EDT---
Jan 17 15:22:47 main-menu[384]: INFO: Menu item 'bootstrap-base' selected
Jan 17 15:22:48
Comment on post #12 above (as one cannot edit):
Step 4 can be omitted as I don't think the service needs to be
restarted.
I think the hostnamectl command starts this service on demand when
changing the hostname.
--
You received this bug notification because you are a member of Ubuntu
Touch
Thanks for that PrivateNetwork=no hint - works like a charm!
For those that need this, follow the steps below:
1. systemctl edit systemd-hostnamed
Add the 2 lines below then exit the editor (don't forget to save when
prompted):
[Service]
PrivateNetwork=no
2. This will create an
Ubuntu 17.04 has reached end of life. No further bugfixes will be
applied to this version.
** Changed in: apt (Ubuntu Zesty)
Status: Fix Committed => Won't Fix
** Changed in: unattended-upgrades (Ubuntu Zesty)
Status: New => Won't Fix
--
You received this bug notification
Please edit or delete any data that is not important. I just posted the
whole log file from several different commands.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1743939
Public bug reported:
A Canon MF8380CDW printer will not print any thing after upgrading to
17.10. I ran all the steps from this
https://wiki.ubuntu.com/DebuggingPrintingProblems web site.
I have attached a lot of log files. Not sure which one is needed. The
printer did work back under 15.10
myuseraccount@myuseraccount-System-Product-Name:~$ ifconfig
enp3s0: flags=4163 mtu 1500
inet 192.168.1.66 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2600:1700:5270:9c00:180c:2f00:4a3d:95e0 prefixlen 64 scopeid
0x0
inet6
I am not sure if my issue would have the same bug report number or not
but I did a search and this bug is very close to the same issue I am
having. I am using dual boot with grub2, windows 7 and Ubuntu Mate 17. I
mainly use windows and the clock works fine reboot after reboot no
issues, and when I
The attachment "disable_system_service_session_keyrings.patch" seems to
be a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a
--- Comment From danie...@au1.ibm.com 2018-01-17 22:56 EDT---
code submitted upstream: https://github.com/madler/zlib/pull/335
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1743931
Title:
package linux-image-extra-3.13.0-139-generic 3.13.0-139.188
Public bug reported:
Running hooks in /etc/ca-certificates/update.ddone.
Processing triggers for tex-common (4.04) ...
Running mktexlsr. This may take some time... done.
Processing triggers for ureadahead (0.100.0-16) ...
Errors were encountered while processing:
linux-firmware
A systemd build with my patch applied is available here:
https://launchpad.net/~foresto/+archive/ubuntu/ubuntutweaks/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718658
The ecryptfs-manager workaround helps the mount to succeed, but (at
least in my case) the system refuses to unmount it afterward. This is a
problem for those of us who open our ecryptfs volumes only for as long
as they're needed.
--
You received this bug notification because you are a member of
This is a systemd bug, created by this commit:
https://github.com/systemd/systemd/commit/74dd6b5
It looks like poettering has attempted to address it in more recent
versions of systemd (though that doesn't help us in ubuntu 17.10):
https://github.com/systemd/systemd/pull/6832
--
You received
Here's a simple patch to disable the broken systemd feature, and restore
ecryptfs functionality.
** Patch added: "disable_system_service_session_keyrings.patch"
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
*** This bug is a duplicate of bug 1718658 ***
https://bugs.launchpad.net/bugs/1718658
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 1718658
ecryptfs-mount-private fails to initialize ecryptfs keys
--
You
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1718658
Title:
ecryptfs-mount-private fails
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 1743773
When reporting bugs in the future please use apport by using 'ubuntu-
Indeed we need to get this fix released in bionic first.
Possibly confusing is that "LP: #1718824" is only mentioned in the
changelog entry for "1:11.1-1ubuntu3" and not "1:11.1-1ubuntu4". But the
fix is still there in both.
--
You received this bug notification because you are a member of
Second you here. In most cases, a user has his mobile phone on him.
There are also cases when one user has more than one computer and it's
quite a hustle to keep all these devices in sync. One of the Apple's
advantages is everything is in sync. I can see Ubuntu team bringing
Syncthing as a default
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
** Also affects: juniperopenstack
Importance: Undecided
Status: New
** No longer affects: procps (Ubuntu)
** Changed in: juniperopenstack
Assignee: (unassigned) => Prabhu Seshachellam (sprabhu72)
** Changed in: juniperopenstack
Importance: Undecided => High
** Also affects:
Public bug reported:
Syntax for the new option - "no_run" :
server-manager provision --cluster_id five-node ga_8 --no_run
>> Main Entry <<
Namespace(cluster_id='five-node', contrail_image_id=None, interactive=False,
no_confirm=False, no_run=True, package_image_id='ga_8',
This seems to be fixed for some time.
** Changed in: procps (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/686000
Title:
This seems to be fixed for some time.
** Changed in: procps (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1073543
Title:
Now in Bionic the only systemd problem known to me is the
quoting/unquoting turnaround problem mentioned here.
In system-config-printer this problem got worked around upstream by
calling the systemd service with the simpler bus and device IDs and not
with the device path. This works reliably in
** Changed in: gdebi (Ubuntu Artful)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1719746
Title:
gdebi 0.9.5.7+nmu1ubuntu3 broke being
This is fixed in Zesty and later versions.
** Changed in: procps (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1743182
Title:
This bug was fixed in the package gdebi - 0.9.5.7+nmu2
---
gdebi (0.9.5.7+nmu2) unstable; urgency=medium
[ Julien Lavergne ]
* Add a gdebi-gtk-pkexec executable to launch without gksu (LP: #189617).
* debian/control:
- Make gdebi depends on policykit-1 | gksu.
[ Simon
Public bug reported:
boot loader not repairing
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.15
Public bug reported:
My mic not working, so i decide to reainstal alsa and pulseaudio, after
this i dont have sound
Description:Ubuntu 17.10
Release:17.10
alsa-base:
Zainstalowana: 1.0.25+dfsg-0ubuntu5
Kandydująca: 1.0.25+dfsg-0ubuntu5
Tabela wersji:
***
Marked as fix-released.
I tested today with 20180115.1 image from bionic.
wget http://cloud-images.ubuntu.com/bionic/20180115.1/bionic-server-
cloudimg-amd64.img -O bionic-server-cloudimg-amd64.img
url="https://smoser.brickies.net/ubuntu/nocloud/;
qemu-system-x86_64 -enable-kvm -m 768 \
-net
Xenial ships 1.5.6-2 so marking as fix released.
** Changed in: xmltooling (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
My Unity Launcher now works after installing the January 17, 2018 update
from the Software Updater(gnome-software).
I'm a newbie so I wasn't able to use the fixes noted in the other
comments but after the install, I clicked on the side panel and the
Dash, File Manager, Chromium browser and the
To be clear I understand your issue here to be that only your username
(the logged in user) was replaced in the file JournalErrors.txt and that
you'd like to see every username replaced in JournalErrors.txt. Is that
a correct statement?
** Changed in: apport (Ubuntu)
Status: New =>
Uploaded the latest and greatest last week:
ncurses (6.0+20171125-1ubuntu1) bionic; urgency=low
* Merge from Debian unstable (LP: #1637239). Remaining changes:
- Add a simple autopkgtest to the package.
- Build x32 packages.
- Build lib32 packages on s390x.
* Fix typo in libx32
yes, but I'm not uploading systemd until after the build-farm is open.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in getaddrinfo(): calls
Public bug reported:
Any chance that rsync could be updated to 3.1.2 for xenial?
The --backup-dir option in 3.1.1 doesn't work properly - it creates
empty directories even when no files need to be put in them.
Thanks,
-Jeff
** Affects: rsync (Ubuntu)
Importance: Undecided
Status:
@Nate,
there is some suggestions about that in bug 1433761.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1089389
Title:
juju bootstrap fail behind a proxy
@ken-vandine: I'd not name the system user 'lpadmin' but rather 'cups-
pk-helper', which is more precise, especially as its creation/deletion
is handled by the cups-pk-helper maintainer scripts.
Other than that, it looks like a good solution.
That said, only the cups-pk-helper maintainer in
again fixed since 17.04
** Changed in: libxcomposite (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcomposite in Ubuntu.
https://bugs.launchpad.net/bugs/1743582
Title:
this has been fixed since 17.04
** Changed in: libxi (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxi in Ubuntu.
https://bugs.launchpad.net/bugs/1743584
Title:
Cannot
As mentioned in the upstream bug report, this issue has been fixed in
OpenSSH, and the fix is included in the openssh package (1:7.5p1-10) in
Ubuntu 17.10 and later.
** Changed in: openssh (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
Thanks. That works.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1713457
Title:
DNS search domain not removed from resolv.conf on disconnect
Status in
I managed make headphones work by reinstalling pulseaudio and alsa, and
shutting down the computer (for any reason just rebooting didn't work).
Now, everything works except I don't hear the "popping" sound when
changing the volume anymore, and "Test Speakers" from Sound Settings
doesn't produce
I've been Running default flavor of Ubuntu since 12/22 without issue;
still version 16.04.3. I didn't switch to 17 or 18 because I use my
machine for my work, and I do like to run the most stable version. I've
realized that Ubuntu doesn't run simulated 7.1 surround sound well. I
got it working a
On Wed, Jan 17, 2018 at 05:05:07PM -, Robie Basak wrote:
> > The problem is that if you upgrade from Xenial to Zesty or (soon)
> Artful and we haven't SRUed the fixes then users could either become
> unfixed or in some cases (didn't check / don't remember for this bug)
> package versions might
Public bug reported:
Hi,
nm-applet segfaults every time I attempt to click "connection
information",
root@raminfp:~$ gdb nm-applet
GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
Whether you want to go to Tenerife or Tokyo, we'll find low cost flights to
get you there.
We also find the cheapest hotels and car hire deals.
Just dial: +1 (888) 369-2751.
Skyscanner is free! When you find your flights and dial (888) 369-2751, we
redirect your call through directly
> The problem is that if you upgrade from Xenial to Zesty or (soon)
Artful and we haven't SRUed the fixes then users could either become
unfixed or in some cases (didn't check / don't remember for this bug)
package versions might go backwards.
Worse, a user may not receive future security updates
@odyx do you think the patch in comment #53 is suitable for debian? I'd
like to avoid a delta with debian if possible, so i'll defer sponsoring
this until we have some agreement on the fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
closer.
still need artful to be updated. but seems like next build would do that.
$ for f in *-initrd; do echo == $f ==; lsinitramfs $f | grep zfs; done
== artful-20180109-initrd ==
== bionic-20180115.1-initrd ==
lib/modules/4.13.0-25-generic/kernel/zfs
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1742301
** No longer affects: ubuntu-keyboard
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1516564
Title:
Remove 'Ç' key from Portuguese (PT-PT) layout
Status in
** Also affects: ubuntu-keyring (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-keyring (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyring in
This can be fixed by adding `acpi_backlight=vendor` to the `linux`
stanza in `grub.cfg` which is effectively done by adding it to
`GRUB_CMDLINE_LINUX_DEFAULT` in `/etc/default/grub` in Ubuntu 17.10 or
possibly earlier.
I'm leaving this open in order to suggest improvement of automatic
handling
Sorry I didn't think about this before, but I gave the non-ASAN version
of the application a spin with valgrind 3.13 and it doesn't report any
memory errors with it - so it's possible this is either something
valgrind won't catch or a false positive by ASAN.
--
You received this bug notification
I could find the missing keyboard layout by typing this in the terminal:
gsettings set org.gnome.desktop.input-sources show-all-sources true
I think it would be a good idea to add a button to show more layout...
or at least to document how to proceed to get those additional layout
--
You
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~17.10.2
---
mesa (17.2.4-0ubuntu1~17.10.2) artful; urgency=medium
* i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
(LP: #1727401, #1735594)
mesa
The verification of the Stable Release Update for mesa 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
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~16.04.4
---
mesa (17.2.4-0ubuntu1~16.04.4) xenial; urgency=medium
* control: Relax mesa-opencl-icd dependency on libclc. (LP: #1743018)
mesa (17.2.4-0ubuntu1~16.04.3) xenial; urgency=medium
*
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~17.10.2
---
mesa (17.2.4-0ubuntu1~17.10.2) artful; urgency=medium
* i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
(LP: #1727401, #1735594)
mesa
The verification of the Stable Release Update for mesa 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
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~17.10.2
---
mesa (17.2.4-0ubuntu1~17.10.2) artful; urgency=medium
* i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
(LP: #1727401, #1735594)
mesa
The verification of the Stable Release Update for mesa 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
The verification of the Stable Release Update for mesa 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
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~16.04.4
---
mesa (17.2.4-0ubuntu1~16.04.4) xenial; urgency=medium
* control: Relax mesa-opencl-icd dependency on libclc. (LP: #1743018)
mesa (17.2.4-0ubuntu1~16.04.3) xenial; urgency=medium
*
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~17.10.2
---
mesa (17.2.4-0ubuntu1~17.10.2) artful; urgency=medium
* i965-disable-l3-cache-alloc-for-ext-buffers.diff:
- Replaced with five backported commits from upstream
(LP: #1727401, #1735594)
mesa
The verification of the Stable Release Update for mesa 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
This bug was fixed in the package mesa - 17.2.4-0ubuntu1~16.04.4
---
mesa (17.2.4-0ubuntu1~16.04.4) xenial; urgency=medium
* control: Relax mesa-opencl-icd dependency on libclc. (LP: #1743018)
mesa (17.2.4-0ubuntu1~16.04.3) xenial; urgency=medium
*
i've tested artful too, marking verified
** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
artful works fine still
** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Public bug reported:
A few months after upgrading to Ubuntu 16.04, my graphics card stopped
working. I got a black screen after booting. I was able to work around
that problem, and then around the problem of losing my external display
when I closed my laptop lid, so I can now boot normally and
I see pulseaudio in the SRU queue for stable releases. But this bug
doesn't appear to be fixed in Bionic yet, and AFAICT you have tried
multiple times to fix it in Bionic so it isn't clear to me that the
uploads for the stable releases are still current.
Please confirm what you want doing with
Hi,
I'm coming here from bug 1730744.
Is this bug expected to be fixed for 18.04?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1739672
Title:
Regression in
--- Comment From heinz-werner_se...@de.ibm.com 2018-01-17 08:56 EDT---
IBM Bugzilla status -> closed, Fix Released by Canonical.
** Tags removed: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Updated the bug title, as it's not really related to suspend/resume
** Summary changed:
- Installed printer removed after suspend/resume
+ Installed network printer removed automatically when turned off
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
closing this ticket - since Zesty ran out of support on Jan the 13th:
https://www.google.de/url?https://lists.ubuntu.com/archives/ubuntu-announce/2018-January/000227.html
and kernel 4.10 is no longer supported.
Even on Xenial we moved the HWE kernel already from 4.10 to 4.13
** Changed in:
Public bug reported:
I'm running Ubuntu 17.10 and installed today a bunch of updates from the
software updater. After that, there's no sound from headphones anymore,
even if they are detected when plugged in and show up in sound settings
and alsamixer.
The headphones work on other devices, and
I would like to test it here with our public company-network that uses
securelogin.arubanetworks.com.
However, I run 17.10 on my laptop and installing the whole new systemd
235 from Bionic is not so straightforward I experienced. I gave up with
too many unfulfilled dependencies.
So could you
** Description changed:
moving mouse is fine, clicking does nothing. Just upgraded some packages
in 17.10
+
+ in the /var/log/Xorg.0.log:
+
+ config/udev: Adding input device Logitech G Pro Gaming Mouse
(/dev/input/mouse0)
+ no input driver specified , ignoring this device
+
+ I wrote
Public bug reported:
moving mouse is fine, clicking does nothing. Just upgraded some packages
in 17.10
in the /var/log/Xorg.0.log:
config/udev: Adding input device Logitech G Pro Gaming Mouse (/dev/input/mouse0)
no input driver specified , ignoring this device
I wrote that out as I can't copy
PyGObject warns that gi.require_version() wasn't used. That's something
that needs to be fixed by the library user.
** Changed in: pygobject (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
This bug was fixed in the package iproute2 - 4.3.0-1ubuntu3.16.04.3
---
iproute2 (4.3.0-1ubuntu3.16.04.3) xenial; urgency=medium
* Fix ip maddr show (LP: #1732032):
- d/p/1005-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
long
-
This bug was fixed in the package iproute2 - 3.12.0-2ubuntu1.2
---
iproute2 (3.12.0-2ubuntu1.2) trusty; urgency=medium
* Fix ip maddr show (LP: #1732032):
- d/p/1003-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
long
-
This bug was fixed in the package iproute2 - 4.9.0-1ubuntu2.1
---
iproute2 (4.9.0-1ubuntu2.1) artful; urgency=medium
* Fix ip maddr show (LP: #1732032):
- d/p/1003-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
long
-
I'm sorry, but I still don't understand what you're saying or what
you're doing.
It's reported fixed in earlier releases OF LVM2, not of Ubuntu. It has
not been fixed in Ubuntu, because Ubuntu hasn't upgraded the LVM2 it
ships to the newer release.
Furthermore, the project you keep marking
The verification of the Stable Release Update for iproute2 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
This bug was fixed in the package iproute2 - 4.9.0-1ubuntu2.1
---
iproute2 (4.9.0-1ubuntu2.1) artful; urgency=medium
* Fix ip maddr show (LP: #1732032):
- d/p/1003-ip-maddr-fix-igmp-parsing.patch: fix igmp parsing when iface is
long
-
The verification of the Stable Release Update for iproute2 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
This workaround is not bad indeed and saves me, too. But it has
drawbacks that people need to know
1) In newer Ubuntu versions, "dnsmasq" is the default DNS option, so the
config does not have this option to comment out. Instead you have to set
"dns=default" there.
2) With this workaround, some
Take a look at https://wiki.ubuntu.com/DebuggingPrintingProblems
** Package changed: xorg (Ubuntu) => cups (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1742433
tl;dr: your system is in a mess.
Please contact user support if you don't know how to handle it, but it's most
likely due to some odd thing you did rather than a bug.
** Changed in: libxml2 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
how can fix this bug.
On Mon, Jan 15, 2018 at 11:57 PM, dino99 <1718...@bugs.launchpad.net> wrote:
> That version is now dead
> http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-
> has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
>
> ** Changed in: xorg (Ubuntu)
>
1 - 100 of 104 matches
Mail list logo