[Touch-packages] [Bug 2059417] Re: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

[Markus Klyver]

CIA is not happy this got discovered.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xz-utils in Ubuntu.
https://bugs.launchpad.net/bugs/2059417

Title:
  Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

Status in xz-utils package in Ubuntu:
  Won't Fix

Bug description:
  NOTE: THIS IS AN ATTEMPT AT INCLUDING A BACKDOOR. THIS IS LEFT FOR
  HISTORICAL PURPOSES ONLY AND MUST NOT BE DONE.

  
  Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

  Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1
  was recently released and uploaded to Debian as a bugfix only release.
  Notably, this fixes a bug that causes Valgrind to issue a warning on
  any application dynamically linked with liblzma. This includes a lot of
  important applications. This could break build scripts and test
  pipelines that expect specific output from Valgrind in order to pass.

  Additionally, this fixes a small typo for the man pages translations
  for Brazilian Portuguese, German, French, Korean, Romanian, and
  Ukrainian, and removes the need for patches applied for version
  5.6.0-0.2.

  The other bugfixes in this release have no impact on Ubuntu. They
  involve building with CMake or when building on a system without
  Landlock system calls defined (these are defined in Ubuntu).

  Changelog entries since current noble version 5.6.0-0.2:

  xz-utils (5.6.1-1) unstable; urgency=medium

    * Non-maintainer upload.
    * Import 5.6.1 (Closes: #1067708).
    * Takeover maintenance of the package.

   -- Sebastian Andrzej Siewior   Wed, 27 Mar
  2024 22:53:21 +0100

  Excerpt from the NEWS entry from upstream:

  5.6.1 (2024-03-09)

  * liblzma: Fixed two bugs relating to GNU indirect function (IFUNC)
    with GCC. The more serious bug caused a program linked with
    liblzma to crash on start up if the flag -fprofile-generate was
    used to build liblzma. The second bug caused liblzma to falsely
    report an invalid write to Valgrind when loading liblzma.

  * xz: Changed the messages for thread reduction due to memory
    constraints to only appear under the highest verbosity level.

  * Build:

  - Fixed a build issue when the header file 
    was present on the system but the Landlock system calls were
    not defined in .

  - The CMake build now warns and disables NLS if both gettext
    tools and pre-created .gmo files are missing. Previously,
    this caused the CMake build to fail.

  * Minor improvements to man pages.

  * Minor improvements to tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/2059417/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.

[Markus S]

@Christian, thanks for exercising this issue a bit more and confirming
that the mouse becomes invisible when pressing Ctrl+Alt+G in the
GTK_BACKEND=x11 setting. Can you also confirm that trying to switch
windows via Alt+Tab does not work when GTK_BACKEND=x11 is active?

Also, in fact I tried this on a computer with a single screen attached.

My current understanding is that this issue is not fully resolved
because with GTK_BACKEND=x11 input grabbing does not work correctly and
without this setting fullscreen does not work reliably if host and guest
resolution are equal.

From my personal perspective, it would be fine if it works in either of
the two settings, i.e., GTK_BACKEND=x11 enabled or not. I appreciate
your efforts regarding this hard to debug issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2000739

Title:
  Window actions (like maximize) no more work in wayland for QEMU using
  GTK backend once the guest UI is intialized.

Status in gtk+3.0 package in Ubuntu:
  New
Status in qemu package in Ubuntu:
  Confirmed

Bug description:
  Window actions (like maximize) no more work in wayland for QEMU using
  GTK backend once the guest UI is intialized.

  This can be seen by running an installed or even a trial Ubuntu from
  an ISO like:

  $ qemu-system-x86_64 \
    -boot d \
    -cdrom ubuntu-22.04.1-desktop-amd64.iso \
    -m 4096M \
    -machine type=q35,accel=kvm \
    -cpu host \
    -smp 2 \
    -device qxl-vga

  The GTK UI of qemu has a feature called "fullscreen" which disables
  the screen decorations and sets the window to maximize. The
  decorations go away, but maximize doesn't work.

  
  The following details were found so far:
  - running with GDK_BACKEND=x11 works
  - using sdl instead of gtk backend works
  - using the old qemu of Focal, or the newest from upstream git in jammy all 
fails (no qemu change AFAICS)
  - host UI widgets (the square at the window top) do not work either
  - hotkeys (super-up) do not work either

  It seems that once the guest has enabled the desktop something changes
  and the maximize/minimize/... actions are no more processed. Not sure
  were to debug next in regard to the gnome/wayland UI handling of this
  - any idea?

  P.S. We can reproduce this in git builds of qemu, so we can debug of
  modify the code as needed. The code for this is mostly in [1]

  [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c

  --- original report ---

  Running QEMU version 4.2.1 on Ubuntu 20.04 via

  qemu-system-x86_64 \
    -boot d \
    -cdrom ubuntu-22.04.1-desktop-amd64.iso \
    -m 4096M \
    -machine type=q35,accel=kvm \
    -cpu host \
    -smp 2 \
    -device qxl-vga

  and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and
  adjusting the display resolution to match the native resolution, works
  as expected, i.e., the VM screen is correctly displayed in fullscreen.

  However, after running the same command for QEMU version 6.2.0 on
  Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution
  adjustment, yields a fullscreen view where the space occupied by the
  GNOME top bar (top panel with date in center) of the host is not used.
  The top bar itself is not visible but instead the purple background is
  shown where the top bar resides.

  The problem also occurs when replacing '-device qxl-vga' by '-device
  VGA,vgamem_mb=64'. The problem however does not occur when using
  '-device virtio-vga'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2000739/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008053] [NEW] Screen corruption and laggy mouse cursor in lower quarter of screen

[Markus Konrad]

Public bug reported:

After a software upgrade yesterday, I see screen glitches and a
"stumbling" mouse cursor whenever I move the mouse in the lower quarter
of my laptop screen. When I have connected an external display, the
external display doesn't show any issues, but the problem remains on the
laptop screen.

(This is my first bug report and I used the "ubuntu-bug" utility to
collect the necessary data. I hope it is attached here somewhere.)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 22 08:58:07 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
 virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed
 virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0b04]
InstallationDate: Installed on 2022-11-30 (83 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: Dell Inc. Latitude 5430
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/05/2022
dmi.bios.release: 1.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.6.1
dmi.board.name: 04X33N
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd09/05/2022:br1.6:svnDellInc.:pnLatitude5430:pvr:rvnDellInc.:rn04X33N:rvrA00:cvnDellInc.:ct10:cvr:sku0B04:
dmi.product.family: Latitude
dmi.product.name: Latitude 5430
dmi.product.sku: 0B04
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug corruption jammy ubuntu wayland-session

-- 
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/2008053

Title:
  Screen corruption and laggy mouse cursor in lower quarter of screen

Status in xorg package in Ubuntu:
  New

Bug description:
  After a software upgrade yesterday, I see screen glitches and a
  "stumbling" mouse cursor whenever I move the mouse in the lower
  quarter of my laptop screen. When I have connected an external
  display, the external display doesn't show any issues, but the problem
  remains on the laptop screen.

  (This is my first bug report and I used the "ubuntu-bug" utility to
  collect the necessary data. I hope it is attached here somewhere.)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 22 08:58:07 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-60-generic, x86_64: installed
   virtualbox/6.1.38, 5.19.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0b04]
  InstallationDate: Installed on 2022-11-30 (83 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: Dell Inc. Latitude 5430
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-32-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2022
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  

[Touch-packages] [Bug 2007600] [NEW] Not possible to dismiss/cancel authentication dialog

[Markus Strobl]

Public bug reported:

In system settings -> Online accounts I started adding google. During
the authentication it said I needed to approve the sign on with the
youtube app on my mobile device. I don't have the youtube app installed
on my phone and don't want it so I decided to cancel the sign on.

Problem is it is not possible to cancel the sign on to google. There is
no cancel button and if I close the window a new, identical, window
opens up. I also tried to kill it with ctrl-alt-esc and it just opens up
a new window right away.

What I expect: Closing the window should cancel the sign-on attempt and
a new window should not open.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: signon-ui-x11 0.17+18.04.20171027+really20160406-0ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
Uname: Linux 5.19.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Thu Feb 16 11:48:08 2023
ExecutablePath: /usr/bin/signon-ui
SourcePackage: signon-ui
UpgradeStatus: Upgraded to kinetic on 2022-10-23 (116 days ago)

** Affects: signon-ui (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-ui in Ubuntu.
https://bugs.launchpad.net/bugs/2007600

Title:
  Not possible to dismiss/cancel authentication dialog

Status in signon-ui package in Ubuntu:
  New

Bug description:
  In system settings -> Online accounts I started adding google. During
  the authentication it said I needed to approve the sign on with the
  youtube app on my mobile device. I don't have the youtube app
  installed on my phone and don't want it so I decided to cancel the
  sign on.

  Problem is it is not possible to cancel the sign on to google. There
  is no cancel button and if I close the window a new, identical, window
  opens up. I also tried to kill it with ctrl-alt-esc and it just opens
  up a new window right away.

  What I expect: Closing the window should cancel the sign-on attempt
  and a new window should not open.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: signon-ui-x11 0.17+18.04.20171027+really20160406-0ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Feb 16 11:48:08 2023
  ExecutablePath: /usr/bin/signon-ui
  SourcePackage: signon-ui
  UpgradeStatus: Upgraded to kinetic on 2022-10-23 (116 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/2007600/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2000739] Re: Window actions (like maximize) no more work in wayland for QEMU using GTK backend once the guest UI is intialized.

[Markus S]

Thank you very much Christian for the confirmation (upstream as well)
and your further analysis of the issue. Your comment #12 (qemu-
system-x86_64 -display gtk) is also reflected in my observation in
comment #7.

I also appreciate your GDK_BACKEND=x11 ... workaround.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2000739

Title:
  Window actions (like maximize) no more work in wayland for QEMU using
  GTK backend once the guest UI is intialized.

Status in qemu package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  New

Bug description:
  Window actions (like maximize) no more work in wayland for QEMU using
  GTK backend once the guest UI is intialized.

  This can be seen by running an installed or even a trial Ubuntu from
  an ISO like:

  $ qemu-system-x86_64 \
    -boot d \
    -cdrom ubuntu-22.04.1-desktop-amd64.iso \
    -m 4096M \
    -machine type=q35,accel=kvm \
    -cpu host \
    -smp 2 \
    -device qxl-vga

  The GTK UI of qemu has a feature called "fullscreen" which disables
  the screen decorations and sets the window to maximize. The
  decorations go away, but maximize doesn't work.

  
  The following details were found so far:
  - running with GDK_BACKEND=x11 works
  - using sdl instead of gtk backend works
  - using the old qemu of Focal, or the newest from upstream git in jammy all 
fails (no qemu change AFAICS)
  - host UI widgets (the square at the window top) do not work either
  - hotkeys (super-up) do not work either

  It seems that once the guest has enabled the desktop something changes
  and the maximize/minimize/... actions are no more processed. Not sure
  were to debug next in regard to the gnome/wayland UI handling of this
  - any idea?

  P.S. We can reproduce this in git builds of qemu, so we can debug of
  modify the code as needed. The code for this is mostly in [1]

  [1]: https://gitlab.com/qemu-project/qemu/-/blob/master/ui/gtk.c

  --- original report ---

  Running QEMU version 4.2.1 on Ubuntu 20.04 via

  qemu-system-x86_64 \
    -boot d \
    -cdrom ubuntu-22.04.1-desktop-amd64.iso \
    -m 4096M \
    -machine type=q35,accel=kvm \
    -cpu host \
    -smp 2 \
    -device qxl-vga

  and pressing ctrl+alt+f after booting the Ubuntu 22.04 live ISO and
  adjusting the display resolution to match the native resolution, works
  as expected, i.e., the VM screen is correctly displayed in fullscreen.

  However, after running the same command for QEMU version 6.2.0 on
  Ubuntu 22.04 and pressing ctrl+alt+f after making the resolution
  adjustment, yields a fullscreen view where the space occupied by the
  GNOME top bar (top panel with date in center) of the host is not used.
  The top bar itself is not visible but instead the purple background is
  shown where the top bar resides.

  The problem also occurs when replacing '-device qxl-vga' by '-device
  VGA,vgamem_mb=64'. The problem however does not occur when using
  '-device virtio-vga'.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1991919] [NEW] libgoogle-glog-dev has unmet dependencies due to libunwind

[Markus Pielmeier]

Public bug reported:

# Error Description

Installing `libgoogle-glog-dev` results in an error:

```
$ sudo apt install libgoogle-glog-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libunwind-14-dev : Breaks: libunwind-dev but 1.3.2-2build2 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.
```

# Comments

I have the packages libc++-14-dev and libc++-dev installed.
The package libgoogle-glog-dev dependes on "libunwind-dev | libunwind7-dev". 
But Package 'libunwind7-dev' has no installation candidate. Package 
'libunwind-dev' is incompatible with libc++-14-dev and libc++-dev:

```
$ sudo apt install libunwind-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  libc++-14-dev libc++-dev libunwind-14-dev
The following NEW packages will be installed:
  libunwind-dev
0 upgraded, 1 newly installed, 3 to remove and 14 not upgraded.
Need to get 0 B/1.882 kB of archives.
After this operation, 3.176 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
```

# Additional information:

$ lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04

$ apt-cache policy libgoogle-glog-dev
libgoogle-glog-dev:
  Installed: (none)
  Candidate: 0.5.0+really0.4.0-2
  Version table:
 0.5.0+really0.4.0-2 500
500 http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

$ apt show libgoogle-glog-dev
Package: libgoogle-glog-dev
Version: 0.5.0+really0.4.0-2
Priority: optional
Section: universe/libdevel
Source: google-glog
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Laszlo Boszormenyi (GCS) 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 388 kB
Depends: libgoogle-glog0v5 (= 0.5.0+really0.4.0-2), libgflags-dev, 
libunwind-dev | libunwind7-dev
Homepage: https://github.com/google/glog
Download-Size: 91,9 kB
APT-Sources: http://de.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
Description: library that implements application-level logging.
 This library provides logging APIs based on C++-style streams and
 various helper macros.
 .
 This package contains static and debug libraries and header files for
 developing applications.

** Affects: google-glog (Ubuntu)
 Importance: Undecided
 Status: New

** Summary changed:

- libgoogle-glog-dev has umet dependencies due to libunwind
+ libgoogle-glog-dev has unmet dependencies due to libunwind

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to google-glog in Ubuntu.
https://bugs.launchpad.net/bugs/1991919

Title:
  libgoogle-glog-dev has unmet dependencies due to libunwind

Status in google-glog package in Ubuntu:
  New

Bug description:
  # Error Description

  Installing `libgoogle-glog-dev` results in an error:

  ```
  $ sudo apt install libgoogle-glog-dev
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libunwind-14-dev : Breaks: libunwind-dev but 1.3.2-2build2 is to be installed
  E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.
  ```

  # Comments

  I have the packages libc++-14-dev and libc++-dev installed.
  The package libgoogle-glog-dev dependes on "libunwind-dev | libunwind7-dev". 
But Package 'libunwind7-dev' has no installation candidate. Package 
'libunwind-dev' is incompatible with libc++-14-dev and libc++-dev:

  ```
  $ sudo apt install libunwind-dev
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages will be REMOVED:
libc++-14-dev libc++-dev libunwind-14-dev
  The following NEW packages will be installed:
libunwind-dev
  0 upgraded, 1 newly installed, 3 to remove and 14 not upgraded.
  Need to get 0 B/1.882 kB of archives.
  After this operation, 3.176 kB disk space will be freed.
  Do you want to continue? [Y/n] n
  Abort.
  ```

  # Additional information:

  $ lsb_release -rd
  Description:Ubuntu 22.04.1 LTS
  Release:22.04

  $ apt-cache policy libgoogle-glog-dev
  libgoogle-glog-dev:
Installed: (none)

[Touch-packages] [Bug 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it

[Markus]

Confirming this problem.
The work-around does not work for me.

-- 
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/1933880

Title:
  systemd-logind crash when suspend with nvidia-suspend.service masked,
  bringing session down with it

Status in nvidia-graphics-drivers-465 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a 
restart, run `sudo apt autoremove nvidia-driver-465`.
  2. Leaving the terminal open, suspend the machine.

  Expected behavior: the machine suspend successfully and can be woken up 
successfully.
  Actual behavior: the machine doesn't suspend. It either:
  - hang with no respond other than SysRq+REISUB (or maybe network, but I 
didn't test), or
  - return you back to the login screen. Upon logging in, you'll notice that 
the terminal you opened is gone.

  Upon further inspection (on a session that doesn't hang), it's been
  found that X server died with:

  Fatal server error:
  [66.422] (EE) systemd-logind disappeared (stopped/restarted?)

  And checking journal for systemd-logind log, it said:

  Error during inhibitor-delayed operation (already returned success to
  client): Unit nvidia-suspend.service is masked.

  before the new process takes it place.

  The system is Ubuntu 20.04, X.org session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jun 29 03:34:00 2021
  InstallationDate: Installed on 2021-03-15 (105 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 82B5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=th_TH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2021
  dmi.bios.release: 1.31
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EUCN31WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55756 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Legion 5 15ARH05
  dmi.ec.firmware.release: 1.31
  dmi.modalias: 
dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
  dmi.product.family: Legion 5 15ARH05
  dmi.product.name: 82B5
  dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
  dmi.product.version: Lenovo Legion 5 15ARH05
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933880/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1945888] [NEW] DHCPv6 too strict when the response is missing IAID for some sections

[Ole Markus With]

Public bug reported:

Systemd incorrectly ignores whole messages when IAID is missing for some 
sections.
This has been reported upstream [1] and fixed [2].

$ lsb_release -rd
Description:Ubuntu 21.04
Release:21.04

 $ apt-cache policy systemd
systemd:
  Installed: 247.3-3ubuntu3.6
  Candidate: 247.3-3ubuntu3.6
  Version table:
 *** 247.3-3ubuntu3.6 500
500 http://no.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 247.3-3ubuntu3.4 500
500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
 247.3-3ubuntu3 500
500 http://no.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages


What is expected to happen is that systemd will ignore only the relevant part 
of the message, not the entire message. 

What is happening is that the entire message is ignored, leading to DHCP
leases not being renewed. This is fairly easy to replicate e.g in AWS by
enabling both an IPv6 prefix and an IPv6 single address to the same
interface.

[1] https://github.com/systemd/systemd/issues/20803
[2] https://github.com/systemd/systemd/pull/20807

** 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/1945888

Title:
  DHCPv6 too strict when the response is missing IAID for some sections

Status in systemd package in Ubuntu:
  New

Bug description:
  Systemd incorrectly ignores whole messages when IAID is missing for some 
sections.
  This has been reported upstream [1] and fixed [2].

  $ lsb_release -rd
  Description:Ubuntu 21.04
  Release:21.04

   $ apt-cache policy systemd
  systemd:
Installed: 247.3-3ubuntu3.6
Candidate: 247.3-3ubuntu3.6
Version table:
   *** 247.3-3ubuntu3.6 500
  500 http://no.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   247.3-3ubuntu3.4 500
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
   247.3-3ubuntu3 500
  500 http://no.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  
  What is expected to happen is that systemd will ignore only the relevant part 
of the message, not the entire message. 

  What is happening is that the entire message is ignored, leading to
  DHCP leases not being renewed. This is fairly easy to replicate e.g in
  AWS by enabling both an IPv6 prefix and an IPv6 single address to the
  same interface.

  [1] https://github.com/systemd/systemd/issues/20803
  [2] https://github.com/systemd/systemd/pull/20807

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1945887] [NEW] org.bluez.obex.service contains unresolved '@libexecdir@'

[Markus Ueberall]

Public bug reported:

After upgrading a machine from Ubuntu Bionic to Ubuntu Focal yesterday,
the following error message showed up in the syslog:

Oct  2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760]
Activated service 'org.bluez.obex' failed: Failed to execute program
org.bluez.obex: No such file or directory

Upon inspection, this was due to the fact that the service definition
contained the line 'Exec=@libexecdir@/obexd' which could not be resolved
(this placeholder is supposedly to be replaced at build time).

Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this
(together with 'systemctl --user daemon-reload; systemctl --user restart
obex').

Note that this problem should be part of *all* current versions of the
bluez[-obexd] package, regardless of the used architecture (including
Focal, Impish):

% wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb
[...]
Länge: 217906 (213K) [application/x-debian-package]
Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert.
[...]
2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« 
gespeichert [217906/217906]

% dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish
% grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service
Exec=@libexecdir@/obexd
% wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb
[...]
Länge: 160832 (157K) [application/x-debian-package]
Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert.
[...]
2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« 
gespeichert [160832/160832]

% dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal
% grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service
Exec=@libexecdir@/obexd
%


# lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:20.04
# apt-cache policy bluez-obexd
bluez-obexd:
[...]
 5.53-0ubuntu3.3 500
500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
[...]

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


** Tags: focal impish

-- 
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/1945887

Title:
  org.bluez.obex.service contains unresolved '@libexecdir@'

Status in bluez package in Ubuntu:
  New

Bug description:
  After upgrading a machine from Ubuntu Bionic to Ubuntu Focal
  yesterday, the following error message showed up in the syslog:

  Oct  2 23:14:52 desktop01 dbus-daemon[1764]: [session uid=0 pid=1760]
  Activated service 'org.bluez.obex' failed: Failed to execute program
  org.bluez.obex: No such file or directory

  Upon inspection, this was due to the fact that the service definition
  contained the line 'Exec=@libexecdir@/obexd' which could not be
  resolved (this placeholder is supposedly to be replaced at build
  time).

  Replacing '@libexecdir@' with '/usr/lib/bluetooth' resolved this
  (together with 'systemctl --user daemon-reload; systemctl --user
  restart obex').

  Note that this problem should be part of *all* current versions of the
  bluez[-obexd] package, regardless of the used architecture (including
  Focal, Impish):

  % wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.60-0ubuntu2_amd64.deb
  [...]
  Länge: 217906 (213K) [application/x-debian-package]
  Wird in »bluez-obexd_5.60-0ubuntu2_amd64.deb« gespeichert.
  [...]
  2021-10-03 07:40:36 (1,53 MB/s) - »bluez-obexd_5.60-0ubuntu2_amd64.deb« 
gespeichert [217906/217906]

  % dpkg-deb -R bluez-obexd_5.60-0ubuntu2_amd64.deb impish
  % grep '@' impish/usr/share/dbus-1/services/org.bluez.obex.service
  Exec=@libexecdir@/obexd
  % wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez-obexd_5.53-0ubuntu3.3_arm64.deb
  [...]
  Länge: 160832 (157K) [application/x-debian-package]
  Wird in »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« gespeichert.
  [...]
  2021-10-03 07:43:13 (2,06 MB/s) - »bluez-obexd_5.53-0ubuntu3.3_arm64.deb« 
gespeichert [160832/160832]

  % dpkg-deb -R bluez-obexd_5.53-0ubuntu3.3_arm64.deb focal
  % grep '@' focal/usr/share/dbus-1/services/org.bluez.obex.service
  Exec=@libexecdir@/obexd
  %

  
  # lsb_release -rd
  Description:Ubuntu 20.04.3 LTS
  Release:20.04
  # apt-cache policy bluez-obexd
  bluez-obexd:
  [...]
   5.53-0ubuntu3.3 500
  500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  [...]

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1929833] Re: bluez: meshctl missing

[Markus Becker]

I do see an update to 5.88 with
https://git.launchpad.net/ubuntu/+source/bluez/commit/?id=f0877af285d9360c02762de34a79ed11c72a84ca,
but I do not see the binary meshctl being added.

-- 
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/1929833

Title:
  bluez: meshctl missing

Status in bluez package in Ubuntu:
  Fix Committed
Status in bluez package in Debian:
  Fix Released

Bug description:
  bluez has added a new tool for BT mesh handling.

  Debian has a new binary package: https://packages.debian.org/bullseye
  /bluez-meshd

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1929833] Re: bluez: meshctl missing

[Markus Becker]

I do see an update of bluez to 5.58
https://git.launchpad.net/ubuntu/+source/bluez/commit/?id=f0877af285d9360c02762de34a79ed11c72a84ca
5.58, but no changes that would add meshctl.

-- 
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/1929833

Title:
  bluez: meshctl missing

Status in bluez package in Ubuntu:
  Fix Committed
Status in bluez package in Debian:
  Fix Released

Bug description:
  bluez has added a new tool for BT mesh handling.

  Debian has a new binary package: https://packages.debian.org/bullseye
  /bluez-meshd

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1929833] [NEW] bluez: meshctl missing

[Markus Becker]

Public bug reported:

bluez has added a new tool for BT mesh handling.

Debian has a new binary package: https://packages.debian.org/bullseye
/bluez-meshd

Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579

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

-- 
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/1929833

Title:
  bluez: meshctl missing

Status in bluez package in Ubuntu:
  New

Bug description:
  bluez has added a new tool for BT mesh handling.

  Debian has a new binary package: https://packages.debian.org/bullseye
  /bluez-meshd

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1923075] [NEW] Unmaximizing a window by dragging is buggy

[Markus Ilmola]

Public bug reported:

In Ubuntu 21.04 beta (using the wayland session) when unmaximizing a
window by dragging it off from the top bar at least two bugs happen
randomly.

1. The window might not unmaximize at all but keeps it's maximized size.
2. The unmaximize animation does not play correctly (only "slides" but does not 
"scale").

Note that unmaximizing by using the maximize button or alt+f10 works correctly.
Also X applications such as xterm unmaximize correctly when dragged off from 
the top bar.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
ApportVersion: 2.20.11-0ubuntu62
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  8 17:42:01 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:5024]
InstallationDate: Installed on 2021-04-06 (1 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
MachineType: LENOVO 80B6QB0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=431ba979-ee7c-490a-b2db-4996f68514e9 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/07/2013
dmi.bios.release: 2.2
dmi.bios.vendor: LENOVO
dmi.bios.version: J7ET57WW (2.02 )
dmi.board.asset.tag: Not Available
dmi.board.name: 80B6QB0
dmi.board.vendor: LENOVO
dmi.board.version: 31900058 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 2.2
dmi.modalias: 
dmi:bvnLENOVO:bvrJ7ET57WW(2.02):bd11/07/2013:br2.2:efr2.2:svnLENOVO:pn80B6QB0:pvrB5400:rvnLENOVO:rn80B6QB0:rvr31900058STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: B5400
dmi.product.name: 80B6QB0
dmi.product.sku: LENOVO_MT_80B6
dmi.product.version: B5400
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.104-1build1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute ubuntu wayland-session

** Description changed:

  In Ubuntu 21.04 beta (using the wayland session) when unmaximizing a
  window by dragging it off from the top bar at least two bugs happen
  randomly.
  
- 1. The window might not unmaximize at all but keep it's maximized size.
+ 1. The window might not unmaximize at all but keeps it's maximized size.
  2. The unmaximize animation does not play correctly (only "slides" but does 
not "scale").
  
  Note that unmaximizing by using the maximize button or alt+f10 works 
correctly.
- Also X applications such as xterm unmaximize correctly when dragged of the 
top bar.
+ Also X applications such as xterm unmaximize correctly when dragged off from 
the top bar.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu62
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  8 17:42:01 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
-Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:5024]
+  Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:5024]
  InstallationDate: Installed on 2021-04-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  MachineType: LENOVO 80B6QB0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic 
root=UUID=431ba979-ee7c-490a-b2db-4996f68514e9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present 

[Touch-packages] [Bug 1879770] Re: Renaming interfaces using *.link file does not work

[Markus Lindberg]

I experiencing the same problem. My two Ethernet interfaces does not get
renamed. I want to accomplish the following.

eth0 => eth1
eth1 => eth0

Basically switching names between the Ethernet interfaces.

I had the same exact setup on 18.04 which worked.

You can find some information about my system below. Please let me know
if I should provide more information.

== networkctl(1) ==

# networkctl status eth0
WARNING: systemd-networkd is not running, output will be incomplete.

Failed to query link bit rates: Unit dbus-org.freedesktop.network1.service not 
found.
● 2: eth0
 Link File: n/a  
  Network File: n/a  
  Type: ether
 State: n/a (unmanaged)  
HW Address: e0:d5:5e:43:7e:52 (GIGA-BYTE TECHNOLOGY CO.,LTD.)
   MTU: 1500 (min: 68, max: 9000)
  Queue Length (Tx/Rx): 1/1  
  Auto negotiation: yes  
 Speed: 1Gbps
Duplex: full 
  Port: tp   
   Address: 10.88.130.28 
fe80::e2d5:5eff:fe43:7e52
   Gateway: 10.88.0.1 (Hewlett Packard)  

May 28 16:23:44 lnxjohansy systemd-udevd[503]: eth0: Failed to rename network 
interface 2 from 'eth0' to 'eth1': File exists
May 28 16:23:44 lnxjohansy systemd-udevd[503]: eth0: Failed to process device, 
ignoring: File exists

# networkctl status eth1
WARNING: systemd-networkd is not running, output will be incomplete.

Failed to query link bit rates: Unit dbus-org.freedesktop.network1.service not 
found.
● 3: eth1  
 Link File: n/a
  Network File: n/a
  Type: ether  
 State: n/a (unmanaged)
HW Address: 68:05:ca:75:3d:65 (Intel Corporate)
   MTU: 1500 (min: 68, max: 9212)  
  Queue Length (Tx/Rx): 1/1
  Auto negotiation: yes
 Speed: n/a
  Port: tp 

May 28 16:23:44 lnxjohansy systemd-udevd[503]: eth1: Failed to rename network 
interface 3 from 'eth1' to 'eth0': File exists
May 28 16:23:44 lnxjohansy systemd-udevd[503]: eth1: Failed to process device, 
ignoring: File exists

== systemd.link(5) ==

# ls -l /etc/systemd/network
total 8
-rw-r--r-- 1 root root 55 May 28 14:23 70-eth0.link
-rw-r--r-- 1 root root 55 May 28 14:23 70-eth1.link

# cat /etc/systemd/network/70-eth0.link 
[Match]
MACAddress=68:05:ca:75:3d:65

[Link]
Name=eth0

# cat /etc/systemd/network/70-eth1.link 
[Match]
MACAddress=e0:d5:5e:43:7e:52

[Link]
Name=eth1

# find / -iname "*.link"
/usr/lib/systemd/network/73-usb-net-by-mac.link
/usr/lib/systemd/network/99-default.link
/etc/systemd/network/70-eth1.link
/etc/systemd/network/70-eth0.link

== netplan(5) ==

# ls -l /etc/netplan/
total 4
-rw-r--r-- 1 root root 104 May 28 14:23 01-network-manager-all.yaml

# cat /etc/netplan/01-network-manager-all.yaml 
# Let NetworkManager manage all devices on this system
network:
  version: 2
  renderer: NetworkManager

== interfaces(5) ==

# cat /etc/network/interfaces
auto lo eth0 eth1
iface lo inet loopback

iface eth1 inet dhcp
wpa-driver wired
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

iface eth0 inet static
address 192.168.0.1
netmask 255.255.255.0

== systemd.network(5) ==

# systemctl is-active systemd-network
inactive

-- 
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/1879770

Title:
  Renaming interfaces using *.link file does not work

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Dear Ubuntu team,

  I wanted to use "systemd-networkd" intead of "udev" to rename network
  interface like this:

  (replace MAC by real one)

  
  echo '[Match]
  MACAddress=12:34:56:78:90:11

  [Link]
  Name=myname123' | sudo tee '/etc/systemd/network/myname123.link'
  

  (and reboot)

  But it does not work. And it should work based on the systemd
  documentation. I googled the issue but I didn't find anything
  interesting instead that I should run 

[Touch-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

[Markus Majer]

BT device is in the wrong mode / on the wrong profile.

Solution is here: https://askubuntu.com/questions/889737/video-not-
playing-in-web-browser-with-bluetooth-headphones-connected-how-can-i

wget
https://gist.github.com/pylover/d68be364adac5f946887b85e6ed6e7ae/archive/d698974910bbb7d016ec0ad08c1bf41b4b524364.zip

unzip d698974910bbb7d016ec0ad08c1bf41b4b524364.zip

in there is a a2dp.py

chmod +x a2dp.py

Run the file (modify python3.5 to python3 if needed in the first line)
when you have the device connected.

Choose it from the list.

It changes the profile, now everything works, the video is also running.
What the reason is, I cant tell, but I can tell you that this solves it

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1589008

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Markus W]

One additional aspect to note is that some desktop monitors reconnect to
the system when returning from power-save mode. In my case the sound
selection is changed to HDMI/DisplayPort whenever this happens. Changing
the sound setting back 10+ times a day is extremely annoying.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1847570

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Eoan:
  Triaged
Status in pulseaudio source package in Focal:
  Triaged

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile

[Markus Reuther]

I am also affected by this issue: I would like to use my Jabra ENVOLVE
65 headset with A2DP for the headphones in combination with the
microphone of the headset at the same time. Hope that A2DP (for the
headphones) and HSP/HFP (for the microphone) can be used simultaneously
via Bluetooth and that someone finds out how and that someone fixes
this. While this is not fixed I can not use my headset for voip calls
under Ubuntu (18.04) (HSP/HFP quality is too poor for a multiple-hour
call).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/508522

Title:
  Mic is not available with A2DP Bluetooth profile

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  I'm testing a Nokia BH-905i headset (see 
http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The 
Bluetooth module correctly identifies the headset and the both audio profiles 
"HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music 
playback only A2DP is suitable (HSP/HFP sounds like listening to music played 
through an old telephone). A2DP does not have an INPUT mode, so use of the 
headset for VoiP isn't possible.
  What would be needed is a separate selection to allow to select A2DP for 
output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do 
that (or they switch on the fly?).

  Formal structure:
  1) Ubuntu 10.10
  2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1
  consisting og pluseaudio, pulseaudio-esound-compat, 
pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, 
pulseaudio-utils
  3) Select high quality audio output and still use the Bluetooth microphone
  4) Had to choose: either high quality audio or "telephone quality" with 
microphone

  I can change the profile without the Bluetooth connection dropping,
  but that's ridiculous. E.g. listening to music, a call comes in. Then
  I would need to switch the profile before answering. Please note that
  in Windows, Mac OS, iOS, Android, and Windows Mobile it's done
  automatically.

  Check out attached screencast.

  ProblemType: Bug
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  oivasyuv   2309 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30e8,00100400'
     Controls  : 22
     Simple ctrls  : 14
  Date: Sat Jan 16 22:31:41 2010
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Package: pulseaudio 1:0.9.19-0ubuntu4
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae
  SourcePackage: pulseaudio
  Uname: Linux 2.6.31-17-generic-pae i686

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1832834] Re: Irregular system freezes after updating to 1.1.1b-1ubuntu2.2

[Markus Birth]

With 1.1.1b-1ubuntu2.3 it's a bit different. The system doesn't seem to
freeze anymore, but network traffic stops working. Happend about 1-2
hours after a fresh reboot (after applying updates). It still answered
to PINGs, but no other network traffic. Neither SSH, nor HTTP/HTTPS or
XMPP. After downgrading to 1.1.1b-1ubuntu2.1 it's now running for 3
hours without problems.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1832834

Title:
  Irregular system freezes after updating to 1.1.1b-1ubuntu2.2

Status in openssl package in Ubuntu:
  New

Bug description:
  Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco
  arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41
  CEST. About 12:36 the system froze. I was able to reset the system at
  around 17:17. It froze again at around 17:55. Reset it again 19:09,
  froze again 00:15.

  Freeze = solid green "busy" light and doesn't answer to anything.
  Since it's a headless system, I only have the logfiles but they don't
  show anything obvious.

  At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have
  ANY freeze at all since then (13:13 now here).

  The system is running ejabberd, SyncThing and a few more programs,
  that make heavy use of OpenSSL.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1832834] [NEW] Irregular system freezes after updating to 1.1.1b-1ubuntu2.2

[Markus Birth]

Public bug reported:

Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco
arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41
CEST. About 12:36 the system froze. I was able to reset the system at
around 17:17. It froze again at around 17:55. Reset it again 19:09,
froze again 00:15.

Freeze = solid green "busy" light and doesn't answer to anything. Since
it's a headless system, I only have the logfiles but they don't show
anything obvious.

At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have ANY
freeze at all since then (13:13 now here).

The system is running ejabberd, SyncThing and a few more programs, that
make heavy use of OpenSSL.

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

** Description changed:

  Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco
  arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41
  CEST. About 12:36 the system froze. I was able to reset the system at
  around 17:17. It froze again at around 17:55. Reset it again 19:09,
  froze again 00:15.
  
  Freeze = solid green "busy" light and doesn't answer to anything. Since
  it's a headless system, I only have the logfiles but they don't show
  anything obvious.
  
  At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have ANY
- freeze at all since then.
+ freeze at all since then (13:13 now here).
  
  The system is running ejabberd, SyncThing and a few more programs, that
  make heavy use of OpenSSL.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1832834

Title:
  Irregular system freezes after updating to 1.1.1b-1ubuntu2.2

Status in openssl package in Ubuntu:
  New

Bug description:
  Yesterday, I've updated openssl on my Raspberry Pi 3B+ running disco
  arm64 from 1.1.1b-1ubuntu2.1 to 1.1.1b-1ubuntu2.2 . That was at 10:41
  CEST. About 12:36 the system froze. I was able to reset the system at
  around 17:17. It froze again at around 17:55. Reset it again 19:09,
  froze again 00:15.

  Freeze = solid green "busy" light and doesn't answer to anything.
  Since it's a headless system, I only have the logfiles but they don't
  show anything obvious.

  At 01:06, I've downgraded back to 1.1.1b-1ubuntu2.1 and didn't have
  ANY freeze at all since then (13:13 now here).

  The system is running ejabberd, SyncThing and a few more programs,
  that make heavy use of OpenSSL.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1805027] Re: systemd-resolved can't resolve Comcast mail server addresses

[Markus Alexander Kuppe]

*** This bug is a duplicate of bug 1811471 ***
https://bugs.launchpad.net/bugs/1811471

The same symptons appear for "emea.mail.microsoft.com" even with systemd
237-3ubuntu10.21 from -updates.

-- 
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/1805027

Title:
  systemd-resolved can't resolve Comcast mail server addresses

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  1) Ubuntu release:  18.10
  2) systemd-resolved version: (Default latest version that comes with Ubuntu 
18.10)
  3) Expected behavior: Comcast's POP3 mail server addresses to be resolved to 
IP addresses
  4) Actual behavior:  Comcast's POP3 mail server addresses can't be resolved 
to IP addresses

  Starting on Monday, November 19, 2018, Comcast made a DNS change
  related to its POP3 mail servers (mail.comcast.net and
  pop3.comcast.net) that prevent resolved from being able to resolve
  those domains into IP addresses.  When I try to ping either host
  (mail.comcast.net or pop2.comcast.net), I get this error:

  tom@deathstar:~$ ping mail.comcast.net
  ping: mail.comcast.net: Name or service not known
  tom@deathstar:~$

  When I manually lookup up the domain, I get these results:

  tom@deathstar:~$ nslookup mail.comcast.net
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  Non-authoritative answer:
  mail.comcast.net  canonical name = imap.ge.xfinity.com.
  Name: imap.ge.xfinity.com
  Address: 96.118.242.209
  Name: imap.ge.xfinity.com
  Address: 96.118.242.197
  Name: imap.ge.xfinity.com
  Address: 96.118.242.233
  Name: imap.ge.xfinity.com
  Address: 96.118.242.225
  Name: imap.ge.xfinity.com
  Address: 96.118.242.226
  Name: imap.ge.xfinity.com
  Address: 96.118.242.217
  Name: imap.ge.xfinity.com
  Address: 96.118.242.208
  Name: imap.ge.xfinity.com
  Address: 96.118.242.230
  Name: imap.ge.xfinity.com
  Address: 96.118.242.232
  Name: imap.ge.xfinity.com
  Address: 96.118.242.218
  Name: imap.ge.xfinity.com
  Address: 96.118.242.211
  Name: imap.ge.xfinity.com
  Address: 96.118.242.242
  Name: imap.ge.xfinity.com
  Address: 96.118.242.221
  Name: imap.ge.xfinity.com
  Address: 96.118.242.196
  Name: imap.ge.xfinity.com
  Address: 96.118.208.40
  Name: imap.ge.xfinity.com
  Address: 96.118.208.99
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fee8:4f07
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe7d:1b0c
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe25:5ae5
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fef6:babc
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe87:c172
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fee6:7a57
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:9:f816:3eff:fe0f:a4a
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc11:2:f816:3eff:fec7:cb93
  Name: imap.ge.xfinity.com
  Address: 2001:558:fee2:1000:f816:3eff:fe42:4f14
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe33:9aaa
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:feb2:8c0d
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fef1:25a5
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:febd:320a
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe36:aba3
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe3f:76f2
  Name: imap.ge.xfinity.com
  Address: 2001:558:fc18:0:f816:3eff:fe45:1d1e

  tom@deathstar:~$ dig mail.comcast.net

  ; <<>> DiG 9.11.4-3ubuntu5-Ubuntu <<>> mail.comcast.net
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15037
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 17, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mail.comcast.net.IN  A

  ;; ANSWER SECTION:
  mail.comcast.net. 15  IN  CNAME   imap.ge.xfinity.com.
  imap.ge.xfinity.com.  12  IN  A   96.117.3.119
  imap.ge.xfinity.com.  12  IN  A   96.117.3.96
  imap.ge.xfinity.com.  12  IN  A   96.117.3.143
  imap.ge.xfinity.com.  12  IN  A   96.117.3.145
  imap.ge.xfinity.com.  12  IN  A   96.117.3.129
  imap.ge.xfinity.com.  12  IN  A   96.117.3.148
  imap.ge.xfinity.com.  12  IN  A   96.117.3.201
  imap.ge.xfinity.com.  12  IN  A   96.117.3.136
  imap.ge.xfinity.com.  12  IN  A   96.118.133.238
  imap.ge.xfinity.com.  12  IN  A   96.117.3.128
  imap.ge.xfinity.com.  12  IN  A   96.117.3.144
  imap.ge.xfinity.com.  12  IN  A   96.117.2.238
  imap.ge.xfinity.com.  12  IN  A   96.117.3.110
  imap.ge.xfinity.com.  12  IN  A   96.117.3.140
  imap.ge.xfinity.com.  12  IN  A   96.117.3.154
  

[Touch-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot

[Markus Birth]

I have this, too, on a Raspberry Pi 3 with arm64 Ubuntu. However, I've
also upgraded my Raspberry Pi 2 with armhf and there, NetworkManager
still autoconnects just fine after boot. The configuration looks
identical on both machines.

-- 
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/1826403

Title:
  Ethernet won't connect when cable is plugged in at boot

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When booting Ubuntu 19.04 with the Ethernet cable plugged in, after
  boot, network manager won't connect. Unplugging and plugging back in
  the cable with the system running doesn't work to establish a
  connection.

  The workaround is to boot with the cable unplugged, then to plug it in
  after boot.

  This problem emerged immediately following an upgrade from 18.10 to
  19.04. On the first boot networking was fine, but from the first
  reboot a networking connection through the Ethernet cable couldn't be
  established if the cable was plugged in at boot.

  This issue is also described here:
  https://askubuntu.com/questions/1135412/updated-to-19-04-and-no-
  ethernet-now/1135726#1135726 and here: https://ubuntu-
  mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect-
  when-plugged-in-before-boot/19333/6

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: network-manager 1.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr 25 21:50:27 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto enp4s0f1
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-23 (153 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 
   169.254.0.0/16 dev enp4s0f1 scope link metric 1000 
   192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2019-04-25T20:03:28.380204
  nmcli-dev:
   DEVICETYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTIONCON-UUID   
   CON-PATH   
   enp4s0f1  ethernet  connectedfull  limited   
/org/freedesktop/NetworkManager/Devices/2  Automatic connection  
e906293b-df71-435b-8909-7d88ca006540  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp3s0wifi  unavailable  limited   limited   
/org/freedesktop/NetworkManager/Devices/3  ---- 
   -- 
   loloopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.16.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826403/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1819369] Re: When specifying minute, hour, day-of-month, month, day-of-week values/ranges, given day-of-month range is *ignored*

[Markus Ueberall]

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd'
  # lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04
  
  2) The version of the package you are using, via 'apt-cache policy pkgname'
  # apt-cache policy cron
  cron:
    Installed: 3.0pl1-128ubuntu2
    Candidate: 3.0pl1-128ubuntu2
    Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  
  3) What you expected to happen
  /etc/crontab contains the following entries (each line lives on a separate 
host with identical setup, system clocks are in sync):
  # m h dom mon dow user  command
  00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
  00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
  00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
  00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4
  
  The expectation was that none of the entries is executed in parallel at
- any given point in time due to column three (date of month range).
- (Note: All other (default) entries work as expected, syntax of all
- crontab files has been checked using
+ any given point in time due to column three (day-of-month range). (Note:
+ All other (default) entries work as expected, syntax of all crontab
+ files has been checked using
  https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)
  
  4) What happened instead
  Yesterday (Saturday, March 9th), the same script was executed in parallel on 
all four hosts.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1819369

Title:
  When specifying minute,hour,day-of-month,month,day-of-week
  values/ranges, given day-of-month range is *ignored*

Status in cron package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd'
  # lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname'
  # apt-cache policy cron
  cron:
    Installed: 3.0pl1-128ubuntu2
    Candidate: 3.0pl1-128ubuntu2
    Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /etc/crontab contains the following entries (each line lives on a separate 
host with identical setup, system clocks are in sync):
  # m h dom mon dow user  command
  00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
  00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
  00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
  00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4

  The expectation was that none of the entries is executed in parallel
  at any given point in time due to column three (day-of-month range).
  (Note: All other (default) entries work as expected, syntax of all
  crontab files has been checked using
  https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)

  4) What happened instead
  Yesterday (Saturday, March 9th), the same script was executed in parallel on 
all four hosts.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1819369] [NEW] When specifying minute, hour, day-of-month, month, day-of-week values/ranges, given day-of-month range is *ignored*

[Markus Ueberall]

Public bug reported:

1) The release of Ubuntu you are using, via 'lsb_release -rd'
# lsb_release -rd
Description:Ubuntu 16.04.6 LTS
Release:16.04

2) The version of the package you are using, via 'apt-cache policy pkgname'
# apt-cache policy cron
cron:
  Installed: 3.0pl1-128ubuntu2
  Candidate: 3.0pl1-128ubuntu2
  Version table:
 *** 3.0pl1-128ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status

3) What you expected to happen
/etc/crontab contains the following entries (each line lives on a separate host 
with identical setup, system clocks are in sync):
# m h dom mon dow user  command
00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4

The expectation was that none of the entries is executed in parallel at
any given point in time due to column three (date of month range).
(Note: All other (default) entries work as expected, syntax of all
crontab files has been checked using
https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)

4) What happened instead
Yesterday (Saturday, March 9th), the same script was executed in parallel on 
all four hosts.

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

** Description changed:

  1) The release of Ubuntu you are using, via 'lsb_release -rd'
  # lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04
  
- 
  2) The version of the package you are using, via 'apt-cache policy pkgname'
  # apt-cache policy cron
  cron:
-   Installed: 3.0pl1-128ubuntu2
-   Candidate: 3.0pl1-128ubuntu2
-   Version table:
-  *** 3.0pl1-128ubuntu2 500
- 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
- 
+   Installed: 3.0pl1-128ubuntu2
+   Candidate: 3.0pl1-128ubuntu2
+   Version table:
+  *** 3.0pl1-128ubuntu2 500
+ 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  3) What you expected to happen
  /etc/crontab contains the following entries (each line lives on a separate 
host with identical setup, system clocks are in sync):
  # m h dom mon dow user  command
  00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
  00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
  00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
  00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4
  
  The expectation was that none of the entries is executed in parallel at
  any given point in time due to column three (date of month range).
  (Note: All other (default) entries work as expected, syntax of all
- crontab files have been checked using
+ crontab files has been checked using
  https://code.google.com/archive/p/chkcrontab/wikis/CheckCrontab.wiki)
- 
  
  4) What happened instead
  Yesterday (Saturday, March 9th), the same script was executed in parallel on 
all four hosts.

** Summary changed:

- When specifying specific minute,hour,day-of-month,month,day-of-week 
values/ranges, given day-of-month range is *ignored*
+ When specifying minute,hour,day-of-month,month,day-of-week values/ranges, 
given day-of-month range is *ignored*

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/1819369

Title:
  When specifying minute,hour,day-of-month,month,day-of-week
  values/ranges, given day-of-month range is *ignored*

Status in cron package in Ubuntu:
  New

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd'
  # lsb_release -rd
  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname'
  # apt-cache policy cron
  cron:
    Installed: 3.0pl1-128ubuntu2
    Candidate: 3.0pl1-128ubuntu2
    Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  /etc/crontab contains the following entries (each line lives on a separate 
host with identical setup, system clocks are in sync):
  # m h dom mon dow user  command
  00 05 1-7 1,3,5,7,9,11 SAT  sys-maint   some-task some-option   #host1
  00 05 8-14 1,3,5,7,9,11 SAT sys-maint   some-task some-option   #host2
  00 05 15-21 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host3
  00 05 22-28 1,3,5,7,9,11 SATsys-maint   some-task some-option   #host4

  The expectation was that none of the entries is executed in parallel
  at any given point in time 

[Touch-packages] [Bug 917231] Re: Mutual exclusion for cronjobs

[Markus Ueberall]

For the record: There's https://github.com/poeml/withlock which can
simply be put "between" cron and the applications in question…

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cron in Ubuntu.
https://bugs.launchpad.net/bugs/917231

Title:
  Mutual exclusion for cronjobs

Status in cron package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 12.04 dev with cron 3.0pl1-120ubuntu2. I encountered
  in the past a problem which can be solved with a new feature. Here is
  an example of the problem:

  0 0 * * * root /usr/local/share/python/backup_to_media.py
  0 0 1 * * root /usr/local/share/python/backup_to_internet.py

  These cronjobs do backup some data every day to a media and one time a
  month to the internet. The problem is on the first day of every month
  both backups are running at the same time. This can cause some
  problems like the backuped data to the internet is one day older as it
  should be or there are maybe exceptions because both jobs are
  accessing the files at the same time.

  Maybe there could be a priority column which controls this:

  0 0 * * * root 0 /usr/local/share/python/backup_to_media.py
  0 0 1 * * root 1 /usr/local/share/python/backup_to_internet.py

  The priority column ensures that jobs which are running at the same
  time are excuted sequentially (if the priority of every job is the
  same number we will have the current behaviour). On the first day of
  every month /usr/local/share/python/backup_to_media.py is executed
  first because it has a lower number and if it finishes
  /usr/local/share/python/backup_to_internet.py is executed.

  This would prevent complicated entries in the crontab or own complex
  mutual exclusion to solve this problem.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1813266] [NEW] udhcpd: not dying on SIGTERM

[Markus Schade]

Public bug reported:

udhcpd in bionic does not stop on SIGTERM due to an upstream change.
This was corrected by the following patch:

https://git.busybox.net/busybox/commit/?id=3293bc146985c56790033409facc0ad64a471084

Please apply and backport/SRU this change to bionic.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1813266

Title:
  udhcpd: not dying on SIGTERM

Status in busybox package in Ubuntu:
  New

Bug description:
  udhcpd in bionic does not stop on SIGTERM due to an upstream change.
  This was corrected by the following patch:

  
https://git.busybox.net/busybox/commit/?id=3293bc146985c56790033409facc0ad64a471084

  Please apply and backport/SRU this change to bionic.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1273524] Re: LXDE guest session shows error message "no session for pid "

[Markus Kwaśnicki]

Sadly, I confirm this bug still exists in Lubuntu 18.04.1 :-(

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1273524

Title:
  LXDE guest session shows error message "no session for pid "

Status in One Hundred Papercuts:
  Triaged
Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.18 series:
  Triaged
Status in lightdm package in Ubuntu:
  Confirmed
Status in lxsession package in Ubuntu:
  Triaged
Status in lightdm source package in Xenial:
  Confirmed
Status in lxsession source package in Xenial:
  Confirmed

Bug description:
  EXPECTED RESULTS:
  Log into guest session with no error messages.

  ACTUAL RESULTS:
  Upon log in to guest session, an error "no session for pid " is printed.

  STEPS TO REPRODUCE:
  1. Using Lubuntu in trusty, utopic, or vivid with either real or virtual 
hardware, log into guest session.
  2. After being logged in, see error message.

  AFFECTED VERSIONS:
  lightdm 1.10.0-0ubuntu3 to 1.12.1-0ubuntu1
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-10-18 (384 days ago)
  InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=lightdm-gtk-greeter
   user-session=Lubuntu
  LightdmGreeterLog:
   ** (lightdm-gtk-greeter:1874): WARNING **: Failed to load user image: Failed 
to open file '/home/brendy/.face': No such file or directory
   g_dbus_connection_real_closed: Remote peer vanished with error: Underlying 
GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
  LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2073): WARNING **: Failed to 
load user image: Failed to open file '/home/brendy/.face': No such file or 
directory
  NonfreeKernelModules: wl
  Package: lxsession
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (202 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1807367] Re: segfault when using ommongodb with ssl

[Markus Ziermann]

** Attachment added: "apport"
   
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1807367/+attachment/5219976/+files/rsyslog%20bugreport

** Description changed:

