[Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries

2018-01-06 Thread Kyoku
I set up an Ubuntu 18.04 test server today as an LXD host machine and
ran into this issue.

network:
  version: 2
  renderer: networkd
  ethernets:
ens33:
  dhcp4: no
  dhcp6: no

  bridges:
br0:
  interfaces: [ens33]
  dhcp4: no
  dhcp6: no
  addresses: [192.168.1.101/24]
  gateway4: 192.168.1.1
  nameservers:
addresses: [192.168.1.1, 8.8.8.8, 8.8.4.4]

root@bionic:/home/bionic# systemd-resolve --status
Global
 DNS Servers: 192.168.1.1
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 6 (tun0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 5 (veth0OI7SQ)
  Current Scopes: LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 3 (br0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
 DNSSEC supported: no
 DNS Servers: 192.168.1.1
  8.8.8.8
  8.8.4.4

Link 2 (ens33)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

root@bionic:/home/bionic# ping google.com
ping: google.com: Temporary failure in name resolution

Also the error message is misleading, there's nothing "temporary" about
this failure.  It's permanent.

I can reach IP addresses directly but all DNS lookups are failing,
preventing me from doing upgrades and normal operations.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624320

Title:
  systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
  entries

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1386005] Re: Password not accepted graphical boot for encrypted root system

2017-05-10 Thread Kyoku
Same problem for me when doing a fresh install of 16.04 LTS and 17.04.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386005

Title:
  Password not accepted graphical boot for encrypted root system

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1386005/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1017327] [NEW] Monit 5.3.2 not working on Ubuntu 12.04 x86_64

2012-06-24 Thread Kyoku
Public bug reported:

I have monit working on several servers but when I install it on Ubuntu
12.04 64-bit server I get the following error reported in the log file
and monitoring doesn't work.

[EDT Jun 24 21:26:20] error: State file '/var/lib/monit/state':
Unable to read magic

I installed monit with apt-get install monit and the version is 5.3.2

** Affects: monit (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: ubuntu = monit (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017327

Title:
  Monit 5.3.2 not working on Ubuntu 12.04 x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/monit/+bug/1017327/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 977313] Re: Too many logins - sessions not cleared

2012-04-09 Thread Kyoku
** Visibility changed 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/977313

Title:
  Too many logins - sessions not cleared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/977313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 977313] Re: Too many logins - sessions not cleared

2012-04-09 Thread Kyoku
I don't know which package it relates to.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977313

Title:
  Too many logins - sessions not cleared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/977313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 977313] Re: Too many logins - sessions not cleared

2012-04-09 Thread Kyoku
After some more research it seems this may be libpam-modules package.

** Package changed: ubuntu = pam (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977313

Title:
  Too many logins - sessions not cleared

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/977313/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 30447] Re: Lockup problems with both the free xorg ATI driver and the proprietary fglrx driver, using various ATI cards

2007-02-03 Thread kyoku
On my acer aspire 1692 (with mobility radeon x700) i have the same
freezing problem when i switch to console or logout/switchuser/etc. I
tried to modify gdm.conf and xorg.conf but no way.

So, like Henrik, if i start in recovery mode and lauch gdm from the
console i don't get the problems.

-- 
Lockup problems with both the free xorg ATI driver and the proprietary fglrx 
driver, using various ATI cards
https://launchpad.net/bugs/30447

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs