[Bug 1769016] Re: nsswitch.conf doesn't specify 'resolve' to support systemd-resolved

2021-10-24 Thread Derek V Giroulle
This didn't resolve my problem , of an incorrect /etc/resolv.conf

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

Title:
  nsswitch.conf doesn't specify 'resolve' to support systemd-resolved

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


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

[Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

2021-10-24 Thread Derek V Giroulle
Using Ubuntu 20.04.3 latest update Oct 19th

After the one but last update Oct 10th suddenly I had a problem
resolving DNS. Before the update my /etc/resolv.conf read :

nameserver 127.0.0.53

In my netmanager settings I had/have entered 2 DNS-Server IP adresses of
my ISP : 1xx.2xx.xxx.21 1xx.2xx.xxx.22

the result of command

$ ls -al /etc/resolv.conf

lrwxrwxrwx 1 root root 32 okt 13 14:10 /etc/resolv.conf ->
/run/systemd/resolve/resolv.conf

So I did

$ sudo rm -f /etc/resolv.conf

$ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

Only to find it didn't change anything : the content of new
/etc/resolv.conf after restarting the systemd-resolve service still
reads

nameserver ::1

I managed to complete the updates by repeatedly saving manually an
/etc/resolv.conf file and overwriting the file written by the systemd-
resolve service (workaround). to make certain that people don't doubt my
capacity to read : I DO understand the warning at the top of the file
saying that the file is overwritten regularly.

I manage to maintain a "usable connection" by regularly overwriting the
file /run/systemd/resolve/resolv.conf,  with following content

nameserver 1xx.2xx.xxx.21

nameserver 1xx.2xx.xxx.22

until i restart the systemd-resolve service and the file is overwritten
by resolve and it reverts to

nameserver ::1

I also checked the /run/systemd/resolve/stub-resolv.conf file which has
the following content

nameserver 127.0.0.53
options edns0 trust-ad

My question is :

A- How can I make sure that the resolve service writes the correct file
content in /etc/resolv.conf = I do understand that this is a sym-link

B- Where is the parameter file that systemd-resolve uses to produce
/etc/resolv.conf and /run/systemd/resolve/resolv.conf, because it sure
doesn't read the configuration entered in netmanager settings

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

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

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


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

[Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

2021-10-23 Thread Derek V Giroulle
OS Ubuntu 20.04.3 LTS
After a recent update a working laptop suddently developped the following 
problem : 
- DNS problems for al Internet related apps
- Ping :  termporary failure in Name resolution 
editing manually allows internet access for short term until systemd-resolve 
overwrites the file.
Its no use to replace /etc/resolv.conf with a file as it get overwritten 
regulary. 

The stub-file  /run/systemd/resolve/stub-resolv.conf contains

> nameserver 127.0.0.53
> options edsn0 trust-ad 

In my Network options I have  
DHCP auto 
DNS  manual  19*.2*8.*.21, 19*.2*8.*.22 which are my ISP dedicated DNS servers 
(stars are hiding numbers)

when i overwrite /etc/resolv.conf with 
>  nameserver 19*.2*8.*.21
>  nameserver 19*.2*8.*.22 
my internet connection temporarily works 

The /run/systemd/resolve/resolve.conf contains
> nameserver ::1

I tried overwriting /run/systemd/resolve/stub-resolv.conf with the correct 
nameservers and 
then  applied your solution : 
$ sudo rm -f /etc/resolv.conf
$ sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf   

And restarted the systemd-resolve  service

and the /etc/resolv.conf and /run/systemd/resolve/resolv.conf files
showed again

> nameserver ::1

Your solution doesn't work

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

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

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


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

[Bug 1774632] Re: The symbolic link /etc/resolv.conf points to the wrong file by default

2021-10-23 Thread Derek V Giroulle
Sorry  typo in my previous message ;  it should read

I tried overwriting /run/systemd/resolve/resolv.conf with the correct
nameservers and then applied your solution :

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

Title:
  The symbolic link /etc/resolv.conf points to the wrong file by default

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


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

[Bug 1786008] [NEW] package libpam-systemd:amd64 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

2018-08-08 Thread derek v. Giroulle
Public bug reported:

havent got a clue what happened

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpam-systemd:amd64 229-4ubuntu21.4
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
Uname: Linux 4.4.0-131-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Sun Aug  5 00:24:27 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2016-09-24 (682 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: systemd
Title: package libpam-systemd:amd64 229-4ubuntu21.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libpam-systemd:amd64 229-4ubuntu21.4 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 128

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

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