+ rsyslog-mongodb 8.32.0-1ubuntu4
+ 
  A segfault will occur when you are trying to access a mongodb with
  enabled authentication or when using ssl.
  
  module(load="ommongodb")
  *.* action(type="ommongodb"
-   uristr="mongodb://localhost:27017/?ssl=true"
-   db="syslog" collection="log")
+   uristr="mongodb://localhost:27017/?ssl=true"
+   db="syslog" collection="log")
  
  Dec 07 11:15:44 syslog rsyslogd[31455]:  [origin software="rsyslogd" 
swVersion="8.32.0" x-pid="31455" x-info="http://www.rsyslog.com;] start
  Dec 07 11:15:44 syslog rsyslogd[31455]: action 'action 2' suspended (module 
'ommongodb'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.32.0 try http://www.rsyslog.com/e/2007 ]
  Dec 07 11:15:44 syslog rsyslogd[31455]: action 'action 2' resumed (module 
'ommongodb') [v8.32.0 try http://www.rsyslog.com/e/2359 ]
  Dec 07 11:15:44 syslog kernel: rs:main Q:Reg[31478]: segfault at 8 ip 
7f29456b6f18 sp 7f29419efb78 error 4 in 
libmongoc-1.0.so.0.0.0[7f2945691000+71000]
  Dec 07 11:15:44 syslog systemd[1]: rsyslog.service: Main process exited, 
code=killed, status=11/SEGV

** Summary changed:

- segfault when using ommongodb with ssl
+ rsyslog-mongodb 8.32.0-1ubuntu4: segfault when using ommongodb with ssl

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1807367

Title:
  rsyslog-mongodb 8.32.0-1ubuntu4: segfault when using ommongodb with
  ssl

Status in rsyslog package in Ubuntu:
  New

Bug description:
  rsyslog-mongodb 8.32.0-1ubuntu4

  A segfault will occur when you are trying to access a mongodb with
  enabled authentication or when using ssl.

  module(load="ommongodb")
  *.* action(type="ommongodb"
    uristr="mongodb://localhost:27017/?ssl=true"
    db="syslog" collection="log")

  Dec 07 11:15:44 syslog rsyslogd[31455]:  [origin software="rsyslogd" 
swVersion="8.32.0" x-pid="31455" x-info="http://www.rsyslog.com;] start
  Dec 07 11:15:44 syslog rsyslogd[31455]: action 'action 2' suspended (module 
'ommongodb'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.32.0 try http://www.rsyslog.com/e/2007 ]
  Dec 07 11:15:44 syslog rsyslogd[31455]: action 'action 2' resumed (module 
'ommongodb') [v8.32.0 try http://www.rsyslog.com/e/2359 ]
  Dec 07 11:15:44 syslog kernel: rs:main Q:Reg[31478]: segfault at 8 ip 
7f29456b6f18 sp 7f29419efb78 error 4 in 
libmongoc-1.0.so.0.0.0[7f2945691000+71000]
  Dec 07 11:15:44 syslog systemd[1]: rsyslog.service: Main process exited, 
code=killed, status=11/SEGV

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1807367] [NEW] segfault when using ommongodb with ssl

[Markus Ziermann]

Public bug reported:

A segfault will occur when you are trying to access a mongodb with
enabled authentication or when using ssl.

module(load="ommongodb")
*.* action(type="ommongodb"
  uristr="mongodb://localhost:27017/?ssl=true"
  db="syslog" collection="log")

Dec 07 11:15:44 syslog rsyslogd[31455]:  [origin software="rsyslogd" 
swVersion="8.32.0" x-pid="31455" x-info="http://www.rsyslog.com;] start
Dec 07 11:15:44 syslog rsyslogd[31455]: action 'action 2' suspended (module 
'ommongodb'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.32.0 try http://www.rsyslog.com/e/2007 ]
Dec 07 11:15:44 syslog rsyslogd[31455]: action 'action 2' resumed (module 
'ommongodb') [v8.32.0 try http://www.rsyslog.com/e/2359 ]
Dec 07 11:15:44 syslog kernel: rs:main Q:Reg[31478]: segfault at 8 ip 
7f29456b6f18 sp 7f29419efb78 error 4 in 
libmongoc-1.0.so.0.0.0[7f2945691000+71000]
Dec 07 11:15:44 syslog systemd[1]: rsyslog.service: Main process exited, 
code=killed, status=11/SEGV

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


** Tags: ommongodb ssl

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1807367

Title:
  segfault when using ommongodb with ssl

Status in rsyslog package in Ubuntu:
  New

Bug description:
  A segfault will occur when you are trying to access a mongodb with
  enabled authentication or when using ssl.

  module(load="ommongodb")
  *.* action(type="ommongodb"
uristr="mongodb://localhost:27017/?ssl=true"
db="syslog" collection="log")

  Dec 07 11:15:44 syslog rsyslogd[31455]:  [origin software="rsyslogd" 
swVersion="8.32.0" x-pid="31455" x-info="http://www.rsyslog.com;] start
  Dec 07 11:15:44 syslog rsyslogd[31455]: action 'action 2' suspended (module 
'ommongodb'), retry 0. There should be messages before this one giving the 
reason for suspension. [v8.32.0 try http://www.rsyslog.com/e/2007 ]
  Dec 07 11:15:44 syslog rsyslogd[31455]: action 'action 2' resumed (module 
'ommongodb') [v8.32.0 try http://www.rsyslog.com/e/2359 ]
  Dec 07 11:15:44 syslog kernel: rs:main Q:Reg[31478]: segfault at 8 ip 
7f29456b6f18 sp 7f29419efb78 error 4 in 
libmongoc-1.0.so.0.0.0[7f2945691000+71000]
  Dec 07 11:15:44 syslog systemd[1]: rsyslog.service: Main process exited, 
code=killed, status=11/SEGV

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1768789] Re: connectivity results in limited when behind proxy

[Markus Lindberg]

Has someone taken a look at this? Bionic has been out for a couple of
months now.

-- 
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/1768789

Title:
  connectivity results in limited when behind proxy

Status in network-manager package in Ubuntu:
  New

Bug description:
  The connectivity for a connection results in limited when behind a
  proxy for NetworkManager.

  $ sudo nmcli general 
  STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
  connected (site only)  limited   enabled  enabled  enabled  enabled

  $ sudo nmcli networking connectivity check 
  limited

  I have configured my proxy in both '/etc/environment' and via the GUI
  under 'Settings'->'Network'->'Network Proxy'->'Automatic'.

  After this is set I can do an HTTP GET against the URL/URI you have
  configured in the '/usr/lib/NetworkManager/conf.d/20-connectivity-
  ubuntu.conf' file.

  $ curl -I http://connectivity-check.ubuntu.com/
  HTTP/1.1 204 No Content
  Date: Thu, 03 May 2018 09:01:34 GMT
  Server: Apache/2.4.18 (Ubuntu)
  X-NetworkManager-Status: online
  X-Cache: MISS from proxy.example.com
  X-Cache-Lookup: MISS from proxy.example.com:3128
  Via: 1.1 proxy.example.com (squid/3.3.8)
  Connection: keep-alive

  $ env|grep -i proxy
  auto_proxy=http://proxy.example.com/auto
  https_proxy=http://proxy.example.com:3128
  http_proxy=http://proxy.example.com:3128

  But network connectivity still fails to use the proxy.

  I assume that the 'network-manager-config-connectivity-ubuntu' package
  is used for this feature after reading the following output.

  $ dpkg -S /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  network-manager-config-connectivity-ubuntu: 
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf

  If I remove the '/usr/lib/NetworkManager/conf.d/20-connectivity-
  ubuntu.conf' file the connectivity check succeeds or I don't get
  limited connectivity at least.

  --
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  $ uname -a
  Linux lnxhplap2 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  $ dpkg -l|grep network-manager
  ii  network-manager1.10.6-2ubuntu1
 amd64network management framework (daemon and userspace tools)
  ii  network-manager-config-connectivity-ubuntu 1.10.6-2ubuntu1
 all  NetworkManager configuration to enable connectivity checking
  ii  network-manager-gnome  1.8.10-2ubuntu1
 amd64network management framework (GNOME frontend)
  ii  network-manager-pptp   1.2.6-1
 amd64network management framework (PPTP plugin core)
  ii  network-manager-pptp-gnome 1.2.6-1
 amd64network management framework (PPTP plugin GNOME GUI)
  --

  Note: I have used "proxy.example.com" as substitute for our proxy
  server in this bug report for privacy reasons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1768789/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1644643] Re: apt failed to run due to link time reference error

[Markus Neubauer]

#18 agreed
#19 Thanx

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1644643

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1644643] Re: apt failed to run due to link time reference error

[Markus Neubauer]

#15 ...and dont forget to hold the package or will run in the same
situation each update process, see link in #14

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1644643

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1644643] Re: apt failed to run due to link time reference error

[Markus Neubauer]

The Problem occured also using a Zentyal 5.1 community version:
A workaround is here 
https://forum.zentyal.org/index.php/topic,32403.msg109031.html#msg109031

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1644643

Title:
  apt failed to run due to link time reference error

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After update apt and its related library to 1.2.15 from 1.2.10ubuntu1,
  I get following message when I try to invoke apt:

  apt-get: relocation error: /usr/lib/x86_64-linux-gnu/libapt-
  private.so.0.0: symbol _ZlsRSoRKN3APT9PrettyPkgE, version APTPKG_5.0
  not defined in file libapt-pkg.so.5.0 with link time reference

  1.2.10 do not have this problem. Now I manually downgrade from 1.2.15
  to 1.2.10 to solve this problem.

  Ubuntu release: 
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  what I expect to happen: apt would show the helper message
  what happened instead: apt shows me the line on above

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1784499] Re: AppArmor treats regular NFS file access as network op

[Markus Kuhn]

See also
https://lists.ubuntu.com/archives/apparmor/2018-October/011823.html

-- 
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/1784499

Title:
  AppArmor treats regular NFS file access as network op

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic.

  I have the usr.bin.man profile enforced, and home directories in NFS.

  The log excerpt copied below is the result of a single invocation of
  "man ls" by an unprivileged user. (The program did display the man
  page correctly to the user.)

  It does not seem appropriate for AppArmor to report the man(1) program
  as having attempted to contact the NFS server directly, when it only
  tried to access an NFS-served file in the normal way. "man" is not a
  network-aware program and the log below misleadingly implies
  otherwise.

  

  Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 
callbacks suppressed
  Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 
audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 
audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 
audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 
audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 
audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 
audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 
audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 
audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 
audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.066434] audit: type=1400 
audit(1532986715.866:223): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2788 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 

[Touch-packages] [Bug 1784499] Re: AppArmor treats regular NFS file access as network op

[Markus Kuhn]

AppArmor really should restrict NFS access only via the file-path rules,
not via the network rules, since if an application accesses a file via
NFS, all related network traffic is initiated and controlled by the
kernel (or by kernel helper processes like automount, rpc.gssd and
nfsidmap), and not by the application.

Workaround (for /usr/bin/man only):

Add to /etc/apparmor.d/local/usr.bin.man the lines

  # TCP/UDP network access for NFS
  network inet  stream,
  network inet6 stream,
  network inet  dgram,
  network inet6 dgram,

then run

# systemctl reload apparmor

This really should be fixed in the kernel, but until then, perhaps
adding a widely-included /etc/apparmor.d/abstractions/nfs with the above
lines would be useful, as /usr/bin/man is just one example of an
affected application.

See also bug #1662552

-- 
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/1784499

Title:
  AppArmor treats regular NFS file access as network op

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic.

  I have the usr.bin.man profile enforced, and home directories in NFS.

  The log excerpt copied below is the result of a single invocation of
  "man ls" by an unprivileged user. (The program did display the man
  page correctly to the user.)

  It does not seem appropriate for AppArmor to report the man(1) program
  as having attempted to contact the NFS server directly, when it only
  tried to access an NFS-served file in the normal way. "man" is not a
  network-aware program and the log below misleadingly implies
  otherwise.

  

  Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 
callbacks suppressed
  Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 
audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 
audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 
audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 
audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 
audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 
audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 
audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 
audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 

[Touch-packages] [Bug 1794284] [NEW] PCI/internal sound card not detected

[Markus Strenn]

Public bug reported:

my sound was working in xenial. with internal intel sound. without any change 
it stopped working, no soundcard found. 
update to bionic didn't change anything :(

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 25 14:16:55 2018
InstallationDate: Installed on 2016-03-10 (929 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago)
dmi.bios.date: 03/22/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0906
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z270-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
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/1794284

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  my sound was working in xenial. with internal intel sound. without any change 
it stopped working, no soundcard found. 
  update to bionic didn't change anything :(

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 25 14:16:55 2018
  InstallationDate: Installed on 2016-03-10 (929 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago)
  dmi.bios.date: 03/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0906
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z270-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0906:bd03/22/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ270-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1794284/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774857] Re: sort doesn't sort and uniq loses data for many non-Latin scripts on UTF-8 locales

[Miikka-Markus Alhonen]

One user on debbugs.gnu.org reported that the problem is more likely
related to the locale / glibc than coreutils, and that it occurs on
Ubuntu 18.04 but not Fedora 28, in case that helps any. He thought it
might have already been fixed in glibc, since Fedora tends to be more up
to date than Ubuntu.

** Also affects: glibc (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1774857

Title:
  sort doesn't sort and uniq loses data for many non-Latin scripts on
  UTF-8 locales

Status in coreutils package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New

Bug description:
  I’ve found out that sort doesn’t sort strings for many non-Latin
  scripts at all if the locale you’re using is one of en_US.UTF-8,
  fr_FR.UTF-8 or fi_FI.UTF-8 (probably others, too, but these are the
  ones I have tested). For locales ”C” and ko_KR.UTF-8, things work as
  expected. Here’s a test case:

  Open xterm, launch sort and input some lines of Syriac, Ethiopic,
  Korean, Japanese (Hiragana or Katakana, not Han) or Thai text
  repeating one of the lines twice. Here’s an example in Syriac:

  ܡܠܬܐ
  ܒܝܬܐ
  ܒܪܢܫܐ
  ܡܠܬܐ

  Sort produces the following:

  ܡܠܬܐ
  ܒܝܬܐ
  ܡܠܬܐ
  ܒܪܢܫܐ

  Here strings are ordered only according to their length but not
  characters. Even the two instances of the word ܡܠܬܐ are found on non-
  adjacent lines (1 and 3). The expected sort order based on Unicode
  points would be:

  ܒܝܬܐ
  ܒܪܢܫܐ
  ܡܠܬܐ
  ܡܠܬܐ

  If you further pass sort’s output to uniq, it produces the following:

  ܡܠܬܐ
  ܒܪܢܫܐ

  Here the word on line 2 ܒܝܬܐ is completely lost since, like sort, uniq
  seems to consider all Syriac strings of equal length as the same.

  Although this issue affects locale, I think it is not a locale issue
  per se, since perl seems to handle similar cases expectedly. For
  instance, the following command produces the expected result:

  perl -CDS -e 'use locale; use utf8; @str = ("ܡܠܬܐ", "ܒܝܬܐ", "ܒܪܢܫܐ",
  "ܡܠܬܐ"); foreach $i (sort @str) { print "$i\n"; }'

  Curiously enough, codepoints in Plane 1 seem to count as two
  codepoints of the basic plane, so that if you sort | uniq the
  following (six codepoints of Syriac and three codepoints of
  Phoenician):

  ܥܠܝܟܘܢ
  ँउक

  you get ”ܥܠܝܟܘܢ" as the result whereas ”ँउक” is lost. This is of
  course due to the UTF-8 representation of Plane 1 characters as two
  surrogate characters on the basic plane.

  Also curiously, LTR scripts seem to conflate with each other and RTL
  scripts among themselves but not across the directionality line, so
  that if you sort | uniq the following (three codepoints each in
  Ethiopic, Hangul, Syriac, Hiragana and Thai):

  ዘመን
  스물셋
  ܐܢܐ
  わたし
  ฟ้า

  you are left with:

  ܐܢܐ
  ዘመን

  That’s one line of Syriac and one line of Ethiopic; everything else
  was lost. This issue does not seem to affect most Indic scripts
  (Devanagari, Bengali, Telugu etc.) or Arabic. For CJK, things work as
  expected for the main Unicode block (4E00..9FFF) but not for Extension
  A (3400..4DBF, such as 㗖 or 㡘 or 㰋). For Greek, monotonic accents work
  fine but all polytonic letters are conflated (αὐλὸς and αὐλῆς conflate
  to αὐλῆς). For Hebrew, letters and vowel marks work fine but
  cantillation marks are conflated.

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  coreutils:
Installed: 8.28-1ubuntu1
Candidate: 8.28-1ubuntu1
Version table:
   *** 8.28-1ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  3 10:13:06 2018
  InstallationDate: Installed on 2017-02-13 (474 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (2 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648107] Re: $XAUTHORITY should move into $XDG_RUNTIME_DIR

[Markus Kuhn]

LightDM is already able to create the xauthority file locally under
$XDG_RUNTIME_DIR, using configuration option user-authority-in-system-
dir. This option is off by default on Ubuntu 16.04/18.04, but can be
enabled with

# echo -e '[LightDM]\nuser-authority-in-system-dir=true'
>/etc/lightdm/lightdm.conf.d/50-user-authority-in-system-dir.conf

LightDM then sets XAUTHORITY=/var/run/lightdm/$USER/xauthority instead
of $HOME/.Xauthority. However, this path goes through the symbolic link
/var/run -> /run. For some reason (why?) snap does not like such
symlinks, resulting in a warning:

# snap install pdftk
# pdftk
2018/08/24 17:32:48.267771 cmd_run.go:442: WARNING: XAUTHORITY environment 
value is not a clean path: "/run/lightdm/mgk25/xauthority"

A workaround to canonicalize the XAUTHORITY path (to eliminate symlinks)
can be installed with e.g.

# echo 'XAUTHORITY=`readlink -f "$XAUTHORITY"` && [ -z "$XAUTHORITY" ]
&& export XAUTHORITY' >/etc/X11/Xsession.d/10canonicalize-xauthority

It would be nicer if LightDM directly used a canonical path in
XAUTHORITY with user-authority-in-system-dir=true, or if snap didn't
have to be so picky about symbolic links.

(LightDM currently does not set ICEAUTHORITY when user-authority-in-
system-dir=true.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1648107

Title:
  $XAUTHORITY should move into $XDG_RUNTIME_DIR

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Historically, the X authority file was placed into $HOME/.Xauthority
  such that X11 clients on remote servers could access it in
  environments in which $HOME is located on a network file system.

  Today, this practice has become an anachronism that causes far more
  problems than it solves:

  a) Remote X11 clients are typically started today via "ssh -X", which
  emulates its own X11 server port $DISPLAY and therefore always creates
  its own X authority file entry on the remote server. Therefore, there
  is no longer any practical benefit from having the X authority file
  located in $HOME.

  b) If $HOME is on a network file system that implements "root squash",
  then commands such as "sudo xterm" or "sudo wireshark" won't work to
  start an X client with root privileges, as root is not able to read
  ~/.Xauthority via NFS. :-(

  c) If $HOME is on a network file system with Kerberos authentication,
  then users can easily get locked out by their screensavers once the
  Kerberos ticket expires. This is because some screen lockers (e.g.,
  gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome-
  screensaver/gnome-screensaver-dialog) in order to ask the user of a
  locked screen for their password. Such a tool needs to access
  $XAUTHORITY right before it can display the password prompt, which
  will fail if the user's Kerberos ticket has expired (e.g. because a
  machine was suspended for 24 hours and therefore the ticket was not
  refreshed automatically on time). Without the ability to ask for a
  password, the screensaver then cannot call pam_krb5 to renew the
  user's Kerberos ticket, and the user remains locked out in a deadlock
  situation. :-(

  Both b) and c) are regular reasons for support requests in
  educational/corporate Linux environments with $HOME on Kerberized NFS.

  The solution is simple. Instead of $HOME/.Xauthority, just use in
  future $XDG_RUNTIME_DIR/xauthority as the location of the X authority
  file. (In case $XDG_RUNTIME_DIR/ does not exist, /tmp/xauthority-$USER
  might be a suitable fallback option.)

  According to https://standards.freedesktop.org/basedir-spec/basedir-
  spec-latest.html the $XDG_RUNTIME_DIR has all the right properties for
  holding the X authority file: it is always located in a local tmpfs
  filesystem, guaranteed to be accessible only to the current user, and
  will be wiped when the user has closed all sessions.

  On modern Linux systems, pam_systemd usually creates
  XDG_RUNTIME_DIR=/run/user/$UID, and wipes it in the end.

  (Note that according to https://standards.freedesktop.org/basedir-spec
  /basedir-spec-latest.html you should set the "sticky bit" on any files
  created in $XDG_RUNTIME_DIR whose timestamp is not updated regularly.)

  Feature request: please provide an option for LightDM to do the
  equivalent of

export XAUTHORITY=$XDG_RUNTIME_DIR/xauthority
chmod +t $XAUTHORITY

  and encourage Linux distribution maintainers to set this option by
  default, such that ~/.Xauthority is no longer used.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1648107] Re: $XAUTHORITY should move into $XDG_RUNTIME_DIR

[Markus Kuhn]

see also bug 685194

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1648107

Title:
  $XAUTHORITY should move into $XDG_RUNTIME_DIR

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Historically, the X authority file was placed into $HOME/.Xauthority
  such that X11 clients on remote servers could access it in
  environments in which $HOME is located on a network file system.

  Today, this practice has become an anachronism that causes far more
  problems than it solves:

  a) Remote X11 clients are typically started today via "ssh -X", which
  emulates its own X11 server port $DISPLAY and therefore always creates
  its own X authority file entry on the remote server. Therefore, there
  is no longer any practical benefit from having the X authority file
  located in $HOME.

  b) If $HOME is on a network file system that implements "root squash",
  then commands such as "sudo xterm" or "sudo wireshark" won't work to
  start an X client with root privileges, as root is not able to read
  ~/.Xauthority via NFS. :-(

  c) If $HOME is on a network file system with Kerberos authentication,
  then users can easily get locked out by their screensavers once the
  Kerberos ticket expires. This is because some screen lockers (e.g.,
  gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome-
  screensaver/gnome-screensaver-dialog) in order to ask the user of a
  locked screen for their password. Such a tool needs to access
  $XAUTHORITY right before it can display the password prompt, which
  will fail if the user's Kerberos ticket has expired (e.g. because a
  machine was suspended for 24 hours and therefore the ticket was not
  refreshed automatically on time). Without the ability to ask for a
  password, the screensaver then cannot call pam_krb5 to renew the
  user's Kerberos ticket, and the user remains locked out in a deadlock
  situation. :-(

  Both b) and c) are regular reasons for support requests in
  educational/corporate Linux environments with $HOME on Kerberized NFS.

  The solution is simple. Instead of $HOME/.Xauthority, just use in
  future $XDG_RUNTIME_DIR/xauthority as the location of the X authority
  file. (In case $XDG_RUNTIME_DIR/ does not exist, /tmp/xauthority-$USER
  might be a suitable fallback option.)

  According to https://standards.freedesktop.org/basedir-spec/basedir-
  spec-latest.html the $XDG_RUNTIME_DIR has all the right properties for
  holding the X authority file: it is always located in a local tmpfs
  filesystem, guaranteed to be accessible only to the current user, and
  will be wiped when the user has closed all sessions.

  On modern Linux systems, pam_systemd usually creates
  XDG_RUNTIME_DIR=/run/user/$UID, and wipes it in the end.

  (Note that according to https://standards.freedesktop.org/basedir-spec
  /basedir-spec-latest.html you should set the "sticky bit" on any files
  created in $XDG_RUNTIME_DIR whose timestamp is not updated regularly.)

  Feature request: please provide an option for LightDM to do the
  equivalent of

export XAUTHORITY=$XDG_RUNTIME_DIR/xauthority
chmod +t $XAUTHORITY

  and encourage Linux distribution maintainers to set this option by
  default, such that ~/.Xauthority is no longer used.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774857] Re: sort doesn't sort and uniq loses data for many non-Latin scripts on UTF-8 locales

[Miikka-Markus Alhonen]

Since nobody has reacted to this report for a couple of months, I
decided to file an upstream report at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=32472

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1774857

Title:
  sort doesn't sort and uniq loses data for many non-Latin scripts on
  UTF-8 locales

Status in coreutils package in Ubuntu:
  New

Bug description:
  I’ve found out that sort doesn’t sort strings for many non-Latin
  scripts at all if the locale you’re using is one of en_US.UTF-8,
  fr_FR.UTF-8 or fi_FI.UTF-8 (probably others, too, but these are the
  ones I have tested). For locales ”C” and ko_KR.UTF-8, things work as
  expected. Here’s a test case:

  Open xterm, launch sort and input some lines of Syriac, Ethiopic,
  Korean, Japanese (Hiragana or Katakana, not Han) or Thai text
  repeating one of the lines twice. Here’s an example in Syriac:

  ܡܠܬܐ
  ܒܝܬܐ
  ܒܪܢܫܐ
  ܡܠܬܐ

  Sort produces the following:

  ܡܠܬܐ
  ܒܝܬܐ
  ܡܠܬܐ
  ܒܪܢܫܐ

  Here strings are ordered only according to their length but not
  characters. Even the two instances of the word ܡܠܬܐ are found on non-
  adjacent lines (1 and 3). The expected sort order based on Unicode
  points would be:

  ܒܝܬܐ
  ܒܪܢܫܐ
  ܡܠܬܐ
  ܡܠܬܐ

  If you further pass sort’s output to uniq, it produces the following:

  ܡܠܬܐ
  ܒܪܢܫܐ

  Here the word on line 2 ܒܝܬܐ is completely lost since, like sort, uniq
  seems to consider all Syriac strings of equal length as the same.

  Although this issue affects locale, I think it is not a locale issue
  per se, since perl seems to handle similar cases expectedly. For
  instance, the following command produces the expected result:

  perl -CDS -e 'use locale; use utf8; @str = ("ܡܠܬܐ", "ܒܝܬܐ", "ܒܪܢܫܐ",
  "ܡܠܬܐ"); foreach $i (sort @str) { print "$i\n"; }'

  Curiously enough, codepoints in Plane 1 seem to count as two
  codepoints of the basic plane, so that if you sort | uniq the
  following (six codepoints of Syriac and three codepoints of
  Phoenician):

  ܥܠܝܟܘܢ
  ँउक

  you get ”ܥܠܝܟܘܢ" as the result whereas ”ँउक” is lost. This is of
  course due to the UTF-8 representation of Plane 1 characters as two
  surrogate characters on the basic plane.

  Also curiously, LTR scripts seem to conflate with each other and RTL
  scripts among themselves but not across the directionality line, so
  that if you sort | uniq the following (three codepoints each in
  Ethiopic, Hangul, Syriac, Hiragana and Thai):

  ዘመን
  스물셋
  ܐܢܐ
  わたし
  ฟ้า

  you are left with:

  ܐܢܐ
  ዘመን

  That’s one line of Syriac and one line of Ethiopic; everything else
  was lost. This issue does not seem to affect most Indic scripts
  (Devanagari, Bengali, Telugu etc.) or Arabic. For CJK, things work as
  expected for the main Unicode block (4E00..9FFF) but not for Extension
  A (3400..4DBF, such as 㗖 or 㡘 or 㰋). For Greek, monotonic accents work
  fine but all polytonic letters are conflated (αὐλὸς and αὐλῆς conflate
  to αὐλῆς). For Hebrew, letters and vowel marks work fine but
  cantillation marks are conflated.

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  coreutils:
Installed: 8.28-1ubuntu1
Candidate: 8.28-1ubuntu1
Version table:
   *** 8.28-1ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  3 10:13:06 2018
  InstallationDate: Installed on 2017-02-13 (474 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (2 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1786821] Re: pam.7.gz is a symlink to PAM.7.gz . This does not work for caseinsensitive filesystems e.g. Windows Subsystem for Linux

[Markus Werner]

Full ACK

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1786821

Title:
  pam.7.gz is a symlink to PAM.7.gz . This does not work for
  caseinsensitive filesystems e.g. Windows Subsystem for Linux

Status in pam package in Ubuntu:
  Won't Fix

Bug description:
  The package libpam-runtime contains a symlink pam.7.gz -> PAM.7.gz in
  ./usr/share/man/man7 and this doesn't work in Windows Subsystem for
  Linux since Windows has a caseinsensitive filesystem.

  On ubuntu 18.04 this PAM.7.gz exists too. I know it's not a linux
  centric issue. But why libpam-runtime is using Uppercase and symlinks
  anyway? Other packgages in man7 just use lowercase, and this is what
  I'm expecting.

  Hopefully you can fix it.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1786821] Re: pam.7.gz is a symlink to PAM.7.gz . This does not work for caseinsensitive filesystems e.g. Windows Subsystem for Linux

