[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault

[Denys Fedoryshchenko]

Here is more meaningful result from valgrind with dbgsym present

** Attachment added: "vagrind output"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5508373/+files/valgrind-bug.txt

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

Title:
  systemd-resolve segfault

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-resolve keep crashing and it is very annoying as sometimes it
  severely interrupt normal dns resolving.

  Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
  Typical error in dmesg: 
  systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 
7ffe2fd0b758 error 15

  apport hints me that problem is related to mdns

  #3  0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd
  /libsystemd-shared-245.so

  It might be (or not) related that some hosts with mdns in my network
  have ipv6 enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
  Uname: Linux 5.4.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  1 08:22:51 2021
  InstallationDate: Installed on 2018-12-05 (938 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X399-E GAMING
  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.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+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 1794517] Re: Empty Display property in org.freedesktop.login1.session

[Valentyna]

Problem still exists.

** Tags added: focal

** Changed in: systemd (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Empty Display property in org.freedesktop.login1.session

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.04 when get property of Display variable using DBus
  org.freedesktop.login1.session get empty value.

  In Ubuntu 16.04 release these values isn`t empty and get for example
  Display = :0.

  I use:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Package info:

  Package: systemd
  Version: 237-3ubuntu10.3
  Priority: important
  Section: admin
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 12,9 MB
  Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), 
libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), 
libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 
0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), 
libselinux1 (>= 2.1.9)
  Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), 
libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), 
libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), 
util-linux (>= 2.27.1), mount (>= 2.26), adduser, procps
  Recommends: libpam-systemd, dbus, networkd-dispatcher
  Suggests: systemd-container, policykit-1
  Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 
1.68~), systemd-shim (<< 10-3~), udev (<< 228-5)
  Replaces: udev (<< 228-5)
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Task: minimal, ubuntu-core
  Supported: 5y
  Download-Size: 2 947 kB
  APT-Manual-Installed: yes
  APT-Sources: http://my.repo/ubuntu-current bionic-updates/main i386 Packages
  Description: system and service manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1794517/+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 1794516] Re: systemd-logind does not track all user processes

[Valentyna]

The problem still exists.

** Tags added: focal

** Changed in: systemd (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  systemd-logind does not track all user processes

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04(xenial) release all user processes are in session
  scope for example:

  └─user.slice
    └─user-200463.slice
  ├─user@200463.service
  │ └─init.scope
  │   ├─5886 /lib/systemd/systemd --user
  │   └─5888 (sd-pam)
  └─session-c2.scope
    ├─  419 bash
    ├─  471 mc
    ├─  473 bash -rcfile .bashrc
    ├─ 1432 bash
    ├─ 1455 mc
    ├─ 1457 bash -rcfile .bashrc
    ├─ 1915 /usr/sbin/sssd -D -f

  In Ubuntu 18.04 (bionic) some processes are in session scope and other
  are in user service for example:

  ├─user.slice
  │ ├─user-200463.slice
  │ │ ├─session-84.scope
  │ │ │ ├─14992 gdm-session-worker [pam/gdm-password]
  │ │ │ ├─15013 /usr/bin/gnome-keyring-daemon --daemonize --login
  │ │ │ ├─15057 /usr/lib/gdm3/gdm-x-session --run-script env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
  │ │ │ ├─15059 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/200463/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  │ │ │ ├─15114 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu
  │ │ │ ├─15205 /usr/bin/ssh-agent /usr/bin/im-launch env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
  │ │ │ ├─15317 /usr/bin/gnome-shell
  │ │ │ ├─15326 /usr/bin/pulseaudio --start --log-target=syslog
  │ │ │ ├─15345 ibus-daemon --xim --panel disable
  │ │ │ ├─15349 /usr/lib/ibus/ibus-dconf
  │ │ │ ├─15353 /usr/lib/ibus/ibus-x11 --kill-daemon
  │ │ │ ├─15417 /usr/lib/gnome-settings-daemon/gsd-power
  │ │ │ ├─15419 /usr/lib/gnome-settings-daemon/gsd-print-notifications
  │ │ │ ├─15420 /usr/lib/gnome-settings-daemon/gsd-rfkill
  │ │ │ ├─15423 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  │ │ │ ├─15425 /usr/lib/gnome-settings-daemon/gsd-sharing
  │ │ │ ├─15431 /usr/lib/gnome-settings-daemon/gsd-smartcard
  │ │ │ ├─15434 /usr/lib/gnome-settings-daemon/gsd-xsettings
  │ │ │ ├─15439 /usr/lib/gnome-settings-daemon/gsd-wacom
  │ │ │ ├─15442 /usr/lib/gnome-settings-daemon/gsd-sound
  │ │ │ ├─15452 /usr/lib/gnome-settings-daemon/gsd-clipboard
  │ │ │ ├─15454 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
  │ │ │ ├─15457 /usr/lib/gnome-settings-daemon/gsd-datetime
  │ │ │ ├─15461 /usr/lib/gnome-settings-daemon/gsd-color
  │ │ │ ├─15464 /usr/lib/gnome-settings-daemon/gsd-keyboard
  │ │ │ ├─15465 /usr/lib/gnome-settings-daemon/gsd-housekeeping
  │ │ │ ├─15469 /usr/lib/gnome-settings-daemon/gsd-mouse
  │ │ │ ├─15472 /usr/lib/gnome-settings-daemon/gsd-media-keys
  │ │ │ ├─15510 diodon
  │ │ │ ├─15515 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify
  │ │ │ ├─15516 
/usr/lib/i386-linux-gnu/indicator-messages/indicator-messages-service
  │ │ │ ├─15519 
/usr/lib/i386-linux-gnu/indicator-application/indicator-application-service
  │ │ │ ├─15527 /usr/lib/gnome-settings-daemon/gsd-printer
  │ │ │ ├─15531 nautilus-desktop
  │ │ │ ├─15593 /usr/lib/ibus/ibus-engine-simple
  │ │ │ ├─15711 update-notifier
  │ │ │ └─16083 /usr/lib/deja-dup/deja-dup-monitor
  │ │ └─user@200463.service
  │ │   ├─zeitgeist.service
  │ │   │ └─15551 /usr/bin/zeitgeist-daemon
  │ │   ├─gnome-terminal-server.service
  │ │   │ ├─15661 /usr/lib/gnome-terminal/gnome-terminal-server
  │ │   │ ├─15671 bash
  │ │   │ ├─15682 systemd-cgls
  │ │   │ └─15683 pager
  │ │   ├─gvfs-gphoto2-volume-monitor.service
  │ │   │ └─15400 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
  │ │   ├─zeitgeist-fts.service
  │ │   │ └─15557 /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts
  │ │   ├─at-spi-dbus-bus.service
  │ │   │ ├─15267 /usr/lib/at-spi2-core/at-spi-bus-launcher
  │ │   │ ├─15277 /usr/bin/dbus-daemon 
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork 
--print-address 3
  │ │   │ └─15282 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
  │ │   ├─dbus.service
  │ │   │ ├─15110 /usr/bin/dbus-daemon --session --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only
  │ │   │ ├─15298 /usr/bin/gnome-keyring-daemon --start --foreground 
--components=secrets
  │ │   │ ├─15357 /usr/lib/ibus/ibus-portal
  │ │   │ ├─15364 /usr/lib/gnome-shell/gnome-shell-calendar-server
  │ │   │ ├─15376 /usr/lib/gnome-online-accounts/goa-daemon
  │ │   │ ├─15387 /usr/lib/gnome-online-accounts/goa-identity-service
  │ │   │ └─15602 /usr/lib/dconf/dconf-service
  │ │   ├─gvfs-udisks2-volume-monitor.service
  │ │   │ └─15396 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
  │ │   ├─evolution-calendar-factory.service
  │ │   │ ├─15567 /usr/lib/evolution/evolution-calendar-factory
  │ │   │ └─15603 /usr/lib/evolution/evolution-calendar

[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault

[Denys Fedoryshchenko]

I run it with valgrind and here is what i got:
(not sure yet how to add debug symbols, will try it too)


root@threadpc:~# valgrind -v /lib/systemd/systemd-resolved
==1798854== Memcheck, a memory error detector
==1798854== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==1798854== Using Valgrind-3.15.0-608cb11914-20190413 and LibVEX; rerun with -h 
for copyright info
==1798854== Command: /lib/systemd/systemd-resolved
==1798854== 
--1798854-- Valgrind options:
--1798854---v
--1798854-- Contents of /proc/version:
--1798854--   Linux version 5.4.0-75-generic (buildd@lgw01-amd64-034) (gcc 
version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #84-Ubuntu SMP Fri May 28 
16:28:37 UTC 2021
--1798854-- 
--1798854-- Arch and hwcaps: AMD64, LittleEndian, 
amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand
--1798854-- Page sizes: currently 4096, max supported 4096
--1798854-- Valgrind library directory: /usr/lib/x86_64-linux-gnu/valgrind
--1798854-- Reading syms from /lib/systemd/systemd-resolved
--1798854--object doesn't have a symbol table
--1798854-- Reading syms from /lib/x86_64-linux-gnu/ld-2.31.so
--1798854--   Considering /lib/x86_64-linux-gnu/ld-2.31.so ..
--1798854--   .. CRC mismatch (computed b1e31cec wanted 7bd1f8ba)
--1798854--   Considering /lib/x86_64-linux-gnu/ld-2.31.so ..
--1798854--   .. CRC mismatch (computed b1e31cec wanted 7bd1f8ba)
--1798854--   Considering /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.31.so ..
--1798854--   .. CRC is valid
--1798854-- Reading syms from 
/usr/lib/x86_64-linux-gnu/valgrind/memcheck-amd64-linux
--1798854--object doesn't have a symbol table
--1798854--object doesn't have a dynamic symbol table
--1798854-- Scheduler: using generic scheduler lock implementation.
--1798854-- Reading suppressions file: 
/usr/lib/x86_64-linux-gnu/valgrind/default.supp
==1798854== embedded gdbserver: reading from 
/tmp/vgdb-pipe-from-vgdb-to-1798854-by-root-on-???
==1798854== embedded gdbserver: writing to   
/tmp/vgdb-pipe-to-vgdb-from-1798854-by-root-on-???
==1798854== embedded gdbserver: shared mem   
/tmp/vgdb-pipe-shared-mem-vgdb-1798854-by-root-on-???
==1798854== 
==1798854== TO CONTROL THIS PROCESS USING vgdb (which you probably
==1798854== don't want to do, unless you know exactly what you're doing,
==1798854== or are doing some strange experiment):
==1798854==   /usr/lib/x86_64-linux-gnu/valgrind/../../bin/vgdb --pid=1798854 
...command...
==1798854== 
==1798854== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==1798854==   /path/to/gdb /lib/systemd/systemd-resolved
==1798854== and then give GDB the following command
==1798854==   target remote | /usr/lib/x86_64-linux-gnu/valgrind/../../bin/vgdb 
--pid=1798854
==1798854== --pid is optional if only one valgrind process is running
==1798854== 
--1798854-- REDIR: 0x4022f60 (ld-linux-x86-64.so.2:strlen) redirected to 
0x580c9ce2 (???)
--1798854-- REDIR: 0x4022d30 (ld-linux-x86-64.so.2:index) redirected to 
0x580c9cfc (???)
--1798854-- Reading syms from 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_core-amd64-linux.so
--1798854--object doesn't have a symbol table
--1798854-- Reading syms from 
/usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so
--1798854--object doesn't have a symbol table
==1798854== WARNING: new redirection conflicts with existing -- ignoring it
--1798854-- old: 0x04022f60 (strlen  ) R-> (.0) 0x580c9ce2 
???
--1798854-- new: 0x04022f60 (strlen  ) R-> (2007.0) 0x0483f060 
strlen
--1798854-- REDIR: 0x401f740 (ld-linux-x86-64.so.2:strcmp) redirected to 
0x483ffd0 (strcmp)
--1798854-- REDIR: 0x40234c0 (ld-linux-x86-64.so.2:mempcpy) redirected to 
0x4843a20 (mempcpy)
--1798854-- Reading syms from /lib/x86_64-linux-gnu/libc-2.31.so
--1798854--   Considering /lib/x86_64-linux-gnu/libc-2.31.so ..
--1798854--   .. CRC mismatch (computed 11759501 wanted 88150686)
--1798854--   Considering /lib/x86_64-linux-gnu/libc-2.31.so ..
--1798854--   .. CRC mismatch (computed 11759501 wanted 88150686)
--1798854--   Considering /usr/lib/debug/lib/x86_64-linux-gnu/libc-2.31.so ..
--1798854--   .. CRC is valid
--1798854-- Reading syms from /lib/systemd/libsystemd-shared-245.so
--1798854--object doesn't have a symbol table
--1798854-- Reading syms from /lib/x86_64-linux-gnu/libgpg-error.so.0.28.0
--1798854--object doesn't have a symbol table
--1798854-- Reading syms from /lib/x86_64-linux-gnu/libm-2.31.so
--1798854--   Considering /lib/x86_64-linux-gnu/libm-2.31.so ..
--1798854--   .. CRC mismatch (computed 5f7b2a42 wanted ffb185de)
--1798854--   Considering /lib/x86_64-linux-gnu/libm-2.31.so ..
--1798854--   .. CRC mismatch (computed 5f7b2a42 wanted ffb185de)
--1798854--   Considering /usr/lib/debug/lib/x86_64-linux-gnu/libm-2.31.so ..
--1798854--   .. CRC is valid
--1798854-- Reading syms from /usr/lib/x86_64-linux-gnu/libidn2.so.0.3.6
--1798854--object doesn't have a symbol table
--1798854-- Reading syms from /usr/lib/x86_64-linu

[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault

[Denys Fedoryshchenko]

Here is backtrace, as i am unable to attach crash report (launchpad gives error)
apport-retrace -g _lib_systemd_systemd-resolved.102.crash 
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Reading symbols from /lib/systemd/systemd-resolved...
(No debugging symbols found in /lib/systemd/systemd-resolved)
warning: core file may not match specified executable file.
[New LWP 1792202]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/lib/systemd/systemd-resolved'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x564ff982f3e0 in ?? ()
(gdb) bt full
#0  0x564ff982f3e0 in ?? ()
No symbol table info available.
#1  0x564ff772a97f in ?? ()
No symbol table info available.
#2  0x7f3e903c2b96 in ?? () from /lib/systemd/libsystemd-shared-245.so
No symbol table info available.
#3  0x7f3e903c2f11 in sd_event_dispatch () from 
/lib/systemd/libsystemd-shared-245.so
No symbol table info available.
#4  0x7f3e903c4948 in sd_event_run () from 
/lib/systemd/libsystemd-shared-245.so
No symbol table info available.
#5  0x7f3e903c4b6f in sd_event_loop () from 
/lib/systemd/libsystemd-shared-245.so
No symbol table info available.
#6  0x564ff770522a in ?? ()
No symbol table info available.
#7  0x7f3e905cc0b3 in __libc_start_main (main=0x564ff7703e40, argc=1, 
argv=0x7ffe2fd0ba18, init=, fini=, 
rtld_fini=, stack_end=0x7ffe2fd0ba08)
at ../csu/libc-start.c:308
self = 
result = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {94901453980416, 
-7807279351804040094, 94901453740880, 140729700629008, 0, 0, 
7807736978364591202, 7916158757757021282}, mask_was_saved = 0}}, priv = {pad = {
  0x0, 0x0, 0x1, 0x7ffe2fd0ba18}, data = {prev = 0x0, cleanup = 
0x0, canceltype = 1}}}
not_first_call = 
#8  0x564ff7705b7e in ?? ()
No symbol table info available.


** Attachment added: "bug.png"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+attachment/5508351/+files/bug.png

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

Title:
  systemd-resolve segfault

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-resolve keep crashing and it is very annoying as sometimes it
  severely interrupt normal dns resolving.

  Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
  Typical error in dmesg: 
  systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 
7ffe2fd0b758 error 15

  apport hints me that problem is related to mdns

  #3  0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd
  /libsystemd-shared-245.so

  It might be (or not) related that some hosts with mdns in my network
  have ipv6 enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
  Uname: Linux 5.4.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  1 08:22:51 2021
  InstallationDate: Installed on 2018-12-05 (938 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X399-E GAMING
  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.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.

[Touch-packages] [Bug 1934221] [NEW] systemd-resolve segfault

[Denys Fedoryshchenko]

Public bug reported:

systemd-resolve keep crashing and it is very annoying as sometimes it
severely interrupt normal dns resolving.

Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
Typical error in dmesg: 
systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 
7ffe2fd0b758 error 15

apport hints me that problem is related to mdns

#3  0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd
/libsystemd-shared-245.so

It might be (or not) related that some hosts with mdns in my network
have ipv6 enabled.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.7
ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
Uname: Linux 5.4.0-75-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jul  1 08:22:51 2021
InstallationDate: Installed on 2018-12-05 (938 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
dmi.bios.date: 05/12/2020
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1205
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX X399-E GAMING
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.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "attaching empty file, otherwise launchpad giving error"
   https://bugs.launchpad.net/bugs/1934221/+attachment/5508334/+files/x

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

Title:
  systemd-resolve segfault

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-resolve keep crashing and it is very annoying as sometimes it
  severely interrupt normal dns resolving.

  Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6
  Typical error in dmesg: 
  systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 
7ffe2fd0b758 error 15

  apport hints me that problem is related to mdns

  #3  0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd
  /libsystemd-shared-245.so

  It might be (or not) related that some hosts with mdns in my network
  have ipv6 enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.7
  ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119
  Uname: Linux 5.4.0-75-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  1 08:22:51 2021
  InstallationDate: Installed on 2018-12-05 (938 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic 
root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago)
  dmi.bios.date: 05/12/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1205
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX X399-E GAMING
  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.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Steve Langasek]

** Changed in: apt (Ubuntu)
 Assignee: metin bağdat (metinbagdat) => (unassigned)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom/

[Touch-packages] [Bug 1876071] Re: text cursor is moved to start of line even if in login prompt

[Norbert]

Still a problem on VirtualBox. Please dig into this bug and fix it.

** Changed in: systemd (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: util-linux (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  text cursor is moved to start of line even if in login prompt

Status in systemd package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Switch to text tty with ++
  3. Enter login, press 

  Expected results:
  * after pressing  the cursor is located next to ":" in "Password:"

  Actual results:
  * after pressing  the cursor is moved in the beginning of the line 
with "Password:"
  * in some case the cursor is located at the first symbol of hostname like in 
the attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Apr 30 12:33:12 2020
  InstallationDate: Installed on 2020-04-24 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=e3b26c22-1835-445d-955d-9221190a83ed ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876071/+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 1801325] Re: User processes/sessions lingering after logoff

[Norbert]

** Tags added: bionic

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

Title:
  User processes/sessions lingering after logoff

Status in Ubuntu MATE:
  Invalid
Status in mate-session-manager package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi!

  Logoff doesn't terminate all user processes/sessions, which means
  after mutiple logon/logoff operations lots of sessions and processes
  are leaking (you can see them with systemctl status). Verified with
  redshift(-gtk), at least. This can be worked around with
  KillUserProcesses=yes on /etc/systemd/logind.conf, but it breaks GNU
  Screen, for example. Tested on 18.04 and 18.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1801325/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[metin bağdat]

** Changed in: apt (Ubuntu)
 Assignee: (unassigned) => metin bağdat (metinbagdat)

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom/

[Touch-packages] [Bug 1934198] Re: Se detuvo la actualizacion a 16.4 / 18.4

[Daniel van Vugt]

Ubuntu 14.04 (trusty) reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Won't Fix

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

Title:
  Se detuvo la actualizacion a 16.4 / 18.4

Status in Ubuntu:
  Won't Fix

Bug description:
  Estuve tratando de actualizar pero se me apago la pc y se extropeo
  todo

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  CasperVersion: 1.340.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jun 30 23:17:27 2021
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF119 [NVS 315] [10de:107c] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:102f]
  LiveMediaBuild: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5)
  MachineType: Hewlett-Packard HP Compaq 8000 Elite SFF PC
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/ubnkern initrd=/ubninit 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G7 v01.02
  dmi.board.asset.tag: MXL03416LB
  dmi.board.name: 3646h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL03416LB
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G7v01.02:bd10/22/2009:svnHewlett-Packard:pnHPCompaq8000EliteSFFPC:pvr:rvnHewlett-Packard:rn3646h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq 8000 Elite SFF PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Jun 30 22:54:34 2021
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1934198/+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 1599446] Re: 16.04, wrong units start order

[sles]

Excellent result :-)

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

Title:
  16.04, wrong units start order

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  Hello!

  squid uses ldap and mysql for authorization , so I added them to squid
  dependencies:

  ### BEGIN INIT INFO
  # Provides:  squid
  # Required-Start:$network $remote_fs $syslog mysql slapd

  
  After=systemd-journald.socket basic.target systemd-journald-dev-log.socket 
mysql.service remote-fs.target network-online.target nss-lookup.target 
system.slice sysinit.target slapd.service


  And symlinks are created in right order:

  S03slapd
  S04mysql
  S05squid

  But really squid is started before mysql (mariadb) and slapd are
  started:

  journalctl -u squid
  -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:44:41 
SAMT. --
  июл 06 13:10:31 inetgw2 systemd[1]: Starting LSB: Squid HTTP Proxy version 
3.x...

  journalctl -u slapd
  -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:45:36 
SAMT. --
  июл 06 13:10:42 inetgw2 systemd[1]: Starting LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...

  journalctl -u mysql
  -- Logs begin at Ср 2016-07-06 13:10:30 SAMT, end at Ср 2016-07-06 13:45:46 
SAMT. --
  июл 06 13:10:42 inetgw2 systemd[1]: Starting LSB: Start and stop the mysql 
database server daemon...
  июл 06 13:10:43 inetgw2 mysql[2647]:  * Starting MariaDB database server 
mysqld

  
  i.e. real start order is:
  sqiud
  slapd
  mysql

  Expected result is folowing
  slapd
  mysql
  squid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1599446/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Won't Fix
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+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

Re: [Touch-packages] [Bug 1821462] Re: Ubuntu 19.04 Desktop:slow boot

[Stephen Waines]

Hello

Thanks for the email hope you're doing well. Apparently that was a bug in 
19.04. I'm on 20.04 and I have exactly no issues.

Thank you for the follow-up.

I actually barely remember reporting this bug.

Steve

On June 30, 2021 6:36:30 p.m. Dan Streetman <1821...@bugs.launchpad.net>
wrote:

> please reopen if this is still an issue
>
> ** Changed in: systemd (Ubuntu)
>   Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1821462
>
> Title:
>  Ubuntu 19.04 Desktop:slow boot
>
> Status in systemd package in Ubuntu:
>  Invalid
>
> Bug description:
>  Hello,
>  I have my ubuntu desktop set to boot text only mode.
>
>  it seems a removable hard drive was pplugged into my machine some time ago.
>  On every boot the boot takes a minute and a half to search to see if that 
>  drive is plugged in.
>
>  I ran systemd-analyze blame
>
>
>  Below is my output:
>
>   37.816s apt-daily.service
>2.383s dev-sda4.device
>2.381s NetworkManager-wait-online.service
>1.198s man-db.service
>1.112s dev-loop9.device
>1.108s dev-loop8.device
>1.098s dev-loop4.device
>1.083s dev-loop6.device
>1.071s dev-loop10.device
>1.057s dev-loop13.device
>1.057s dev-loop11.device
>1.051s dev-loop7.device
>1.051s dev-loop12.device
>1.046s dev-loop2.device
>1.032s dev-loop14.device
>1.024s apt-daily-upgrade.service
>1.017s snap-core18-782.mount
> 988ms snap-vice\x2djz-22.mount
> 983ms snap-gnome\x2dcalculator-260.mount
> 949ms dev-loop15.device
> 930ms dev-loop3.device
> 905ms dev-loop5.device
> 901ms dev-loop1.device
> 899ms dev-loop0.device
> 891ms dev-loop16.device
> 878ms snap-gnome\x2d3\x2d26\x2d1604-78.mount
> 868ms snap-remmina-2831.mount
> 855ms snap-gnome\x2dcharacters-139.mount
> 845ms snap-youtube\x2ddl\x2dsnap-1.mount
> 844ms dev-loop17.device
> 834ms snap-gnome\x2d3\x2d26\x2d1604-74.mount
> 824ms snap-gnome\x2d3\x2d28\x2d1804-15.mount
> 814ms snap-remmina-2823.mount
> 803ms snap-gnome\x2dclocks-85.mount
> 798ms snap-gnome\x2dcharacters-206.mount
> 793ms snap-core-6350.mount
> 783ms snap-core-6531.mount
> 776ms udisks2.service
> 773ms snap-gnome\x2dlogs-45.mount
> 763ms snap-vice\x2djz-20.mount
> 753ms snap-gtk\x2dcommon\x2dthemes-1198.mount
> 744ms snap-core-6405.mount
> 734ms snap-vice\x2djz-19.mount
> 733ms snap-gnome\x2dcharacters-124.mount
> 725ms snap-gtk\x2dcommon\x2dthemes-1122.mount
> 719ms dev-loop18.device
> 715ms snap-core18-731.mount
> 706ms snap-core18-719.mount
> 695ms snap-gnome\x2dcalculator-238.mount
> 680ms upower.service
> 662ms snap-gnome\x2d3\x2d28\x2d1804-19.mount
> 646ms dev-loop19.device
> 643ms snap-gtk\x2dcommon\x2dthemes-818.mount
> 638ms dev-loop23.device
> 626ms snap-gnome\x2dlogs-57.mount
> 626ms dev-loop26.device
> 610ms snap-gnome\x2dsystem\x2dmonitor-70.mount
> 596ms dev-loop21.device
> 589ms dev-loop25.device
> 587ms dev-loop20.device
> 583ms dev-loop24.device
> 528ms logrotate.service
> 523ms systemd-journal-flush.service
> 496ms dev-loop22.device
> 491ms dev-loop30.device
> 490ms dev-loop27.device
> 487ms dev-loop28.device
> 433ms networkd-dispatcher.service
> 427ms snapd.service
> 397ms ModemManager.service
> 382ms snap-gnome\x2d3\x2d26\x2d1604-82.mount
> 379ms snap-gnome\x2dcalculator-352.mount
> 369ms snap-remmina-2819.mount
> 362ms snap-gnome\x2d3\x2d28\x2d1804-23.mount
> 359ms snap-gnome\x2dsystem\x2dmonitor-57.mount
> 340ms accounts-daemon.service
> 307ms systemd-logind.service
> 281ms keyboard-setup.service
> 280ms kmod-static-nodes.service
> 261ms dev-hugepages.mount
> 260ms avahi-daemon.service
> 259ms sys-kernel-debug.mount
> 259ms ufw.service
> 255ms apport-autoreport.service
> 251ms systemd-udev-trigger.service
> 242ms systemd-modules-load.service
> 232ms systemd-journald.service
> 230ms fwupd.service
> 206ms apport.service
> 196ms dev-mqueue.mount
> 194ms apparmor.service
> 186ms rsyslog.servic

[Touch-packages] [Bug 1934199] Re: Switch from Livepatch service to UA client

[Robert Ancell]

The current implementation shows "Last check for updates". As far as I can tell 
this information is not available via the UA client. It also shows a list of 
applied CVE fixes, which again I don't think is available from the UA client.
 
See attached screenshot of current implementation in 18.04 LTS.

** Attachment added: "Screenshot from 2021-07-01 12-28-24.png"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+attachment/5508251/+files/Screenshot%20from%202021-07-01%2012-28-24.png

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

Title:
  Switch from Livepatch service to UA client

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  New
Status in software-properties source package in Impish:
  New

Bug description:
  software-properties currently uses a HTTP over Unix domain socket
  service from the livepatch snap to get the status and enable/disable
  it. This service is being deprecated with the 'ua' command line tool
  now providing this functionality. software-properties also installed
  the snap to gain access to this service. This is no longer required as
  the 'ua' tool does this.

  (*) The Livepatch service is a HTTP over Unix domain service running
  on livepatchd.sock inside the livepatch snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1934199] [NEW] Switch from Livepatch service to UA client

[Robert Ancell]

Public bug reported:

software-properties currently uses a HTTP over Unix domain socket
service from the livepatch snap to get the status and enable/disable it.
This service is being deprecated with the 'ua' command line tool now
providing this functionality. software-properties also installed the
snap to gain access to this service. This is no longer required as the
'ua' tool does this.

(*) The Livepatch service is a HTTP over Unix domain service running on
livepatchd.sock inside the livepatch snap.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: software-properties (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: software-properties (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: software-properties (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: software-properties (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

** Affects: software-properties (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Also affects: software-properties (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: software-properties (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

Title:
  Switch from Livepatch service to UA client

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  New
Status in software-properties source package in Impish:
  New

Bug description:
  software-properties currently uses a HTTP over Unix domain socket
  service from the livepatch snap to get the status and enable/disable
  it. This service is being deprecated with the 'ua' command line tool
  now providing this functionality. software-properties also installed
  the snap to gain access to this service. This is no longer required as
  the 'ua' tool does this.

  (*) The Livepatch service is a HTTP over Unix domain service running
  on livepatchd.sock inside the livepatch snap.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934199/+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 1932331] Re: ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

[Thomas Ward]

Thanks for the confirm, Steve.  However, these may be 'upstream' but
aren't yet in Ubuntu, so.  The two issues on my radar are the one I
discovered needs fixed for something to properly WORK for torbrowser-
launcher, and the other is this one Seth poked at me to include on any
SRU for HIrsute.  (Or uploads for Impish, they're incoming)

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

Title:
  ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  New

Bug description:
  It only affects arm64:

  ...
   06/15 13:09:11 ERROR| utils:0153| [stderr] running i18n

   06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed. Test
   'i18n (194) OPEN (octal) "/tmp/sdtest.411763-18905-et6mgO/file_Š_post"
   RW' was expected to 'pass'. Reason for failure 'FAIL: open 
/tmp/sdtest.411763-18905-et6mgO/file_Š_post failed - Permission denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed.
  Test 'i18n (195) OPEN (octal)
  "/tmp/sdtest.411763-18905-et6mgO/file_Ê_post" RW' was expected to
  'pass'. Reason for failure 'FAIL: open
  /tmp/sdtest.411763-18905-et6mgO/file_Ê_post failed - Permission
  denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed.
  Test 'i18n (196) OPEN (octal)
  "/tmp/sdtest.411763-18905-et6mgO/file_ÄŠ_post" RW' was expected to
  'pass'. Reason for failure 'FAIL: open
  /tmp/sdtest.411763-18905-et6mgO/file_ÄŠ_post failed - Permission
  denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed. Test 'i18n 
(197) OPEN (octal) "/tmp/sdtest.411763-18905-et6mgO/file_ÅŠ_post" RW' was 
expected to 'pass'. Reason for failure 'FAIL: open 
/tmp/sdtest.411763-18905-et6mgO/file_ÅŠ_post failed - Permission denied'
  ...

  
  Full log without LP manging the formatting: 
http://paste.ubuntu.com/p/3PHcCWb9Jw/plain/

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1932331/+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 1932331] Re: ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

[Steve Beattie]

The root issue is likely something in the utf-8 handling code in glibc
on arm64 hirsute and impish; the reproducer is:

  bash -c 'i=210; echo -n $(printf "\\$(printf "%03o" $i)") | od -An -t uC'
  210 138

running valgrind in a default environemnt (so LANG=en_US.UTF-8) turned
up

==46656== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
==46653== Conditional jump or move depends on uninitialised value(s)
==46653==at 0x48EA5EC: utf8_internal_loop (loop.c:336)
==46653==by 0x48EA5EC: __gconv_transform_utf8_internal (skeleton.c:620)
==46653==by 0x494BF57: mbrtowc (mbrtowc.c:86)
==46653==by 0x17FFBB: command_substitute (in /usr/bin/bash)

and running the test with LANG=C results in the trailing artifact (138)
to not show up.

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

Title:
  ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  New

Bug description:
  It only affects arm64:

  ...
   06/15 13:09:11 ERROR| utils:0153| [stderr] running i18n

   06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed. Test
   'i18n (194) OPEN (octal) "/tmp/sdtest.411763-18905-et6mgO/file_Š_post"
   RW' was expected to 'pass'. Reason for failure 'FAIL: open 
/tmp/sdtest.411763-18905-et6mgO/file_Š_post failed - Permission denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed.
  Test 'i18n (195) OPEN (octal)
  "/tmp/sdtest.411763-18905-et6mgO/file_Ê_post" RW' was expected to
  'pass'. Reason for failure 'FAIL: open
  /tmp/sdtest.411763-18905-et6mgO/file_Ê_post failed - Permission
  denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed.
  Test 'i18n (196) OPEN (octal)
  "/tmp/sdtest.411763-18905-et6mgO/file_ÄŠ_post" RW' was expected to
  'pass'. Reason for failure 'FAIL: open
  /tmp/sdtest.411763-18905-et6mgO/file_ÄŠ_post failed - Permission
  denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed. Test 'i18n 
(197) OPEN (octal) "/tmp/sdtest.411763-18905-et6mgO/file_ÅŠ_post" RW' was 
expected to 'pass'. Reason for failure 'FAIL: open 
/tmp/sdtest.411763-18905-et6mgO/file_ÅŠ_post failed - Permission denied'
  ...

  
  Full log without LP manging the formatting: 
http://paste.ubuntu.com/p/3PHcCWb9Jw/plain/

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1932331/+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 1934198] [NEW] Se detuvo la actualizacion a 16.4 / 18.4

[ronald2]

Public bug reported:

Estuve tratando de actualizar pero se me apago la pc y se extropeo todo

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
Uname: Linux 4.4.0-142-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: i386
CasperVersion: 1.340.2
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jun 30 23:17:27 2021
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GF119 [NVS 315] [10de:107c] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company Device [103c:102f]
LiveMediaBuild: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5)
MachineType: Hewlett-Packard HP Compaq 8000 Elite SFF PC
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/ubnkern initrd=/ubninit 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G7 v01.02
dmi.board.asset.tag: MXL03416LB
dmi.board.name: 3646h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: MXL03416LB
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G7v01.02:bd10/22/2009:svnHewlett-Packard:pnHPCompaq8000EliteSFFPC:pvr:rvnHewlett-Packard:rn3646h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.name: HP Compaq 8000 Elite SFF PC
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Jun 30 22:54:34 2021
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.3~trusty4
xserver.video_driver: nouveau

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


** Tags: apport-bug compiz-0.9 i386 trusty 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/1934198

Title:
  Se detuvo la actualizacion a 16.4 / 18.4

Status in xorg package in Ubuntu:
  New

Bug description:
  Estuve tratando de actualizar pero se me apago la pc y se extropeo
  todo

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168~14.04.1-generic 4.4.167
  Uname: Linux 4.4.0-142-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: i386
  CasperVersion: 1.340.2
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jun 30 23:17:27 2021
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF119 [NVS 315] [10de:107c] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Device [103c:102f]
  LiveMediaBuild: Ubuntu 14.04.6 LTS "Trusty Tahr" - Release i386 (20190304.5)
  MachineType: Hewlett-Packard HP Compaq 8000 Elite SFF PC
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/ubnkern initrd=/ubninit 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/22/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G7 v01.02
  dmi.board.asset.tag: MXL03416LB
  dmi.board.name: 3646h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL03416LB
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G7v01.02:bd10/22/2009:svnHewlett-Packard:pnHPCompaq8000EliteSFFPC:pvr:rvnHewlett-Packard:rn3646h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.name: HP Compaq 8000 Elite SFF PC
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdr

[Touch-packages] [Bug 1932331] Re: ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

[Steve Beattie]

Georgia's patch was committed in the upstream apparmor project in
https://gitlab.com/apparmor/apparmor/-/commit/458a981b6242e8b1cce1599ca95d89dcd10f60e7
in https://gitlab.com/apparmor/apparmor/-/merge_requests/765 and was
cherrypicked to the apparmor-3.0 branch amongst others in
https://gitlab.com/apparmor/apparmor/-/commit/0729b13293d775dfd6ec4c9a3b9313b6e125d540
.

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

Title:
  ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  New

Bug description:
  It only affects arm64:

  ...
   06/15 13:09:11 ERROR| utils:0153| [stderr] running i18n

   06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed. Test
   'i18n (194) OPEN (octal) "/tmp/sdtest.411763-18905-et6mgO/file_Š_post"
   RW' was expected to 'pass'. Reason for failure 'FAIL: open 
/tmp/sdtest.411763-18905-et6mgO/file_Š_post failed - Permission denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed.
  Test 'i18n (195) OPEN (octal)
  "/tmp/sdtest.411763-18905-et6mgO/file_Ê_post" RW' was expected to
  'pass'. Reason for failure 'FAIL: open
  /tmp/sdtest.411763-18905-et6mgO/file_Ê_post failed - Permission
  denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed.
  Test 'i18n (196) OPEN (octal)
  "/tmp/sdtest.411763-18905-et6mgO/file_ÄŠ_post" RW' was expected to
  'pass'. Reason for failure 'FAIL: open
  /tmp/sdtest.411763-18905-et6mgO/file_ÄŠ_post failed - Permission
  denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed. Test 'i18n 
(197) OPEN (octal) "/tmp/sdtest.411763-18905-et6mgO/file_ÅŠ_post" RW' was 
expected to 'pass'. Reason for failure 'FAIL: open 
/tmp/sdtest.411763-18905-et6mgO/file_ÅŠ_post failed - Permission denied'
  ...

  
  Full log without LP manging the formatting: 
http://paste.ubuntu.com/p/3PHcCWb9Jw/plain/

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1932331/+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 1932331] Re: ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

[Thomas Ward]

Seth Arnold has affirmed the patch is going to fix things, so it's been
reviewed by Seth.

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

Title:
  ubuntu_qrt_apparmor: i18n test fails on arm64 Hirsute / Impish

Status in AppArmor:
  In Progress
Status in apparmor package in Ubuntu:
  New

Bug description:
  It only affects arm64:

  ...
   06/15 13:09:11 ERROR| utils:0153| [stderr] running i18n

   06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed. Test
   'i18n (194) OPEN (octal) "/tmp/sdtest.411763-18905-et6mgO/file_Š_post"
   RW' was expected to 'pass'. Reason for failure 'FAIL: open 
/tmp/sdtest.411763-18905-et6mgO/file_Š_post failed - Permission denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed.
  Test 'i18n (195) OPEN (octal)
  "/tmp/sdtest.411763-18905-et6mgO/file_Ê_post" RW' was expected to
  'pass'. Reason for failure 'FAIL: open
  /tmp/sdtest.411763-18905-et6mgO/file_Ê_post failed - Permission
  denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed.
  Test 'i18n (196) OPEN (octal)
  "/tmp/sdtest.411763-18905-et6mgO/file_ÄŠ_post" RW' was expected to
  'pass'. Reason for failure 'FAIL: open
  /tmp/sdtest.411763-18905-et6mgO/file_ÄŠ_post failed - Permission
  denied'

  06/15 13:09:11 ERROR| utils:0153| [stderr] Error: open failed. Test 'i18n 
(197) OPEN (octal) "/tmp/sdtest.411763-18905-et6mgO/file_ÅŠ_post" RW' was 
expected to 'pass'. Reason for failure 'FAIL: open 
/tmp/sdtest.411763-18905-et6mgO/file_ÅŠ_post failed - Permission denied'
  ...

  
  Full log without LP manging the formatting: 
http://paste.ubuntu.com/p/3PHcCWb9Jw/plain/

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1932331/+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

Re: [Touch-packages] [Bug 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot

[Robert Dinse]

Not an issue, found that I was using the wrong GPU driver for my hardware,
when I fixed that it fixed the shutdown issue as well as some graphics issues.

-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
  Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting.
Knowledgeable human assistance, not telephone trees or script readers.
  See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.

On Wed, 30 Jun 2021, Dan Streetman wrote:

> Date: Wed, 30 Jun 2021 22:26:48 -
> From: Dan Streetman <1824...@bugs.launchpad.net>
> To: nan...@eskimo.com
> Subject: [Bug 1824893] Re: When I type systemctl reboot system reaches Target
> Reboot but then does not reboot
> 
> please reopen if this is still an issue
>
> ** Changed in: systemd (Ubuntu)
>   Status: Confirmed => Invalid
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1824893
>
> Title:
>  When I type systemctl reboot system reaches Target Reboot but then
>  does not reboot
>
> Status in systemd package in Ubuntu:
>  Invalid
>
> Bug description:
>  This is similar to the bug where systemd used to get stuck in target
>  Shutdown except that bug affected all my hardware, now it gets stuck
>  at target Reboot but this only affects my elderly Mac Pro 1,1 and does
>  not affect my laptop or i7-6700k and i7-6850k based servers.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 19.04
>  Package: systemd 240-6ubuntu5
>  ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
>  Uname: Linux 5.0.0-8-lowlatency x86_64
>  ApportVersion: 2.20.10-0ubuntu27
>  Architecture: amd64
>  CurrentDesktop: MATE
>  Date: Mon Apr 15 16:30:34 2019
>  InstallationDate: Installed on 2018-12-06 (130 days ago)
>  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
> (20181017.2)
>  MachineType: Apple Computer, Inc. MacPro2,1
>  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency 
> root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1
>  SourcePackage: systemd
>  SystemdDelta:
>   [EXTENDED]   /lib/systemd/system/ondemand.service → 
> /lib/systemd/system/ondemand.service.d/ubuntustudio.conf
>   [EXTENDED]   /lib/systemd/system/rc-local.service → 
> /lib/systemd/system/rc-local.service.d/debian.conf
>   [EXTENDED]   /lib/systemd/system/user@.service → 
> /lib/systemd/system/user@.service.d/timeout.conf
>
>   3 overridden configuration files found.
>  UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago)
>  dmi.bios.date: 07/02/07
>  dmi.bios.vendor: Apple Computer, Inc.
>  dmi.bios.version: MP21.88Z.007F.B06.0707021348
>  dmi.board.asset.tag: Base Board Asset Tag#
>  dmi.board.name: Mac-F4208DC8
>  dmi.board.vendor: Apple Inc.
>  dmi.board.version: PVT
>  dmi.chassis.asset.tag: Asset Tag#
>  dmi.chassis.type: 2
>  dmi.chassis.vendor: Apple Computer, Inc.
>  dmi.chassis.version: Mac-F4208DC8
>  dmi.modalias: 
> dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
>  dmi.product.family: MacPro
>  dmi.product.name: MacPro2,1
>  dmi.product.sku: System SKU#
>  dmi.product.version: 1.0
>  dmi.sys.vendor: Apple Computer, Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+subscriptions
>

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

Title:
  When I type systemctl reboot system reaches Target Reboot but then
  does not reboot

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This is similar to the bug where systemd used to get stuck in target
  Shutdown except that bug affected all my hardware, now it gets stuck
  at target Reboot but this only affects my elderly Mac Pro 1,1 and does
  not affect my laptop or i7-6700k and i7-6850k based servers.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
  Uname: Linux 5.0.0-8-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Apr 15 16:30:34 2019
  InstallationDate: Installed on 2018-12-06 (130 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Apple Computer, Inc. MacPro2,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency 
root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/ondemand.service → 
/lib/systemd/system/ondemand.service.d/ubuntustudio.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/sy

[Touch-packages] [Bug 1931901] Re: Revert background key patch removal breaks dependent packages

[Treviño]

Yeah, wasn't using the libgnome-desktop3 API though, so we should just
drop it from unity-settings-daemon.

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

Title:
  Revert background key patch removal breaks dependent packages

Status in gnome-desktop3 package in Ubuntu:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Invalid

Bug description:
  in the package gnome-desktop3 there is a custom ubuntu patch that
  tries to write to the draw-background key that has now been removed in
  gsettings-desktop-schemas 40.0-1ubuntu1

  All packages that depend on the gnome-desktop3 library now crash such
  as budgie-desktop

  Suggestion - either re-add the patch again ... or revert the gnome-
  desktop3 custom patch.

  The latter option changes the symbols so probably I'm guessing a so-
  name version bump is needed and any dependent packages need a rebuild?

  I'll try to locally rebuild gnome-desktop3 without the custom ubuntu
  patch to see what happens with budgie-desktop

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: gsettings-desktop-schemas 40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
  Uname: Linux 5.11.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Budgie:GNOME
  Date: Mon Jun 14 20:52:16 2021
  InstallationDate: Installed on 2021-06-14 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Alpha amd64 (20210614)
  PackageArchitecture: all
  SourcePackage: gsettings-desktop-schemas
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1931901/+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 1902748] Re: ubuntu-seed / ubuntu-boot partition detection could be improved

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  ubuntu-seed / ubuntu-boot partition detection could be improved

Status in snapd:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  ubuntu-seed / ubuntu-boot partition detection could be improved

  Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
  ubuntu-seed partition by label or by UEFI variable that was set by sd-
  boot.

  sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PATH,
  HARDDRIVE_DEVICEPATH, GUID, Signature aka partuuid that was used to
  boot.

  
https://github.com/tianocore/edk2/blob/master/MdePkg/Include/Protocol/DevicePath.h

  This is nice, but not unique enough. It would be nice if we were able
  to modify sd-boot stub to export something more specific that ideally
  maps to a sysfs path.

  For example PCI_DEVICE_PATH, SCSI_DEVICE_PATH, SATA_DEVICE_PATH,
  USB_DEVICE_PATH, NVME_NAMESPACE_DEVICE_PATH, SD_DEVICE_PATH,
  UFS_DEVICE_PATH, EMMC_DEVICE_PATH or some such.

  That way initrd would be able to resolve better which block device to
  key off.

  Given that EFI device handle is passed to the kernel, doesn't kernel
  also know where it came from? or not?

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1902748/+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 1889668] Re: set-cpufreq error when cpu is offline

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  set-cpufreq error when cpu is offline

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I have hyperthreading disabled on my Ubuntu 19.10 machine, which makes
  some processors in /sys/devices/system/cpu/cpu* have their "online"
  set to 0.

  However, when the for-loop in /lib/systemd/set-cpufreq iterates over
  the processors, it doesn't check if the processor is online before
  trying to write the governor name into scaling_governor.

  The script appears to have the same bug in Ubuntu 20.04.

  I modified the script to print the cpu it is trying to set before doing so, 
and I get the following:
  Setting powersave scheduler for all CPUs
  /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
  /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
  /sys/devices/system/cpu/cpu10/cpufreq/scaling_governor
  /lib/systemd/set-cpufreq: 43: echo: echo: I/O error

  Since the script doesn't continue to try other processors in the loop,
  it means that only cpu0 and cpu1 on my machine get set to powersave
  and the others remain with the performance governor. The cpufreq-info
  command confirms this.

  Checking if the processor has online==1 before writing, or putting the
  echo within a "set +e" "set -e" pair would fix the problem (although
  the latter approach would still print error messages).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1889668/+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 1888442] Re: upgrade did not go well

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  upgrade did not go well

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hello, I had some problems during my most recent apt upgrade. A
  confounding factor to these problems was removing my laptop from its
  docking station a few minutes earlier.

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
linux-headers-5.4.0-42 linux-headers-5.4.0-42-generic 
linux-image-5.4.0-42-generic
linux-modules-5.4.0-42-generic linux-modules-extra-5.4.0-42-generic 
python3-click python3-colorama
  The following packages will be upgraded:
base-files libnss-mymachines libnss-systemd libpam-systemd 
libpulse-mainloop-glib0 libpulse0 libpulsedsp
libseccomp2 libsystemd0 libudev1 libvirt-clients libvirt-daemon 
libvirt-daemon-driver-qemu
libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-zfs 
libvirt-daemon-system
libvirt-daemon-system-systemd libvirt0 linux-firmware linux-generic 
linux-headers-generic linux-image-generic
pulseaudio pulseaudio-utils python3-distupgrade sudo systemd 
systemd-container systemd-journal-remote
systemd-sysv systemd-timesyncd ubuntu-drivers-common 
ubuntu-release-upgrader-core udev
  34 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
  Need to get 110 MB/184 MB of archives.
  After this operation, 360 MB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Get:1 http://wopr.domain/ubuntu focal-proposed/main amd64 base-files amd64 
11ubuntu5.1 [60.1 kB]
  Get:2 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-systemd 
amd64 245.4-4ubuntu3.2 [95.6 kB]
  Get:3 http://wopr.domain/ubuntu focal-proposed/universe amd64 
systemd-journal-remote amd64 245.4-4ubuntu3.2 [61.9 kB]
  Get:4 http://wopr.domain/ubuntu focal-proposed/main amd64 udev amd64 
245.4-4ubuntu3.2 [1,363 kB]
  Get:5 http://wopr.domain/ubuntu focal-proposed/main amd64 libudev1 amd64 
245.4-4ubuntu3.2 [78.9 kB]
  Get:6 http://wopr.domain/ubuntu focal-proposed/main amd64 
libvirt-daemon-system amd64 6.0.0-0ubuntu8.2 [67.5 kB]
  Get:7 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-clients 
amd64 6.0.0-0ubuntu8.2 [343 kB]
  Get:8 http://wopr.domain/ubuntu focal-proposed/main amd64 
libvirt-daemon-driver-qemu amd64 6.0.0-0ubuntu8.2 [605 kB]
  Get:9 http://wopr.domain/ubuntu focal-proposed/universe amd64 
libvirt-daemon-driver-storage-zfs amd64 6.0.0-0ubuntu8.2 [21.4 kB]
  Get:10 http://wopr.domain/ubuntu focal-proposed/main amd64 
libvirt-daemon-driver-storage-rbd amd64 6.0.0-0ubuntu8.2 [28.3 kB]
  Get:11 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt0 amd64 
6.0.0-0ubuntu8.2 [1,444 kB]
  Get:12 http://wopr.domain/ubuntu focal-proposed/main amd64 libvirt-daemon 
amd64 6.0.0-0ubuntu8.2 [404 kB]
  Get:13 http://wopr.domain/ubuntu focal-proposed/main amd64 libnss-mymachines 
amd64 245.4-4ubuntu3.2 [131 kB]
  Get:14 http://wopr.domain/ubuntu focal-proposed/main amd64 libseccomp2 amd64 
2.4.3-1ubuntu3.20.04.3 [42.4 kB]
  Get:15 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-container 
amd64 245.4-4ubuntu3.2 [317 kB]
  Get:16 http://wopr.domain/ubuntu focal-proposed/main amd64 
libvirt-daemon-system-systemd amd64 6.0.0-0ubuntu8.2 [12.3 kB]
  Get:17 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-sysv amd64 
245.4-4ubuntu3.2 [10.3 kB]
  Get:18 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd-timesyncd 
amd64 245.4-4ubuntu3.2 [28.0 kB]
  Get:19 http://wopr.domain/ubuntu focal-proposed/main amd64 libpam-systemd 
amd64 245.4-4ubuntu3.2 [186 kB]
  Get:20 http://wopr.domain/ubuntu focal-proposed/main amd64 systemd amd64 
245.4-4ubuntu3.2 [3,796 kB]
  Get:21 http://wopr.domain/ubuntu focal-proposed/main amd64 libsystemd0 amd64 
245.4-4ubuntu3.2 [271 kB]
  Get:22 http://wopr.domain/ubuntu focal-proposed/main amd64 
libpulse-mainloop-glib0 amd64 1:13.99.1-1ubuntu3.5 [11.7 kB]
  Get:23 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulsedsp amd64 
1:13.99.1-1ubuntu3.5 [21.7 kB]
  Get:24 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio-utils 
amd64 1:13.99.1-1ubuntu3.5 [55.0 kB]
  Get:25 http://wopr.domain/ubuntu focal-proposed/main amd64 pulseaudio amd64 
1:13.99.1-1ubuntu3.5 [815 kB]
  Get:26 http://wopr.domain/ubuntu focal-proposed/main amd64 libpulse0 amd64 
1:13.99.1-1ubuntu3.5 [263 kB]
  Get:27 http://wopr.domain/ubuntu focal/main amd64 python3-colorama all 
0.4.3-1build1 [23.9 kB]
  Get:28 http://wopr.domain/ubuntu focal/main amd64 python3-click all 7.0-3 
[64.8 kB]
  Get:29 http://wopr.domain/ubuntu focal-proposed/main amd64 
ubuntu

[Touch-packages] [Bug 1890133] Re: User login screen is not offered

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  User login screen is not offered

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hello.
  I know how to solve some connection problems.  I can't find enough 
explanation to understand the cause of this problem!
  It seems to loop forever on the user login and network acquisition sequences.

  First stage
  "try ubuntu before installing it"
  This step goes smoothly. The present screen forces you to choose the 
NOMODESET option. which has become very easy ..
  I didn't notice anything abnormal.

  Second step
  "Install ubuntu"
  I didn't notice anything abnormal.
  Initially I had chosen not to update the software during installation and to 
automatically log in the user.
  I restarted the installation by asking to update the software during the 
installation and to propose the user connection grid.
  There is no change

  Third step
  "The normal boot"
  The screen proposing to enter the username does not appear regardless of the 
chosen kernel.
  Removing the two "quiet splash" options allows you to see a significant 
amount of failed and the loop that seems eternal. I even waited over 30 minutes 


  Fourth step
  "Boot recovery"
  The recovery screen is displayed.
  I can do the proposed actions.
  Some go wrong.
  For example, the fsck command says the partition is "already mounted". I 
don't think the problem is there.
   The most important is the network enable command which does not seem to 
indicate any errors and which does not activate the network!
  Ping 8.8.8.8 says network is not operational

  Fifth step
  "The start by CHROOT"
  This technique allows me to access the log of the installed instance 
(journalctl -D / mnt / var / log / journald)
  and find the first level of errors. Some advice says to dig deeper with the 
systemctl command but this one does not work in chroot mode.

  Sixth step
  "The diagnosis".
  As the normal boot never ends except by power-off, I used the recovery mode 
to access the logs of the previous boot.
  It is not that easy. I put in .txt files that I will send to you.
  I think reading the contents of some of these files will allow you to give me 
additional commands to find the cause of the problem.

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890133/+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 1888889] Re: Ubuntu software center is not opening after a fresh Ubuntu install resuing /home from an earlier install

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Ubuntu software center is not opening after a fresh Ubuntu install
  resuing /home from an earlier install

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I tried renaming ~/.local/share/gnome-software-center but no luck

  Any other help is appreciated

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-systemd:amd64 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jul 24 23:26:04 2020
  ErrorMessage: installed libpam-systemd:amd64 package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2020-07-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 245.4-4ubuntu3.2 failed to 
install/upgrade: installed libpam-systemd:amd64 package post-installation 
script subprocess returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/189/+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 1896372] Re: systemd (sbin/init/ splash) consumes 12% CPU and doesn't stop

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  systemd (sbin/init/ splash) consumes 12% CPU and doesn't stop

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Right after login, the process systemd (sbin/init/ splash), which is
  run by root, consumes 12% CPU and doesn't stop. The CPU fan is always
  on for that reason. That doesn't happen in Focal on the same laptop,
  which has both Focal and Groovy, and they both share the same /home
  partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sun Sep 20 10:50:27 2020
  InstallationDate: Installed on 2020-09-16 (3 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:2113 Acer, Inc SunplusIT Integrated Camera
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0461:4e57 Primax Electronics, Ltd HID compliant device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20LTS01800
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=301ac90f-9a29-425d-9b75-b6b2a43bf00a ro quiet splash
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2019
  dmi.bios.release: 1.37
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET60W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LTS01800
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.37
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET60W(1.37):bd12/18/2019:br1.37:efr1.37:svnLENOVO:pn20LTS01800:pvrThinkPadL480:rvnLENOVO:rn20LTS01800:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LTS01800
  dmi.product.sku: LENOVO_MT_20LT_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896372/+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 1889416] Re: pulseaudio.service: Start request repeated too quickly.

[Dan Streetman]

** Package changed: systemd (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  pulseaudio.service: Start request repeated too quickly.

Status in fscrypt package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  PA doesn't start on it's own after the latest update.

  ```
  nafallo@wendigo:~$ systemctl --user status pulseaudio
  ● pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 
11min ago
  TriggeredBy: ● pulseaudio.socket
  Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no 
--log-target=journal (code=exited, status=1/FAILURE)
 Main PID: 2774 (code=exited, status=1/FAILURE)

  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart 
job, restart counter is at 5.
  Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service.
  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request 
repeated too quickly.
  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 
'exit-code'.
  Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service.
  Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request 
repeated too quickly.
  Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 
'exit-code'.
  Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service.
  ```

  But works after starting it manually.

  ```
  nafallo@wendigo:~$ systemctl --user start pulseaudio
  nafallo@wendigo:~$ systemctl --user status pulseaudio
  ● pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago
  TriggeredBy: ● pulseaudio.socket
 Main PID: 5675 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal

  Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service...
  Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nafallo5675 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 15:11:28 2020
  InstallationDate: Installed on 2018-06-27 (763 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+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 1884281] Re: UC20 images do not use predictable interface names on RPi4

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  UC20 images do not use predictable interface names on RPi4

Status in snapd:
  Triaged
Status in linux-raspi package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Image tested: http://cdimage.ubuntu.com/ubuntu-core/20/dangerous-
  beta/pending/ubuntu-core-20-arm64+raspi.img.xz

  Boot the image and check the naming of the ethernet interfaces. On
  most devices (amd64, rpi3 etc) systemd predicatable interface naming
  is applied e.g. enxb827eb7d1eee. However on specifically RPi4 devices
  traditional naming is used e.g. eth0, eth1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1884281/+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 1904549] Re: MTU is not set on vlan interface

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  MTU is not set on vlan interface

Status in netplan:
  New
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hello,

  Upon changing the following configuration, adding the MTU lines, I
  ended up with the VLAN interfaces still in MTU 1500 after a `netplan
  generate && netplan apply`

  # lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.1 LTS
  Release:20.04
  Codename:   focal

  # uname -a
  Linux il3-fw2 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  # dpkg -l netplan.io
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   VersionArchitecture Description
  
+++-==-==--===
  ii  netplan.io 0.100-0ubuntu4~20.04.2 amd64YAML network 
configuration abstraction for various backends

  ==

  # This is the network config written by 'subiquity'
  network:
ethernets:
  ens10f0: {}
  ens10f1: {}
  ens10f2: {}
  ens10f3: {}
  ens1f0: {}
  ens1f1: {}
bonds:
  bond-oam:
interfaces: [ens10f0, ens10f1]
parameters:
  mode: 802.3ad
  transmit-hash-policy: layer3+4
  mii-monitor-interval: 100
  lacp-rate: fast
mtu: 9000

  bond-manlan:
interfaces: [ens10f2, ens10f3]
parameters:
  mode: 802.3ad
  transmit-hash-policy: layer3+4
  mii-monitor-interval: 100
  lacp-rate: fast

  bond-core:
interfaces: [ens1f0, ens1f1]
parameters:
  mode: 802.3ad
  transmit-hash-policy: layer3+4
  mii-monitor-interval: 100
  lacp-rate: fast
mtu: 9000

vlans:
  vlan3001:
id: 3001
link: bond-manlan
addresses: [ "10.130.1.3/24" ]
  vlan3002:
id: 3002
link: bond-manlan
addresses: [ "10.130.2.3/24" ]
  vlan3003:
id: 3003
link: bond-manlan
addresses: [ "10.130.3.3/24" ]

  
  vlan3054:
id: 3054
link: bond-core
addresses: [ "10.130.56.3/24" ]
mtu: 9000

  
  vlan3065:
id: 3065
link: bond-oam
addresses: [ "10.130.63.3/24" ]
mtu: 9000
   
version: 2
  ==

  And here is the result after the `netplan apply`

  ===
  # netstat -in 

   
  Kernel Interface table
   
  Iface  MTURX-OK RX-ERR RX-DRP RX-OVRTX-OK TX-ERR TX-DRP TX-OVR 
Flg 

  bond-cor  9000 19448696  0  0 0   6858767  0  1  0 
BMmRU 
  bond-man  1500  7981199  0  1 0   1755800  0  2  0 
BMmRU 
  bond-oam  9000  6236232  0  0 0   4488877  0  1  0 
BMmU  
  ens10f0   9000  3961100  0  0 0   2271891  0  0  0 
BMsU

  ens10f1   9000  2288169  0  0 0   2218120  0  0  0 
BMsU  
  ens10f2   1500  2506083  0  0 0   1226075  0  0  0 
BMsRU 
  ens10f3   1500  5475116  0  0 0529725  0  0  0 
BMsRU 
  ens1f09000  9513761  0  0 0   3970465  0  0  0 
BMsRU   

  ens1f19000  9934935  0  0 0   2888302  0  0  0 
BMsRU   

  lo   6553621336  0  0 0 21336  0  0  0 
LRU 

[Touch-packages] [Bug 1904700] Re: Mouse settings not reapplied after reconnect or resume

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Mouse settings not reapplied after reconnect or resume

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I upgraded from 18.04 to 20.04 and notice that my mouse settings (I
  mouse lefthanded) are no longer restored/reapplied when I reconnect
  its usb receiver (gets disconnected due to use of KVM switch) or when
  resuming (after suspend). I now have to reselect the right button as
  my primary every time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.xonotic.rules 
70-snap.gnome-calculator.rules 70-snap.gnome-characters.rules 
70-snap.canonical-livepatch.rules 70-snap.chromium.rules 60-vboxdrv.rules
  Date: Wed Nov 18 09:12:11 2020
  InstallationDate: Installed on 2016-07-01 (1600 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20L7001LMH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-54-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=512M-:192M vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to focal on 2020-11-14 (3 days ago)
  dmi.bios.date: 06/04/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET65W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7001LMH
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:svnLENOVO:pn20L7001LMH:pvrThinkPadT480s:rvnLENOVO:rn20L7001LMH:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7001LMH
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1904700/+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 1899146] Re: systemd-resolve has no --verbose or --debug flag

[Dan Streetman]

this is a request that must be taken upstream, not to ubuntu

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  systemd-resolve has no --verbose or --debug flag

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I understand that systemd-resolve is the tool to test queries through
  systemd-resolved.

  When investigation resolution issues (if it resolves fine with dig
  @server domain.to.test but not with systemd-resolved), you can use
  systemd-resolve --status to view the active configuration with the
  link related parameters, OR use systemd-resolve domain.to.test to test
  the resolution (but you have no details, just either a result, or a
  simple "not found").

  It would really help a lot to have either a --verbose or a --debug
  flag, to see which server is queried, why, which domains are actually
  sent in the query (based on the search domains), was the cache used
  (something like the dig output would already be better).

  Thanks!

  Ubuntu version: Ubuntu 18.04.5 LTS
  Systemd version: 237-3ubuntu10.42

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1899146/+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 1895424] Re: duplicate rc local service

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  duplicate rc local service

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Upgrading from Ubuntu 18.04 to 20.04 using "do-release-upgrade -d"

  Creates two systemd services: rc.local and rc-local

  This has the unfortunate event of running /etc/rc.local multiple times
  during bootup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1895424/+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 1874144] Re: Suspends when lid closed despite "do nothing" option after using ext monitor

[Raphael Raccuia]

Still an issue...

** Changed in: systemd (Ubuntu)
   Status: Invalid => 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/1874144

Title:
  Suspends when lid closed despite "do nothing" option after using ext
  monitor

Status in systemd package in Ubuntu:
  New

Bug description:
  I use "do nothing" (... I guess, "ne rien faire" in french) option on
  both battery and supply in power manager. It works until I plug an
  external monitor (DisplayPort), disconnect, then it suspends when
  closing lid.

  Changing options changes nothing in /etc/systemd/logind.conf:

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  #HandleLidSwitch=suspend
  #HandleLidSwitchDocked=ignore
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  #IdleAction=ignore
  #IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192
  #UserTasksMax=33%

  Problem appeared after Mint 18 -> 19 upgrade with 'mintupgrade' tool.

  System:
  Toshiba Tecra A50-A-130

  Linux Mint 19 (= bionic)
  Cinnamon 3.8.9
  5.3.0-46-generic
  Intel© Core™ i7-4600M CPU @ 2.90GHz × 2

  apt-cache policy systemd
  systemd:
Installé : 237-3ubuntu10.39
Candidat : 237-3ubuntu10.39
   Table de version :
   *** 237-3ubuntu10.39 500
  500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10.38 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874144/+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 1890654] Re: udev service does not log

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  udev service does not log

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  By default udev is supposed to log to /var/log.  In Ubuntu 20 it is
  not logging.  Logging was then explicitly enabled by uncommenting this
  line in /etc/udev/udev.conf:

  "udev_log=info"

  After running "systemctl restart udev" and plugging in a USB drive,
  there is still no udev log in /var/log.  Yet /var/log/system shows
  that a device was in fact attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890654/+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 1874144] Re: Suspends when lid closed despite "do nothing" option after using ext monitor

[Raphael Raccuia]

Still an issue. Kernel 5.4.0-74,

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

Title:
  Suspends when lid closed despite "do nothing" option after using ext
  monitor

Status in systemd package in Ubuntu:
  New

Bug description:
  I use "do nothing" (... I guess, "ne rien faire" in french) option on
  both battery and supply in power manager. It works until I plug an
  external monitor (DisplayPort), disconnect, then it suspends when
  closing lid.

  Changing options changes nothing in /etc/systemd/logind.conf:

  [Login]
  #NAutoVTs=6
  #ReserveVT=6
  #KillUserProcesses=no
  #KillOnlyUsers=
  #KillExcludeUsers=root
  #InhibitDelayMaxSec=5
  #HandlePowerKey=poweroff
  #HandleSuspendKey=suspend
  #HandleHibernateKey=hibernate
  #HandleLidSwitch=suspend
  #HandleLidSwitchDocked=ignore
  #PowerKeyIgnoreInhibited=no
  #SuspendKeyIgnoreInhibited=no
  #HibernateKeyIgnoreInhibited=no
  #LidSwitchIgnoreInhibited=yes
  #HoldoffTimeoutSec=30s
  #IdleAction=ignore
  #IdleActionSec=30min
  #RuntimeDirectorySize=10%
  #RemoveIPC=yes
  #InhibitorsMax=8192
  #SessionsMax=8192
  #UserTasksMax=33%

  Problem appeared after Mint 18 -> 19 upgrade with 'mintupgrade' tool.

  System:
  Toshiba Tecra A50-A-130

  Linux Mint 19 (= bionic)
  Cinnamon 3.8.9
  5.3.0-46-generic
  Intel© Core™ i7-4600M CPU @ 2.90GHz × 2

  apt-cache policy systemd
  systemd:
Installé : 237-3ubuntu10.39
Candidat : 237-3ubuntu10.39
   Table de version :
   *** 237-3ubuntu10.39 500
  500 http://ubuntu.ethz.ch/ubuntu bionic-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10.38 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://ubuntu.ethz.ch/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874144/+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 1882547] Re: systemd-resolved dumps core all the time

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: systemd (Ubuntu)
   Status: Invalid => Incomplete

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

Title:
  systemd-resolved dumps core all the time

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  It dumps core all the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jun  8 16:51:11 2020
  ExecutablePath: /usr/lib/systemd/systemd-resolved
  InstallationDate: Installed on 2019-09-30 (252 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. Precision 5530
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: Upgraded to focal on 2020-05-28 (11 days ago)
  dmi.bios.date: 08/22/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.0
  dmi.board.name: 0FP2W2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.0:bd08/22/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5530
  dmi.product.sku: 087D
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.logind.conf: 2019-11-18T09:50:53.885999
  mtime.conffile..etc.systemd.resolved.conf: 2020-06-04T14:51:08.011600

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882547/+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 1876071] Re: text cursor is moved to start of line even if in login prompt

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** Changed in: util-linux (Ubuntu)
   Status: New => Invalid

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

Title:
  text cursor is moved to start of line even if in login prompt

Status in systemd package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Switch to text tty with ++
  3. Enter login, press 

  Expected results:
  * after pressing  the cursor is located next to ":" in "Password:"

  Actual results:
  * after pressing  the cursor is moved in the beginning of the line 
with "Password:"
  * in some case the cursor is located at the first symbol of hostname like in 
the attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Apr 30 12:33:12 2020
  InstallationDate: Installed on 2020-04-24 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/12p, 480M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=e3b26c22-1835-445d-955d-9221190a83ed ro quiet splash
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876071/+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 1881226] Re: package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed
  udev package post-installation script subprocess returned error exit
  status 1

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  ?

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.3.0-55.49-generic 5.3.18
  Uname: Linux 5.3.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Thu May 28 21:49:38 2020
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2019-02-09 (474 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Shuttle Inc. DS81D
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-55-generic 
root=UUID=ea9922c0-ef41-4846-8661-d5e00af2a309 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3.1 failed to install/upgrade: installed 
udev package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-29 (0 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.14
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: FS81
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.14:bd09/17/2018:svnShuttleInc.:pnDS81D:pvrV1.0:rvnShuttleInc.:rnFS81:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: R
  dmi.product.name: DS81D
  dmi.product.sku: 1.0
  dmi.product.version: V1.0
  dmi.sys.vendor: Shuttle Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1881226/+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 1876831] Re: Microbit WebUSB Udev Rule Missing

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Microbit WebUSB Udev Rule Missing

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  
  Expected Result: Micro:Bit shows under Web USB devices in chrome as in 19.10
  What happened: Micro:bit does not show under Web USB Devices unless Udev 
rules are added.

  I re-installed my computer recently to 20.04 as my SSD Died around the
  time it came out so decided to use it as a chance to upgrade at the
  same time.

  I noticed when trying to use the WebUSB Feature of the Micro:bit it
  was no longer detected by chrome (not via the snap and was direct deb)
  and to confirm this issue I tried on my Ubuntu 19.10 laptop and it
  detected the micro:bit via webusb no issue.

  After looking around I added the Udev rule from the microbit site at
  https://support.microbit.org/support/solutions/articles/19000105428
  -webusb-troubleshooting#Linux

  and it did start to work under 20.04.

  I would call this a bug, as for many users going from where it's
  working on one version to not on another I suspect I won't be the only
  user wondering why it isn't working. If it is where Ubuntu 19.10 and
  19.04 (and maybe even earlier) worked then I wouldn't be opening this
  bug.


  Thanks -
  Ryan

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 50-microbit.rules 60-brother-libsane-type1-inst.rules 
.50-microbit.rules.swp 70-snap.snapd.rules
  Date: Tue May  5 00:13:23 2020
  InstallationDate: Installed on 2020-04-26 (8 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS M
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f28437b5-488a-45d8-b5e1-5e26fb587038 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS M
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSM:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSM:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450 AORUS M
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1876831/+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 1850775] Re: DNS info is not loaded by dhclient

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850775/+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 1848623] Re: package systemd 237-3ubuntu10.31 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  package systemd 237-3ubuntu10.31 failed to install/upgrade: installed
  systemd package post-installation script subprocess returned error
  exit status 1

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This error appeared during release upgrade from 17.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.31
  ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16
  Uname: Linux 4.13.0-46-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: amd64
  Date: Fri Oct 18 06:15:02 2019
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: DigitalOcean Droplet
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-46-generic 
root=UUID=a1c86501-45f5-4b0f-a356-9421fe46b341 ro console=tty1 console=ttyS0
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: systemd
  Title: package systemd 237-3ubuntu10.31 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2019-10-18 (0 days ago)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: DigitalOcean
  dmi.bios.version: 20171212
  dmi.chassis.type: 1
  dmi.chassis.vendor: Bochs
  dmi.modalias: 
dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr:
  dmi.product.family: DigitalOcean_Droplet
  dmi.product.name: Droplet
  dmi.product.version: 20171212
  dmi.sys.vendor: DigitalOcean

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1848623/+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 1843857] Re: IPMasquerade=yes -> ignored on eoan

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  IPMasquerade=yes -> ignored on eoan

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I'm testing out eoan, I have a [Network] section with IPMasquerade=yes.
  The system starts without complaint from systemd in the logs, but I see no 
evidence of source natting going on.
  I'm not sure of sub-dependencies, but I think source natting depends on 
libiptc-dev, which I don't see among the listings in eoan.

  I found Systemd-networkd updates 'iptables-legacy' with the source 
