It seems like this is by design, the workaround is to install xserver-
xorg-legacy.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802544
And
http://sources.debian.net/src/xorg-server/2:1.19.3-1/debian/xserver-xorg-core.NEWS/?hl=15#L15
** Bug watch added: Debian Bug tracker #802544
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
The verification of the Stable Release Update for systemd 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 systemd 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 systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
The verification of the Stable Release Update for systemd 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 systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
This bug was fixed in the package systemd - 232-21ubuntu3
---
systemd (232-21ubuntu3) zesty; urgency=medium
[ Martin Pitt ]
* resolved: Disable DNSSEC by default on stretch and zesty.
Both Debian stretch and Ubuntu zesty are close to releasing, switch to
DNSSEC=off by
The verification of the Stable Release Update for systemd 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 systemd 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
Public bug reported:
I messed up the ssh_config file and I need the stock config files for
ssh server.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
I apologize, but my comment #9 was wrong :
After more precise testing of 'systemd' version 232-21ubuntu2 from
Ubuntu 17.04 Zesty with 'IdleAction=suspend' and 'IdleActionSec=2min' :
'systemd' does NOT unduly suspend my computer when there is an opened
user session (OK).
But 'systemd' does NOT
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libsdl2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
Also affected by this bug on Ububtu 17.04. Using my computer as a wifi hotspot
I couldn't connect from other devices and the log presented a lot of "inux
wpa_supplicant[1385]: handle_probe_req: send failed
" messages.
The solution presented by Jesse (juderichbourne) on post #1 solved the
For what it's worth, I reported a related issue up to the systemd-devel
mailing list, and it looks like in systemd 233 (the next version) things
work much better with DNSSEC. https://lists.freedesktop.org/archives
/systemd-devel/2017-April/038698.html
I rebuilt the 233 out of debian
Unable to check 16.10 ext4 file-system from 16.04 LTS (!).
Here is log:
sudo fsck -fy /dev/sdc1
fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/sdc1 has unsupported feature(s): metadata_csum
e2fsck: Get a newer version of e2fsck!
--
You received this bug
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1685022
Title:
package openssh-server 1:7.2p2-4ubuntu2.1 failed to install/upgrade:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mir (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
You say that the resolvconf SRU from #1649931 fixed it /mostly/ but not
in all cases. If you are able to reproduce this problem, can you
provide journalctl output from the affected environment so we can see
what isn't happening in the right order? Do you have step-by-step
instructions we can
There's a lot in this bug report:
- It appears a bluez snap is in use? that'll complicate the distro-provided
bluez
- It appears a bluez package is in use? that'll complicate the snap-provided
bluez
- It appears an i386 build of bluez is reporting errors, but the system
otherwise reports amd64
** Changed in: systemd (Ubuntu Xenial)
Status: New => Triaged
--
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/1673860
Title:
systemd-resolved unit should run
Even if we don't make this change across the board in SRU, we should
look at changing Ubuntu Core 16 to use only the stub resolver. This
might even turn out to be the root cause of bug #1659195.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
Once we have systemd-resolved's stub DNS resolver on a solid footing
everywhere (LP: #1682499; LP: #1647031), we should stop using
libnss_resolve.so for name resolution and *only* use the DNS stub
resolver via libnss_dns.so.
The reason is that libnss_resolve.so is
Confirmed this fix in yakkety. Behavior with systemd 231-9ubuntu3:
# journalctl -o short-precise -u systemd-resolved -u network-online.target
--no-pager
-- Logs begin at Thu 2017-04-20 23:50:20 UTC, end at Fri 2017-04-21 03:22:45 UTC
Apr 20 23:51:06.897218 ubuntu systemd[1]: Starting Network
Tobias, sorry for being so long in coming back around to this, but I
followed a pointer to this bug from another one and am now trying to
understand the regression that you're describing.
You described this as "bricking" your servers, but per the SRU
regression analysis:
Running [networkd]
Ok, so that's an apparmor or apparmor profile problem.
LXD recently changed to also allow for apparmor profiles to be loaded
inside privileged containers. This seems to align with your timeline
above.
Before that change, your kvm process wasn't itself confined when run
inside a privileged LXD
Verified by way of a slightly modified test case:
- boot a yakkety cloud image
- verify 127.0.0.53 in /etc/resolv.conf
- sudo sed -i -e's/resolve \[[^]]*\] //' /etc/nsswitch.conf
- ping www.freedesktop.org -> FAIL
- install systemd from -proposed
- ping www.freedesktop.org -> SUCCESS
**
Ubuntu Core 16 also uses resolved, so this bug also needs to be fixed in
xenial.
** Changed in: systemd (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Xenial)
Status: New => Triaged
** Changed in: systemd (Ubuntu Xenial)
Milestone: None =>
Its true there are a few issues with apparmor profiles being loaded as
part of a stack when namespacing is involved. However this does not
appear to be one of them.
However the application may be behaving slightly differently resulting
in the profile needed to be extended. Can you please attach
I have exactly the same. can't access my University's vpn on my new
laptop running 10.04. vpn works without any issue on another laptop
running 14.04.
I am wondering if I can rollback vpnc and the necessary packages back to
14.04? need to use vpn to connect to work computers.
using the above
Christopher, you don't need to remove the account. You just need to
restart your computer.
** Summary changed:
- Can't add any online accounts
+ GNOME Online Accounts breaks if you log out (until you reboot)
** Changed in: gnome-online-accounts (Ubuntu)
Importance: Undecided => Critical
**
Hello Carl, thanks for the report; can you please run apport-collect
1684902 to upload some logs that may help diagnose the issue?
Thanks
** Information type changed from Private Security to Public Security
** Package changed: ubuntu => webbrowser-app (Ubuntu)
** Also affects: apparmor
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: software-properties (Ubuntu Trusty)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
On 20 Apr 2017 22:20, "Sean Dague" wrote:
For what it's worth, I reported a related issue up to the systemd-devel
mailing list, and it looks like in systemd 233 (the next version) things
work much better with DNSSEC. https://lists.freedesktop.org/archives
As a note to any backporters, the original fix for this bug should
include the following change as well:
https://code.launchpad.net/~tyhicks/lightdm/guest-dir-
perms/+merge/322906
It is technically optional but definitely recommended.
--
You received this bug notification because you are a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: url-dispatcher (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to url-dispatcher in Ubuntu.
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug:
Integrated browser (app?) that comes pre-loaded with Ubuntu 16.04.2
amd64 (A lightweight web browser tailored for Ubuntu, based on the Oxide
browser engine and using the Ubuntu UI components.), Shown
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1685007
Title:
package bluez:i386 5.37-0ubuntu5 failed to install/upgrade:
I'm having the same problem since when I fresh installed Ubuntu (Budgie) 17.04.
I then reinstalled Ubuntu (Unity) 16.04 LTS and having the same problem, LIVE
versions included.
Interestingly this seems happening on my home router only, at work
(always wifi) it works with no issue.
--
You
This bug was fixed in the package systemd - 231-9ubuntu4
---
systemd (231-9ubuntu4) yakkety; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if
resolved is going to be started, make sure this blocks
network-online.target. LP: #1673860.
*
Hi
Thanks for the update
---
Thanks,
Noam Rathaus
On Apr 21, 2017 04:15, "Tyler Hicks" wrote:
> As a note to any backporters, the original fix for this bug should
> include the following change as well:
>
> https://code.launchpad.net/~tyhicks/lightdm/guest-dir-
>
The verification of the Stable Release Update for systemd 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 systemd 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 systemd 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
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
[Expired for apparmor (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apparmor (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
This bug was fixed in the package systemd - 231-9ubuntu4
---
systemd (231-9ubuntu4) yakkety; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if
resolved is going to be started, make sure this blocks
network-online.target. LP: #1673860.
*
This bug was fixed in the package systemd - 231-9ubuntu4
---
systemd (231-9ubuntu4) yakkety; urgency=medium
* debian/extra/units/systemd-resolved.service.d/resolvconf.conf: if
resolved is going to be started, make sure this blocks
network-online.target. LP: #1673860.
*
The verification of the Stable Release Update for software-properties
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
This bug was fixed in the package software-properties - 0.96.24.7.1
---
software-properties (0.96.24.7.1) yakkety-proposed; urgency=medium
* Add knowledge of OpenStack releases Ocata, Pike and Queens. (LP:
#1670385)
[ Scott Moser & Dimitri John Ledkov ]
* When failing to
This bug was fixed in the package software-properties - 0.96.24.7.1
---
software-properties (0.96.24.7.1) yakkety-proposed; urgency=medium
* Add knowledge of OpenStack releases Ocata, Pike and Queens. (LP:
#1670385)
[ Scott Moser & Dimitri John Ledkov ]
* When failing to
The verification of the Stable Release Update for software-properties
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
** Changed in: gnome-online-accounts
Status: Unknown => Confirmed
** Changed in: gnome-online-accounts
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnome-online-accounts in
I installed Ubuntu 17.04 as a VirtualBox guest and I have the same problem:
syslog output:
systemd-resolved[947]: DNSSEC validation failed for question . in DNSKEY:
missing-key
systemd-resolved[947]: DNSSEC validation failed for question com in DS:
missing-key
systemd-resolved[947]: DNSSEC
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
@duggalsudeep
This is not a regression, we are intentionally disabling DNSSEC by
default; and yes you do need to change /etc/systemd/resolved.conf to
enable DNSSEC - just like in yakkety. It was a mistake that we enabled
it for zesty.
--
You received this bug notification because you are a
This appears to have been fixed in 17.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1645375
Title:
Xorg freeze when starting chromium-browser
Status in xorg package in
*** This bug is a duplicate of bug 1682484 ***
https://bugs.launchpad.net/bugs/1682484
I totally missed this bug report, however, I have opened a new one at
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682484
Good news, is the fix for this issue is now in zesty-proposed. I have
Public bug reported:
ADT upstream tests should run with QEMU on more architectures.
Currently there is:
TEST RUN: Job-related tests
Could not find a suitable QEMU binary
W: can't run QEMU, skipping
On e.g. ppc64el.
This needs testing to make sure upstream tests know how to correctly
setup a
For the record, Faeria looks just fine on my Intel without
libgles1-mesa, which btw should not be used by anything provided by
Steam. Also, Fedora never packaged it so surely there should be more
upset users?
You probably are just seeing a bug with mesa 17.0.2 on your hw, and
updating to oibaf
Easier test is from
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1613751
$ grep -e NetworkManager -e gnome-session-binary /var/log/kern.log
Before it would have loads of messages
$ sudo rm /var/log/kern.log
# upgrade to -proposed package
Now with new package there is only two audit
Same here. Adding 8.8.8.8 in NetworkManager didn't work. Pinging
websites didn't work, but pinging their IP did work. Weirdly, even when
ping didn't work, it printed the IP.
As suggested here:
https://askubuntu.com/questions/905543/ubuntu-17-04-weird-dns-issue
I disabled DNSSEC. Now I can
Public bug reported:
Setup:
- Xenial host
- lxd guests with Trusty, Xenial, ...
- add a LXD profile to allow kvm [3] (inspired by stgraber)
- spawn KVM guests in the LXD guests using the different distro release versions
- guests are based on the uvtool default template which has a serial console
Thanks for your help.
I did what you suggested. Here is the result.
** Attachment added: "dmesg1"
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1675683/+attachment/4865383/+files/dmesg1
** Changed in: pm-utils (Ubuntu)
Status: Incomplete => New
--
You received this bug
Ok, I've succeeded in verifying this by adding an artificial
ExecStartPre=/bin/sleep 10 to both old and new resolvconf.service. Old:
# journalctl -o short-precise --unit resolvconf.service --unit
network-online.target --unit systemd-networkd-wait-online.service --unit
systemd-networkd.service
I also use brand new Lenovo P50 and there is no sound at all (I don't
use docking station).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1559228
Title:
[20ENCTO1WW,
By "fixed version" I meant 13.10.0+14.04.20170403-0ubuntu1 from trusty
proposed.
No regression so far.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ido in Ubuntu.
https://bugs.launchpad.net/bugs/1506427
Title:
Using
It does; in fact, the login screen is pretty much all black. So does
Payday 2 (loading/credits screens are black apart from the text) and
probably other games I haven't checked.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Dell xps 9333, same problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1684213
Title:
Intel Wireless 7260 often crashes
Status in linux package in Ubuntu:
I filed https://bugzilla.gnome.org/show_bug.cgi?id=781295 requesting
that this setting be configurable in GNOME Settings>Network.
** Bug watch added: GNOME Bug Tracker #781295
https://bugzilla.gnome.org/show_bug.cgi?id=781295
--
You received this bug notification because you are a member of
Install yakkety in an Ubuntu KVM with two network interfaces.
Enabled yakkety-proposed, did apt full-upgrade.
Executed do-release-upgrade.
It upgraded to zesty, including zesty-proposed.
At the end of do-release-upgrade accepted to reboot.
After reboot, the system come up fine, with network
A note on severity - I'm seeing this error or the one in bug #1650877
for every single non-gov domain in the .il root, including google.co.il,
all major universities under .ac.il, and every newspaper I can think of
under .co.il. Might also indicate some common thread in the DNS roots
affected.
--
test_bridge_init (__main__.BridgeTest) ... ok
test_bridge_port_priority (__main__.BridgeTest) ... ok
test_bridge_port_priority_set_zero (__main__.BridgeTest)
It should be possible to set the bridge port priority to 0 ... ok
Passed on all architectures.
** Also affects: systemd (Ubuntu Yakkety)
Thanks for the reply, but no joy. Still no sound.
On 04/19/2017 10:18 PM, Luke Yelavich wrote:
> Try moving your pulseaudio config out of the way. Log out of your
> desktop session, switch to a text virtual terminal by pressing control +
> alt + f1, logging in there, and moving the pulseaudio
Depends. Should Faeria show this issue already on the login screen?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1682913
Title:
Missing libgles1 in Ubuntu 17.04 repos
Hello sir.
Could you please tell me the reason of freezing my Ubuntu 16.04 LTS version.
I am having good hardware configration
On 20-Apr-2017 2:51 AM, "Seth Arnold" <1684...@bugs.launchpad.net> wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better. We
@Don Cady:
The source of the problem is the Linux kernel driver for the specific
WiFi adapter or perhaps the firmware of the WiFi adapter.
In most of the drivers, they have implemented the facility to change (by
software) the MAC address.
There are even tools to change the MAC address, like
Public bug reported:
Since the update to Kubuntu 17.04 / plasma 5.9.4 all qt4 based
applications (e.g. KeePassX) render using wrong font instead of my
personal configured font. When I run qtconfig-qt4 (4.8.7), change font
and click 'save', a fresh .config/Trolltech.conf is saved, contains the
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1684481
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
systemd version 232-21ubuntu3: verified OK.
How do I correctly enable DNSSEC as default ?
--
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/1682499
Title:
disable dnssec
linux-image-...-extra was installed
i linux-image-extra-4.4.0-74-generic -Linux kernel extra modules for version
4.4.0 on 64 bit x86 SMP
i linux-image-extra-virtual-lts-vivid - Transitional
package.
i
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1684481
Title:
KVM guest execution start
Not detecting arachsys containers is a high impact bug. My production
servers running on Ubuntu 16.04 can no longer be updated anymore as apt
is stuck on applying the makedev package which of course always fails.
I understand it is cumbersome to add all possible container types to the
script.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1684481
Title:
KVM guest execution start apparmor blocks on
Regression Confirmed: Setting DNSSEC=yes in /etc/systemd/resolved.conf
after 232-21ubuntu3 update
--
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/1682499
Title:
disable
This is still an issue in Ubuntu 16.04 derivative (Linux Mint 18.1)
Using the workaround (imwheel -k -b "0 0 0 0 11 10") helped.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Hopefully I've attached the right files you need.
At the moment, I can't run updates because the same error pops up. At
boot I get a red 'STOP' icon in the top right corner of the menu bar and
if I try to update I get a message telling me the "Package system is
broken". Following the
I have tried the above work around, unfortunately without success.
Dell Inspiron 1012 running 17.04
Kernel 4.8.0-47
I have the same symptoms: WiFi fails to connect repeatedly.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
Since Ubuntu 17.04 uses systemd-resolved for DNS lookups the default
behaviour for search domains changed. By default systemd-resolved does
not use the domain supplied by DHCP as a search domain.
So network-manager should at least have an option to tell systemd-
networkd to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sudo (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
I think this is a consequence of
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1682499 — if so,
please mark (also those others listed in #7) as duplicate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Bug #1650877 and the others linked there (see comment #7) appear to be
duplicates.
--
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/1682499
Title:
disable dnssec
Status in
** Tags added: yakkety
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1637129
Title:
network-manager suddenly reports ethernet is unmanaged
Status in
Possible dup of bug 1676547 ??
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1683836
Title:
WIFI stoped working when updating 16.10 -> 17.04
Status in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I just upgraded from 16.04 (via >16.10) to 17.04 and now I'm seeing this
too. I tried the strace and observed that ps was hanging trying to list
the commandline of the thunderbird process. I had already exited
Thunderbird and there were no indications in the GUI that it was still
running. I had no
Possible dup of 1676547 ??
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1671873
Title:
Upgrade to Yakkety removes eth0 from /etc/network/interfaces
Status in
** Tags removed: verification-needed
** Tags added: verification-done-xenial verification-done-yakkety
--
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/1670385
1 - 100 of 164 matches
Mail list logo