[Markus Werner]

Filled Bug to WSL since this is a better place to fix the bug.

https://github.com/Microsoft/WSL/issues/3461


** Bug watch added: github.com/Microsoft/WSL/issues #3461
   https://github.com/Microsoft/WSL/issues/3461

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1786821

Title:
  pam.7.gz is a symlink to PAM.7.gz . This does not work for
  caseinsensitive filesystems e.g. Windows Subsystem for Linux

Status in pam package in Ubuntu:
  Incomplete

Bug description:
  The package libpam-runtime contains a symlink pam.7.gz -> PAM.7.gz in
  ./usr/share/man/man7 and this doesn't work in Windows Subsystem for
  Linux since Windows has a caseinsensitive filesystem.

  On ubuntu 18.04 this PAM.7.gz exists too. I know it's not a linux
  centric issue. But why libpam-runtime is using Uppercase and symlinks
  anyway? Other packgages in man7 just use lowercase, and this is what
  I'm expecting.

  Hopefully you can fix it.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1786821] Re: pam.7.gz is a symlink to PAM.7.gz . This does not work for caseinsensitive filesystems e.g. Windows Subsystem for Linux

[Markus Werner]

Hi Balint,

dpkg -i libpam-runtime* will throws an error cause it trys to symlink pam.7.gz 
to PAM.7.gz since Windows filesystem is case*in*sensitive this both files are 
the same and so the symlink will get refused cause the file already exists.
So apt upgrade won't work on Windows. Maybe there is also a Windows way to 
upgrade Windows Subsystem for Linux (WSL) but since apt tools are working it 
should be fix IMHO.

So if there is no reason behind "PAM && pam"  it would be good if it
will be removed. If there is a reason maybe the postinstall scripts
could generate the symlink after checking that it is a casesensitive fs.

Thanks for the msdn link. I will check if it works. This might be a
solution, cause other linux packages might have the same issue.

Markus

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1786821

Title:
  pam.7.gz is a symlink to PAM.7.gz . This does not work for
  caseinsensitive filesystems e.g. Windows Subsystem for Linux

Status in pam package in Ubuntu:
  Incomplete

Bug description:
  The package libpam-runtime contains a symlink pam.7.gz -> PAM.7.gz in
  ./usr/share/man/man7 and this doesn't work in Windows Subsystem for
  Linux since Windows has a caseinsensitive filesystem.

  On ubuntu 18.04 this PAM.7.gz exists too. I know it's not a linux
  centric issue. But why libpam-runtime is using Uppercase and symlinks
  anyway? Other packgages in man7 just use lowercase, and this is what
  I'm expecting.

  Hopefully you can fix it.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1786821] Re: pam.7.gz is a symlink to PAM.7.gz . This does not work for caseinsensitive filesystems e.g. Windows Subsystem for Linux

[Markus Werner]

New dep file

** Attachment added: "libpam-runtime_1.1.8-3.2ubuntu2.1_all_fixed.dep"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1786821/+attachment/5174840/+files/libpam-runtime_1.1.8-3.2ubuntu2.1_all_fixed.dep

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1786821

Title:
  pam.7.gz is a symlink to PAM.7.gz . This does not work for
  caseinsensitive filesystems e.g. Windows Subsystem for Linux

Status in pam package in Ubuntu:
  New

Bug description:
  The package libpam-runtime contains a symlink pam.7.gz -> PAM.7.gz in
  ./usr/share/man/man7 and this doesn't work in Windows Subsystem for
  Linux since Windows has a caseinsensitive filesystem.

  On ubuntu 18.04 this PAM.7.gz exists too. I know it's not a linux
  centric issue. But why libpam-runtime is using Uppercase and symlinks
  anyway? Other packgages in man7 just use lowercase, and this is what
  I'm expecting.

  Hopefully you can fix it.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1786821] Re: pam.7.gz is a symlink to PAM.7.gz . This does not work for caseinsensitive filesystems e.g. Windows Subsystem for Linux

[Markus Werner]

Update of the fix for version 1.1.8-3.2ubuntu2.1_all


Patch:
mkdir libpam-runtime-fix
dbpk-dep -R libpam-runtime_1.1.8-3.2ubuntu2.1_all.dep libpam-runtime-fix
rm libpam-runtime-fix/usr/share/man/man7/pam.7.gz
mv libpam-runtime-fix/usr/share/man/man7/PAM.7.gz 
libpam-runtime-fix/usr/share/man/man7/pam.7.gz
dbpk-dep -b libpam-runtime-fix libpam-runtime_1.1.8-3.2ubuntu2.1_all_fixed.dep

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1786821

Title:
  pam.7.gz is a symlink to PAM.7.gz . This does not work for
  caseinsensitive filesystems e.g. Windows Subsystem for Linux

Status in pam package in Ubuntu:
  New

Bug description:
  The package libpam-runtime contains a symlink pam.7.gz -> PAM.7.gz in
  ./usr/share/man/man7 and this doesn't work in Windows Subsystem for
  Linux since Windows has a caseinsensitive filesystem.

  On ubuntu 18.04 this PAM.7.gz exists too. I know it's not a linux
  centric issue. But why libpam-runtime is using Uppercase and symlinks
  anyway? Other packgages in man7 just use lowercase, and this is what
  I'm expecting.

  Hopefully you can fix it.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1786821] Re: pam.7.gz is a symlink to PAM.7.gz . This does not work for caseinsensitive filesystems e.g. Windows Subsystem for Linux

[Markus Werner]

Fixed the issue by my self. And it's working under windows now

** Attachment added: "Fixed DEP"
   
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1786821/+attachment/5174823/+files/libpam-runtime_1.1.8-3.2ubuntu2_all_fixed.deb

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1786821

Title:
  pam.7.gz is a symlink to PAM.7.gz . This does not work for
  caseinsensitive filesystems e.g. Windows Subsystem for Linux

Status in pam package in Ubuntu:
  New

Bug description:
  The package libpam-runtime contains a symlink pam.7.gz -> PAM.7.gz in
  ./usr/share/man/man7 and this doesn't work in Windows Subsystem for
  Linux since Windows has a caseinsensitive filesystem.

  On ubuntu 18.04 this PAM.7.gz exists too. I know it's not a linux
  centric issue. But why libpam-runtime is using Uppercase and symlinks
  anyway? Other packgages in man7 just use lowercase, and this is what
  I'm expecting.

  Hopefully you can fix it.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1786821] [NEW] pam.7.gz is a symlink to PAM.7.gz . This does not work for caseinsensitive filesystems e.g. Windows Subsystem for Linux

[Markus Werner]

Public bug reported:

The package libpam-runtime contains a symlink pam.7.gz -> PAM.7.gz in
./usr/share/man/man7 and this doesn't work in Windows Subsystem for
Linux since Windows has a caseinsensitive filesystem.

On ubuntu 18.04 this PAM.7.gz exists too. I know it's not a linux
centric issue. But why libpam-runtime is using Uppercase and symlinks
anyway? Other packgages in man7 just use lowercase, and this is what I'm
expecting.

Hopefully you can fix it.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1786821

Title:
  pam.7.gz is a symlink to PAM.7.gz . This does not work for
  caseinsensitive filesystems e.g. Windows Subsystem for Linux

Status in pam package in Ubuntu:
  New

Bug description:
  The package libpam-runtime contains a symlink pam.7.gz -> PAM.7.gz in
  ./usr/share/man/man7 and this doesn't work in Windows Subsystem for
  Linux since Windows has a caseinsensitive filesystem.

  On ubuntu 18.04 this PAM.7.gz exists too. I know it's not a linux
  centric issue. But why libpam-runtime is using Uppercase and symlinks
  anyway? Other packgages in man7 just use lowercase, and this is what
  I'm expecting.

  Hopefully you can fix it.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1781634] [NEW] SIGFPE on GtkMessageDialog

[Markus Kitsinger]

Public bug reported:

Trying to open a gtk2 message box crashes the hosting program. Easiest
way I've been able to reproduce this is to run gtk-demo from the
gtk2.0-examples package, and try to spawn a message dialog from the
Dialog and Message Boxes demo. Nothing is printed to stdout or stderr.

I'm running Ubuntu MATE 18.04, and the libgtk2.0-0 package version is
2.42.32-1ubuntu1.

I do not recall this happening on the other bionic system running in the
office, so it could be related to UI scaling for my HiDPI displays.
That's just a hunch, though.

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1781634

Title:
  SIGFPE on GtkMessageDialog

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Trying to open a gtk2 message box crashes the hosting program. Easiest
  way I've been able to reproduce this is to run gtk-demo from the
  gtk2.0-examples package, and try to spawn a message dialog from the
  Dialog and Message Boxes demo. Nothing is printed to stdout or stderr.

  I'm running Ubuntu MATE 18.04, and the libgtk2.0-0 package version is
  2.42.32-1ubuntu1.

  I do not recall this happening on the other bionic system running in
  the office, so it could be related to UI scaling for my HiDPI
  displays. That's just a hunch, though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1781634/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster

[Markus]

Here the same issue with Kubuntu 18.04. on a Asus Prime Z370-A. I hope
for fixing this problem.

-- 
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/1764965

Title:
  [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x
  faster

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recording applications (audacity, arecord, gnome-sound-recorder)
  record extremely slowly (at what seems to be 0,1x speed), which means
  that at playback the sound is played at a very high pitch and much
  faster than the original.

  To help you understand the issue, I've attached an archive containing two 
files recorded at the same time, one with arecord -f cd and the other with a 
stand-alone Olympus recorder.
  A video of Audacity's behavior when trying to record is also available: 
https://youtu.be/Fe20eQNvZVA
  Look at the seconds hand of the xclock and how much it is moving before 
Audacity is done recording one second of audio.

  Things I've already tried:
  *  Purging and reinstalling Audacity
  *  Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki
  *  Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 
audacity as suggested on AskUbuntu
  *  Reinstalling Ubuntu on a new hard disk
  *  Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 
daily and Xubuntu 17.10.1, 18.04)

  The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard.

  The problem can be reproduced as follows:

  * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've 
tested with)
  * Install audacity via the terminal
  * Start recording, microphone is connected to the rear microphone jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacopo 2417 F pulseaudio
   /dev/snd/controlC0:  jacopo 2417 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 18 09:35:50 2018
  InstallationDate: Installed on 2018-03-03 (45 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: None of the above
  Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1764965/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774857] [NEW] sort doesn't sort and uniq loses data for many non-Latin scripts on UTF-8 locales

[Miikka-Markus Alhonen]

Public bug reported:

I’ve found out that sort doesn’t sort strings for many non-Latin scripts
at all if the locale you’re using is one of en_US.UTF-8, fr_FR.UTF-8 or
fi_FI.UTF-8 (probably others, too, but these are the ones I have
tested). For locales ”C” and ko_KR.UTF-8, things work as expected.
Here’s a test case:

Open xterm, launch sort and input some lines of Syriac, Ethiopic,
Korean, Japanese (Hiragana or Katakana, not Han) or Thai text repeating
one of the lines twice. Here’s an example in Syriac:

ܡܠܬܐ
ܒܝܬܐ
ܒܪܢܫܐ
ܡܠܬܐ

Sort produces the following:

ܡܠܬܐ
ܒܝܬܐ
ܡܠܬܐ
ܒܪܢܫܐ

Here strings are ordered only according to their length but not
characters. Even the two instances of the word ܡܠܬܐ are found on non-
adjacent lines (1 and 3). The expected sort order based on Unicode
points would be:

ܒܝܬܐ
ܒܪܢܫܐ
ܡܠܬܐ
ܡܠܬܐ

If you further pass sort’s output to uniq, it produces the following:

ܡܠܬܐ
ܒܪܢܫܐ

Here the word on line 2 ܒܝܬܐ is completely lost since, like sort, uniq
seems to consider all Syriac strings of equal length as the same.

Although this issue affects locale, I think it is not a locale issue per
se, since perl seems to handle similar cases expectedly. For instance,
the following command produces the expected result:

perl -CDS -e 'use locale; use utf8; @str = ("ܡܠܬܐ", "ܒܝܬܐ", "ܒܪܢܫܐ",
"ܡܠܬܐ"); foreach $i (sort @str) { print "$i\n"; }'

Curiously enough, codepoints in Plane 1 seem to count as two codepoints
of the basic plane, so that if you sort | uniq the following (six
codepoints of Syriac and three codepoints of Phoenician):

ܥܠܝܟܘܢ
ँउक

you get ”ܥܠܝܟܘܢ" as the result whereas ”ँउक” is lost. This is of course
due to the UTF-8 representation of Plane 1 characters as two surrogate
characters on the basic plane.

Also curiously, LTR scripts seem to conflate with each other and RTL
scripts among themselves but not across the directionality line, so that
if you sort | uniq the following (three codepoints each in Ethiopic,
Hangul, Syriac, Hiragana and Thai):

ዘመን
스물셋
ܐܢܐ
わたし
ฟ้า

you are left with:

ܐܢܐ
ዘመን

That’s one line of Syriac and one line of Ethiopic; everything else was
lost. This issue does not seem to affect most Indic scripts (Devanagari,
Bengali, Telugu etc.) or Arabic. For CJK, things work as expected for
the main Unicode block (4E00..9FFF) but not for Extension A (3400..4DBF,
such as 㗖 or 㡘 or 㰋). For Greek, monotonic accents work fine but all
polytonic letters are conflated (αὐλὸς and αὐλῆς conflate to αὐλῆς). For
Hebrew, letters and vowel marks work fine but cantillation marks are
conflated.


Description:Ubuntu 18.04 LTS
Release:18.04

coreutils:
  Installed: 8.28-1ubuntu1
  Candidate: 8.28-1ubuntu1
  Version table:
 *** 8.28-1ubuntu1 500
500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: coreutils 8.28-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  3 10:13:06 2018
InstallationDate: Installed on 2017-02-13 (474 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: coreutils
UpgradeStatus: Upgraded to bionic on 2018-05-31 (2 days ago)

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


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1774857

Title:
  sort doesn't sort and uniq loses data for many non-Latin scripts on
  UTF-8 locales

Status in coreutils package in Ubuntu:
  New

Bug description:
  I’ve found out that sort doesn’t sort strings for many non-Latin
  scripts at all if the locale you’re using is one of en_US.UTF-8,
  fr_FR.UTF-8 or fi_FI.UTF-8 (probably others, too, but these are the
  ones I have tested). For locales ”C” and ko_KR.UTF-8, things work as
  expected. Here’s a test case:

  Open xterm, launch sort and input some lines of Syriac, Ethiopic,
  Korean, Japanese (Hiragana or Katakana, not Han) or Thai text
  repeating one of the lines twice. Here’s an example in Syriac:

  ܡܠܬܐ
  ܒܝܬܐ
  ܒܪܢܫܐ
  ܡܠܬܐ

  Sort produces the following:

  ܡܠܬܐ
  ܒܝܬܐ
  ܡܠܬܐ
  ܒܪܢܫܐ

  Here strings are ordered only according to their length but not
  characters. Even the two instances of the word ܡܠܬܐ are found on non-
  adjacent lines (1 and 3). The expected sort order based on Unicode
  points would be:

  ܒܝܬܐ
  ܒܪܢܫܐ
  ܡܠܬܐ
  ܡܠܬܐ

  If you further pass sort’s output to uniq, it produces the following:

  ܡܠܬܐ
  ܒܪܢܫܐ

  Here the word on line 2 ܒܝܬܐ is completely lost since, like sort, uniq
  seems to consider all Syriac strings of equal length as the same.

  Although 

[Touch-packages] [Bug 1772537] Re: Wrong combining sequence in Compose for the Finnish locale

[Miikka-Markus Alhonen]

I filed the report upstream at:
https://bugs.freedesktop.org/show_bug.cgi?id=106649

** Bug watch added: freedesktop.org Bugzilla #106649
   https://bugs.freedesktop.org/show_bug.cgi?id=106649

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1772537

Title:
  Wrong combining sequence in Compose for the Finnish locale

Status in libx11 package in Ubuntu:
  Triaged

Bug description:
  The Compose file for the fi_FI.UTF-8 locale at
  /usr/share/X11/locale/fi_FI.UTF-8/Compose contains the following
  lines:

  :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND ACUTE
   :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND DOT BELOW

  Thus the codepoint "Ệ" U1EC6 is produced with two different sequences.
  Based on the key sequences and the comments at the ends of the lines,
  it is clear that the first line is a mistake. Instead of "Ệ"  U1EC6,
  the line should read "Ế"  U1EBE, a character which cannot be produced
  with the current Compose file otherwise at all.

  Description:  Ubuntu 17.10
  Release:  17.10

  libx11-data:
Installed: 2:1.6.4-3
Candidate: 2:1.6.4-3
Version table:
   *** 2:1.6.4-3 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://mr.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1772537] [NEW] Wrong combining sequence in Compose for the Finnish locale

[Miikka-Markus Alhonen]

Public bug reported:

The Compose file for the fi_FI.UTF-8 locale at
/usr/share/X11/locale/fi_FI.UTF-8/Compose contains the following lines:

:  "Ệ"  U1EC6  #  LATIN CAPITAL LETTER 
E WITH CIRCUMFLEX AND ACUTE
 :  "Ệ"  U1EC6  #  LATIN CAPITAL LETTER 
E WITH CIRCUMFLEX AND DOT BELOW

Thus the codepoint "Ệ" U1EC6 is produced with two different sequences.
Based on the key sequences and the comments at the ends of the lines, it
is clear that the first line is a mistake. Instead of "Ệ"  U1EC6, the
line should read "Ế"  U1EBE, a character which cannot be produced with
the current Compose file otherwise at all.

Description:Ubuntu 17.10
Release:17.10

libx11-data:
  Installed: 2:1.6.4-3
  Candidate: 2:1.6.4-3
  Version table:
 *** 2:1.6.4-3 500
500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://mr.archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/1772537

Title:
  Wrong combining sequence in Compose for the Finnish locale

Status in libx11 package in Ubuntu:
  New

Bug description:
  The Compose file for the fi_FI.UTF-8 locale at
  /usr/share/X11/locale/fi_FI.UTF-8/Compose contains the following
  lines:

  :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND ACUTE
   :  "Ệ"  U1EC6  #  LATIN CAPITAL 
LETTER E WITH CIRCUMFLEX AND DOT BELOW

  Thus the codepoint "Ệ" U1EC6 is produced with two different sequences.
  Based on the key sequences and the comments at the ends of the lines,
  it is clear that the first line is a mistake. Instead of "Ệ"  U1EC6,
  the line should read "Ế"  U1EBE, a character which cannot be produced
  with the current Compose file otherwise at all.

  Description:  Ubuntu 17.10
  Release:  17.10

  libx11-data:
Installed: 2:1.6.4-3
Candidate: 2:1.6.4-3
Version table:
   *** 2:1.6.4-3 500
  500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://mr.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1553121] Re: Xenial preseed fails to load key for 3rd party repo with apt-setup/local0/key

[Markus Wigge]

I can confirm that bionic is affected too.

Maybe the installer image is missing some gnupg tools? I observed that
with a minimal install I cannot use "apt-key" within the installed
system because there is no gnupg installed at all.

This is really disappointing.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1553121

Title:
  Xenial preseed fails to load key for 3rd party repo with apt-
  setup/local0/key

Status in apt-setup package in Ubuntu:
  Confirmed
Status in base-installer package in Ubuntu:
  Confirmed
Status in console-setup package in Ubuntu:
  Confirmed
Status in debian-installer package in Ubuntu:
  Confirmed

Bug description:
  I have an automated preseed installation that uses these lines to add
  custom repos during the installation:

  d-i apt-setup/local0/repository string deb http://jschule.github.io/ubuntu/ /
  d-i apt-setup/local0/comment string JTS local repository
  d-i apt-setup/local0/source boolean false
  d-i apt-setup/local0/key string http://jschule.github.io/ubuntu/repo.key

  d-i apt-setup/local1/repository string deb 
http://dl.google.com/linux/chrome/deb/ stable main
  d-i apt-setup/local1/comment string Google Chrome Browser
  d-i apt-setup/local1/source boolean false
  d-i apt-setup/local1/key string 
http://dl.google.com/linux/linux_signing_key.pub

  
(seehttps://github.com/jschule/ubuntu/blob/d46f1cef49ed71dc4bfe317119cccd3f39097ef4/preseed/jts.txt
  for complete preseed file that causes the problem).

  In xenial the installation fails because the GPG key for the local0
  repo is not loaded into the system so that it can be used (see
  screenshot). Strangely, "chroot /target apt-key list" shows the key
  9E62229E to be installed.

  Just to be sure that there is no problem with my repo and key I
  started the Xenial live CD and installed my repo there manually. All
  works well. IMHO this shows that the problem is clearly related to the
  automated installation with preseed.

  Maybe this is related to #1512347, that was the only thing I could
  find on Launchpad that is in the same area.

  If you want to reproduce this then you can checkout the scripts from
  https://github.com/jschule/ubuntu/tree/gh-pages/qemu and run "./run.sh
  xenial" to start my installation.

  I found a very ugly workaround by changing the apt-setup lines to
  this:

  d-i apt-setup/local0/repository string deb 
http://archive.canonical.com/ubuntu trusty partner
  d-i apt-setup/local0/source boolean false

  d-i apt-setup/local1/repository string deb http://jschule.github.io/ubuntu/ /
  d-i apt-setup/local1/comment string JTS local repository
  d-i apt-setup/local1/source boolean false
  d-i apt-setup/local1/key string http://jschule.github.io/ubuntu/repo.key

  d-i apt-setup/local2/repository string deb 
http://dl.google.com/linux/chrome/deb/ stable main
  d-i apt-setup/local2/comment string Google Chrome Browser
  d-i apt-setup/local2/source boolean false
  d-i apt-setup/local2/key string 
http://dl.google.com/linux/linux_signing_key.pub

  I suppose that the workaround works because now the local0 repo is one
  where the signing key is already part of Ubuntu. I just hope that
  there is no package in the trusty partner repo that is not also in the
  xenial partner repo.

  For me it is very important that you fix this bug before 16.04 is
  released so that I can continue to use Ubuntu with an automated setup.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1553121/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1768789] [NEW] connectivity results in limited when behind proxy