natting/masquerade detail -- which is disused by default.

  So it has no effect and doesn't throw an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1843857/+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 1862378] Re: libsystemd-shared broken in Multi-Arch

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  libsystemd-shared broken in Multi-Arch

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I noticed that systemd-machined was failing to start on an arm64 box.
  This box had armhf enabled, and turns out systemd had been cross-
  graded over to systemd:armhf[*]. It still had systemd-container:arm64
  installed, so now I had an arm64 /lib/systemd/systemd-machine, but an
  armhf /lib/systemd/libsystemd-shared-244.so.

  libsystemd-shared-244.so is from the systemd package. Since systemd is
  marked Multi-Arch: foreign, systemd:armhf was able to incorrectly
  satisfy systemd-container:arm64's dependency on systemd.

  [*] kudos to Multi-Arch that I simply hadn't noticed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1862378/+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 1884636] Re: systemd 245.5-3ubuntu1 ADT test failure with linux-5.8 5.8.0-1.2

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  systemd 245.5-3ubuntu1 ADT test failure with linux-5.8 5.8.0-1.2

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200619_224023_f687b@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200620_002130_9921a@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200620_002108_b4135@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200619_214658_5b596@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1884636/+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 1846367] Re: udev /dev/null incorrect permissions after package auto upgrades

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  udev /dev/null incorrect permissions after package auto upgrades

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I've been attempting to determine root cause of this problem for
  months.

  Symptom is group/other permissions being dropped from all /dev/*
  files.

  This only occurs on some machines, so some machine udev updates work,
  some machines quietly fail.

  Looks like the problem relates to...

  1) APT /etc/apt/apt.conf.d/10periodic APT::Periodic::Update-Package-
  Lists == 1, which triggers auto upgrades for critical packages.

  2) This triggers the udev package run as an unattended/automatic
  upgrade.

  3) When udev package updates, /var/log/dpkg.log shows no errors.

  4) /dev/* files have group/other permissions stripped.

  5) LXD containers become unstable, as containers /dev points to
  machine /dev.

  Temp fix is change /etc/apt/apt.conf.d/10periodic - APT::Periodic
  ::Update-Package-Lists == 0 to disable all unattended upgrades.

  Someone let me know where I can find APT/DPKG logs detailing exactly
  what post install hook scripts run for udev, so I can look for errors.

  Or if log verbosity has to be increased for this level of logging, let
  me know how to increase verbosity, so next time udev updates, I can
  provide logging detail sufficient to generate a fix for this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1846367/+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 1885901] Re: timedatectl reports wrong status for timesyncd in core18

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: systemd (Ubuntu Bionic)
   Status: Incomplete => Invalid

** Changed in: systemd (Ubuntu Groovy)
   Status: Incomplete => Invalid

** Changed in: systemd (Ubuntu Focal)
   Status: Incomplete => Invalid

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

Title:
  timedatectl reports wrong status for timesyncd in core18

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in systemd source package in Groovy:
  Invalid

Bug description:
  when calling timedatectl in Ubuntu Core 18 the tool reports the status of the
  systemd-timesyncd.service ... 

  sadly it does report it wrongly (the tool reports it inactive while
  the service is actually running):

  ogra@pi4:~$ timedatectl
Local time: Wed 2020-07-01 10:52:48 UTC
Universal time: Wed 2020-07-01 10:52:48 UTC
  RTC time: n/a
 Time zone: n/a (UTC, +)
 System clock synchronized: yes
  systemd-timesyncd.service active: no
   RTC in local TZ: no
  ogra@pi4:~$ systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; 
vendor preset: enabled)
 Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago
   Docs: man:systemd-timesyncd.service(8)
   Main PID: 779 (systemd-timesyn)
 Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)."
  Tasks: 2 (limit: 4915)
 CGroup: /system.slice/systemd-timesyncd.service
 └─779 /lib/systemd/systemd-timesyncd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885901/+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 1842205] Re: 18 second delay during login

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  18 second delay during login

Status in systemd package in Ubuntu:
  Invalid

Bug description:
   I am experiencing an 18 second delay during login between the
  time the X-server and saved applications start, and the background,
  panels, and rest of the Mate desktop draw.

   I have tried new user with no configuration to eliminate user 
configuration date.  I've tried
  different desktop environments to eliminate them.  I've tried different 
greeters and different
  display managers.  Symptoms don't change.

   Out of desperation I grabbed the most recent systemd off of github and 
compiled and installed
  it, version 243 verses version 240 shipped with Ubuntu 19.04.

   With version 243 login no longer has delay but audio breaks.  The fact 
that replacing systemd
  got rid of the delay tells me the delay is in that package.  I can find 
nothing in the logs that
  would give me a clue as to what is wrong, no errors in that time frame, in 
fact NOTHING logs during
  that interval.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu5.4
  ProcVersionSignature: Ubuntu 5.0.0-27.28-lowlatency 5.0.21
  Uname: Linux 5.0.0-27-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Sep  1 03:19:08 2019
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-27-lowlatency 
root=UUID=718970be-1c9c-4b4e-8940-1e26324e158b ro quiet splash 
xdg.force_integrated=1 modprobe.blacklist=nouveau vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1105
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z390-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.:bvr1105:bd06/06/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  modified.conffile..etc.systemd.journald.conf: [modified]
  modified.conffile..etc.systemd.logind.conf: [modified]
  modified.conffile..etc.systemd.networkd.conf: [modified]
  modified.conffile..etc.systemd.resolved.conf: [modified]
  modified.conffile..etc.systemd.system.conf: [modified]
  modified.conffile..etc.systemd.timesyncd.conf: [modified]
  modified.conffile..etc.systemd.user.conf: [modified]
  mtime.conffile..etc.systemd.journald.conf: 2019-08-31T23:59:42.943575
  mtime.conffile..etc.systemd.logind.conf: 2019-09-01T00:28:56.884198
  mtime.conffile..etc.systemd.networkd.conf: 2019-08-31T23:59:42.978575
  mtime.conffile..etc.systemd.resolved.conf: 2019-09-01T00:28:56.953197
  mtime.conffile..etc.systemd.system.conf: 2019-09-01T00:28:56.906198
  mtime.conffile..etc.systemd.timesyncd.conf: 2019-09-01T00:28:56.956197
  mtime.conffile..etc.systemd.user.conf: 2019-09-01T00:28:56.907198

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842205/+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 1865474] Re: sysytemd-resolved automatically use an ipv6 dns server on lan

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  sysytemd-resolved automatically use an ipv6 dns server on lan

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  i installed focal from the netboot version mini.iso.

  i encountered some problem on dsn configuration and i found that
  systemd-resolved was using an ipv6 dns address

  this is my netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  ens3:
    addresses:
  - 192.168.1.1/24
    gateway4: 192.168.1.212
    nameservers:
    search: [xxx.com]
    addresses: [192.168.1.191, 192.168.1.206]

  this is the output of "systemd-resolved --status"

  Global
     LLMNR setting: no
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
    DNSSEC NTA: 10.in-addr.arpa
    16.172.in-addr.arpa
    168.192.in-addr.arpa
    17.172.in-addr.arpa
    18.172.in-addr.arpa
    19.172.in-addr.arpa
    20.172.in-addr.arpa
    21.172.in-addr.arpa
    22.172.in-addr.arpa
    23.172.in-addr.arpa
    24.172.in-addr.arpa
    25.172.in-addr.arpa
    26.172.in-addr.arpa
    27.172.in-addr.arpa
    28.172.in-addr.arpa
    29.172.in-addr.arpa
    30.172.in-addr.arpa
    31.172.in-addr.arpa
    corp
    d.f.ip6.arpa
    home
    internal
    intranet
    lan
    local
    private
    test

  Link 2 (ens3)
    Current Scopes: DNS
  DefaultRoute setting: yes
     LLMNR setting: yes
  MulticastDNS setting: no
    DNSOverTLS setting: no
    DNSSEC setting: no
  DNSSEC supported: no
    Current DNS Server: fe80::6670:2ff:feb5:d9c8
   DNS Servers: 192.168.1.191
    192.168.1.206
    fe80::6670:2ff:feb5:d9c8
    DNS Domain: xxx.com

  --
  as you can see systemd is using the ipv6 dns server.

  i found that such ip was the address of my openwrt wifi router. dnsmasq is 
disabled for ipv4 lan interface on the router and i never configured an ipv6 
network. Anyway i disabled all the ipv6 dnsmasq feature on the router and after 
a restart this fixed the problem.
  But i think that this is a bug.
  In my netplan i never configured an ipv6 dns nor a ipv6 network; furthermore 
none of my other ubuntu bionic servers showed such a behaviour.
  Also another focal netboot installation i made three weeks ago didn't show 
this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1865474/+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 1864781] Re: System with GeForce GT 520 failed to boot when nvidia-390 was installed

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  System with GeForce GT 520 failed to boot when nvidia-390 was
  installed

Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Won't Fix
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  System booted OK with Nouveau driver.   I used Driver Manager to apply
  change of "Using NVIDIA driver metapackage from nvidia-
  driver-390(proprietary,tested)".   After the NVIDIA proprietary driver
  installation, system failed to boot.   All i get was a blank screen,
  with a blinking cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 26 12:02:15 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: I don't know
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 520] [10de:0de4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 520] [1043:83d2]
  InstallationDate: Installed on 2020-02-26 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD3
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=41ad22bc-7a8c-443f-bcf6-d374c9d921da ro quiet splash text vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F11
  dmi.board.name: P55A-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1864781/+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 1840529] Re: System drop to emergency shell if encrypted home password was not provided

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  System drop to emergency shell if encrypted home password was not
  provided

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  System drop to emergency shell if encrypted partition password was not 
provided.
  So I boot my computer, press enter multiple times and it drops to root shell.
  Also if I turned my computer on and didn't enter any password it will 
eventually drop to root shell.

  I've setup home directory on the encrypted partition.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.25
  ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Aug 17 12:21:17 2019
  MachineType: Dell Inc. Inspiron N4050
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic 
root=UUID=e25d8992-fe1b-4d01-9615-b22536141a31 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0GGRV5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd08/03/2012:svnDellInc.:pnInspironN4050:pvrNotSpecified:rvnDellInc.:rn0GGRV5:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N4050
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840529/+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 1888422] Re: Notebook suspends during boot when booting with lid closed

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Notebook suspends during boot when booting with lid closed

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When I am booting notebook with external monitor connected (either
  directly or through a docking station) and the lid closed I enter the
  full disk encryption password and a moment later the notebook goes to
  suspend state (suspend to RAM) before the GDM login screen shows up on
  the monitor. When I wake the notebook using the power button on the
  docking station (the lid is still closed) everything then works
  correctly.

  It does not matter if the power supply is connected or not.

  The problem shows up in over 95% of cases. (At least once the notebook
  booted normally.)

  The Ubuntu was originally installed in version 19.10 then upgraded to
  20.04. The problem was present in the version 19.10 already. No power
  management or booting changes done outside of the standard GUI
  configuration tools. It is installed in UEFI mode on Lenovo ThinkPad
  T540p.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.4-4ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jul 21 21:02:56 2020
  InstallationDate: Installed on 2020-01-06 (196 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20BFS0JJ04
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: Upgraded to focal on 2020-04-23 (88 days ago)
  dmi.bios.date: 08/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET89WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BFS0JJ04
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET89WW(2.37):bd08/23/2019:svnLENOVO:pn20BFS0JJ04:pvrThinkPadT540p:rvnLENOVO:rn20BFS0JJ04:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T540p
  dmi.product.name: 20BFS0JJ04
  dmi.product.sku: LENOVO_MT_20BF
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1888422/+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 1922485] Re: systemd: slice: Failed to migrate controller cgroups

[Dan Streetman]

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

** This bug has been marked a duplicate of bug 1850667
   Switch to "unified" cgroup hierarchy (cgroupv2)

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

Title:
  systemd: slice: Failed to migrate controller cgroups

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Triaged
Status in systemd package in Debian:
  Fix Released

Bug description:
  Hi,

  during boot those error messages appear in the logs:

  # journalctl | grep controller
  [...]
  Apr 02 20:16:23 vougeot systemd[3155]: -.slice: Failed to migrate controller 
cgroups from /user.slice/user-108.slice/user@108.service, ignoring: Permission 
denied
  Apr 02 20:16:31 vougeot systemd[3512]: -.slice: Failed to migrate controller 
cgroups from /user.slice/user-1000.slice/user@1000.service, ignoring: 
Permission denied

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu2
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun Apr  4 13:29:25 2021
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  modified.conffile..etc.systemd.resolved.conf: [modified]
  mtime.conffile..etc.systemd.resolved.conf: 2021-04-02T13:37:46.839143

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1922485/+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 1840772] Re: Script cannot access network when triggered by udev rule

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Script cannot access network when triggered by udev rule

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I have a script that is triggered by a udev rule, and that needs to
  connect to a remote host.

  The example below works fine in 16.04, but fails in 18.04. It seems
  that the process executing the script is somehow limited wrt. network
  access. The script works fine when started from a shell prompt.

  To reproduce:

  
  - create /tmp/myscript:

  #/bin/sh
  wget -o /tmp/wget.log -O /tmp/index.html http://www.google.com

  
  - create /etc/udev/rules.d/52-netaccess.rules

  ACTION=="add", ATTRS{idVendor}=="cafe", MODE="0660", GROUP="root",
  SUBSYSTEM=="usbmisc", RUN+="/tmp/myscript"

  
  - Plugin a USB device with vendor ID 0xcafe, and check the wget output in 
/tmp/wget.log. 

  On ubuntu 18.04 wget fails with this output:

  --2019-08-19 14:49:43--  http://www.google.com/
  Resolving www.google.com (www.google.com)... failed: Name or service not 
known.
  wget: unable to resolve host address 'www.google.com'

  
  If I use an IP address in the URL there is no resolve error, but then wget 
blocks in the socket connect() syscall (according to strace). At some point the 
script is killed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840772/+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 1857639] Re: DNS server capability detection is broken and has fatal consequences to resolving when DNSSEC is enabled

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  DNS server capability detection is broken and has fatal consequences
  to resolving when DNSSEC is enabled

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I'm running Ubuntu 19.10

  I'm on latest version available from repositories, systemd 242

  I'm expecting upstream DNS server capabilities being detected
  correctly and DNSSEC to keep working. Alternatively I'd expect a
  method of disabling capability checks instead of DNSSEC.

  Currently instead resolved misdetect features suddenly, stops
  resolving all together (fails closed, which is somewhat good).
  Capability reset is a very temporary fix.

  A suggested fix could be (ordered based on how nice of a solution it
  is):

  a. The capability detection is fixed
  (https://github.com/systemd/systemd/issues/9384)

  b. Force-disabling capability detection exists (this is what I also
  requested here: https://github.com/systemd/systemd/issues/14435)

  c. Patch Ubuntu version not to allow such a foot gun, update
  documentation (this is theoretically what Ubuntu could do meanwhile)

  d. Remove DNSSEC from resolved

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857639/+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 1861645] Re: PC fails to shutdown.

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  PC fails to shutdown.

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I have a pc with Motherboard Gigabyte H370M D3H, Processor Intel Core I3 8100 
3.6Ghz 6MbL3, RAM Corsair 16Mb 2400 Hz. I can reboot pc without any problem, 
but pc is stuck on ubuntu logo when I shutdown. while shutdown keyboard and 
mouse are turned off but pc remains on. I have to turn the mains power off to 
shutdown the pc. I think this is a major bug in Ubuntu 19.10. I searched for a 
solution on the internet but could not find any that works. Kindly help to fix 
it.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prakash1438 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2020-01-31 (2 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. H370M-D3H
  Package: systemd 242-7ubuntu3.2
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=UUID=a883551d-0fff-4cdb-bc6d-d442860a0ec0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-29-generic N/A
   linux-backports-modules-5.3.0-29-generic  N/A
   linux-firmware1.183.3
  RfKill:
   
  Tags:  eoan
  Uname: Linux 5.3.0-29-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/14/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F12
  dmi.board.asset.tag: Default string
  dmi.board.name: H370M D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12:bd03/14/2019:svnGigabyteTechnologyCo.,Ltd.:pnH370M-D3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH370MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: H370M-D3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861645/+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 1857994] Re: no keyboard and mouse after exit from virtual terminal

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  no keyboard and mouse after exit from virtual terminal

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  What I expected to happen:
  When exiting from virtual terminal I expected to get back to gnome session 
with working keyboard and mouse.

  What happened instead:
  When exiting from virtual terminal I was switched automatically back to 
(locked) gnome session and keyboard and mouse do not work any more.

  Sequence to reproduce the issue:

  Hint: tty1 and tty2 are used by X for display manager and gnome
  session.

  1) Ctrl + Alt + F3 to switch from X to virtual terminal tty3
  2) Login
  3) Exit (switching back to X is performed automatically)
  4) Result: keyboard/mouse do not work any more (stuck with unusable system 
until power off)

  See also: https://askubuntu.com/questions/1099608/exiting-from-
  virtual-terminal-and-automatically-going-back-to-x-disables-keyboar

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.33
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 31 14:15:50 2019
  InstallationDate: Installed on 2018-08-01 (516 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=bdf52b6d-d54e-44a0-b2d6-323550a872c4 ro
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1001
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 PRO GAMING/AURA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1001:bd06/07/2017:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rn970PROGAMING/AURA:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: SKU
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  mtime.conffile..etc.systemd.system.conf: 2019-12-30T17:49:07.187140
  mtime.conffile..etc.systemd.user.conf: 2019-12-30T17:49:49.868572

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1857994/+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 1840817] Re: System won't suspend when closing the lid of my laptop, just shuts down

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  System won't suspend when closing the lid of my laptop, just shuts
  down

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  1) Using Ubuntu MATE 18.04.3 LTS
  2)systemd: version 237-3ubuntu10.25 /pm-utils: version 1.4.1-17
  3) I expected the laptop to suspend when i closed the lid
  4)It just shut down even though in the logs it reports that it suspended

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.25
  ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Aug 20 17:36:30 2019
  InstallationDate: Installed on 2019-08-15 (5 days ago)
  InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 13d3:3423 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X541SC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=70ef06f6-6585-41c0-9a60-fd2b8b761810 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X541SC.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X541SC
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX541SC.301:bd09/14/2016:svnASUSTeKCOMPUTERINC.:pnX541SC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541SC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X541SC
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840817/+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 1853956] Re: 34 wireguard peers result in invalid peer configuration

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  34 wireguard peers result in invalid peer configuration

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  ubuntu server 18.04.3 LTS
  systemd 237-3ubuntu10.31
  wireguard 0.0.20191012-wg1~bionic from PPA.

  We're using systemd-networkd to configure wireguard via
  wireguard.netdev and wireguard.network files in /etc/systemd/network/.
  All endpoints have IPv4 addresses.

  When we include 34, 35, or 36 [WireGuardPeer] entries in the netdev
  file some peers are configured incorrectly. The affected peers seem to
  be related to the total number of peers (counting from 0 here):

  33 peers: No issue
  34 peers: Peer 1 and 2 fail
  35 peers: Peer 2 and 3 fail
  36 peers: Peer 3 and 4 fail
  37 peers: No issue

  In all cases peer 0 is functional. For an affected pair of peers A and
  B, peer A ends up with the allowed IP address range of peer B. Peer B
  ends up with no allowed IP addresses. This can be seen in the output
  of wg. The connections to both peers fail because of incorrect address
  range assignments.

  We first encountered this issue in a production environment when we
  moved from 33 to 34 unique peers on each server. The issue was
  reproduced on 3 different physical servers with similar configuration
  by adding and removing peer 34.

  The [WireGuardPeer] entries do not need to be unique to reproduce the
  issue. In my testing I used 6 distinct peers and then used 28 or more
  identical copies of a 7th peer. The results were the same.

  In January 2019 a bug was reported that was also related to the number of 
wireguard peers, but the description seems sufficiently different from our case 
that I felt I should file a distinct bug report. Here's a link to that report 
in case I'm wrong about that:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811149

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853956/+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 1871429] Re: session of user time out at shutdown/reboot

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  session of user time out at shutdown/reboot

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  closing user session always times out at reboot/shutdown

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871429/+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 1856811] Re: Systemd warning re moving remaining userspace processes

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Systemd warning re moving remaining userspace processes

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  :~$ dmesg|grep error
  [   49.262644] systemd[1]: Couldn't move remaining userspace processes, 
ignoring: Input/output error
  systemd/focal-proposed,now 244-3ubuntu1 amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1856811/+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 1865181] Re: package systemd 244.3-1ubuntu1 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 127

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  package systemd 244.3-1ubuntu1 failed to install/upgrade: installed
  systemd package post-installation script subprocess returned error
  exit status 127

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  upgrade to 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: systemd 244.3-1ubuntu1
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  Date: Fri Feb 28 18:06:33 2020
  DuplicateSignature:
   package:systemd:244.3-1ubuntu1
   Installing new version of config file /etc/systemd/user.conf ...
   systemd-machine-id-setup: error while loading shared libraries: 
libsystemd-shared-242.so: cannot open shared object file: No such file or 
directory
   dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned 
error exit status 127
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 127
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: Hetzner vServer
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.4-050504-generic 
root=UUID=a19fc250-48f4-458e-a151-15fd77030b56 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.0-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.10
  SourcePackage: systemd
  Title: package systemd 244.3-1ubuntu1 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 
127
  UpgradeStatus: Upgraded to focal on 2020-02-28 (0 days ago)
  dmi.bios.date: 11/11/2017
  dmi.bios.vendor: Hetzner
  dmi.bios.version: 2017
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnHetzner:bvr2017:bd11/11/2017:svnHetzner:pnvServer:pvr2017:cvnQEMU:ct1:cvrNotSpecified:
  dmi.product.family: Hetzner_vServer
  dmi.product.name: vServer
  dmi.product.version: 2017
  dmi.sys.vendor: Hetzner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1865181/+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 1849153] Re: systemd-udev-settle.service blocks boot for ~90s with a debug-logged assertion failure

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  systemd-udev-settle.service blocks boot for ~90s with a debug-logged
  assertion failure

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I started seeing this when I booted this morning, and I've seen it in
  the 2 reboots since (one for a new kernel, one to capture debug logs).
  After modifying /etc/udev/udev.conf to capture debug logging, I see:

  $ journalctl -u systemd-udev-settle.service -b0
  -- Logs begin at Wed 2019-08-14 09:26:57 EDT, end at Mon 2019-10-21 11:53:56 
EDT. --
  Oct 21 11:42:50 surprise udevadm[678]: Assertion 's' failed at 
../src/libsystemd/sd-event/sd-event.c:1688, function 
sd_event_source_set_description(). Ignoring.
  Oct 21 11:44:24 surprise systemd[1]: Started udev Wait for Complete Device 
Initialization.

  (Of possible value for debugging: the last time I rebooted before I
  was seeing this issue was on Oct 7th, so I had the 5.3.0-13-generic
  kernel and, looking at the publishing history, an older version of
  systemd too.)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: udev 242-7ubuntu3
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: i3
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules
  Date: Mon Oct 21 11:50:26 2019
  InstallationDate: Installed on 2019-05-07 (166 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (165 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  mtime.conffile..etc.udev.udev.conf: 2019-10-21T11:39:04.067705

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1849153/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  zfs-initramfs fails with multiple rpool on separate disks

Status in grub2 package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  == Test Case ==
  1. On a multi disks setup, install Ubuntu with ZFS on disk 1
  2. Reboot and make sure everything works as expected
  3. Do a second installation and install Ubuntu with ZFS on disk 2
  4. Reboot

  * Expected Result *
  GRUB should display all the machines available and let the user select which 
installation to boot

  * Actual result *
  - Only one machine is listed
  - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
  - Same problem in the systemd generator which will try to import all the 
rpools.

  == Original Description ==

  I had an Ubuntu old installation that used a ZFS root, using the
  layout described in the ZFS on Linux docs. Consequently, the pool name
  for my Ubuntu installation was "rpool". I'm currently encountering an
  issue with that pool that only allows me to mount it read-only. So,
  I'd like to replicate the datasets from there to a new device.

  On the new device, I've set up a ZFS system using the Ubuntu 20.04
  daily installer (March 9, 2020). This setup creates a new pool named
  "rpool". So, with both devices inserted, I have two distinct pools
  each named "rpool", one of which will kernel panic if I try to mount
  it read-write.

  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a
  distinct pool name on import. However, the grub config for booting
  from ZFS doesn't appear to handle multiple pools with the same rpool
  name very well. Rather than using the pool's GUID, it uses the name,
  and as such, it's unable to boot properly when another pool with the
  name "rpool" is attached to the system.

  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't removed the good pool and I haven't re-run `update-
  grub`. Instead of booting, I'm thrown into the grub command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1869435] Re: Performance regression on ubuntu focal

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Performance regression on ubuntu focal

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hello, I noticed that systmed is performin some tasks much faster in
  bionic than in focal,

  I created a script which iterates doing some operations and executed
  that on bionic and focal: https://paste.ubuntu.com/p/zWWQjndtXx/

  I see for example how systemctl daemon reload takes more time in focal
  even where there are less units than in bionic

  results:
  bionic: https://paste.ubuntu.com/p/z32WScydNk/
  eoan: https://paste.ubuntu.com/p/V98vd5CHwq/
  focal: https://paste.ubuntu.com/p/brNjKvC2gF/

  The tests was done in gce using clean instances type n1-standard-2.

  Please tell me if you need any extra info

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869435/+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 1861289] Re: No virtual terminals and NAutoVTs=6 setting ineffective

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  No virtual terminals and NAutoVTs=6 setting ineffective

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This is not the same bug as #1758512 - that bug is about an
  unresponsive key combination, this bug is reproducible without
  pressing any key-combination.

  Reproduce:

  Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by
  uncommenting this:

  [Login]
  NAutoVTs=6
  ReserveVT=6

  According to man logind.conf  this would result 6 virtual terminals
  spawned.

  
  Bug behaviour:

  Reboot and run

  $ sudo fgconsole --next-available
  3

  Expected:

Given I've configured 6 auto virtual terminals this number should be
  higher than 6.

  Bug behaviour

  Reboot and run:
  $ sudo chvt 3

  Got a screen with a black background and a single blinking cursor at
  upper left corner

  Expected:

Seeing a login prompt
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weiwu  1703 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-11 (232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20KHS1BP00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago)
  UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET50W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1BP00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1BP00
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861289/+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 1871726] Re: "systemd --user" and child processes fail to exit when user logs out

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  "systemd --user" and child processes fail to exit when user logs out

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This concerns systemd 245.2-1ubuntu2 in Ubuntu focal.

  I am using the Xfce desktop. After the user logs out from a desktop
  session, numerous desktop-related processes are left over. Here is a
  listing, taken over twenty minutes after logout:

  skunk853  0.0  0.2  18912 10300 ?Ss   17:55   0:00 
/lib/systemd/systemd --user
  skunk854  0.0  0.0 103304  3496 ?S17:55   0:00 (sd-pam)
  skunk881  0.0  0.1   8076  5324 ?Ss   17:55   0:00 
/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile 
--systemd-activation --syslog-only
  skunk970  0.0  0.1 305364  6776 ?Ssl  17:55   0:00 
/usr/libexec/at-spi-bus-launcher
  skunk975  0.0  0.1   7352  4452 ?S17:55   0:00 
/usr/bin/dbus-daemon 
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork 
--print-address 3
  skunk979  0.0  0.1 230196  5900 ?Sl   17:55   0:00 
/usr/lib/x86_64-linux-gnu/xfce4/xfconf/xfconfd
  skunk992  0.0  0.1 239704  7676 ?Ssl  17:55   0:00 
/usr/libexec/gvfsd
  skunk997  0.0  0.1 378332  6444 ?Sl   17:55   0:00 
/usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes
  skunk   1133  0.0  0.1 156116  5596 ?Sl   17:56   0:00 
/usr/libexec/dconf-service
  skunk   1139  0.0  0.1 236884  4828 ?Sl   17:56   0:00 
/usr/libexec/geoclue-2.0/demos/agent
  skunk   1186  0.0  0.8  59324 34792 ?S17:56   0:00 
/usr/bin/python3 /usr/share/system-config-printer/applet.py
  skunk   1201  0.0  0.6 391676 25688 ?Ssl  17:56   0:00 
/usr/libexec/evolution-source-registry
  skunk   1224  0.0  0.8 616644 35492 ?Sl   17:56   0:00 
/usr/libexec/goa-daemon
  skunk   1235  0.0  0.7 708928 30512 ?Ssl  17:56   0:00 
/usr/libexec/evolution-calendar-factory
  skunk   1243  0.0  0.2 314744  8980 ?Sl   17:56   0:00 
/usr/libexec/goa-identity-service
  skunk   1271  0.0  0.7 681460 29344 ?Ssl  17:56   0:00 
/usr/libexec/evolution-addressbook-factory
  skunk   1302  0.0  0.1  43968  6432 ?Ss   17:56   0:00 
/usr/lib/bluetooth/obexd
  skunk   1322  0.0  0.2 313872  9076 ?Ssl  17:56   0:00 
/usr/libexec/gvfs-udisks2-volume-monitor
  skunk   1327  0.0  0.1 235684  6468 ?Ssl  17:56   0:00 
/usr/libexec/gvfs-mtp-volume-monitor
  skunk   1331  0.0  0.1 237956  6876 ?Ssl  17:56   0:00 
/usr/libexec/gvfs-gphoto2-volume-monitor
  skunk   1335  0.0  0.1 235864  5760 ?Ssl  17:56   0:00 
/usr/libexec/gvfs-goa-volume-monitor
  skunk   1339  0.0  0.2 316716  8800 ?Ssl  17:56   0:00 
/usr/libexec/gvfs-afc-volume-monitor
  skunk   1347  0.0  0.1 313684  7836 ?Sl   17:56   0:00 
/usr/libexec/gvfsd-trash --spawner :1.13 /org/gtk/gvfs/exec_spaw/0
  skunk   1353  0.0  0.1 162128  6028 ?Ssl  17:56   0:00 
/usr/libexec/gvfsd-metadata

  
  When a user logs out of the system, all processes associated with the login 
session should be terminated (barring the use of nohup(1) or the like).

  If I sent a SIGINT to the "systemd --user" process above (PID 853),
  then all the processes promptly go away. This needs to occur on
  logout.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1871726/+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 1818253] Re: 18.10 when lid closed and opened again no keyboard

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  18.10 when lid closed and opened again no keyboard

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Using Dell Inspiron 7000 w/Intel corei7.
  With 18.04 power settings had options for what to do when lid was closed.
  Now available with Gnome-tweak in 18.10.
  However does not work correctly. 

  Did Google search happening to others as well especially with detach
  keyboards which is not my case.

  With 18.10 and tweak setting to suspend when lid closed, the system
  does suspend, however when lid is closed it appears that the on board
  keyboard gets totally dropped when lid is opened back up.

  Have to use touch screen to switch user, then touch screen again at
  login to get a screen keyboard,  sometimes I get the on board keyboard
  back, usually have to reboot to get on on board keyboard back.

  If I power off or restart keyboard works fine.

  Definite regression this has worked for several older versions of
  Ubuntu, at least on this system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818253/+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 1816680] Re: Trying to install 18.04.02 over NFS

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Trying to install 18.04.02 over NFS

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I've just setup an PXE server combined with NFS to install various distros.
  I had some problems booting Ubuntu 18.04.02 because it always went to 
maintenance mode. After reading here that this is a know bug I added 
"systemd.mask=tmp.mount" to the APPEND line.

  Altough this allows me to boot, the installation crashes at some
  point, see my log file below.

  2019-02-19 23:51:38,611 subiquitycore.core:430 Exception in controller.run():
  Traceback (most recent call last):
File 
"/snap/subiquity/664/lib/python3.6/site-packages/subiquitycore/core.py", line 
428, in run
  self.common['loop'].run()
File 
"/snap/subiquity/664/usr/lib/python3/dist-packages/urwid/main_loop.py", line 
286, in run
  self._run()
File 
"/snap/subiquity/664/usr/lib/python3/dist-packages/urwid/main_loop.py", line 
388, in _run
  self.stop()
File 
"/snap/subiquity/664/usr/lib/python3/dist-packages/urwid/main_loop.py", line 
368, in stop
  self.screen.stop()
File 
"/snap/subiquity/664/usr/lib/python3/dist-packages/urwid/display_common.py", 
line 760, in stop
  self._stop()
File 
"/snap/subiquity/664/usr/lib/python3/dist-packages/urwid/raw_display.py", line 
265, in _stop
  self.flush()
File 
"/snap/subiquity/664/usr/lib/python3/dist-packages/urwid/raw_display.py", line 
287, in flush
  self._term_output_file.flush()
  OSError: [Errno 5] Input/output error

  The PXE/NFS server is running Ubuntu 18.04.02 and both the client and
  server are running on VMWare ESXI 6.7.

  My apologies if this has been posted before.

  Kind regards.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1816680/+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 1815987] Re: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I am using Ubuntu 18.04LTS, fresh install from the summer, and
  tmpfiles won't launch since November.

  $ sudo systemctl start systemd-tmpfiles-setup
  Job for systemd-tmpfiles-setup.service failed because the control process 
exited with error code.
  See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" 
for details.
  $ sudo systemctl status systemd-tmpfiles-setup
  ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories
 Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; 
static; vendor preset: enabled)
 Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s 
ago
   Docs: man:tmpfiles.d(5)
 man:systemd-tmpfiles(8)
Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot 
--exclude-prefix=/dev (code=exited, status=1/FAILURE)
   Main PID: 28934 (code=exited, status=1/FAILURE)

  Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and 
Directories...
  Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks 
encountered in /var/lib/colord/icc, refusing.
  Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks 
encountered in /var/lib/systemd/coredump, refusing.
  Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: 
Main process exited, code=exited, status=1/FAILURE
  Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: 
Failed with result 'exit-code'.
  Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile 
Files and Directories.

  Looking at /var/lib/colord/icc:
  kris@mythserver2018:/var/lib/colord/icc$ ls -a
  .  ..
  kris@mythserver2018:/var/lib/colord/icc$ 

  I have also deleted these directories and rebuilt them, just to be sure - 
they are NOT symlinked and have no permission issues:
  kris@mythserver2018:/var/lib/systemd$ ls -l
  total 28
  drwxr-xr-x  2 root root 4096 Feb  9 16:04 catalog
  drwxr-xr-x  2 root root 4096 Dec 28 07:04 coredump
  drwxr-xr-x  2 root root 4096 Jul  8  2018 coredumpold
  drwxr-xr-x 20 root root 4096 Feb  9 16:08 deb-systemd-helper-enabled
  drwxr-xr-x  2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked
  -rw---  1 root root  512 Feb  9 17:34 random-seed
  drwxr-xr-x  2 root root 4096 Jul 10  2018 timers
  lrwxrwxrwx  1 root root   27 Jul  8  2018 timesync -> 
../private/systemd/timesync

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815987/+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 1818226] Re: Please backport PR #8429 from systemd to 18.04

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Please backport PR #8429 from systemd to 18.04

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  We just installed 18.04 on our system and ran into this bug:
  https://github.com/systemd/systemd/issues/8155

  As shown in the thread this issue has been resolved in:
  https://github.com/systemd/systemd/pull/8429

  Unfortunately, this has not been backported to the latest 18.04
  release. This forces us to install 16.04 on our machine. (As this is a
  server, we do not want to install 18.10)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818226/+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 1818243] Re: systemd-logind takes 25s to stop when rebooting

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  systemd-logind takes 25s to stop when rebooting

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Cosmic:
  Won't Fix

Bug description:
  During reboot:

  Mar 01 14:15:52 P8lpar5 systemd[1]: Stopping Login Service...
  [...]
  Mar 01 14:16:17 P8lpar5 systemd-logind[2756]: Failed to abandon session 
scope, ignoring: Connection timed out
  Mar 01 14:16:17 P8lpar5 systemd-logind[2756]: Session 5 logged out. Waiting 
for processes to exit.
  Mar 01 14:16:17 P8lpar5 dbus-daemon[2855]: [system] Failed to activate 
service 'org.freedesktop.systemd1': timed out (service_start_timeout=
  25000ms)
  Mar 01 14:16:17 P8lpar5 systemd[1]: Stopped Login Service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818243/+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 1817721] Re: autopkgtest success rate in Bionic reached an unusable amount

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  autopkgtest success rate in Bionic reached an unusable amount

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,
  Sorry to bother you - it seems we have this discussion every few months or so.

  I was looking at this due to an SRU and I realized that the last 50-100 tests 
on all architectures are currently failing.
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/amd64
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/i386
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/ppc64el
  http://autopkgtest.ubuntu.com/packages/s/systemd/bionic/s390x

  On one hand I see the known flaky boot-and-smoke but that is fine.
  On the other hand I see the test "upstream" failing always and it seems not 
related to the actual proposed packages.

  Please help to resolve this mid-term.
  Short term I'll submit a force-badtest for this as it seems to hold up more 
and more with no gain of seeing plenty of peopl just hitting retry every now 
and then.

  If test "upstream" is utterly broken consider skipping it in the next
  upload that you do for regular service. That would bring back at least
  the remaining tests coverage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817721/+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 1815901] Re: Service: Group name with whitespace not working anymore

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Service: Group name with whitespace not working anymore

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  On Ubuntu 16.04.x, I have a perfectly working custom systemd service
  file which sets username and group for the service as

  [Service]
  User=user
  Group=domain users

  where both group and user come from an AD domain joined to with
  winbind.

  This is not working anymore on 18.04. Even with the group name quoted,
  or mangled with systemd-escape. The service doesn't start with one of
  the following messages in the journal (depending on how it's spelled):

  /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric 
ID: domain users
  /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric 
ID: "domain users"
  /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric 
ID: domain\x20users
  /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric 
ID: domain\ users

  The only thing that works is to use the GID instead of the group name.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Thu Feb 14 12:58:59 2019
  InstallationDate: Installed on 2019-01-28 (16 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   TERM=xterm-256color
   LC_COLLATE=C
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/he--puppet--dev04-root ro
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815901/+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 1812356] Re: AlpsPS/2 ALPS GlidePoint vertical pointer speed is very low

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  AlpsPS/2 ALPS GlidePoint vertical pointer speed is very low

Status in libinput package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.freedesktop.org/libinput/libinput/issues/232

  ---

  While moving pointer (cursor) using Touchpad, vertical movement is
  very slow and short (= less velocity and less acceleration compared to
  horizontal axis). Horizontal movement is fine. So, when circle is
  drawn on the Touchpad, the pointer moves in oval shape.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1168 F pulseaudio
   /dev/snd/controlC0:  user   1168 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 18 10:10:35 2019
  HibernationDevice: RESUME=UUID=5eb56af0-cec9-43d4-b84a-46d561cecb30
  InstallationDate: Installed on 2019-01-13 (4 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80N4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=a791b794-48c2-47fb-b2e6-11085529d9ba ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2016
  dmi.bios.vendor: Lenovo
  dmi.bios.version: BDCN71WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Yoga 500-14IBD
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 500-14IBD
  dmi.modalias: 
dmi:bvnLenovo:bvrBDCN71WW:bd08/03/2016:svnLENOVO:pn80N4:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80N4
  dmi.product.version: Lenovo Yoga 500-14IBD
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1812356/+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 1811628] Re: Ubuntu 18.04 systemctl is-system-running always shows degraded in LXD containers

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Ubuntu 18.04 systemctl is-system-running always shows degraded in LXD
  containers

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Issue in Ubuntu 18.04 LTS:
  lxc launch ubuntu-daily:18.04
  lxc shell 
  # systemctl is-system-running
  degraded

  # systemctl --failed
UNIT LOAD   ACTIVE SUBDESCRIPTION   
  
  ● sys-kernel-config.mount  loaded failed failed Kernel Configuration File 
System
  ● systemd-modules-load.service loaded failed failed Load Kernel Modules  

  Fixed in Ubuntu 19.04:
  lxc launch ubuntu-daily:19.04
  lxc shell 
  systemctl is-system-running
  running

  It appears to be fixed by adding: ConditionVirtualization=!container
  to both.  Can this be backported to 18.04 or are we stuck with special
  casing 18.04 vs future versions?

  As far as I know this is the easiest way to see if a container
  finished starting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811628/+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 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Ubuntu CI that runs tests via autopkgtest for systemd on GitHub
  reports the wrong results

Status in Auto Package Testing:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I'm not sure this is the right place to report this, but apparently
  it's the best way to reach out to Dimitri John Ledkov
  (https://github.com/xnox) and Iain Lane (https://github.com/iainlane),
  who I believe at least know who maintains Ubuntu CI there.

  I'm copying the following verbatim from
  https://github.com/systemd/systemd/pull/11531#issuecomment-464731263
  (where we are kind of discussing the issue):

  > The two PRs you referenced to fail in the `make check` unit tests
  (test-path).

  That's correct that test-path failed but it failed in
  https://github.com/systemd/systemd/pull/11685 while Ubuntu CI reported
  it in https://github.com/systemd/systemd/pull/11686 (that is, in
  https://github.com/systemd/systemd/pull/11686 in the logs for some
  reason UPSTREAM_PULL_REQUEST is 11685 instead of 11686 and something
  like that has happened often lately).

  In
  https://github.com/systemd/systemd/pull/11743#issuecomment-464637797,
  the issue is that Ubuntu CI showed the results for the first version
  of the PR (where there was a bug) and it didn't run the tests against
  the latest version. But in that case it's hard to tell because there
  is no way to figure out what exactly Ubuntu CI tested. That's why I
  asked @xnox to add `git describe` to https://salsa.debian.org/systemd-
  team/systemd/blob/master/debian/extra/checkout-upstream so that by
  looking at UPSTREAM_PULL_REQUEST and the output of `git describe` it
  would be possible to find out what Ubuntu CI reports.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1817344/+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 1817627] Re: systemd-analyze verify reports failure

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  systemd-analyze verify reports failure

Status in Ubuntu Manpage Repository:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Version 237 and 238 of systemd-analyze have a known issue:
  https://github.com/systemd/systemd/issues/8592

  When will a fix be posted?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1817627/+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 1816221] Re: package libpam-systemd:amd64 239-7ubuntu10.7 failed to install/upgrade: installed libpam-systemd:amd64 package post-installation script subprocess returned error exi

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package libpam-systemd:amd64 239-7ubuntu10.7 failed to
  install/upgrade: installed libpam-systemd:amd64 package post-
  installation script subprocess returned error exit status 128

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  My mouse locks up and the only way out is a remote reboot

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libpam-systemd:amd64 239-7ubuntu10.7
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Sat Feb 16 00:47:02 2019
  DuplicateSignature:
   package:libpam-systemd:amd64:239-7ubuntu10.7
   Setting up libpam-systemd:amd64 (239-7ubuntu10.7) ...
   Use of uninitialized value $ret in string eq at 
/usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134.
   dpkg: error processing package libpam-systemd:amd64 (--configure):
installed libpam-systemd:amd64 package post-installation script subprocess 
returned error exit status 128
  ErrorMessage: installed libpam-systemd:amd64 package post-installation script 
subprocess returned error exit status 128
  InstallationDate: Installed on 2019-01-28 (19 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 239-7ubuntu10.7 failed to 
install/upgrade: installed libpam-systemd:amd64 package post-installation 
script subprocess returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1816221/+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 1816630] Re: systemd-timedated fails to start with /tmp as a symlink

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  systemd-timedated fails to start with /tmp as a symlink

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When I try to start the `gnome-control-center`, then it hangs after a
  few seconds.

  I recently changed the timezone due to travelling. I can login
  normally.

  Another source of the error could be, that I symlinked the `/tmp` and
  `/opt` directory to another partition.

  ```
  $ gnome-control-center

  (gnome-control-center:29386): datetime-cc-panel-WARNING **: 10:13:23.508: 
could not get proxy for DateTimeMechanism: Fehler beim Aufruf von 
StartServiceByName für org.freedesktop.timedate1: 
GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms)
  **
  ERROR:../shell/cc-panel.c:202:cc_panel_size_allocate: assertion failed: 
(child)
  Abgebrochen (Speicherabzug geschrieben)
  ```

  ```
  $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path 
/org/freedesktop/timedate1
  Fehler: Zeitüberschreitung wurde erreicht
  ```

  ```
  $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path /
  Fehler: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate 
service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms)
  ```

  ```
  $ timedatectl
  Failed to query server: Failed to activate service 
'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms)
  ```

  ```
  $ timedatectl --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid
  ```

  systemd-timedated service is not starting:
  ```
  $ sudo systemctl status systemd-timedated.service
  ● systemd-timedated.service - Time & Date Service
     Loaded: loaded (/lib/systemd/system/systemd-timedated.service; static; 
vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2019-02-19 10:47:33 CST; 2min 
53s ago
   Docs: man:systemd-timedated.service(8)
     man:localtime(5)
     https://www.freedesktop.org/wiki/Software/systemd/timedated
    Process: 3618 ExecStart=/lib/systemd/systemd-timedated (code=exited, 
status=226/NAMESPACE)
   Main PID: 3618 (code=exited, status=226/NAMESPACE)

  Feb 19 10:47:33 home systemd[1]: Starting Time & Date Service...
  Feb 19 10:47:33 home systemd[3618]: systemd-timedated.service: Failed to set 
up mount namespacing: No such file or directory
  Feb 19 10:47:33 home systemd[3618]: systemd-timedated.service: Failed at step 
NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or directory
  Feb 19 10:47:33 home systemd[1]: systemd-timedated.service: Main process 
exited, code=exited, status=226/NAMESPACE
  Feb 19 10:47:33 home systemd[1]: systemd-timedated.service: Failed with 
result 'exit-code'.
  Feb 19 10:47:33 home systemd[1]: Failed to start Time & Date Service.
  ```

  ```
  $ journalctl -xe
  Feb 19 18:03:59 home ntpd[21785]: 176.221.42.125 local addr 192.168.0.102 -> 

  Feb 19 18:04:05 home sudo[17719]: sebastian : TTY=pts/0 ; PWD=/home/sebastian 
; USER=root ; COMMAND=/bin/systemctl start systemd-timedated
  Feb 19 18:04:05 home sudo[17719]: pam_unix(sudo:session): session opened for 
user root by (uid=0)
  Feb 19 18:04:05 home systemd[1]: Starting Time & Date Service...
  -- Subject: Unit systemd-timedated.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- Unit systemd-timedated.service has begun starting up.
  Feb 19 18:04:05 home systemd[17724]: systemd-timedated.service: Failed to set 
up mount namespacing: No such file or directory
  Feb 19 18:04:05 home systemd[17724]: systemd-timedated.service: Failed at 
step NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or 
directory
  -- Subject: Process /lib/systemd/systemd-timedated could not be executed
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- The process /lib/systemd/systemd-timedated could not be executed and 
failed.
  -- 
  -- The error number returned by this process is 2.
  Feb 19 18:04:05 home systemd[1]: systemd-timedated.service: Main process 
exited, code=exited, status=226/NAMESPACE
  Feb 19 18:04:05 home systemd[1]: systemd-timedated.service: Failed with 
result 'exit-code'.
  Feb 19 18:04:05 home systemd[1]: Failed to start Time & Date Service.
  -- Subject: Unit systemd-timedated.service has failed
  -- Defined-By: systemd
  -- Support: http://www.ubuntu.com/support
  -- 
  -- Unit systemd-timedated.service has failed.
  -- 
  -- The result is RESULT.
  Feb 19

[Touch-packages] [Bug 1817424] Re: Unable to resolve local DNS names provided by router on bootup.

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Unable to resolve local DNS names provided by router on bootup.

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  On boot, I can see systemd-resolve is configured properly; the router
  (192.168.1.254) is listed as a DNS server:

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

  Link 3 (wlp0s20f3)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  Link 2 (eno1)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 192.168.1.254
DNS Domain: telus

  Local names are not resolved:

  $ nslookup zf1

  Server:   127.0.0.53
  Address:  127.0.0.53#53

  ** server can't find zf1: SERVFAIL

  $ dig zf1

  ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> zf1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 39908
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Sat Feb 23 09:46:12 PST 2019
  ;; MSG SIZE  rcvd: 32

  Restarting netplan and network-manager services make no difference.

  Restarting the systemd-resolved (or clearing systemd-resolved caches)
  solve the problem:

  $ sudo systemd-resolve --flush-caches

  OR

  $ sudo service systemd-resolved restart

  $ nslookup zf1
  Server:   127.0.0.53
  Address:  127.0.0.53#53

  Non-authoritative answer:
  Name: zf1.telus
  Address: 192.168.1.71
  ** server can't find zf1.telus: NXDOMAIN

  Dig still can't find server though:

  $ dig zf1

  ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> zf1
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20375
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

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

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Sat Feb 23 09:47:38 PST 2019
  ;; MSG SIZE  rcvd: 32

  Unless I specify the server manually:

  $ dig @192.168.1.254 zf1
  ;; Warning: Message parser reports malformed message packet.

  ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> @192.168.1.254 zf1
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50811
  ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ; COOKIE: 94b92f65104856d4 (echoed)
  ;; QUESTION SECTION:
  ;zf1. IN  A

  ;; ADDITIONAL SECTION:
  zf1.  1   IN  A   192.168.1.71

  ;; Query time: 6 msec
  ;; SERVER: 192.168.1.254#53(192.168.1.254)
  ;; WHEN: Sat Feb 23 09:59:05 PST 2019
  ;; MSG SIZE  rcvd: 60

  Once I get local names resolved, the systemd-resolve status remains
  the same:

  $ systemd-resolve --status
  Global
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
 

[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  storage / luks / dmsetup regressed (or got better) on ppc64le

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  New
Status in systemd source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in systemd source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Won't Fix
Status in systemd package in Debian:
  Fix Released

Bug description:
  in disco proposed with new systemd and v4.19 kernel it appears that
  dmsetup / cryptsetup storage either got better or worse.

  Devices take very long to activate, and sometimes remain in use during
  test clean up.

  This leads to udisks autopkgtest failing on ppc64le and systemd's
  "storage" autopkgtest is also failing.

  I've tried to make ppc64le test more resilient, but it's still odd
  that it became unstable in disco, and used to be rock solid on
  ppc64le.

  --
  sru template for systemd upload:

  [impact]
  buffer overflow can cause memory corruption; this is seen in failed 
autopkgtests

  [test case]
  see comment 6

  [regression potential]
  the patch is minimal and clearly correct; however the regression potential is 
around invalid/corrupted keys read from the keyring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1814457] Re: package udev 239-7ubuntu10.6 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package udev 239-7ubuntu10.6 failed to install/upgrade: installed udev
  package post-installation script subprocess returned error exit status
  1

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  udev failed to upgrade during the upgrade from 18.04.1 LTS to 18.10.

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.6
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CustomUdevRuleFiles: 70-snap.core.rules 70-snap.vlc.rules 
70-snap.spotify.rules 70-snap.brave.rules
  Date: Sun Feb  3 15:49:53 2019
  DuplicateSignature:
   package:udev:239-7ubuntu10.6
   Installing new version of config file /etc/udev/udev.conf ...
   The group `kvm' already exists and is not a system group. Exiting.
   dpkg: error processing package udev (--configure):
installed udev package post-installation script subprocess returned error 
exit status 1
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-07-29 (189 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. XPS13 9333
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: systemd
  Title: package udev 239-7ubuntu10.6 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to cosmic on 2019-02-03 (0 days ago)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay System
  dmi.product.name: XPS13 9333
  dmi.product.sku: 060A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1814457/+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 1812637] Re: systemd-resolved stops resolving

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  systemd-resolved stops resolving

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Regularly (= after about 15 mins of use) the systemd-resolved service
  stops resolving DNS names (any).

  Configuration:
  Two domains defined - one internal, one for external services
  DNS server does not provide DNSSEC services
  Both domains are in the search path (served by DHCP)

  Effect:
  Clients refuse to resolve internal domain servers (short or FQDN) after about 
15 mins.

  Workaround:
  from the client CLI
  sudo systemctl restart systemd-resolved.service

  Background:
  A Github error (https://github.com/systemd/systemd/issues/6490) describes the 
cause to be (missing) DNSSEC.

  I found discussions about "the correct way" DNS works (with only one
  domain).

  Happens exclusively on Ubuntu clients (Windows, Mac and Fedora worked
  fine).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu10.6
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 21 11:57:32 2019
  InstallationDate: Installed on 2018-04-30 (266 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (92 days ago)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812637/+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 1814958] Re: package systemd 237-3ubuntu10 failed to install/upgrade: bloqué en boucle sur le traitement des actions différées (« triggers »), abandon

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  package systemd 237-3ubuntu10 failed to install/upgrade: bloqué en
  boucle sur le traitement des actions différées (« triggers »), abandon

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hi,
  I'm not sure this issue is really a bug.
  Since August 2018, I try to upgrade 16.04.5 to 18.04 LTS with no success.
  Each upgrades are aborted with a loop detected when installing python's 
packages.

  Since PPAs was purged, and I left only one line uncommented in sources.list :
 deb http://fr.archive.ubuntu.com/ubuntu/ bionic main restricted

  So, this is the first time my do-release-upgrade has gone so far, I think 
almost at the end of the upgrade.
  Regards,

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Feb  6 01:01:48 2019
  ErrorMessage: bloqué en boucle sur le traitement des actions différées (« 
triggers »), abandon
  InstallationDate: Installed on 2016-08-16 (904 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 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 062a:4102 Creative Labs 
   Bus 001 Device 002: ID 04b4:8328 Cypress Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-142-generic.efi.signed 
root=/dev/mapper/vgubuntu16-lvroot ro
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: systemd
  Title: package systemd 237-3ubuntu10 failed to install/upgrade: bloqué en 
boucle sur le traitement des actions différées (« triggers »), abandon
  UpgradeStatus: Upgraded to bionic on 2019-02-06 (0 days ago)
  dmi.bios.date: 09/10/2016
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SYSKLi35.86A.0052.2016.0910.1456
  dmi.board.asset.tag: �=\�
  dmi.board.name: NUC6i3SYB
  dmi.board.vendor: Intel corporation
  dmi.board.version: H81132-503
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0052.2016.0910.1456:bd09/10/2016:svn:pn:pvr:rvnIntelcorporation:rnNUC6i3SYB:rvrH81132-503:cvn:ct3:cvr:
  mtime.conffile..etc.systemd.journald.conf: 2018-07-22T13:41:52

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1814958/+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 1814980] Re: timedatectl set-timezone UTC Fails

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  timedatectl set-timezone UTC Fails

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Sorry for the pre-mature post.  First time using this interface.

  I noticed this today; an automated AMI build process failed.

  The AMI in question is ami-0326c210edce0ffa5 AKA (ubuntu-
  eks/k8s_1.10/images/hvm-ssd/ubuntu-
  bionic-18.04-amd64-server-20190204.2).

  The automated build process uses a t2.micro, if that's helpful.

  ```
  ubuntu@ip-172-31-29-182:~$ lsb_release --all
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic
  ```

  Here's the bug:
  ```
  ubuntu@ip-172-31-29-182:~$ timedatectl list-timezones
  UTC
  ubuntu@ip-172-31-29-182:~$ timedatectl set-timezone UTC
  Failed to set time zone: Invalid time zone 'UTC'
  ubuntu@ip-172-31-29-182:~$ timedatectl
    Local time: Thu 2019-02-07 00:10:43 UTC
    Universal time: Thu 2019-02-07 00:10:43 UTC
  RTC time: Thu 2019-02-07 00:10:44
     Time zone: n/a (UTC, +)
     System clock synchronized: yes
  systemd-timesyncd.service active: yes
   RTC in local TZ: no
  ```

  If there's anything else that you need, let me know!.

  EDIT:

  
  ```
  ubuntu@ip-172-31-26-66:~$ timedatectl --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid
  ```

  (hostname is different because this is a new instance, same AMI)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1814980/+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 1813408] Re: package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 127

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Attempting upgrade from 16.04 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 237-3ubuntu10.11
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   systemd: Configure
   initramfs-tools: Configure
   libnss-systemd: Configure
   libpam-systemd: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jan 26 07:52:16 2019
  DpkgTerminalLog:
   Setting up systemd (237-3ubuntu10.11) ...
   systemd-machine-id-setup: error while loading shared libraries: 
libcryptsetup.so.12: cannot open shared object file: No such file or directory
   dpkg: error processing package systemd (--configure):
subprocess installed post-installation script returned error exit status 127
   Setting up initramfs-tools (0.130ubuntu3.6) ...
  DuplicateSignature:
   package:systemd:237-3ubuntu10.11
   Setting up systemd (237-3ubuntu10.11) ...
   systemd-machine-id-setup: error while loading shared libraries: 
libcryptsetup.so.12: cannot open shared object file: No such file or directory
   dpkg: error processing package systemd (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 127
  InstallationDate: Installed on 2016-09-15 (863 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  Lspci: Error: command ['lspci', '-vvnn'] failed with exit code 1: lspci: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by 
/lib/x86_64-linux-gnu/libudev.so.1)
  Lsusb: Error: command ['lsusb'] failed with exit code 1: lsusb: 
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by 
/lib/x86_64-linux-gnu/libudev.so.1)
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-127-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: systemd
  SystemdDelta: Error: command ['systemd-delta'] failed with exit code 127: 
systemd-delta: error while loading shared libraries: libcryptsetup.so.12: 
cannot open shared object file: No such file or directory
  SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', 
'Error:'] failed with exit code 127: systemctl: error while loading shared 
libraries: libcryptsetup.so.12: cannot open shared object file: No such file or 
directory
  Title: package systemd 237-3ubuntu10.11 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 127
  UdevDb:
   Error: command ['udevadm', 'info', '--export-db'] failed with exit code 1: 
udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found 
(required by udevadm)
   udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found 
(required by udevadm)
   udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found 
(required by /lib/x86_64-linux-gnu/libblkid.so.1)
   udevadm: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found 
(required by /lib/x86_64-linux-gnu/libuuid.so.1)
  UpgradeStatus: Upgraded to xenial on 2019-01-26 (0 days ago)
  dmi.bios.date: 07/28/2017
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/28/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  modified.conffile..etc.dhcp.dhclient-enter-hooks.d.resolved: [deleted]
  mtime.conffile..etc.pam.d.systemd-user: 2016-04-12T03:34:03
  mtime.conffile..etc.systemd.journald.conf: 2016-04-12T03:34:03
  mtime.conffile..etc.systemd.logind.conf: 2016-04-12T03:34:03
  mtime.conffile..etc.systemd.resolved.conf: 2016-04-12T03:34:04
  mtime.conffile..etc.systemd.system.conf: 2016-09-07T02:32:47
  mtime.conffile..etc.systemd.timesyncd.conf: 2016-04-12T03:34:04
  mtime.conffile..etc.systemd.user.conf: 2016-04-12T03:34:03

To manage notifications about this bug

[Touch-packages] [Bug 1815045] Re: Failed unmounting /var when it is a separate filesystem

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Failed unmounting /var when it is a separate filesystem

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  In a fresh install of Ubuntu Server 18.04.1 LTS with the /var-
  Filesystem on a separate partition (LVM), there are Errors on
  shutdown/reboot (Failed unmounting /var).

  1) The release
  Release: Ubuntu 18.04.1 LTS

  2) The version
  Version:apt-cache policy systemd
  systemd:  Installed: 237-3ubuntu10.12
Candidate: 237-3ubuntu10.12

  3) What you expected to happen
  Clean unmount of /var Filesystem without Failure

  4) What happened instead
  Console output on shutdown/reboot
  [...]
  [  OK  ] Stopped Flush Journal to Persistent Storage.
  [  OK  ] Stopped target Local File Systems.
   Unmounting /boot...
   Unmounting /var...
   Unmounting /run/user/1000...
  [FAILED] Failed unmounting /var.
  [  OK  ] Stopped File System Check on /dev/mapper/vg_system-lv_var.
  [  OK  ] Unmounted /run/user/1000
  [...]

  Extract from journalctl
  [...]
  Feb 07 13:13:31 x systemd[1]: Stopped Flush Journal to Persistent Storage.
  Feb 07 13:13:31 x systemd[1]: Stopped target Local File Systems.
  Feb 07 13:13:31 x systemd[1]: Unmounting /boot...
  Feb 07 13:13:31 x systemd[1]: Unmounting /var...
  Feb 07 13:13:31 x systemd[1]: Unmounting /run/user/1000...
  Feb 07 13:13:31 x umount[1775]: umount: /var: target is busy.
  Feb 07 13:13:31 x systemd[1]: var.mount: Mount process exited, 
code=exited status=32
  Feb 07 13:13:31 x systemd[1]: Failed unmounting /var.
  Feb 07 13:13:31 x systemd[1]: Stopped File System Check on 
/dev/mapper/vg_system-lv_var.
  Feb 07 13:13:31 x systemd[1]: Unmounted /run/user/1000.
  [...]

  Applying the changes described here:

  https://github.com/systemd/systemd/issues/867#issuecomment-250202183

  let the Error-Messages go away. But are there any side-effects?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815045/+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 1813052] Re: who returns no results

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  who returns no results

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Who returns no results on xenial.

  Here's an strace.  I don't see any obvious difference between it and
  an strace on a system that works (an unupdated xenial or a bionic
  system).

  # strace who
  execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
  brk(NULL)   = 0x9f9000
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
  mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
  close(3)= 0
  access("/etc/ld.so.nohwcap", F_OK)  = -1 ENOENT (No such file or 
directory)
  open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f2253eed000
  mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f225391c000
  mprotect(0x7f2253adc000, 2097152, PROT_NONE) = 0
  mmap(0x7f2253cdc000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f2253cdc000
  mmap(0x7f2253ce2000, 14752, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f2253ce2000
  close(3)= 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f2253eec000
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f2253eeb000
  arch_prctl(ARCH_SET_FS, 0x7f2253eec700) = 0
  mprotect(0x7f2253cdc000, 16384, PROT_READ) = 0
  mprotect(0x60a000, 4096, PROT_READ) = 0
  mprotect(0x7f2253f0b000, 4096, PROT_READ) = 0
  munmap(0x7f2253eee000, 117369)  = 0
  brk(NULL)   = 0x9f9000
  brk(0xa1a000)   = 0xa1a000
  open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
  mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253644000
  close(3)= 0
  access("/var/run/utmpx", F_OK)  = 0
  open("/var/run/utmpx", O_RDONLY|O_CLOEXEC) = 3
  lseek(3, 0, SEEK_SET)   = 0
  alarm(0)= 0
  rt_sigaction(SIGALRM, {0x7f2253a5d380, [], SA_RESTORER, 0x7f22539514b0}, 
{SIG_DFL, [], 0}, 8) = 0
  alarm(10)   = 0
  fcntl(3, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
  read(3, 0x7f2253ce5120, 384)= -1 EISDIR (Is a directory)
  fcntl(3, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
  alarm(0)= 10
  rt_sigaction(SIGALRM, {SIG_DFL, [], SA_RESTORER, 0x7f22539514b0}, NULL, 8) = 0
  close(3)= 0
  close(1)= 0
  close(2)= 0
  exit_group(0)   = ?
  +++ exited with 0 +++

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: coreutils 8.25-2ubuntu3~16.04
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Jan 23 10:39:00 2019
  InstallationDate: Installed on 2016-07-08 (929 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813052/+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 1815876] Re: netdev should be unmounted before NetworkManager stops

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  netdev should be unmounted before NetworkManager stops

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Whenever I try to shutdown my computer it hangs at umounting _netdev
  mounted drives.

  The reason looks as if NetworkManager is stopped and therefore
  connection to the remote devices are lost.

  Suggestion is that NetworkManager shutdown is put at the end of the
  chain. Just as it should be in the beginning to ensure that _netdev
  devices can be mounted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815876/+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 1813400] Re: systemctl doesn't respect --dry-run

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  systemctl doesn't respect --dry-run

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  [Expected behaviour]

  When I use the --dry-run flag with systemctl, I would expect it not to
  take any action, but instead print what it is going to do.

  [Actual behaviour]

  Passing --dry-run doesn't affect the behaviour of systemctl.

  [Test case]

  $ systemctl --dry-run reboot

  Ubuntu version: 18.04.1
  systemd version: 237-3ubuntu10.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1813400/+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 1821496] Re: Sennheiser GSX 1000/1200 Volume control is interpreted badly

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Sennheiser GSX 1000/1200 Volume control is interpreted badly

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  These cards are picked up as having mute/VolUp/VolDown buttons, but
  they only ever report a VolDown. Windows behavior (without manually
  installed drivers) appears to match OS-side volume to the display on
  the card, which suggests the card tries to report its volume level as
  an absolute value. Ubuntu interprets it as turning the volume down
  (even if the volume was actually turned up).

  My workaround was to remap the "buttons" on the card to "reserved"
  using the hwdb and manage OS-side volume with media keys on my actual
  keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.15
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 90-pulseaudio-local.rules 70-snap.core.rules
  Date: Sat Mar 23 23:42:31 2019
  InstallationDate: Installed on 2018-09-12 (193 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=fec38878-ce70-47ad-a40b-7710266eb99b ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87M-E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd08/07/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821496/+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 1824893] Re: When I type systemctl reboot system reaches Target Reboot but then does not reboot

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  When I type systemctl reboot system reaches Target Reboot but then
  does not reboot

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This is similar to the bug where systemd used to get stuck in target
  Shutdown except that bug affected all my hardware, now it gets stuck
  at target Reboot but this only affects my elderly Mac Pro 1,1 and does
  not affect my laptop or i7-6700k and i7-6850k based servers.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-lowlatency 5.0.1
  Uname: Linux 5.0.0-8-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Apr 15 16:30:34 2019
  InstallationDate: Installed on 2018-12-06 (130 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Apple Computer, Inc. MacPro2,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-lowlatency 
root=UUID=a0174789-1f6b-4641-91aa-cbb9d1790807 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/ondemand.service → 
/lib/systemd/system/ondemand.service.d/ubuntustudio.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  UpgradeStatus: Upgraded to disco on 2019-03-08 (38 days ago)
  dmi.bios.date: 07/02/07
  dmi.bios.vendor: Apple Computer, Inc.
  dmi.bios.version: MP21.88Z.007F.B06.0707021348
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F4208DC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Computer, Inc.
  dmi.chassis.version: Mac-F4208DC8
  dmi.modalias: 
dmi:bvnAppleComputer,Inc.:bvrMP21.88Z.007F.B06.0707021348:bd07/02/07:svnAppleComputer,Inc.:pnMacPro2,1:pvr1.0:rvnAppleInc.:rnMac-F4208DC8:rvrPVT:cvnAppleComputer,Inc.:ct2:cvrMac-F4208DC8:
  dmi.product.family: MacPro
  dmi.product.name: MacPro2,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Computer, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+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 1820361] Re: Unable to mount USB hard drive

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  Unable to mount USB hard drive

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  https://github.com/systemd/systemd/issues/12019

  ---

  The USB hard drive does not appear in Nautilus.

  The error that appears in journalctl is:
  systemd-udevd[3453]: Process 'ata_id --export /dev/sdb' failed with exit code 
2.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: systemd 240-6ubuntu1
  Uname: Linux 5.0.2-050002-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 15 20:26:26 2019
  InstallationDate: Installed on 2018-12-02 (103 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.2-050002-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: Upgraded to disco on 2018-12-02 (103 days ago)
  dmi.bios.date: 11/08/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.32:bd11/08/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820361/+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 1820874] Re: [xenial] udev cannot identify fs uuid by builtin blkid (fixed in upstream)

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

Title:
  [xenial] udev cannot identify fs uuid by builtin blkid (fixed in
  upstream)

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  see upstream bug https://github.com/systemd/systemd/issues/6110

  fix
  
https://github.com/poettering/systemd/commit/e2c48187ccb9668dab9f025c9c4228e97927179f

  udev calls libblkid with flag BLKID_SUBLKS_BADCSUM to see all superblocks but
  data in filesystem could be detected as broken superblock of other filesystem:

  root@vla2-4101:~# wipefs -n /dev/sdf2 
  offset   type
  
  0xae9c36ff006nilfs2   [filesystem]
   LABEL:  9-627f5c82-a8f363c9-a716ffb1)
ea9a210be67212ac0ae104ca29ef
  2019-02-14 05:
   UUID:  2c205265-6164-5365-7373-696f6e49643a

  0x438ext4   [filesystem]
   LABEL: /yt/disk5
   UUID:  778742b8-1ac6-45cf-a459-2f7919ba5dd4

  
  normal blkid is fine

  root@vla2-4101:~# blkid -p /dev/sdf2 
  /dev/sdf2: LABEL="/yt/disk5" UUID="778742b8-1ac6-45cf-a459-2f7919ba5dd4" 
VERSION="1.0" TYPE="ext4" USAGE="filesystem" PART_ENTRY_SCHEME="gpt" 
PART_ENTRY_NAME="primary" 
PART_ENTRY_UUID="259f0f4b-eb1e-4c34-a03d-65d04875f10c" 
PART_ENTRY_TYPE="ebd0a0a2-b9e5-4433-87c0-68b6b72699c7" PART_ENTRY_NUMBER="2" 
PART_ENTRY_OFFSET="30720" PART_ENTRY_SIZE="23435786240" PART_ENTRY_DISK="8:80"

  
  builtin blkid sees two different superblocks and cannot decide

  root@vla2-4101:~# udevadm test-builtin blkid /class/block/sdf2
  calling: test-builtin
  === trie on-disk ===
  tool version:  229
  file size: 6841781 bytes
  header size 80 bytes
  strings1755245 bytes
  nodes  5086456 bytes
  Load module index
  Network interface NamePolicy= disabled on kernel command line, ignoring.
  timestamp of '/etc/systemd/network' changed
  timestamp of '/lib/systemd/network' changed
  Parsed configuration file /lib/systemd/network/99-default.link
  Created link configuration context.
  probe /dev/sdf2 raid offset=0
  Unload module index
  Unloaded link configuration context.

  
  root@vla2-4101:~# apt-cache policy udev
  udev:
Installed: 229-4ubuntu21.17
Candidate: 229-4ubuntu21.17

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1820874/+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 1823721] Re: systemctl fstrim.timer freeze computer with a SSD on a dual boot system Windows 10/Ubuntu 18.04

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  systemctl fstrim.timer freeze computer with a SSD  on a dual boot
  system Windows 10/Ubuntu 18.04

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
  computer once a week (usually on Monday midnight) in the case of a
  dual boot system installed on a SSD (Windows/Ubuntu) due to high IO
  overhead. I also had several freeze at boot due to the same problem.

  When the freeze occur I can open a tty terminal and type the command
  iotop to see the process which use that amount of IO. It was mount
  .ntfs-3g which point to my mount point to my Windows 10 install on my
  SSD.

  When the freeze occur the system is not responsive for about 10-15
  minutes.

  I solved my issue by disabling the fstrim.timer entirely with this
  command:

  sudo systemctl disable fstrim.timer

  I can reproduce the problem on my installation by launching the
  fstrim-timer:

  sudo systemctl start fstrim.timer

  Imediately after launching fstrim.timer, iotop display this line at
  top, with my Windows 10 mount point:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
    893 be/4 root0.00 B/s0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user

  And a few minutes later:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
  20077 be/4 root0.00 B/s0.00 B/s  0.00 % 99.45 % fstrim -av

  
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2
  Linux 4.18.0-17-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823721/+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 1874887] Re: package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev
  package post-installation script subprocess returned error exit status
  1

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  this was generated by a report

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   udev:amd64: Install
   libudev1:amd64: Install
   libudev1:amd64: Configure
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.chromium.rules 70-snap.subtitle-edit.rules 
70-snap.core.rules 70-snap.minetest.rules 70-snap.mc-installer.rules
  Date: Fri Apr 24 10:09:35 2020
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2020-04-17 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: ASUSTeK COMPUTER INC. N56VV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=185a0301-89b3-4798-b58b-80794b55d1b7 ro quiet splash
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3 failed to install/upgrade: installed udev 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VV.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VV.201:bd06/05/2013:svnASUSTeKCOMPUTERINC.:pnN56VV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N56VV
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1874887/+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 1821462] Re: Ubuntu 19.04 Desktop:slow boot

[Dan Streetman]

please reopen if this is still an issue

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Ubuntu 19.04 Desktop:slow boot

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Hello,
  I have my ubuntu desktop set to boot text only mode.

  it seems a removable hard drive was pplugged into my machine some time ago.
  On every boot the boot takes a minute and a half to search to see if that 
drive is plugged in.

  I ran systemd-analyze blame

  
  Below is my output:

   37.816s apt-daily.service
2.383s dev-sda4.device
2.381s NetworkManager-wait-online.service
1.198s man-db.service
1.112s dev-loop9.device
1.108s dev-loop8.device
1.098s dev-loop4.device
1.083s dev-loop6.device
1.071s dev-loop10.device
1.057s dev-loop13.device
1.057s dev-loop11.device
1.051s dev-loop7.device
1.051s dev-loop12.device
1.046s dev-loop2.device
1.032s dev-loop14.device
1.024s apt-daily-upgrade.service
1.017s snap-core18-782.mount
 988ms snap-vice\x2djz-22.mount
 983ms snap-gnome\x2dcalculator-260.mount
 949ms dev-loop15.device
 930ms dev-loop3.device
 905ms dev-loop5.device
 901ms dev-loop1.device
 899ms dev-loop0.device
 891ms dev-loop16.device
 878ms snap-gnome\x2d3\x2d26\x2d1604-78.mount
 868ms snap-remmina-2831.mount
 855ms snap-gnome\x2dcharacters-139.mount
 845ms snap-youtube\x2ddl\x2dsnap-1.mount
 844ms dev-loop17.device
 834ms snap-gnome\x2d3\x2d26\x2d1604-74.mount
 824ms snap-gnome\x2d3\x2d28\x2d1804-15.mount
 814ms snap-remmina-2823.mount
 803ms snap-gnome\x2dclocks-85.mount
 798ms snap-gnome\x2dcharacters-206.mount
 793ms snap-core-6350.mount
 783ms snap-core-6531.mount
 776ms udisks2.service
 773ms snap-gnome\x2dlogs-45.mount
 763ms snap-vice\x2djz-20.mount
 753ms snap-gtk\x2dcommon\x2dthemes-1198.mount
 744ms snap-core-6405.mount
 734ms snap-vice\x2djz-19.mount
 733ms snap-gnome\x2dcharacters-124.mount
 725ms snap-gtk\x2dcommon\x2dthemes-1122.mount
 719ms dev-loop18.device
 715ms snap-core18-731.mount
 706ms snap-core18-719.mount
 695ms snap-gnome\x2dcalculator-238.mount
 680ms upower.service
 662ms snap-gnome\x2d3\x2d28\x2d1804-19.mount
 646ms dev-loop19.device
 643ms snap-gtk\x2dcommon\x2dthemes-818.mount
 638ms dev-loop23.device
 626ms snap-gnome\x2dlogs-57.mount
 626ms dev-loop26.device
 610ms snap-gnome\x2dsystem\x2dmonitor-70.mount
 596ms dev-loop21.device
 589ms dev-loop25.device
 587ms dev-loop20.device
 583ms dev-loop24.device
 528ms logrotate.service
 523ms systemd-journal-flush.service
 496ms dev-loop22.device
 491ms dev-loop30.device
 490ms dev-loop27.device
 487ms dev-loop28.device
 433ms networkd-dispatcher.service
 427ms snapd.service
 397ms ModemManager.service
 382ms snap-gnome\x2d3\x2d26\x2d1604-82.mount
 379ms snap-gnome\x2dcalculator-352.mount
 369ms snap-remmina-2819.mount
 362ms snap-gnome\x2d3\x2d28\x2d1804-23.mount
 359ms snap-gnome\x2dsystem\x2dmonitor-57.mount
 340ms accounts-daemon.service
 307ms systemd-logind.service
 281ms keyboard-setup.service
 280ms kmod-static-nodes.service
 261ms dev-hugepages.mount
 260ms avahi-daemon.service
 259ms sys-kernel-debug.mount
 259ms ufw.service
 255ms apport-autoreport.service
 251ms systemd-udev-trigger.service
 242ms systemd-modules-load.service
 232ms systemd-journald.service
 230ms fwupd.service
 206ms apport.service
 196ms dev-mqueue.mount
 194ms apparmor.service
 186ms rsyslog.service
 184ms dev-loop29.device
 182ms NetworkManager.service
 181ms systemd-remount-fs.service
 180ms gdm.service
 174ms nmbd.service
 164ms smbd.service
 164ms wpa_supplicant.service
 157ms dev-loop32.device
 154ms networking.service
 142ms thermald.service