[Markus Lindberg]

Public bug reported:

The connectivity for a connection results in limited when behind a proxy
for NetworkManager.

$ sudo nmcli general 
STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
connected (site only)  limited   enabled  enabled  enabled  enabled

$ sudo nmcli networking connectivity check 
limited

I have configured my proxy in both '/etc/environment' and via the GUI
under 'Settings'->'Network'->'Network Proxy'->'Automatic'.

After this is set I can do an HTTP GET against the URL/URI you have
configured in the '/usr/lib/NetworkManager/conf.d/20-connectivity-
ubuntu.conf' file.

$ curl -I http://connectivity-check.ubuntu.com/
HTTP/1.1 204 No Content
Date: Thu, 03 May 2018 09:01:34 GMT
Server: Apache/2.4.18 (Ubuntu)
X-NetworkManager-Status: online
X-Cache: MISS from proxy.example.com
X-Cache-Lookup: MISS from proxy.example.com:3128
Via: 1.1 proxy.example.com (squid/3.3.8)
Connection: keep-alive

$ env|grep -i proxy
auto_proxy=http://proxy.example.com/auto
https_proxy=http://proxy.example.com:3128
http_proxy=http://proxy.example.com:3128

But network connectivity still fails to use the proxy.

I assume that the 'network-manager-config-connectivity-ubuntu' package
is used for this feature after reading the following output.

$ dpkg -S /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
network-manager-config-connectivity-ubuntu: 
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf

If I remove the '/usr/lib/NetworkManager/conf.d/20-connectivity-
ubuntu.conf' file the connectivity check succeeds or I don't get limited
connectivity at least.

--
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04 LTS
Release:18.04
Codename:   bionic

$ uname -a
Linux lnxhplap2 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ dpkg -l|grep network-manager
ii  network-manager1.10.6-2ubuntu1  
   amd64network management framework (daemon and userspace tools)
ii  network-manager-config-connectivity-ubuntu 1.10.6-2ubuntu1  
   all  NetworkManager configuration to enable connectivity checking
ii  network-manager-gnome  1.8.10-2ubuntu1  
   amd64network management framework (GNOME frontend)
ii  network-manager-pptp   1.2.6-1  
   amd64network management framework (PPTP plugin core)
ii  network-manager-pptp-gnome 1.2.6-1  
   amd64network management framework (PPTP plugin GNOME GUI)
--

Note: I have used "proxy.example.com" as substitute for our proxy server
in this bug report for privacy reasons.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1768789

Title:
  connectivity results in limited when behind proxy

Status in network-manager package in Ubuntu:
  New

Bug description:
  The connectivity for a connection results in limited when behind a
  proxy for NetworkManager.

  $ sudo nmcli general 
  STATE  CONNECTIVITY  WIFI-HW  WIFI WWAN-HW  WWAN
  connected (site only)  limited   enabled  enabled  enabled  enabled

  $ sudo nmcli networking connectivity check 
  limited

  I have configured my proxy in both '/etc/environment' and via the GUI
  under 'Settings'->'Network'->'Network Proxy'->'Automatic'.

  After this is set I can do an HTTP GET against the URL/URI you have
  configured in the '/usr/lib/NetworkManager/conf.d/20-connectivity-
  ubuntu.conf' file.

  $ curl -I http://connectivity-check.ubuntu.com/
  HTTP/1.1 204 No Content
  Date: Thu, 03 May 2018 09:01:34 GMT
  Server: Apache/2.4.18 (Ubuntu)
  X-NetworkManager-Status: online
  X-Cache: MISS from proxy.example.com
  X-Cache-Lookup: MISS from proxy.example.com:3128
  Via: 1.1 proxy.example.com (squid/3.3.8)
  Connection: keep-alive

  $ env|grep -i proxy
  auto_proxy=http://proxy.example.com/auto
  https_proxy=http://proxy.example.com:3128
  http_proxy=http://proxy.example.com:3128

  But network connectivity still fails to use the proxy.

  I assume that the 'network-manager-config-connectivity-ubuntu' package
  is used for this feature after reading the following output.

  $ dpkg -S /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf
  network-manager-config-connectivity-ubuntu: 
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf

  If I remove the '/usr/lib/NetworkManager/conf.d/20-connectivity-
  ubuntu.conf' file the connectivity check succeeds or I don't get
  limited connectivity at least.

  --
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  

[Touch-packages] [Bug 1765189] [NEW] Partial User Interface freeze

[Markus Haider]

Public bug reported:

I have a Dell Precision 5520 and experience the following problem: After
a resume from suspend, I have problems with my keyboard and touchpad: At
the password screen everything is working fine, I can click on the
password field and enter my password. Then when the screen is unlocked,
I can move the mouse cursor, and clicks on the top menu, e.g. on the
network button or the shutdown button work perfectly, but a click on an
open window like a terminal or on firefox does not give focus to the
window and I cannot write into the terminal. Also, shortcuts like the
Windows key or Windows+tab key are not working. I can only solve this by
rebooting.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 18 22:01:56 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-13-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
 virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 
InstallationDate: Installed on 2018-04-12 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: Cannot 
open /sys/bus/pci/devices/:07:00.0/resource: No such file or directory
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f3:24a1 Elan Microelectronics Corp. 
 Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 004: ID 0c45:6713 Microdia 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 5520
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.1
dmi.board.name: 0R6JFH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.1:bd01/25/2018:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 5520
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze possible-manual-nvidia-install ubuntu

-- 
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/1765189

Title:
  Partial User Interface freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell Precision 5520 and experience the following problem:
  After a resume from suspend, I have problems with my keyboard and
  touchpad: At the password screen everything is working fine, I can
  click on the password field and enter my password. Then when the
  screen is unlocked, I can move the mouse cursor, and clicks on the top
  menu, e.g. on the network button or the shutdown button work
  perfectly, but a click on an open window like a terminal or on firefox
  does not give focus to the window and I cannot write into the
  terminal. Also, shortcuts like the Windows key or Windows+tab key are
  not working. I can only solve this by rebooting.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 

[Touch-packages] [Bug 1762630] Re: Why does not python3 depend on dh-python?

[Markus Lindberg]

I'm sorry the environment I'm using does not have all the base packages.
But I'm still curious why the dh-python dependency was removed from the
python3 package.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1762630

Title:
  Why does not python3 depend on dh-python?

Status in python3-defaults package in Ubuntu:
  Incomplete

Bug description:
  I get the following while trying to install python3 on Bionic.

  dpkg-query: package 'dh-python' is not installed
  Use dpkg --info (= dpkg-deb --info) to examine archive files,
  and dpkg --contents (= dpkg-deb --contents) to list their contents.

  What I can tell, every other Ubuntu release has this dependency but
  not Bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1762630/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1762630] Re: Why does not python3 depend on dh-python?

[Markus Lindberg]

Here is the complete output while trying to install python3 in a bionic
environment (debootstrap).

# apt-get install python3
Reading package lists... Done
Building dependency tree... Done
The following additional packages will be installed:
  adduser apt apt-utils bzip2 ca-certificates debconf debconf-i18n dpkg file 
gcc-8-base gpgv libacl1 libapt-inst2.0 libapt-pkg5.0 libattr1 libaudit-common 
libaudit1 libbz2-1.0 libc6
  libcap-ng0 libdb5.3 libexpat1 libffi6 libgcc1 libgcrypt20 libgmp10 
libgnutls30 libgpg-error0 libgpm2 libhogweed4 libidn2-0 liblocale-gettext-perl 
liblz4-1 liblzma5 libmagic-mgc
  libmagic1 libmpdec2 libncursesw5 libnettle6 libp11-kit0 libpam-modules 
libpam-modules-bin libpam0g libpcre3 libpython3-stdlib libpython3.6-minimal 
libpython3.6-stdlib libreadline7
  libseccomp2 libselinux1 libsemanage-common libsemanage1 libsepol1 
libsqlite3-0 libssl1.1 libstdc++6 libtasn1-6 libtext-charwidth-perl 
libtext-iconv-perl libtext-wrapi18n-perl
  libtinfo5 libudev1 libunistring2 mime-support openssl passwd perl-base 
python3-minimal python3.6 python3.6-minimal readline-common tar ubuntu-keyring 
update-motd xz-utils zlib1g
Suggested packages:
  perl ecryptfs-utils apt-doc aptitude | synaptic | wajig dpkg-dev gnupg | 
gnupg2 | gnupg1 powermgmt-base bzip2-doc debconf-doc debconf-utils whiptail | 
dialog
  libterm-readline-gnu-perl libgtk3-perl libnet-ldap-perl libqtgui4-perl 
libqtcore4-perl debsig-verify gnupg glibc-doc locales rng-tools gnutls-bin gpm 
libpam-doc python3-doc
  python3-tk python3-venv python3.6-venv python3.6-doc binutils binfmt-support 
readline-doc ncompress tar-scripts tar-doc
The following NEW packages will be installed:
  adduser apt apt-utils bzip2 ca-certificates debconf debconf-i18n dpkg file 
gcc-8-base gpgv libacl1 libapt-inst2.0 libapt-pkg5.0 libattr1 libaudit-common 
libaudit1 libbz2-1.0 libc6
  libcap-ng0 libdb5.3 libexpat1 libffi6 libgcc1 libgcrypt20 libgmp10 
libgnutls30 libgpg-error0 libgpm2 libhogweed4 libidn2-0 liblocale-gettext-perl 
liblz4-1 liblzma5 libmagic-mgc
  libmagic1 libmpdec2 libncursesw5 libnettle6 libp11-kit0 libpam-modules 
libpam-modules-bin libpam0g libpcre3 libpython3-stdlib libpython3.6-minimal 
libpython3.6-stdlib libreadline7
  libseccomp2 libselinux1 libsemanage-common libsemanage1 libsepol1 
libsqlite3-0 libssl1.1 libstdc++6 libtasn1-6 libtext-charwidth-perl 
libtext-iconv-perl libtext-wrapi18n-perl
  libtinfo5 libudev1 libunistring2 mime-support openssl passwd perl-base 
python3 python3-minimal python3.6 python3.6-minimal readline-common tar 
ubuntu-keyring update-motd xz-utils
  zlib1g
0 upgraded, 77 newly installed, 0 to remove and 0 not upgraded.
Need to get 21.3 MB of archives.
After this operation, 94.3 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://debian.lth.se/ubuntu bionic/main amd64 gcc-8-base amd64 
8-20180408-0ubuntu1 [18.1 kB]
Get:2 http://debian.lth.se/ubuntu bionic/main amd64 libc6 amd64 2.27-0ubuntu3 
[2823 kB]
Get:3 http://debian.lth.se/ubuntu bionic/main amd64 libgcc1 amd64 
1:8-20180408-0ubuntu1 [40.9 kB]
Get:4 http://debian.lth.se/ubuntu bionic/main amd64 libbz2-1.0 amd64 1.0.6-8.1 
[30.9 kB]
Get:5 http://debian.lth.se/ubuntu bionic/main amd64 liblzma5 amd64 5.2.2-1.3 
[90.8 kB]
Get:6 http://debian.lth.se/ubuntu bionic/main amd64 libpcre3 amd64 2:8.39-9 
[229 kB]
Get:7 http://debian.lth.se/ubuntu bionic/main amd64 libselinux1 amd64 
2.7-2build2 [68.2 kB]
Get:8 http://debian.lth.se/ubuntu bionic/main amd64 zlib1g amd64 
1:1.2.11.dfsg-0ubuntu2 [56.5 kB]
Get:9 http://debian.lth.se/ubuntu bionic/main amd64 libattr1 amd64 
1:2.4.47-2build1 [9524 B]
Get:10 http://debian.lth.se/ubuntu bionic/main amd64 libacl1 amd64 
2.2.52-3build1 [16.1 kB]
Get:11 http://debian.lth.se/ubuntu bionic/main amd64 tar amd64 1.29b-2 [233 kB]
Get:12 http://debian.lth.se/ubuntu bionic/main amd64 dpkg amd64 1.19.0.5ubuntu1 
[1140 kB]
Get:13 http://debian.lth.se/ubuntu bionic/main amd64 perl-base amd64 5.26.1-5 
[1390 kB]
Get:14 http://debian.lth.se/ubuntu bionic/main amd64 libaudit-common all 
1:2.8.2-1ubuntu1 [4132 B]
Get:15 http://debian.lth.se/ubuntu bionic/main amd64 libcap-ng0 amd64 0.7.7-3.1 
[11.1 kB]
Get:16 http://debian.lth.se/ubuntu bionic/main amd64 libaudit1 amd64 
1:2.8.2-1ubuntu1 [38.9 kB]
Get:17 http://debian.lth.se/ubuntu bionic/main amd64 debconf all 1.5.66 [124 kB]
Get:18 http://debian.lth.se/ubuntu bionic/main amd64 libpam0g amd64 
1.1.8-3.6ubuntu2 [55.1 kB]
Get:19 http://debian.lth.se/ubuntu bionic/main amd64 libsemanage-common all 
2.7-2build2 [6904 B]
Get:20 http://debian.lth.se/ubuntu bionic/main amd64 libsepol1 amd64 2.7-1 [251 
kB]
Get:21 http://debian.lth.se/ubuntu bionic/main amd64 libsemanage1 amd64 
2.7-2build2 [84.6 kB]
Get:22 http://debian.lth.se/ubuntu bionic/main amd64 libdb5.3 amd64 5.3.28-13.1 
[672 kB]
Get:23 http://debian.lth.se/ubuntu bionic/main amd64 libpam-modules-bin amd64 
1.1.8-3.6ubuntu2 [36.7 kB]
Get:24 http://debian.lth.se/ubuntu bionic/main amd64 libpam-modules 

[Touch-packages] [Bug 1762630] [NEW] Why does not python3 depend on dh-python?

[Markus Lindberg]

Public bug reported:

I get the following while trying to install python3 on Bionic.

dpkg-query: package 'dh-python' is not installed
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.

What I can tell, every other Ubuntu release has this dependency but not
Bionic.

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1762630

Title:
  Why does not python3 depend on dh-python?

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  I get the following while trying to install python3 on Bionic.

  dpkg-query: package 'dh-python' is not installed
  Use dpkg --info (= dpkg-deb --info) to examine archive files,
  and dpkg --contents (= dpkg-deb --contents) to list their contents.

  What I can tell, every other Ubuntu release has this dependency but
  not Bionic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1762630/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1761861] Re: dh-python dependency removal changing behaviour of installing virtualenv

[Markus Lindberg]

Why does not python3 depend on dh-python?

I get the following while trying to install python3:

dpkg-query: package 'dh-python' is not installed
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.

What I can tell, every other Ubuntu release has this dependency.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1761861

Title:
  dh-python dependency removal changing behaviour of installing
  virtualenv

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  root@6de0badbae8b:/# apt-get install --no-install-recommends virtualenv
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
ca-certificates libexpat1 libmpdec2 libpython3-stdlib libpython3.6-minimal 
libpython3.6-stdlib libssl1.1 mime-support openssl python-pip-whl python3 
python3-minimal
python3-pkg-resources python3-virtualenv python3.6 python3.6-minimal
  Suggested packages:
python3-doc python3-tk python3-venv python3-setuptools python3.6-venv 
python3.6-doc binutils binfmt-support
  Recommended packages:
bzip2 file xz-utils
  The following NEW packages will be installed:
ca-certificates libexpat1 libmpdec2 libpython3-stdlib libpython3.6-minimal 
libpython3.6-stdlib libssl1.1 mime-support openssl python-pip-whl python3 
python3-minimal
python3-pkg-resources python3-virtualenv python3.6 python3.6-minimal 
virtualenv
  0 upgraded, 17 newly installed, 0 to remove and 43 not upgraded.
  Need to get 7375 kB of archives.
  After this operation, 29.9 MB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://archive.ubuntu.com/ubuntu bionic/main amd64 libssl1.1 amd64 
1.1.0g-2ubuntu3 [1128 kB]
  Get:2 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython3.6-minimal 
amd64 3.6.5-3 [529 kB]
  Get:3 http://archive.ubuntu.com/ubuntu bionic/main amd64 libexpat1 amd64 
2.2.5-3 [80.2 kB]
  Get:4 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3.6-minimal 
amd64 3.6.5-3 [1425 kB]
  Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3-minimal 
amd64 3.6.5-2 [23.9 kB]
  Get:6 http://archive.ubuntu.com/ubuntu bionic/main amd64 mime-support all 
3.60ubuntu1 [30.1 kB]
  Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 libmpdec2 amd64 
2.4.2-1 [82.6 kB]
  Get:8 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython3.6-stdlib 
amd64 3.6.5-3 [1648 kB]
  Get:9 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3.6 amd64 
3.6.5-3 [186 kB]
  Get:10 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpython3-stdlib 
amd64 3.6.5-2 [7372 B]
  Get:11 http://archive.ubuntu.com/ubuntu bionic/main amd64 python3 amd64 
3.6.5-2 [8780 B]
  Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 openssl amd64 
1.1.0g-2ubuntu3 [532 kB]
  Get:13 http://archive.ubuntu.com/ubuntu bionic/main amd64 ca-certificates all 
20170717 [167 kB]
  Get:14 http://archive.ubuntu.com/ubuntu bionic/universe amd64 python-pip-whl 
all 9.0.1-2 [1379 kB]
  Get:15 http://archive.ubuntu.com/ubuntu bionic/main amd64 
python3-pkg-resources all 39.0.1-2 [98.8 kB]
  Get:16 http://archive.ubuntu.com/ubuntu bionic/universe amd64 
python3-virtualenv all 15.1.0+ds-1 [43.2 kB]
  Get:17 http://archive.ubuntu.com/ubuntu bionic/universe amd64 virtualenv all 
15.1.0+ds-1 [4376 B]
  Fetched 7375 kB in 14s (515 kB/s)
  debconf: delaying package configuration, since apt-utils is not installed
  Selecting previously unselected package libssl1.1:amd64.
  (Reading database ... 4416 files and directories currently installed.)
  Preparing to unpack .../0-libssl1.1_1.1.0g-2ubuntu3_amd64.deb ...
  Unpacking libssl1.1:amd64 (1.1.0g-2ubuntu3) ...
  Selecting previously unselected package libpython3.6-minimal:amd64.
  Preparing to unpack .../1-libpython3.6-minimal_3.6.5-3_amd64.deb ...
  Unpacking libpython3.6-minimal:amd64 (3.6.5-3) ...
  Selecting previously unselected package libexpat1:amd64.
  Preparing to unpack .../2-libexpat1_2.2.5-3_amd64.deb ...
  Unpacking libexpat1:amd64 (2.2.5-3) ...
  Selecting previously unselected package python3.6-minimal.
  Preparing to unpack .../3-python3.6-minimal_3.6.5-3_amd64.deb ...
  Unpacking python3.6-minimal (3.6.5-3) ...
  Selecting previously unselected package python3-minimal.
  Preparing to unpack .../4-python3-minimal_3.6.5-2_amd64.deb ...
  Unpacking python3-minimal (3.6.5-2) ...
  Selecting previously unselected package mime-support.
  Preparing to unpack .../5-mime-support_3.60ubuntu1_all.deb ...
  Unpacking mime-support (3.60ubuntu1) ...
  Selecting previously unselected package libmpdec2:amd64.
  Preparing to unpack .../6-libmpdec2_2.4.2-1_amd64.deb ...
  Unpacking libmpdec2:amd64 (2.4.2-1) ...
  Selecting previously unselected package 

[Touch-packages] [Bug 1754759] Lsusb.txt

[Markus Baumann]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1754759/+attachment/5078546/+files/Lsusb.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   

[Touch-packages] [Bug 1754759] WifiSyslog.txt

[Markus Baumann]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078557/+files/WifiSyslog.txt

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  

[Touch-packages] [Bug 1754759] ProcModules.txt

[Markus Baumann]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078554/+files/ProcModules.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   

[Touch-packages] [Bug 1754759] ProcInterrupts.txt

[Markus Baumann]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078553/+files/ProcInterrupts.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic 

[Touch-packages] [Bug 1754759] NetDevice.enp0s25.txt

[Markus Baumann]

apport information

** Attachment added: "NetDevice.enp0s25.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078547/+files/NetDevice.enp0s25.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   

[Touch-packages] [Bug 1754759] UdevDb.txt

[Markus Baumann]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1754759/+attachment/5078556/+files/UdevDb.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   

[Touch-packages] [Bug 1754759] RfKill.txt

[Markus Baumann]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1754759/+attachment/5078555/+files/RfKill.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   

[Touch-packages] [Bug 1754759] ProcCpuinfoMinimal.txt

[Markus Baumann]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078552/+files/ProcCpuinfoMinimal.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   

[Touch-packages] [Bug 1754759] PciNetwork.txt

[Markus Baumann]

apport information

** Attachment added: "PciNetwork.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078551/+files/PciNetwork.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   

[Touch-packages] [Bug 1754759] NetworkManager.conf.txt

[Markus Baumann]

apport information

** Attachment added: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078550/+files/NetworkManager.conf.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   

[Touch-packages] [Bug 1754759] NetDevice.wlp3s0.txt

[Markus Baumann]

apport information

** Attachment added: "NetDevice.wlp3s0.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078549/+files/NetDevice.wlp3s0.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   

[Touch-packages] [Bug 1754759] NetDevice.lo.txt

[Markus Baumann]

apport information

** Attachment added: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078548/+files/NetDevice.lo.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
  

[Touch-packages] [Bug 1754759] Lspci.txt

[Markus Baumann]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1754759/+attachment/5078545/+files/Lspci.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   

[Touch-packages] [Bug 1754759] IpAddr.txt

[Markus Baumann]

apport information

** Attachment added: "IpAddr.txt"
   https://bugs.launchpad.net/bugs/1754759/+attachment/5078542/+files/IpAddr.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   

[Touch-packages] [Bug 1754759] IwConfig.txt

[Markus Baumann]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078543/+files/IwConfig.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   

[Touch-packages] [Bug 1754759] JournalErrors.txt

[Markus Baumann]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078544/+files/JournalErrors.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A

[Touch-packages] [Bug 1754759] Dependencies.txt

[Markus Baumann]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078541/+files/Dependencies.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
  

[Touch-packages] [Bug 1754759] CurrentDmesg.txt

[Markus Baumann]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1754759/+attachment/5078540/+files/CurrentDmesg.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
  

[Touch-packages] [Bug 1754759] CRDA.txt

[Markus Baumann]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1754759/+attachment/5078539/+files/CRDA.txt

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xubuntu3822 F pulseaudio
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  MachineType: LENOVO 2333B15
  Package: network-manager 1.8.4-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   

[Touch-packages] [Bug 1754759] Re: LAN connection keeps connecting and disconnecting in an infinite loop

[Markus Baumann]

apport information

** Tags added: apport-collected

** Description changed:

  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop
  
  (No wireless network is configured.)
  
  The error did not occur on Xubuntu 16.04. The same situation occurs with
  Xubuntu installed on the SSD. I took the ISO for this bug report, in
  order to exclude wrong settings on the installed system.
  
  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
   Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
  nmcli-dev:
   DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
   wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  
--  ----
  
   lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  
--  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.7
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  xubuntu3822 F pulseaudio
+ CasperVersion: 1.387
+ DistroRelease: Ubuntu 17.10
+ IfupdownConfig:
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  auto lo
+  iface lo inet loopback
+ IpRoute:
+  default via 10.110.120.1 dev enp0s25 proto static metric 100 
+  10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
+  169.254.0.0/16 dev enp0s25 scope link metric 1000
+ LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
+ MachineType: LENOVO 2333B15
+ Package: network-manager 1.8.4-1ubuntu3
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
+ ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
+ PulseList:
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.13.0-21-generic N/A
+  linux-backports-modules-4.13.0-21-generic  N/A
+  linux-firmware 1.169.1
+ Tags:  artful
+ Uname: Linux 4.13.0-21-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 04/19/2017
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: G2ETA8WW (2.68 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 2333B15
+ dmi.board.vendor: LENOVO
+ 

[Touch-packages] [Bug 1754759] [NEW] LAN connection keeps connecting and disconnecting in an infinite loop

[Markus Baumann]

Public bug reported:

With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
- Boot from live-ISO
- Click on network icon in title bar and edit LAN-connection
- Change MTU from Auto to 1492
- Connect LAN cable
=> LAN network keeps connecting and disconnecting in an infinite loop

(No wireless network is configured.)

The error did not occur on Xubuntu 16.04. The same situation occurs with
Xubuntu installed on the SSD. I took the ISO for this bug report, in
order to exclude wrong settings on the installed system.

This is my first bug report - I hope I did not do too much wrong. If
necessary, I can provide more information.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: network-manager 1.8.4-1ubuntu3
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: amd64
CasperVersion: 1.387
CurrentDesktop: XFCE
Date: Fri Mar  9 20:26:21 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 10.110.120.1 dev enp0s25 proto static metric 100 
 10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
 169.254.0.0/16 dev enp0s25 scope link metric 1000
LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE   STATE
  ACTIVE-PATH  SLAVE 
 Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  802-3-ethernet  
1520627169  Fr 09 Mär 2018 20:26:09 UTC  yes  4294966297no  
  /org/freedesktop/NetworkManager/Settings/1  yes enp0s25  activated  
/org/freedesktop/NetworkManager/ActiveConnection/32  --
nmcli-dev:
 DEVICE   TYPE  STATE DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
 enp0s25  ethernet  connected /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  db135360-f229-3472-bd3a-eb8d6bc8b601  
/org/freedesktop/NetworkManager/ActiveConnection/32 
 wlp3s0   wifi  disconnected  /org/freedesktop/NetworkManager/Devices/3  -- 
 ----   
   
 lo   loopback  unmanaged /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful xubuntu-exp

-- 
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/1754759

Title:
  LAN connection keeps connecting and disconnecting in an infinite loop

Status in network-manager package in Ubuntu:
  New

Bug description:
  With Xubuntu 17.10 the following problem occurs on a Lenovo X230 Laptop:
  - Boot from live-ISO
  - Click on network icon in title bar and edit LAN-connection
  - Change MTU from Auto to 1492
  - Connect LAN cable
  => LAN network keeps connecting and disconnecting in an infinite loop

  (No wireless network is configured.)

  The error did not occur on Xubuntu 16.04. The same situation occurs
  with Xubuntu installed on the SSD. I took the ISO for this bug report,
  in order to exclude wrong settings on the installed system.

  This is my first bug report - I hope I did not do too much wrong. If
  necessary, I can provide more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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: amd64
  CasperVersion: 1.387
  CurrentDesktop: XFCE
  Date: Fri Mar  9 20:26:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 10.110.120.1 dev enp0s25 proto static metric 100 
   10.110.120.0/24 dev enp0s25 proto kernel scope link src 10.110.120.57 metric 
100 
   169.254.0.0/16 dev enp0s25 scope link metric 1000
  LiveMediaBuild: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   

[Touch-packages] [Bug 1648107] Re: $XAUTHORITY should move into $XDG_RUNTIME_DIR

[Markus Kuhn]

While we are at it, we could probably also set

  ICEAUTHORITY=$XDG_RUNTIME_DIR/ICEauthority

in a similar fashion, as this is the equivalent cookie facility for X11
client-client communication.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1648107

Title:
  $XAUTHORITY should move into $XDG_RUNTIME_DIR

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Historically, the X authority file was placed into $HOME/.Xauthority
  such that X11 clients on remote servers could access it in
  environments in which $HOME is located on a network file system.

  Today, this practice has become an anachronism that causes far more
  problems than it solves:

  a) Remote X11 clients are typically started today via "ssh -X", which
  emulates its own X11 server port $DISPLAY and therefore always creates
  its own X authority file entry on the remote server. Therefore, there
  is no longer any practical benefit from having the X authority file
  located in $HOME.

  b) If $HOME is on a network file system that implements "root squash",
  then commands such as "sudo xterm" or "sudo wireshark" won't work to
  start an X client with root privileges, as root is not able to read
  ~/.Xauthority via NFS. :-(

  c) If $HOME is on a network file system with Kerberos authentication,
  then users can easily get locked out by their screensavers once the
  Kerberos ticket expires. This is because some screen lockers (e.g.,
  gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome-
  screensaver/gnome-screensaver-dialog) in order to ask the user of a
  locked screen for their password. Such a tool needs to access
  $XAUTHORITY right before it can display the password prompt, which
  will fail if the user's Kerberos ticket has expired (e.g. because a
  machine was suspended for 24 hours and therefore the ticket was not
  refreshed automatically on time). Without the ability to ask for a
  password, the screensaver then cannot call pam_krb5 to renew the
  user's Kerberos ticket, and the user remains locked out in a deadlock
  situation. :-(

  Both b) and c) are regular reasons for support requests in
  educational/corporate Linux environments with $HOME on Kerberized NFS.

  The solution is simple. Instead of $HOME/.Xauthority, just use in
  future $XDG_RUNTIME_DIR/xauthority as the location of the X authority
  file. (In case $XDG_RUNTIME_DIR/ does not exist, /tmp/xauthority-$USER
  might be a suitable fallback option.)

  According to https://standards.freedesktop.org/basedir-spec/basedir-
  spec-latest.html the $XDG_RUNTIME_DIR has all the right properties for
  holding the X authority file: it is always located in a local tmpfs
  filesystem, guaranteed to be accessible only to the current user, and
  will be wiped when the user has closed all sessions.

  On modern Linux systems, pam_systemd usually creates
  XDG_RUNTIME_DIR=/run/user/$UID, and wipes it in the end.

  (Note that according to https://standards.freedesktop.org/basedir-spec
  /basedir-spec-latest.html you should set the "sticky bit" on any files
  created in $XDG_RUNTIME_DIR whose timestamp is not updated regularly.)

  Feature request: please provide an option for LightDM to do the
  equivalent of

export XAUTHORITY=$XDG_RUNTIME_DIR/xauthority
chmod +t $XAUTHORITY

  and encourage Linux distribution maintainers to set this option by
  default, such that ~/.Xauthority is no longer used.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

[Markus Birth]

*** This bug is a duplicate of bug 1726930 ***
https://bugs.launchpad.net/bugs/1726930

** This bug has been marked a duplicate of bug 1726930
   System fails to start (boot) on battery due to read-only root file-system

-- 
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/1725458

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

Status in systemd package in Ubuntu:
  New

Bug description:
  After not touching my notebook since 30th September (where I did the
  dist-upgrade to artful and installed all available updates), I did all
  available updates today (20th October) and the system didn't boot
  after that.

  The last message I see is "Reached target Bluetooth". Before that,
  there are several failed services. GDM doesn't come up.

  After logging in on tty2, I saw that the root partition was mounted
  read-only. Inspecting the messages of e.g. systemd-resolved shows that
  it didn't start because of the read-only filesystem. After remounting
  it fw, I was able to restart the daemons and could also start GDM and
  login fine.

  My fstab shows:

  UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4
  errors=remount-ro 0   1

  
  The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 21:46:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-26 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
  dmi.bios.date: 09/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  dmi.board.vendor: HP
  dmi.board.version: 33.76
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Markus Schade]

the updates-proposed build works in my case as well

-- 
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/1727301

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Zesty:
  Invalid
Status in systemd source package in Artful:
  Invalid
Status in systemd source package in Bionic:
  Invalid

Bug description:
  [Impact]

   * Setting [Link] MTUBytes= in .network file has a side-effect of
  overflowing and setting NOARP flag. This is not intended behaviour /
  regression.

   * Trying to fix above by setting ARP=on fails to work as tristate is
  incorrectly acted upon by unconditionally adding NOARP flag

   * This is a regression in -updates.

  [Affected Users]

   * Those who use networkd
   
   * Do not use netplan (as that sets mtubytes in the .link files, not in the 
.network)

   * Specify MTUBytes in .network file (not in the .link file)

  [Test Case]

   * Configure an ethernet device with a .network file alone
   * e.g. Match by mac address and perform DHCP
   * Add [Link] section to the .network file which changes MTUBytes
   * Device brought up using this configuration should not have NOAPR flag in 
the output of iproute link output

   * Further add ARP=off to that .network file, the link should have NOARP flag
   * Further add ARP=on to that .network file, the link should not have NOARP 
flag

  A test script is attached, that given an interface can abuse it to
  validate all of the above.

  [Regression Potential]

   * These are upstream fixes for ARP= key that are part of zesty and up

  [Other Info]

   * Upstream fixes
  
https://github.com/systemd/systemd/commit/b8b40317d0355bc70bb23a6240a36f3630c4952b.patch
  
https://github.com/systemd/systemd/commit/1ed1f50f8277df07918e13cba3331a114eaa6fe3.patch

   * Original bug report

  this breaks existing configurations with bonding on upgrading from
  229-4ubuntu19 to 229-4ubuntu20 on xenial

  as bond interfaces are now by default configured without ARP. Hence
  you suddenly lose network connectivity on upgrade. Very bad for a SRU.

  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.

  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.

  pre-upgrade:

  eth0: 
  eth1: 
  bond0: 

  post-upgrade:
  eth0: 
  eth1: 
  bond0: 

  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Markus Schade]

The ppa package works for my use case. Maybe add this test-case to QA.

-- 
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/1727301

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Zesty:
  Confirmed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * Incomplete cherrypick of ARP functionality in networkd resulted in
  an undesired side-effect, specifically NOARP flag started to be
  applied unconditionally, specifically when it should not have,
  resulting in loss of network connectivity.

  * This is a regression in -updates.

  [Test Case]

   * Configure a bond using networkd
   * Upgrade
   * Make sure NOARP flag is not set on the interfaces / bond

  [Regression Potential]

   * This is an upstream fix for this issue.

  [Other Info]
   
   * Upstream fix
  
https://github.com/systemd/systemd/commit/1ed1f50f8277df07918e13cba3331a114eaa6fe3.patch
   
   * Original bug report

  this breaks existing configurations with bonding on upgrading from
  229-4ubuntu19 to 229-4ubuntu20 on xenial

  as bond interfaces are now by default configured without ARP. Hence
  you suddenly lose network connectivity on upgrade. Very bad for a SRU.

  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.

  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.

  pre-upgrade:

  eth0: 
  eth1: 
  bond0: 

  post-upgrade:
  eth0: 
  eth1: 
  bond0: 

  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1577575] Re: NFS share does not mount on boot using fstab

[Markus Birth]

This bug reappeared (with cifs/smb mounts in fstab) after upgrade to
17.10 "artful" for me. The fix in #5 worked just fine.

-- 
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/1577575

Title:
  NFS share does not mount on boot using fstab

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  What I expected to happen?

  I want an NFS share to be mounted on startup using

  
  192.168.178.66:/media/captainplanet/7EF8B26FF8B22575/ 
/media/captainplanet/banane/ nfs rw 0 0

  What happened instead?

  It does not mount on startup. Systemd waits 91sec instead and finally
  starts after failing.

  I can successfully mount the NFS share with

  sudo mount 192.168.178.66:/media/captainplanet/7EF8B26FF8B22575
  /media/captainplanet/banane/

  When I try to shutdown Xubuntu it hangs forever. Unmounting the NFS
  share manually before shutdown fixes the second problem.

  
  Do you need more information?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May  2 23:10:50 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (10 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20DM003XUK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=eece9973-0430-4a60-9291-9a994782bf86 ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JFET44WW(1.21)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20DM003XUK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJFET44WW(1.21):bd08/26/2015:svnLENOVO:pn20DM003XUK:pvrThinkPadS3Yoga14:rvnLENOVO:rn20DM003XUK:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20DM003XUK
  dmi.product.version: ThinkPad S3 Yoga 14
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1727301] Re: 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Markus Schade]

the networking is configured via systemd-networkd.
bonding module is loaded with 'max_bonds=0' to address upcoming systemd change
https://github.com/systemd/systemd/issues/6184

pre-upgrade:

# networkctl 
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  2 eth0 ether  carrier configuring
  3 eth1 ether  carrier configuring
  4 bond0ether  routableconfigured
  5 bond0.200ether  routableconfigured

# ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:  mtu 9000 qdisc mq master bond0 
state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
3: eth1:  mtu 9000 qdisc mq master bond0 
state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
4: bond0:  mtu 9000 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
5: bond0.200@bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff

interfaces(.d) and netplan are empty and unused/disabled

/etc/systemd/network:

# cat eth1.network 
[Match]
Name=eth1

[Network]
Bond=bond0

# cat eth0.network 
[Match]
Name=eth0

[Network]
Bond=bond0

# cat bond0.netdev 
[NetDev]
Name=bond0
Kind=bond

[Bond]
Mode=802.3ad
MIIMonitorSec=0.1s
LACPTransmitRate=fast
UpDelaySec=0.2s
DownDelaySec=0.2s

# cat bond0.network 
[Match]
Name=bond0

[Address]
Address=192.168.1.100/24

[Route]
Gateway=192.168.1.1

[Network]
VLAN=bond0.200

[Link]
MTUBytes=9000

# cat bond0.200.netdev 
[NetDev]
Name=bond0.200
Kind=vlan

[VLAN]
Id=200

# cat bond0.200.network 
[Match]
Name=bond0.200

[Address]
Address=10.10.0.100/16

[Route]
Gateway=10.10.0.1

[Link]
MTUBytes=9000

After upgrade:

# networkctl 
IDX LINK TYPE   OPERATIONAL SETUP 
  1 lo   loopback   carrier unmanaged 
  2 eth0 ether  carrier configuring
  3 eth1 ether  carrier configuring
  4 bond0ether  routableconfigured
  5 bond0.200ether  routableconfigured

However, the link of eth0, eth1 and the bond and vlan interface changes
to NOARP

# ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
3: eth1:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
4: bond0:  mtu 9000 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff
5: bond0.200@bond0:  mtu 1500 qdisc 
noqueue state UP mode DEFAULT group default qlen 1000
link/ether 5a:42:ff:c5:26:61 brd ff:ff:ff:ff:ff:ff


** Bug watch added: github.com/systemd/systemd/issues #6184
   https://github.com/systemd/systemd/issues/6184

-- 
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/1727301

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  this breaks existing configurations with bonding on upgrading from
  229-4ubuntu19 to 229-4ubuntu20 on xenial

  as bond interfaces are now by default configured without ARP. Hence
  you suddenly lose network connectivity on upgrade. Very bad for a SRU.

  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.

  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.

  pre-upgrade:

  eth0: 
  eth1: 
  bond0: 

  post-upgrade:
  eth0: 
  eth1: 
  bond0: 

  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

To manage 

[Touch-packages] [Bug 1727301] [NEW] 229-4ubuntu20 added ARP option breaks existing bonding interfaces

[Markus Schade]

Public bug reported:

this breaks existing configurations with bonding on upgrading from
229-4ubuntu19 to 229-4ubuntu20 on xenial

as bond interfaces are now by default configured without ARP. Hence you
suddenly lose network connectivity on upgrade. Very bad for a SRU.

Plus adding "ARP=yes" to the Link section of a .network file does not
work.

Before this update, bond interfaces (specifically 802.3ad) were
defaulting to ARP enabled. After the upgrade, they are created with
NOARP set on the link.

pre-upgrade:

eth0: 
eth1: 
bond0: 

post-upgrade:
eth0: 
eth1: 
bond0: 

Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

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


** Tags: regression-updates

** Description changed:

+ this breaks existing configurations with bonding on upgrading from
+ 229-4ubuntu19 to 229-4ubuntu20 on xenial
  
- this breaks existing configurations with bonding on upgrading from 
229-4ubuntu19 to 229-4ubuntu20
- as bond interfaces are now by default configured without ARP. Hence you 
suddenly lose network connectivity on upgrade. Very bad for a SRU.
+ as bond interfaces are now by default configured without ARP. Hence you
+ suddenly lose network connectivity on upgrade. Very bad for a SRU.
  
  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.
  
  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.
  
  pre-upgrade:
  
  eth0: 
  eth1: 
  bond0: 
  
  post-upgrade:
  eth0: 
  eth1: 
  bond0: 
  
  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
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/1727301

Title:
  229-4ubuntu20 added ARP option breaks existing bonding interfaces

Status in systemd package in Ubuntu:
  New

Bug description:
  this breaks existing configurations with bonding on upgrading from
  229-4ubuntu19 to 229-4ubuntu20 on xenial

  as bond interfaces are now by default configured without ARP. Hence
  you suddenly lose network connectivity on upgrade. Very bad for a SRU.

  Plus adding "ARP=yes" to the Link section of a .network file does not
  work.

  Before this update, bond interfaces (specifically 802.3ad) were
  defaulting to ARP enabled. After the upgrade, they are created with
  NOARP set on the link.

  pre-upgrade:

  eth0: 
  eth1: 
  bond0: 

  post-upgrade:
  eth0: 
  eth1: 
  bond0: 

  Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
  2017 x86_64 x86_64 x86_64 GNU/Linux

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

[Markus Schade]

Actually there is. Before this update, bond interfaces (specifically
802.3ad) were defaulting to ARP enabled. After the upgrade, they are
created with NOARP set on the link.

pre-upgrade:

eth0:  
eth1: 
bond0:  

post-upgrade:
eth0:  
eth1: 
bond0:  

Linux cnode11 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
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/1709135

Title:
  add bond primary parameter

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in nplan source package in Zesty:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in nplan source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

[Markus Schade]

I opened LP #1727301 to track this further

-- 
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/1709135

Title:
  add bond primary parameter

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in nplan source package in Zesty:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in nplan source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1709135] Re: add bond primary parameter

[Markus Schade]

this breaks existing configurations with bonding on upgrading from 
229-4ubuntu19 to 229-4ubuntu20
as bond interfaces are now by default configured without ARP. Hence you 
suddenly lose network connectivity on upgrade. Very bad for a SRU.

Plus adding "ARP=yes" to the Link section of a .network file does not
work.

-- 
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/1709135

Title:
  add bond primary parameter

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in nplan source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Fix Released
Status in nplan source package in Zesty:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed
Status in nplan source package in Artful:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Some complex bond configurations require setting a "primary" interface for 
the bond, or setting this greatly improves performance on the network bond.

  [Test case]
  See below for a configuration example.
  1) Apply configuration on a system with netplan.
  2) Run 'netplan apply'
  3) Validate that netplan apply does not return with an error
  4) Validate that netplan properly sets the "primary_slave" value on the bond. 
This can be verified by looking at /sys/class/net//bonding/primary_slave.
  5) Validate that there are no parsing errors from systemd-networkd in the 
journalctl

  [Regression potential]
  If existing configuration fails to be parsed, or lack of primary interface 
breaks configuration for existing bonds, this would be a regression caused by 
this update.

  ---

  ifenslave/eni support a bond parameter:  bond-primary which accepts an
  interface name that can be used to tell the kernel bonding driver
  which interface it should preferred in active-backup (and other
  modes).  This config option is missing in netplan.

   % cat bond-primary.yaml
  network:
    version: 2
    ethernets:
  eth0:
    match:
  driver: virtio
  ens4:
    match:
  driver: e1000
    bonds:
  bond0:
    parameters:
  mode: active-backup
  mii-monitor-interval: 100
  primary: e1000
    dhcp4: true

  % ./generate -r `pwd`/target
  Error in network definition 
/home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 
column 8: unknown key primary

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Markus Birth]

Confirmed on a hp Spectre x360 13-4104ng.

On battery power, the system DOESN'T boot up.

With the charger connected, the system boots up just fine.


See https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725458 for my 
apport logs.

-- 
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/1726930

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for 

[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

[Markus Birth]

Yes, this seems to be a duplicate of your bug.

On battery power, the system DOESN'T boot up.

With the charger connected, the system boots up just fine.

-- 
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/1725458

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

Status in systemd package in Ubuntu:
  New

Bug description:
  After not touching my notebook since 30th September (where I did the
  dist-upgrade to artful and installed all available updates), I did all
  available updates today (20th October) and the system didn't boot
  after that.

  The last message I see is "Reached target Bluetooth". Before that,
  there are several failed services. GDM doesn't come up.

  After logging in on tty2, I saw that the root partition was mounted
  read-only. Inspecting the messages of e.g. systemd-resolved shows that
  it didn't start because of the read-only filesystem. After remounting
  it fw, I was able to restart the daemons and could also start GDM and
  login fine.

  My fstab shows:

  UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4
  errors=remount-ro 0   1

  
  The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 21:46:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-26 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
  dmi.bios.date: 09/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  dmi.board.vendor: HP
  dmi.board.version: 33.76
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

[Markus Birth]

The change in the fstab seems to have worked only once. Today, it
doesn't boot again (with the changed fstab). I've tried switching from
UEFI to Legacy mode without luck, too.

-- 
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/1725458

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

Status in systemd package in Ubuntu:
  New

Bug description:
  After not touching my notebook since 30th September (where I did the
  dist-upgrade to artful and installed all available updates), I did all
  available updates today (20th October) and the system didn't boot
  after that.

  The last message I see is "Reached target Bluetooth". Before that,
  there are several failed services. GDM doesn't come up.

  After logging in on tty2, I saw that the root partition was mounted
  read-only. Inspecting the messages of e.g. systemd-resolved shows that
  it didn't start because of the read-only filesystem. After remounting
  it fw, I was able to restart the daemons and could also start GDM and
  login fine.

  My fstab shows:

  UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4
  errors=remount-ro 0   1

  
  The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 21:46:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-26 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
  dmi.bios.date: 09/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  dmi.board.vendor: HP
  dmi.board.version: 33.76
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1725458] Re: System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

[Markus Birth]

I changed my fstab from

UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 errors=remount-ro 0 1

to

UUID=a936dbe9-5ab5-4272-aaae-d22030824373 / ext4 rw,errors=remount-ro 0
1

and it now boots fine again. I don't know why that is necessary now and
why the update didn't notify me or made the change automatically.

-- 
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/1725458

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

Status in systemd package in Ubuntu:
  New

Bug description:
  After not touching my notebook since 30th September (where I did the
  dist-upgrade to artful and installed all available updates), I did all
  available updates today (20th October) and the system didn't boot
  after that.

  The last message I see is "Reached target Bluetooth". Before that,
  there are several failed services. GDM doesn't come up.

  After logging in on tty2, I saw that the root partition was mounted
  read-only. Inspecting the messages of e.g. systemd-resolved shows that
  it didn't start because of the read-only filesystem. After remounting
  it fw, I was able to restart the daemons and could also start GDM and
  login fine.

  My fstab shows:

  UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4
  errors=remount-ro 0   1

  
  The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 21:46:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-26 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
  dmi.bios.date: 09/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  dmi.board.vendor: HP
  dmi.board.version: 33.76
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre x360 Convertible
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1725458] [NEW] System unbootable with root fs mounted ro after update to systemd 234-2ubuntu12 (from 234-2ubuntu10) on artful

[Markus Birth]

Public bug reported:

After not touching my notebook since 30th September (where I did the
dist-upgrade to artful and installed all available updates), I did all
available updates today (20th October) and the system didn't boot after
that.

The last message I see is "Reached target Bluetooth". Before that, there
are several failed services. GDM doesn't come up.

After logging in on tty2, I saw that the root partition was mounted
read-only. Inspecting the messages of e.g. systemd-resolved shows that
it didn't start because of the read-only filesystem. After remounting it
fw, I was able to restart the daemons and could also start GDM and login
fine.

My fstab shows:

UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4errors
=remount-ro 0   1


The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Fri Oct 20 21:46:36 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-26 (451 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Spectre x360 Convertible
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
dmi.bios.date: 09/28/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.43
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 81A1
dmi.board.vendor: HP
dmi.board.version: 33.76
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd09/28/2016:svnHP:pnHPSpectrex360Convertible:pvr:rvnHP:rn81A1:rvr33.76:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
dmi.product.name: HP Spectre x360 Convertible
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug artful

-- 
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/1725458

Title:
  System unbootable with root fs mounted ro after update to systemd
  234-2ubuntu12 (from 234-2ubuntu10) on artful

Status in systemd package in Ubuntu:
  New

Bug description:
  After not touching my notebook since 30th September (where I did the
  dist-upgrade to artful and installed all available updates), I did all
  available updates today (20th October) and the system didn't boot
  after that.

  The last message I see is "Reached target Bluetooth". Before that,
  there are several failed services. GDM doesn't come up.

  After logging in on tty2, I saw that the root partition was mounted
  read-only. Inspecting the messages of e.g. systemd-resolved shows that
  it didn't start because of the read-only filesystem. After remounting
  it fw, I was able to restart the daemons and could also start GDM and
  login fine.

  My fstab shows:

  UUID=a936dbe9-5ab5-4272-aaae-d22030824373 /   ext4
  errors=remount-ro 0   1

  
  The UUID is correct as "mount / -o remount,rw" works fine. Booting with the 
previous kernel doesn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 20 21:46:36 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-26 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2073 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c7d Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=a936dbe9-5ab5-4272-aaae-d22030824373 ro text
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-09-30 (20 days ago)
  dmi.bios.date: 09/28/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.43
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81A1
  

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Markus Ketterl]

I have the problem too. After the dhcp lease is expired the avahi-daemon
or something else doesn't renew the dhcp lease. It helps to request an
ip address manually:

# sudo dhclient 
sudo dhclient enp3s0

Configure the lease time on your dhcp server to 86400 seconds (one day)
and it should help the most of us to work without problems for a day.
But it doesn't solve the problem.

** Changed in: avahi (Ubuntu)
   Status: Invalid => New

-- 
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/1586528

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1644996] Re: logrotate config uses syslog group

[Markus Zoeller (markus_z)]

As mentioned in the original description, another workaround is:
```
apt install -y rsyslog
```

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1644996

Title:
  logrotate config uses syslog group

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  The default logrotate config uses the "syslog" group.

  > # use the syslog group by default, since this is the owning group
  > # of /var/log/syslog.
  > su root syslog

  This is not correct anymore since 16.04, because:

  1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets 
installed via rsyslog
  2. The owning group is actually "adm".

  This results in logrotate terminating with the following error during
  cron.daily run:

  
  run-parts -v /etc/cron.daily
  run-parts: executing /etc/cron.daily/logrotate
  error: /etc/logrotate.conf:7 unknown group 'syslog'

  And can be fixed by changing syslog to adm group.

  This is not present when rsyslog is installed, but only because that package 
creates the syslog group. This is a common bug in lighter environments, like 
Docker, where syslog-ng is a common choice instead of rsyslog, like in this 
issue: 
  https://github.com/phusion/baseimage-docker/issues/338

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot

[Markus Letschka]

That finally solved it for me, thank you @Eberhard and @all for looking
into this and sharing your insights!

A few notes:

* in addition, I manually deleted file /etc/X11/Xsession.d/20dbus_xdg-
runtime which comes with package dbus-user-session (and is actually the
only file of the package) but was not removed on uninstall (Idk whether
this step is always neccessary)

* logout/login was not sufficient to see this solved. Full reboot was
required.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1689825

Title:
  gnome-keyring not unlocked on boot

Status in chromium-browser package in Ubuntu:
  Invalid
Status in flatpak package in Ubuntu:
  Invalid
Status in gdm package in Ubuntu:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in libgnome-keyring package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  1) Release: 16.04.2
  2) gnome-keyring: 3.18.3-0ubuntu2
  3) Login. gnome-keyring unlocks "login" features including for google chrome
  4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no 
secure password features(sync) functioning.

  For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long
  time (maybe 2 minutes) to start. Once chrome is started, I am not able
  to sync and any secure password features are broken. I found out this
  is due to gnome-keyring not being unlocked at login. There's also no
  way to unlock the "login" portion of the keyring from the running
  daemon by default. I have to kill the gnome-keyring process and start
  without "--login" as a parameter. Then the "login" section shows up
  which I'm able to unlock. From there chrome starts up instantly but
  asks the following:

  Enter password to unlock your login keyring
  The login keyring did not get unlocked when you logged into your computer

  After that, all of it's sync and secure features are functional.

  Starting google-chrome-stable from a command line at boot without
  running the above workaround shows the following error messages:

  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  Gkr-Message: secret service operation failed: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.
  [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to 
decrypt token for service AccountId-108842767310111573264
  [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore 
security token.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-keyring 3.18.3-0ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed May 10 09:43:37 2017
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1701068] Re: motd.ubuntu.com currently shows media item (HBO's Silicon Valley using Ubuntu)

[Markus Ueberall]

Just my 2 cents:
In general, publishing important security/maintenance related notices by means 
of https://motd.ubuntu.com sounds like a good idea (especially if you don't use 
canonical-livepatch in case of critical security hazards), but I'd strongly 
suggest to allow for client side configuration/filtering by means of tags, e.g.,

 * [16.10][maintenance] Ubuntu 16.10 will reach end of life on […] July 20, 2017
 * [16.04][security][<4.4.0-83] Please consider updating your kernel ASAP

(The second example would require version based comparisons, but you get the 
idea.)
There's no need to disclose any client specific information, and it won't hurt 
to transfer a few bytes more.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/1701068

Title:
  motd.ubuntu.com currently shows media item (HBO's Silicon Valley using
  Ubuntu)

Status in base-files package in Ubuntu:
  Opinion

Bug description:
  In Ubuntu 17.04 or newer, there is a script at /etc/update-motd.d/50
  -motd-news that reads https://motd.ubuntu.com/ and displays that text
  with the rest of the MOTD.

  Currently, https://motd.ubuntu.com shows a news item about HBO's Silicon 
Valley which has a reference to Ubuntu. 
  Instead, https://motd.ubuntu.com should show relevant items to those that 
  use Ubuntu Server (relevant security issues, etc), instead of items for 
desktop users.

  =
  Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64)

   * Documentation:  https://help.ubuntu.com
   * Management: https://landscape.canonical.com
   * Support:https://ubuntu.com/advantage

   * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow,
     Keras & React Native on Ubuntu
     - https://ubu.one/HBOubu
  ==

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: base-files 9.6ubuntu13
  ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15
  Uname: Linux 4.10.0-24-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed Jun 28 12:31:24 2017
  InstallationDate: Installed on 2017-05-02 (56 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: base-files
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1605189] Re: Authentication is required for suspending the system

[Markus Kwaśnicki]

I also went into this issue "system is asking for authentication to
suspend" running Xubuntu 17.04 Zesty Zapus.

But luckily I figured out, this behaviour came when I set "lock session
automatically when screensaver is activated" in the security tab of XFCE
power management. Setting it back to "never", suspending the system is
working without authentication again.

Hope that hint helps finding some better solution.

-- 
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/1605189

Title:
  Authentication is required for suspending the system

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Automatic suspend from the xfce power manager does not work, as a
  window opens and asks for my password. Well, if it wants to suspend
  the system after a given timeout, I cannot enter my password as I'm
  not in front of my system then. Once I'm able to enter my password it
  is too late to run the suspend action.

  The window asking for my password prints:

  Password: 

  Details

  Action: org.freedesktop.login1.suspend
  Vendor: The systemd project

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu7
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Jul 21 13:13:12 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-08-17 (703 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: LENOVO 4236ML1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=/dev/mapper/ubuntu--vg-root ro intel_pstate=enable
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to xenial on 2016-05-28 (53 days ago)
  dmi.bios.date: 07/05/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET76WW (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4236ML1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236ML1:pvrThinkPadT420:rvnLENOVO:rn4236ML1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4236ML1
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 919200] Re: Doesn't know system default layout/variant

[Markus J Schmidt]

*** This bug is a duplicate of bug 1051288 ***
https://bugs.launchpad.net/bugs/1051288

** This bug has been marked a duplicate of bug 1051288
   LightDM assumes there's only ONE system default layout

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/919200

Title:
  Doesn't know system default layout/variant

Status in Light Display Manager:
  Fix Released
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  lightdm_get_layout does not return the correct system default keyboard
  layout/variant.

  For that, pitti says we need to access
  xkl_config->layouts[0]/xkl_config->variants[0].

  Currently, we just grab the first layout returned from
  xkl_config_registry_foreach_layout, which only returns the available
  layouts, not the configured layouts.  So "us" will always be first
  there.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp