[Touch-packages] [Bug 1782275] Re: Conflict between resolvconf and systemd-resolved dhclient scripts

2020-04-13 Thread Daniel Richard G.
This issue is still present in Ubuntu focal.

Here is what I see that needs to happen:

systemd: The /etc/dhcp/dhclient-enter-hooks.d/resolved script should be
renamed to something like 00resolved or aaa_resolved, so that other
packages that install scripts into that directory will have their
scripts override whatever definitions are in the "resolved" script. (It
is notable that the avahi-autoipd package installs a file named
"zzz_avahi-autoipd" into /etc/dhcp/dhclient-exit-hooks.d/, apparently so
that it always runs last.)

systemd: The "resolved" script itself is obviously a modified version of
the one shipped with resolvconf; a comment at the top still even names
the original project. There is a conditional at the top that checks for
the presence of /lib/systemd/systemd-resolved (exactly where the
original checks for /sbin/resolvconf), but this check is pointless---the
systemd-resolved file not only belongs to the same package as the
script, the package in question is systemd, which for all intents and
purposes cannot be removed. Instead, the check should be on whether
systemd-resolved is enabled, e.g.

if systemctl is-enabled systemd-resolved | fgrep -q enabled ; then

systemd: In general, the "resolved" script could use some cleanup,
particularly on removing bits related to resolvconf that do not apply to
systemd-resolved.

resolvconf: It may be worthwhile for this package to disable systemd-
resolved upon installation (and re-enable it upon renewal), as that
presumably would be the intent of anyone installing it.

** Tags added: focal

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

Title:
  Conflict between resolvconf and systemd-resolved dhclient scripts

Status in resolvconf package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am setting up an Ubuntu 18.04 (bionic) system with ifupdown instead
  of netplan, as the latter does not meet my needs. I am using
  resolvconf to update /etc/resolv.conf from DHCP, as in earlier
  releases.

  Unfortunately, I am not seeing /etc/resolv.conf (actually a symlink to
  /run/resolvconf/resolv.conf) being updated; it is only the boilerplate
  from /etc/resolvconf/resolv.conf.d/head with no server information
  appended. (My "base" and "tail" files are empty.)

  I poked around the scripts in /etc, and believe I have found the
  problem.

  When resolvconf is installed, the following two files are present:

  /etc/dhcp/dhclient-enter-hooks.d/resolvconf
  /etc/dhcp/dhclient-enter-hooks.d/resolved

  Both of these scripts define the make_resolv_conf() shell function.
  What I am seeing is that dhclient runs these two scripts in the
  (alphabetical) order shown, and as the resolved script runs second, it
  overwrites the resolvconf version of the shell function with its own.
  As a result, dhclient does not invoke the appropriate update command
  for resolvconf, even though the hook script was installed correctly.

  Normally, I would remove the package that is providing the "resolved"
  script, but this package is systemd, which cannot be removed. I am not
  sure which of the two packages (resolvconf or systemd) needs to make
  an accommodation for the other, but it is clear that the current
  approach does not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1782275/+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 1872517] Re: video quality is low, also couldn't switch to nvidia video-card

2020-04-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1815531 ***
https://bugs.launchpad.net/bugs/1815531

That's the wrong driver you are trying to install so this is a duplicate
of bug 1815531.

The driver you are seeking is xserver-xorg-video-intel-hwe-18.04 but
actually you should not even install that. The default 'modeset' driver
is more modern and better supported.

** This bug has been marked a duplicate of bug 1815531
   xserver-xorg-video-intel unmet dependencies

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

Title:
  video quality is low, also couldn't switch to nvidia video-card

Status in xorg package in Ubuntu:
  New

Bug description:
  ~$ sudo apt-get install xserver-xorg-video-intel

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

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 23:47:34 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:1331]
   NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:1332]
  InstallationDate: Installed on 2020-04-02 (11 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0408:a061 Quanta Computer, Inc. 
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 8087:0029 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Nitro AN515-54
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=2e2c213b-e6db-4fe8-aec4-f4e8a886b4d8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/09/2020
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.28
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Octavia_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.28
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.28
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd03/09/2020:svnAcer:pnNitroAN515-54:pvrV1.28:rvnCFL:rnOctavia_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
  dmi.product.family: Nitro 5
  dmi.product.name: Nitro AN515-54
  dmi.product.sku: 
  dmi.product.version: V1.28
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872517/+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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.

2020-04-13 Thread Matthew Ruffell
This bug is triggered when I went to upgrade the avahi packages as part of a
daily upgrade in focal:

$ sudo apt list --upgradable
Listing... Done
avahi-autoipd/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6]
avahi-daemon/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6]
avahi-utils/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6]
libavahi-client3/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6]
libavahi-common-data/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6]
libavahi-common3/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6]
libavahi-core7/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6]
libavahi-glib1/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6]
libavahi-ui-gtk3-0/focal 0.7-4ubuntu7 amd64 [upgradable from: 0.7-4ubuntu6]

When the dpkg hook is run to restart the avahi service, seahorse looses
connection to the avahi-daemon:

Apr 14 16:55:10 ubuntu avahi-daemon[694]: Got SIGTERM, quitting.
Apr 14 16:55:10 ubuntu avahi-daemon[694]: Leaving mDNS multicast group on 
interface enp1s0.IPv6 with address fe80::daf8:4688:8169:19b5.
Apr 14 16:55:10 ubuntu avahi-daemon[694]: Leaving mDNS multicast group on 
interface enp1s0.IPv4 with address 192.168.122.34.
Apr 14 16:55:10 ubuntu avahi-daemon[694]: Leaving mDNS multicast group on 
interface lo.IPv6 with address ::1.
Apr 14 16:55:10 ubuntu avahi-daemon[694]: Leaving mDNS multicast group on 
interface lo.IPv4 with address 127.0.0.1.
Apr 14 16:55:10 ubuntu seahorse[2622]: failure communicating with to avahi: 
Daemon connection failed

>From there, seahorse hits the assert at:
https://github.com/lathiat/avahi/blob/master/avahi-common/simple-
watch.c#L273-L282

Apr 14 16:55:10 ubuntu org.gnome.seahorse.Application[2622]: seahorse:
glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.

The avahi daemon continues to stop, and then restarts:

Apr 14 16:55:10 ubuntu dbus-daemon[713]: [system] Activating via systemd: 
service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service' 
requested by ':1.114' (uid=0 pid=789 comm="/usr/sbin/cups-browsed " 
label="/usr/sbin/cups-browsed (enforce)")
Apr 14 16:55:10 ubuntu systemd[1]: Stopping Avahi mDNS/DNS-SD Stack...
Apr 14 16:55:10 ubuntu avahi-daemon[694]: avahi-daemon 0.7 exiting.
Apr 14 16:55:10 ubuntu systemd[1]: avahi-daemon.service: Succeeded.
Apr 14 16:55:10 ubuntu systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Apr 14 16:55:10 ubuntu systemd[1]: Starting Avahi mDNS/DNS-SD Stack...

Then apport goes and makes a crash report:

Apr 14 16:55:11 ubuntu avahi-daemon[4364]: Server startup complete. Host name 
is ubuntu.local. Local service cookie is 3169540412.
Apr 14 16:55:11 ubuntu systemd[1529]: Starting Notification regarding a crash 
report...
Apr 14 16:55:11 ubuntu update-notifier-crash[4516]: /usr/bin/whoopsie
Apr 14 16:55:11 ubuntu update-notifier-crash[4519]: seahorse

The next interesting thing is, if you launch seahorse, then restart
avahi-daemon.service, it prints an error but does not crash:

$ seahorse
$ sudo systemctl restart avahi-daemon.service
(seahorse:6477): seahorse-WARNING **: 17:09:53.344: failure communicating with 
to avahi: Daemon connection failed

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

Title:
  seahorse assert failure: seahorse: glib-watch.c:195: timeout_update:
  Assertion `!t->dead' failed.

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  -
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  -
  seahorse:
Installed: 3.32-1
Candidate: 3.32-1
Version table:
   *** 3.32-1 500
  500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  -

  I have absolutely no idea why or how. Just collected this report from
  apport-cli.

  Some times receiving "internal error" reports, no details provided,
  just "Cancel" or "Send report" options. So, I decided to check apport
  and there was this report.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: seahorse 3.32-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion 
`!t->dead' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 18:09:01 2019
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2019-03-17 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316)
  ProcCmdline: /usr/bin/seahorse --gapplication-service
  Signal: 6
  SourcePackage: seahorse
  StacktraceTop:
   

[Touch-packages] [Bug 1871873] Re: Xorg becomes unresponsive occasionally when system is under heavy load: BUG: triggered 'if (listener >= ti->num_listeners)'

2020-04-13 Thread Daniel van Vugt
** Summary changed:

- Xorg becomes unresponsive occasionally when system is under heavy load.
+ Xorg becomes unresponsive occasionally when system is under heavy load: BUG: 
triggered 'if (listener >= ti->num_listeners)'

** Package changed: xorg (Ubuntu) => xorg-server (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/1871873

Title:
  Xorg becomes unresponsive occasionally when system is under heavy
  load: BUG: triggered 'if (listener >= ti->num_listeners)'

Status in xorg-server package in Ubuntu:
  New

Bug description:
  It seems that (almost daily) my system will "freeze" requiring a hard
  power-off. I presume the problem is in the X server, as it simply
  stops responding to keyboard / mouse inputs. It seems to happen when
  the system is under heavy load.

  I found these lines in the X log, which may be relevant to the issue:

  [140075.416] (EE) client bug: timer event7 keyboard: scheduled expiry is in 
the past (-471ms), your system is too slow
  [140808.222] (EE) BUG: triggered 'if (listener >= ti->num_listeners)'
  [140808.222] (EE) BUG: ../../../../dix/touch.c:1000 in 
TouchListenerAcceptReject()
  [140808.227] (EE)
  [140808.227] (EE) Backtrace:
  [140808.235] (EE) 0: /usr/lib/xorg/Xorg (SwapShorts+0x1ba4) [0x55d22e503464]
  [140808.236] (EE) 1: /usr/lib/xorg/Xorg 
(InitProximityClassDeviceStruct+0x2863) [0x55d22e5c63c3]
  [140808.236] (EE) 2: /usr/lib/xorg/Xorg (XkbProcessKeyboardEvent+0x3b5) 
[0x55d22e5edd25]
  [140808.237] (EE) 3: /usr/lib/xorg/Xorg (mieqProcessDeviceEvent+0x1f5) 
[0x55d22e6194f5]
  [140808.237] (EE) 4: /usr/lib/xorg/Xorg (mieqProcessInputEvents+0x99) 
[0x55d22e619609]
  [140808.237] (EE) 5: /usr/lib/xorg/Xorg (ProcessInputEvents+0x1d) 
[0x55d22e51665d]
  [140808.238] (EE) 6: /usr/lib/xorg/Xorg (SendErrorToClient+0x103) 
[0x55d22e4d8cf3]
  [140808.238] (EE) 7: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x55d22e4dcfd4]
  [140808.240] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) 
[0x7feb5006b0b3]
  [140808.241] (EE) 9: /usr/lib/xorg/Xorg (_start+0x2e) [0x55d22e4c6a3e]
  [140808.241] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Thu Apr  9 11:58:34 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:832c]
  InstallationDate: Installed on 2020-03-31 (8 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 
(20200329)
  MachineType: HP HP Laptop 15-bs0xx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/hplaptop-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832C
  dmi.board.vendor: HP
  dmi.board.version: 25.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd03/30/2018:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn832C:rvr25.26:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bs0xx
  dmi.product.sku: 2DV78UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/xorg-server/+bug/1871873/+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 1872287] Re: I'm getting CPU freezing issues.

2020-04-13 Thread Daniel van Vugt
Please explain in more detail what "CPU freezing issues" means.

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

** Package changed: xorg (Ubuntu) => 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/1872287

Title:
  I'm getting CPU freezing issues.

Status in Ubuntu:
  Incomplete

Bug description:
  The bugs are related to CSGO, getting fps drops after few minutes of
  usage.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  430.50  Thu Sep  5 22:36:31 
CDT 2019
   GCC version:  gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 16:23:27 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.3.0-46-generic, x86_64: installed
   nvidia, 430.50, 5.3.0-46-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:15e0]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:15e0]
  InstallationDate: Installed on 2020-04-10 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=e042896c-2375-42c9-9d7d-2af9ed9e2121 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.306:bd01/02/2018:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL553VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1872287/+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 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

2020-04-13 Thread Pierre Equoy
@Daniel:

I've tried the workaround I've described in bug 1866194 comment 7, but
it doesn't work on this device.

As Rex mentioned, it's probably a known limitation... for the time
being, I'll use the HDMI audio output and plug my headphones to my
external screen (that works fine).

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1871329/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

2020-04-13 Thread Daniel van Vugt
Rocko, that is probably bug 1851992 and not this one. This one is about
lightdm.

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1776622] Re: snapd updates on focal never finish installing. Can't install any other updates.

2020-04-13 Thread Daniel van Vugt
** Tags removed: cosmic rls-cc-incoming

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

Title:
  snapd updates on focal never finish installing. Can't install any
  other updates.

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

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1776622/+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 1820584] Re: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: Assertion `!t->dead' failed.

2020-04-13 Thread Matthew Ruffell
Still happening under Focal to this day.

** Tags added: focal

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

Title:
  seahorse assert failure: seahorse: glib-watch.c:195: timeout_update:
  Assertion `!t->dead' failed.

Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  -
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  -
  seahorse:
Installed: 3.32-1
Candidate: 3.32-1
Version table:
   *** 3.32-1 500
  500 http://br.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status
  -

  I have absolutely no idea why or how. Just collected this report from
  apport-cli.

  Some times receiving "internal error" reports, no details provided,
  just "Cancel" or "Send report" options. So, I decided to check apport
  and there was this report.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: seahorse 3.32-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AssertionMessage: seahorse: glib-watch.c:195: timeout_update: Assertion 
`!t->dead' failed.
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 17 18:09:01 2019
  ExecutablePath: /usr/bin/seahorse
  InstallationDate: Installed on 2019-03-17 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190316)
  ProcCmdline: /usr/bin/seahorse --gapplication-service
  Signal: 6
  SourcePackage: seahorse
  StacktraceTop:
   __assert_fail_base (fmt=0x7f733ae49588 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 
"glib-watch.c", line=195, function=) at assert.c:92
   __GI___assert_fail (assertion=0x7f733aecf02d "!t->dead", file=0x7f733aecf000 
"glib-watch.c", line=195, function=0x7f733aecf1d8 "timeout_update") at 
assert.c:101
   ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
   ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3
   ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1
  Title: seahorse assert failure: seahorse: glib-watch.c:195: timeout_update: 
Assertion `!t->dead' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1820584/+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 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

2020-04-13 Thread Tim Richardson
I have been trying to work out how to log a failed session with plymouth debug 
messages. I finally succeeded, it is attached.
Note that at the end of log file, it goes into suspend. That was me trying to 
power off the machine, and not holding the button long enough. It actually 
suspends and resume right back to the stuck plymouth display, but I don't know 
any way out except to force the machine off.


** Attachment added: "Boot log including plymouth trace messages"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5353608/+files/plymouth_fail.txt

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

Title:
  booting with splash hangs when external monitors are connected (pure
  intel 8th gen laptop)

Status in plymouth package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I think this is a problem with the splash boot loader. This problem is
  not reproduced if using nosplash.

  I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
  graphics.

  Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
  I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.

  In recovery mood, I can log in.

  With no external monitors attached, it works.

  I am used to having such problems with Nvidia graphics is involved,
  but this is not the case on this laptop. It has been happily running
  18.04.

  External displays are recognised if they are connected after login.

  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  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.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/plymouth/+bug/1872159/+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 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

2020-04-13 Thread Tim Richardson
I have been investigating other bug reports. I can't find anything that
helps my very much, but I did note references to timing. It is very
puzzling why I don't have problems when booting from the installation to
an external drive. That drive is actually a USB stick (ext4 formatted).
My internal ssd uses lvm, the stick not, but the stick is also much
slower, just in case that is relevant.

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

Title:
  booting with splash hangs when external monitors are connected (pure
  intel 8th gen laptop)

Status in plymouth package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I think this is a problem with the splash boot loader. This problem is
  not reproduced if using nosplash.

  I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
  graphics.

  Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
  I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.

  In recovery mood, I can log in.

  With no external monitors attached, it works.

  I am used to having such problems with Nvidia graphics is involved,
  but this is not the case on this laptop. It has been happily running
  18.04.

  External displays are recognised if they are connected after login.

  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  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.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/plymouth/+bug/1872159/+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 1872198] Re: [HP Pavilion 17] Lost the use of the numeric keypad

2020-04-13 Thread Daniel van Vugt
** Summary changed:

- perte pave numerique
+ [HP Pavilion 17] Lost the use of the numeric keypad

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

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

Title:
  [HP Pavilion 17] Lost the use of the numeric keypad

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  I lost the use of the numeric keypad while it works in windows.
  Thank you

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 16:17:54 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed
   ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:227c]
  InstallationDate: Installed on 2020-03-23 (18 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  MonitorsUser.xml:
   
   
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic 
root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.57
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 76.35
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.sku: J2U02EA#ABF
  dmi.product.version: 097510405F1620180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872198/+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 1872110] Re: sonido

2020-04-13 Thread Daniel van Vugt
Please run this command to collect more information:

  apport-collect 1872110

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

** Summary changed:

- sonido
+ [Samsung 100NZA] No sound

** Changed in: pulseaudio (Ubuntu)
   Status: New => Incomplete

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

Title:
  [Samsung 100NZA] No sound

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  tengo instalado ubuntu 18.04 de 32 bits y no hay forma de que pueda
  hacer funcionar el sonido, ya probe reinstalando alsa y pulseaudio y
  no hay forma, necesito una ayuda para poder quedarme con este sistema
  operativo, muchas gracias.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-97.98-generic 4.15.18
  Uname: Linux 4.15.0-97-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Apr 10 14:00:24 2020
  DistUpgraded: 2020-04-10 10:09:39,450 WARNING no activity on terminal for 300 
seconds (printer-driver-foo2zjs (i386) instalado)
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Atom Processor D2xxx/N2xxx Integrated Graphics Controller 
[8086:0be1] (rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd Atom Processor D2xxx/N2xxx 
Integrated Graphics Controller [144d:c664]
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 100NZA
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-97-generic 
root=UUID=0e55513e-8acd-4784-affc-3ae8ec7bd17d ro splash quiet
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-04-10 (0 days ago)
  dmi.bios.date: 10/07/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 00OT
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Intel powered classmate PC
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD
  dmi.board.version: 0.1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr00OT:bd10/07/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn100NZA:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD:rnIntelpoweredclassmatePC:rvr0.1:cvnSAMSUNGELECTRONICSCO.,LTD:ct9:cvr0.1:
  dmi.product.family: CedarTrail System
  dmi.product.name: 100NZA
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Apr 10 13:45:55 2020
  xserver.configfile: default
  xserver.errors:
   modeset(0): glamor initialization failed
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.4
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872110/+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 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system

2020-04-13 Thread Daniel van Vugt
** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  After release upgrade, the user loses permissions for several basic
  actions in the system

Status in gdm3 package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged
Status in lxdm package in Ubuntu:
  Triaged
Status in policykit-desktop-privileges package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  - Upgrade Ubuntu to the next release.

  RESULT:
  - The user looses permissions for several basic actions in the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1240336/+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 1872589] [NEW] systemd-networkd is not honoring UseRoutes=false

2020-04-13 Thread Rafael David Tinoco
Public bug reported:

When netplan configures dhcp4-overrides and set "use-routes" to false,
systemd-networkd should be configured with UseRoutes=false. It is.
Unfortunately looks like systemd-networkd is not honoring it and
configuring the default gateways for the interfaces no matter what.

Ubuntu Focal: systemd: 245.4-2ubuntu1



$ sudo cat /etc/netplan/50-cloud-init.yaml
network:
ethernets:
enp5s0:
match:
macaddress: 00:16:3e:af:c4:d6
set-name: eth0
dhcp4: true
dhcp-identifier: mac
enp6s0:
match:
macaddress: 00:16:3e:50:11:9c
set-name: iscsi01
dhcp4: true
dhcp-identifier: mac
dhcp4-overrides:
  use-routes: false
enp7s0:
match:
macaddress: 00:16:3e:b3:cc:50
set-name: iscsi02
dhcp4: true
dhcp-identifier: mac
dhcp4-overrides:
  use-routes: false
version: 2
renderer: networkd



$ cat /var/run/systemd/network/10-netplan-enp6s0.network

[Match]
MACAddress=00:16:3e:50:11:9c
Name=iscsi01

[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6

[DHCP]
ClientIdentifier=mac
RouteMetric=100
UseMTU=true
UseRoutes=false

--

$ ip route show | grep default
default via 10.250.93.1 dev iscsi02 proto dhcp src 10.250.93.101 metric 100
default via 10.250.94.1 dev iscsi01 proto dhcp src 10.250.94.167 metric 100
default via 10.250.97.1 dev eth0 proto dhcp src 10.250.97.123 metric 100

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

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

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

** Description changed:

+ When netplan configures dhcp4-overrides and set "use-routes" to false,
+ systemd-networkd should be configured with UseRoutes=false. It is.
+ Unfortunately looks like systemd-networkd is not honoring it and
+ configuring the default gateways for the interfaces no matter what.
  
- When netplan configures dhcp4-overrides and set "use-routes" to false, 
systemd-networkd should be configured with UseRoutes=false. It is. 
Unfortunately looks like systemd-networkd is not honoring it and configuring 
the default gateways for the interfaces no matter what.
+ Ubuntu Focal: systemd: 245.4-2ubuntu1
  
  
  
  $ sudo cat /etc/netplan/50-cloud-init.yaml
  network:
- ethernets:
- enp5s0:
- match:
- macaddress: 00:16:3e:af:c4:d6
- set-name: eth0
- dhcp4: true
- dhcp-identifier: mac
- enp6s0:
- match:
- macaddress: 00:16:3e:50:11:9c
- set-name: iscsi01
- dhcp4: true
- dhcp-identifier: mac
- dhcp4-overrides:
-   use-routes: false
- enp7s0:
- match:
- macaddress: 00:16:3e:b3:cc:50
- set-name: iscsi02
- dhcp4: true
- dhcp-identifier: mac
- dhcp4-overrides:
-   use-routes: false
- version: 2
- renderer: networkd
+ ethernets:
+ enp5s0:
+ match:
+ macaddress: 00:16:3e:af:c4:d6
+ set-name: eth0
+ dhcp4: true
+ dhcp-identifier: mac
+ enp6s0:
+ match:
+ macaddress: 00:16:3e:50:11:9c
+ set-name: iscsi01
+ dhcp4: true
+ dhcp-identifier: mac
+ dhcp4-overrides:
+   use-routes: false
+ enp7s0:
+ match:
+ macaddress: 00:16:3e:b3:cc:50
+ set-name: iscsi02
+ dhcp4: true
+ dhcp-identifier: mac
+ dhcp4-overrides:
+   use-routes: false
+ version: 2
+ renderer: networkd
  
  
  
  $ cat /var/run/systemd/network/10-netplan-enp6s0.network
  
  [Match]
  MACAddress=00:16:3e:50:11:9c
  Name=iscsi01
  
  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  
  [DHCP]
  ClientIdentifier=mac
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  
  --
  
  $ ip route show | grep default
  default via 10.250.93.1 dev iscsi02 proto dhcp src 10.250.93.101 metric 100
  default via 10.250.94.1 dev iscsi01 proto dhcp src 10.250.94.167 metric 100
  default via 10.250.97.1 dev eth0 proto dhcp src 10.250.97.123 metric 100

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

Title:
  systemd-networkd is not honoring UseRoutes=false

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When netplan configures dhcp4-overrides and set "use-routes" to false,
  systemd-networkd should be configured with UseRoutes=false. It is.
  Unfortunately looks like systemd-networkd is not honoring it and
  configuring 

[Touch-packages] [Bug 1872303] Re: A print screen button doesn't work

2020-04-13 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xfce4 (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/1872303

Title:
  A print screen button doesn't work

Status in xfce4 package in Ubuntu:
  New

Bug description:
  When I push a print screen button - nothing happens, instead of taking
  a screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Apr 12 14:03:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0459]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0459]
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411)
  MachineType: Acer Aspire 5734Z
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2010
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.01
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5734Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.01
  dmi.modalias: 
dmi:bvnAcer:bvrV1.01:bd04/16/2010:svnAcer:pnAspire5734Z:pvrV1.01:rvnAcer:rnAspire5734Z:rvrV1.01:cvnAcer:ct10:cvrV1.01:
  dmi.product.family: Intel_Mobile
  dmi.product.name: Aspire 5734Z
  dmi.product.sku: Montevina_Fab
  dmi.product.version: V1.01
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/xfce4/+bug/1872303/+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 1872539] Re: pulseaudio crashed with SIGABRT in pa_strlist_remove()

2020-04-13 Thread Daniel van Vugt
Tracking in:

https://errors.ubuntu.com/problem/de93de12105e3945db919094e319354997e24b57
https://errors.ubuntu.com/problem/bd0d691273ff0913dce8beca92c5f51fc5e1b6ae
https://errors.ubuntu.com/problem/bafa8f9c59b67bdf475a3ad1f6c6c7a4a250969c


** Description changed:

+ https://errors.ubuntu.com/problem/de93de12105e3945db919094e319354997e24b57
+ https://errors.ubuntu.com/problem/bd0d691273ff0913dce8beca92c5f51fc5e1b6ae
+ https://errors.ubuntu.com/problem/bafa8f9c59b67bdf475a3ad1f6c6c7a4a250969c
+ 
+ ---
+ 
  Ran `pactl unload-module module-native-protocol-unix` (which I probably
  shouldn't have done - I think it would remove all the listening sockets
  that we normally use).
  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  odeda 299003 F pulseaudio
-  /dev/snd/pcmC2D0c:   odeda 299003 F...m pulseaudio
-  /dev/snd/controlC1:  odeda 299003 F pulseaudio
-  /dev/snd/controlC0:  odeda 299003 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  odeda 299003 F pulseaudio
+  /dev/snd/pcmC2D0c:   odeda 299003 F...m pulseaudio
+  /dev/snd/controlC1:  odeda 299003 F pulseaudio
+  /dev/snd/controlC0:  odeda 299003 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Apr 13 11:48:40 2020
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2017-08-17 (970 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no
  ProcEnviron:
-  LANG=en_IL
-  LANGUAGE=en_IL:en
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  XDG_RUNTIME_DIR=
+  LANG=en_IL
+  LANGUAGE=en_IL:en
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
-  pa_strlist_remove () at 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
-  pa_native_protocol_remove_server_string () at 
/usr/lib/pulse-13.99.1/modules/libprotocol-native.so
-  module_native_protocol_unix_LTX_pa__done () at 
/usr/lib/pulse-13.99.1/modules/module-native-protocol-unix.so
-  () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so
-  () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so
+  pa_strlist_remove () at 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
+  pa_native_protocol_remove_server_string () at 
/usr/lib/pulse-13.99.1/modules/libprotocol-native.so
+  module_native_protocol_unix_LTX_pa__done () at 
/usr/lib/pulse-13.99.1/modules/module-native-protocol-unix.so
+  () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so
+  () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so
  Title: pulseaudio crashed with SIGABRT in pa_strlist_remove()
  UpgradeStatus: Upgraded to focal on 2020-02-09 (64 days ago)
  UserGroups: adm cdrom dip disk docker kvm libvirt lpadmin lxd nopasswdlogin 
plugdev sambashare sudo vboxusers wireshark
  dmi.bios.date: 11/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.
  separator:

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

Title:
  pulseaudio crashed with SIGABRT in pa_strlist_remove()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/de93de12105e3945db919094e319354997e24b57
  https://errors.ubuntu.com/problem/bd0d691273ff0913dce8beca92c5f51fc5e1b6ae
  https://errors.ubuntu.com/problem/bafa8f9c59b67bdf475a3ad1f6c6c7a4a250969c

  ---

  Ran `pactl unload-module module-native-protocol-unix` (which I
  probably shouldn't have done - I think it would remove all the
  listening sockets that we normally use).

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  odeda 299003 F pulseaudio
   /dev/snd/pcmC2D0c:   odeda 299003 F...m pulseaudio
   /dev/snd/controlC1:  odeda 299003 F pulseaudio
   /dev/snd/controlC0:  odeda 

[Touch-packages] [Bug 1872580] [NEW] /usr/bin/pulseaudio:6:raise:abort:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done

2020-04-13 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 1872539 ***
https://bugs.launchpad.net/bugs/1872539

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:13.0-3ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/bd0d691273ff0913dce8beca92c5f51fc5e1b6ae 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: disco eoan focal precise quantal

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

Title:
  
/usr/bin/pulseaudio:6:raise:abort:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:13.0-3ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/bd0d691273ff0913dce8beca92c5f51fc5e1b6ae 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872580/+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 1872579] [NEW] /usr/bin/pulseaudio:6:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done:pa_module_free:pa_module_unload_all

2020-04-13 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 1872539 ***
https://bugs.launchpad.net/bugs/1872539

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:13.99.1-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/bafa8f9c59b67bdf475a3ad1f6c6c7a4a250969c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: cosmic disco eoan focal precise

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

Title:
  
/usr/bin/pulseaudio:6:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done:pa_module_free:pa_module_unload_all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:13.99.1-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/bafa8f9c59b67bdf475a3ad1f6c6c7a4a250969c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872579/+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 1872580] Re: /usr/bin/pulseaudio:6:raise:abort:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done

2020-04-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1872539 ***
https://bugs.launchpad.net/bugs/1872539

** This bug has been marked a duplicate of bug 1872539
   pulseaudio crashed with SIGABRT in pa_strlist_remove()

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

Title:
  
/usr/bin/pulseaudio:6:raise:abort:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:13.0-3ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/bd0d691273ff0913dce8beca92c5f51fc5e1b6ae 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872580/+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 1872539] Re: pulseaudio crashed with SIGABRT in pa_strlist_remove()

2020-04-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: pulseaudio (Ubuntu)
   Status: New => Confirmed

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

Title:
  pulseaudio crashed with SIGABRT in pa_strlist_remove()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/de93de12105e3945db919094e319354997e24b57
  https://errors.ubuntu.com/problem/bd0d691273ff0913dce8beca92c5f51fc5e1b6ae
  https://errors.ubuntu.com/problem/bafa8f9c59b67bdf475a3ad1f6c6c7a4a250969c

  ---

  Ran `pactl unload-module module-native-protocol-unix` (which I
  probably shouldn't have done - I think it would remove all the
  listening sockets that we normally use).

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  odeda 299003 F pulseaudio
   /dev/snd/pcmC2D0c:   odeda 299003 F...m pulseaudio
   /dev/snd/controlC1:  odeda 299003 F pulseaudio
   /dev/snd/controlC0:  odeda 299003 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Apr 13 11:48:40 2020
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2017-08-17 (970 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no
  ProcEnviron:
   LANG=en_IL
   LANGUAGE=en_IL:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_strlist_remove () at 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
   pa_native_protocol_remove_server_string () at 
/usr/lib/pulse-13.99.1/modules/libprotocol-native.so
   module_native_protocol_unix_LTX_pa__done () at 
/usr/lib/pulse-13.99.1/modules/module-native-protocol-unix.so
   () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so
   () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so
  Title: pulseaudio crashed with SIGABRT in pa_strlist_remove()
  UpgradeStatus: Upgraded to focal on 2020-02-09 (64 days ago)
  UserGroups: adm cdrom dip disk docker kvm libvirt lpadmin lxd nopasswdlogin 
plugdev sambashare sudo vboxusers wireshark
  dmi.bios.date: 11/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872539/+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 1872539] Re: pulseaudio crashed with SIGABRT in pa_strlist_remove()

2020-04-13 Thread Daniel van Vugt
** Information type changed from Private to Public

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

Title:
  pulseaudio crashed with SIGABRT in pa_strlist_remove()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/de93de12105e3945db919094e319354997e24b57
  https://errors.ubuntu.com/problem/bd0d691273ff0913dce8beca92c5f51fc5e1b6ae
  https://errors.ubuntu.com/problem/bafa8f9c59b67bdf475a3ad1f6c6c7a4a250969c

  ---

  Ran `pactl unload-module module-native-protocol-unix` (which I
  probably shouldn't have done - I think it would remove all the
  listening sockets that we normally use).

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
  Uname: Linux 5.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  odeda 299003 F pulseaudio
   /dev/snd/pcmC2D0c:   odeda 299003 F...m pulseaudio
   /dev/snd/controlC1:  odeda 299003 F pulseaudio
   /dev/snd/controlC0:  odeda 299003 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Mon Apr 13 11:48:40 2020
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2017-08-17 (970 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170725)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no
  ProcEnviron:
   LANG=en_IL
   LANGUAGE=en_IL:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: pulseaudio
  StacktraceTop:
   pa_strlist_remove () at 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so
   pa_native_protocol_remove_server_string () at 
/usr/lib/pulse-13.99.1/modules/libprotocol-native.so
   module_native_protocol_unix_LTX_pa__done () at 
/usr/lib/pulse-13.99.1/modules/module-native-protocol-unix.so
   () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so
   () at /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so
  Title: pulseaudio crashed with SIGABRT in pa_strlist_remove()
  UpgradeStatus: Upgraded to focal on 2020-02-09 (64 days ago)
  UserGroups: adm cdrom dip disk docker kvm libvirt lpadmin lxd nopasswdlogin 
plugdev sambashare sudo vboxusers wireshark
  dmi.bios.date: 11/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0R6JFH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd11/17/2019:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.product.sku: 07BF
  dmi.sys.vendor: Dell Inc.
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872539/+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 1872579] Re: /usr/bin/pulseaudio:6:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done:pa_module_free:pa_module_unload_all

2020-04-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1872539 ***
https://bugs.launchpad.net/bugs/1872539

** This bug has been marked a duplicate of bug 1872539
   pulseaudio crashed with SIGABRT in pa_strlist_remove()

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

Title:
  
/usr/bin/pulseaudio:6:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done:pa_module_free:pa_module_unload_all

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:13.99.1-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/bafa8f9c59b67bdf475a3ad1f6c6c7a4a250969c 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872579/+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 1872581] Re: /usr/bin/pulseaudio:6:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done:pa_module_free:defer_cb

2020-04-13 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1872539 ***
https://bugs.launchpad.net/bugs/1872539

** This bug has been marked a duplicate of bug 1872539
   pulseaudio crashed with SIGABRT in pa_strlist_remove()

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

Title:
  
/usr/bin/pulseaudio:6:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done:pa_module_free:defer_cb

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:13.99.1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/de93de12105e3945db919094e319354997e24b57 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872581/+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 1872581] [NEW] /usr/bin/pulseaudio:6:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done:pa_module_free:defer_cb

2020-04-13 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 1872539 ***
https://bugs.launchpad.net/bugs/1872539

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:13.99.1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/de93de12105e3945db919094e319354997e24b57 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: focal

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

Title:
  
/usr/bin/pulseaudio:6:pa_strlist_remove:pa_native_protocol_remove_server_string:module_native_protocol_unix_LTX_pa__done:pa_module_free:defer_cb

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:13.99.1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/de93de12105e3945db919094e319354997e24b57 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1872581/+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 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

2020-04-13 Thread Michael Bantjes
I'm having the same problem on a Lenovo T430.  If I boot the laptop on
its own, it boots fine.  If it's on the dock, which has two external
monitors attached to it, it boots until it gets to the Ubuntu splash
screen with the spinning propeller tips and never passes that point.
I've left it on overnight and it never completes booting to the desktop.

If I boot it on it's own, sign in to the desktop, and then dock it, both
external monitors are recognized and opening/closing the lid toggles the
multiple pane layouts as expected.

Like Tim, I can get it to fully boot on the dock with multiple monitors
by updating /etc/default/grub to GRUB_CMDLINE_LINUX_DEFAULT="".

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

Title:
  booting with splash hangs when external monitors are connected (pure
  intel 8th gen laptop)

Status in plymouth package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I think this is a problem with the splash boot loader. This problem is
  not reproduced if using nosplash.

  I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
  graphics.

  Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
  I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.

  In recovery mood, I can log in.

  With no external monitors attached, it works.

  I am used to having such problems with Nvidia graphics is involved,
  but this is not the case on this laptop. It has been happily running
  18.04.

  External displays are recognised if they are connected after login.

  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  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.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/plymouth/+bug/1872159/+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 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

2020-04-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: plymouth (Ubuntu)
   Status: New => Confirmed

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

Title:
  booting with splash hangs when external monitors are connected (pure
  intel 8th gen laptop)

Status in plymouth package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I think this is a problem with the splash boot loader. This problem is
  not reproduced if using nosplash.

  I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
  graphics.

  Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
  I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.

  In recovery mood, I can log in.

  With no external monitors attached, it works.

  I am used to having such problems with Nvidia graphics is involved,
  but this is not the case on this laptop. It has been happily running
  18.04.

  External displays are recognised if they are connected after login.

  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  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.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/plymouth/+bug/1872159/+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 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

2020-04-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: xorg (Ubuntu)
   Status: New => Confirmed

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

Title:
  booting with splash hangs when external monitors are connected (pure
  intel 8th gen laptop)

Status in plymouth package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I think this is a problem with the splash boot loader. This problem is
  not reproduced if using nosplash.

  I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
  graphics.

  Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
  I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.

  In recovery mood, I can log in.

  With no external monitors attached, it works.

  I am used to having such problems with Nvidia graphics is involved,
  but this is not the case on this laptop. It has been happily running
  18.04.

  External displays are recognised if they are connected after login.

  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
   tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  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.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/plymouth/+bug/1872159/+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 1869024] Re: add support for DynamicUser feature of systemd

2020-04-13 Thread Simon Déziel
On 2020-04-11 9:04 p.m., Simon Déziel wrote:
> On 2020-04-10 1:16 p.m., Jamie Strandboge wrote:
>> The abstraction is meant to cover the client, not systemd internal
>> specifics. A client simply accessing that DBus API won't need it and a
>> client simply accessing those sockets won't need it. It very well might
>> be that a profiled application is using some *ctl command from systemd
>> that would need it, but in that case said command would need to be added
>> to the policy and the boot-id could be added at that time.
> 
> I don't know as squid, named and samba (to name a few) generate many
> denials trying to read /proc/sys/kernel/random/boot_id. None of those
> are explicitly trying to use the DynamicUser feature. Could it be just a
> side effect of how nsswitch.conf is setup by default?
> 
> $ grep systemd /etc/nsswitch.conf
> passwd: files systemd
> group:  files systemd

This is indeed due to having systemd in the default nsswitch.conf. I've
report the problem in LP: #1872564

Simon

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

Title:
  add support for DynamicUser feature of systemd

Status in snapd:
  In Progress
Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  systemd offers to create dynamic (and semi-stable) users for services.
  This causes many services using Apparmor profiles to trigger those
  denials (even when they don't use the DynamicUser feature):

  audit: type=1107 audit(1585076282.591:30): pid=621 uid=103
  auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/systemd1"
  interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers"
  mask="send" name="org.freedesktop.systemd1" pid=709
  label="/usr/sbin/squid" peer_pid=1 peer_label="unconfined"

  And more recently with systemd 245 this also get shown:

  audit: type=1400 audit(1585139000.628:39): apparmor="DENIED"
  operation="open" profile="/usr/sbin/squid" name="/run/systemd/userdb/"
  pid=769 comm="squid" requested_mask="r" denied_mask="r" fsuid=0 ouid=0

  
  Additional information:
  # lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  # uname -a
  Linux foo.example.com 5.4.0-18-generic #22-Ubuntu SMP Sat Mar 7 18:13:06 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

  # apt-cache policy apparmor squid
  apparmor:
Installed: 2.13.3-7ubuntu2
Candidate: 2.13.3-7ubuntu2
Version table:
   *** 2.13.3-7ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  squid:
Installed: 4.10-1ubuntu1
Candidate: 4.10-1ubuntu1
Version table:
   *** 4.10-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1869024/+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 1872564] [NEW] /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

2020-04-13 Thread Simon Déziel
Public bug reported:

# Description

On a default Focal install, systemd is used when looking up passwd and
group information:

# grep systemd /etc/nsswitch.conf 
passwd: files systemd
group:  files systemd

Daemons confined by Apparmor that also query those "databases" will
cause this Apparmor denial:

audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
operation="open" namespace="root//lxd-fb1_"
profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
ouid=100

Many daemons confined by Apparmor also happen to downgrade their
privileges so they always end up looking up user/group information.

# Steps to reproduce

1) launch a Focal container (named fb1 here)
$ lxc launch images:ubuntu/focal fb1

2) setup apparmor inside the container (already done on official Ubuntu images)
$ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y

3) install bind9
$ lxc exec fb1 -- apt install bind9 -y

4) check kernel logs for DENIED
$ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'


Step 4, should not return anything. Because systemd is involved in the 
user/group lookups, it currently returns the following:

audit: type=1400 audit(1586826072.115:266): apparmor="DENIED" operation="open" 
namespace="root//lxd-fb1_" profile="/usr/sbin/named" 
name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" 
requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:267): apparmor="DENIED" operation="open" 
namespace="root//lxd-fb1_" profile="/usr/sbin/named" 
name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" 
requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:268): apparmor="DENIED" operation="open" 
namespace="root//lxd-fb1_" profile="/usr/sbin/named" 
name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" 
requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:269): apparmor="DENIED" operation="open" 
namespace="root//lxd-fb1_" profile="/usr/sbin/named" 
name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" 
requested_mask="r" denied_mask="r" fsuid=100 ouid=100
audit: type=1400 audit(1586826072.115:270): apparmor="DENIED" operation="open" 
namespace="root//lxd-fb1_" profile="/usr/sbin/named" 
name="/proc/sys/kernel/random/boot_id" pid=13756 comm="named" 
requested_mask="r" denied_mask="r" fsuid=100 ouid=100


# Workaround

1) remove systemd from nsswitch.conf
$ lxc exec fb1 -- sed -i 's/ systemd$/ # systemd/' /etc/nsswitch.conf
2) restart named
$ lxc exec fb1 -- service named restart
3) notice no more denials in kernel logs

# Additional information

root@fb1:~# apt-cache policy apparmor
apparmor:
  Installed: 2.13.3-7ubuntu4
  Candidate: 2.13.3-7ubuntu4
  Version table:
 *** 2.13.3-7ubuntu4 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

root@fb1:~# uname -a
Linux fb1 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

root@fb1:~# lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04

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

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

Title:
  /proc/sys/kernel/random/boot_id rule missing from
  abstractions/nameservice

Status in apparmor package in Ubuntu:
  New

Bug description:
  # Description

  On a default Focal install, systemd is used when looking up passwd and
  group information:

  # grep systemd /etc/nsswitch.conf 
  passwd: files systemd
  group:  files systemd

  Daemons confined by Apparmor that also query those "databases" will
  cause this Apparmor denial:

  audit: type=1400 audit(1586825456.411:247): apparmor="DENIED"
  operation="open" namespace="root//lxd-fb1_"
  profile="/usr/sbin/named" name="/proc/sys/kernel/random/boot_id"
  pid=7370 comm="named" requested_mask="r" denied_mask="r" fsuid=100
  ouid=100

  Many daemons confined by Apparmor also happen to downgrade their
  privileges so they always end up looking up user/group information.

  # Steps to reproduce

  1) launch a Focal container (named fb1 here)
  $ lxc launch images:ubuntu/focal fb1

  2) setup apparmor inside the container (already done on official Ubuntu 
images)
  $ lxc exec fb1 -- apt update && lxc exec fb1 -- apt install apparmor -y

  3) install bind9
  $ lxc exec fb1 -- apt install bind9 -y

  4) check kernel logs for DENIED
  $ journalctl -o cat -b0 -k | grep 'apparmor="DENIED"' | grep -F 
'profile="/usr/sbin/named"'

  
  Step 4, should not return anything. Because systemd is involved in the 
user/group 

[Touch-packages] [Bug 1872474] Re: Missing gpgme-json prevents use of popular Mailvelope browser extension

2020-04-13 Thread Bug Watch Updater
** Changed in: gpgme1.0 (Debian)
   Status: Unknown => New

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

Title:
  Missing gpgme-json prevents use of popular Mailvelope browser
  extension

Status in gpgme1.0 package in Ubuntu:
  Confirmed
Status in gpgme1.0 package in Debian:
  New

Bug description:
  As described at the Mailvelope GitHub repository wiki here
   users are able to use their local GPG keyring via gpgme-
  json (rather than the included Openpgp.js library) with several
  popular webmail services, provided that the gpgme-json binary is
  available to the browser process. I reviewed the file lists for the
  binary packages produced from this source package and found no mention
  of it. Upon closer inspection of the packaging files, the d/rules has
  an override for dh_missing for the file and a note in the changelog
  from 2018, but there was no mention of what the circumstances were
  that necessitated that decision.

  If it's possible to correct the conditions that led to the file's
  exclusion I think it would be well worth pursuing as e-mail becomes
  evermore commercialized on top of an infrastructure that never did
  place much of a premium on privacy.

  I'm running the dev release of Kubuntu 20.04 LTS "Focal Fossa" with
  version 1.13.1-7ubuntu2 of the libgpgme11 package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1872474/+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 1872485] Re: virtualbox-guest-utils fails to install on 20.04

2020-04-13 Thread Bug Watch Updater
** Changed in: virtualbox (Debian)
   Status: Unknown => 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/1872485

Title:
  virtualbox-guest-utils fails to install on 20.04

Status in systemd package in Ubuntu:
  Triaged
Status in virtualbox package in Ubuntu:
  New
Status in virtualbox package in Debian:
  New

Bug description:
  Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on
  ubuntu:focal (20.04) produces a broken state. Debug of `apt-get
  install virtualbox-guest-utils` below.

  Steps to reproduce:

  1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 
test-container)
  2. lxc exec test-container bash
  3. apt update
  4. apt full-upgrade
  5. apt-get install virtualbox-guest-utils

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

  The following packages have unmet dependencies:
   glib-networking : Depends: gsettings-desktop-schemas but it is not going to 
be installed
   init : PreDepends: systemd-sysv but it is not going to be installed

  
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 59
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 59 as a solution to systemd:amd64 59
Or group remove for systemd:amd64
  Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23
Removing libpam-systemd:amd64 rather than change systemd:amd64
  Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libnss-systemd:amd64 14
Removing libnss-systemd:amd64 rather than change systemd:amd64
  Investigating (3) plymouth:amd64 < 0.9.4git20200323-0ubuntu6 @ii mK Ib >
  Broken plymouth:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (>= 
232-8~)
  

[Touch-packages] [Bug 1872551] Re: kubuntu-driver-manager: nvidia driver version switch fails

2020-04-13 Thread Rik Mills
If you install the package aptdaemon, does that help?

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

Title:
  kubuntu-driver-manager: nvidia driver version switch fails

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching the Nvidia driver version with kubuntu-driver-manager
  doesn't work anymore: Selecting a different driver version (nvidia-
  driver-440 instead of the currently selected / installed -390) and
  clicking "Apply Changes" has no effect and produces this error message
  in the terminal:

Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 895, in on_driver_changes_apply
  for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'):
  NameError: name 'get_dependencies' is not defined

  Steps to reproduce:
  - sudo kubuntu-driver-manager
  - Under "Additional Drivers", select a different Nvidia driver version
(in my case: 440 instead of 390)
  - Click "Apply Changes"
  - (observe error message in the terminal)

  Expected result:
  - No error message
  - Nvidia driver version 440 gets installed

  Actual result:
  - Error message
  - No change in the installed Nvidia driver version

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-driver-manager (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 23:41:56 2020
  InstallationDate: Installed on 2016-11-26 (1234 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: kubuntu-driver-manager
  UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1872561] [NEW] apport-bug crashes when launched

2020-04-13 Thread Panos Asproulis
Public bug reported:

When trying to run apport-bug on Focal the application crashes:

$ apport-bug python
Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
ERROR: AttributeError("'NoneType' object has no attribute 'origins'")

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


** Tags: apport-bug focal

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

Title:
  apport-bug crashes when launched

Status in apport package in Ubuntu:
  New

Bug description:
  When trying to run apport-bug on Focal the application crashes:

  $ apport-bug python
  Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
  Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
  Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
  Gdk-Message: 01:49:45.090: Window 0x20f7270 is a temporary window without 
parent, application will not be able to position it on screen.
  ERROR: AttributeError("'NoneType' object has no attribute 'origins'")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1872561/+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 1872551] Re: kubuntu-driver-manager: nvidia driver version switch fails

2020-04-13 Thread Horst Schirmeier
software-properties-gtk works as expected.

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

Title:
  kubuntu-driver-manager: nvidia driver version switch fails

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching the Nvidia driver version with kubuntu-driver-manager
  doesn't work anymore: Selecting a different driver version (nvidia-
  driver-440 instead of the currently selected / installed -390) and
  clicking "Apply Changes" has no effect and produces this error message
  in the terminal:

Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 895, in on_driver_changes_apply
  for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'):
  NameError: name 'get_dependencies' is not defined

  Steps to reproduce:
  - sudo kubuntu-driver-manager
  - Under "Additional Drivers", select a different Nvidia driver version
(in my case: 440 instead of 390)
  - Click "Apply Changes"
  - (observe error message in the terminal)

  Expected result:
  - No error message
  - Nvidia driver version 440 gets installed

  Actual result:
  - Error message
  - No change in the installed Nvidia driver version

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-driver-manager (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 23:41:56 2020
  InstallationDate: Installed on 2016-11-26 (1234 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: kubuntu-driver-manager
  UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1872551] Re: kubuntu-driver-manager: nvidia driver version switch fails

2020-04-13 Thread Hans P . Möller
Could you please test with software-properties-gtk? (you might need to install 
the package)
Then we could know if it is a software-properties-qt or a software-properties-* 
problem.
Thanks!

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

Title:
  kubuntu-driver-manager: nvidia driver version switch fails

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching the Nvidia driver version with kubuntu-driver-manager
  doesn't work anymore: Selecting a different driver version (nvidia-
  driver-440 instead of the currently selected / installed -390) and
  clicking "Apply Changes" has no effect and produces this error message
  in the terminal:

Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 895, in on_driver_changes_apply
  for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'):
  NameError: name 'get_dependencies' is not defined

  Steps to reproduce:
  - sudo kubuntu-driver-manager
  - Under "Additional Drivers", select a different Nvidia driver version
(in my case: 440 instead of 390)
  - Click "Apply Changes"
  - (observe error message in the terminal)

  Expected result:
  - No error message
  - Nvidia driver version 440 gets installed

  Actual result:
  - Error message
  - No change in the installed Nvidia driver version

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-driver-manager (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 23:41:56 2020
  InstallationDate: Installed on 2016-11-26 (1234 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: kubuntu-driver-manager
  UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-13 Thread Panos Asproulis
I have the same problem with my company's email which uses the Rackspace
Outlook 2016 Exchange service. Rackspace told me that they cannot change
the DH key to a value higher than 1024 bits (which I don't believe) and
they suggested that instead the company upgrades to some Office 365
service which supports a higher DH key size. So, at this moment I cannot
use my company's Exchange E-mail from Evolution as I could in the past.

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1872551] Re: kubuntu-driver-manager: nvidia driver version switch fails

2020-04-13 Thread Rik Mills
kubuntu-driver-manager now just launches software-properties-qt, so
changing package to software-properties where the code for that is.

** Package changed: kubuntu-driver-manager (Ubuntu) => software-
properties (Ubuntu)

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

Title:
  kubuntu-driver-manager: nvidia driver version switch fails

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching the Nvidia driver version with kubuntu-driver-manager
  doesn't work anymore: Selecting a different driver version (nvidia-
  driver-440 instead of the currently selected / installed -390) and
  clicking "Apply Changes" has no effect and produces this error message
  in the terminal:

Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 895, in on_driver_changes_apply
  for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'):
  NameError: name 'get_dependencies' is not defined

  Steps to reproduce:
  - sudo kubuntu-driver-manager
  - Under "Additional Drivers", select a different Nvidia driver version
(in my case: 440 instead of 390)
  - Click "Apply Changes"
  - (observe error message in the terminal)

  Expected result:
  - No error message
  - Nvidia driver version 440 gets installed

  Actual result:
  - Error message
  - No change in the installed Nvidia driver version

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: kubuntu-driver-manager (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 23:41:56 2020
  InstallationDate: Installed on 2016-11-26 (1234 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  SourcePackage: kubuntu-driver-manager
  UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1872551/+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 1872551] [NEW] kubuntu-driver-manager: nvidia driver version switch fails

2020-04-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Switching the Nvidia driver version with kubuntu-driver-manager doesn't
work anymore: Selecting a different driver version (nvidia-driver-440
instead of the currently selected / installed -390) and clicking "Apply
Changes" has no effect and produces this error message in the terminal:

  Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 895, in on_driver_changes_apply
for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'):
NameError: name 'get_dependencies' is not defined

Steps to reproduce:
- sudo kubuntu-driver-manager
- Under "Additional Drivers", select a different Nvidia driver version
  (in my case: 440 instead of 390)
- Click "Apply Changes"
- (observe error message in the terminal)

Expected result:
- No error message
- Nvidia driver version 440 gets installed

Actual result:
- Error message
- No change in the installed Nvidia driver version

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: kubuntu-driver-manager (not installed)
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Mon Apr 13 23:41:56 2020
InstallationDate: Installed on 2016-11-26 (1234 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
SourcePackage: kubuntu-driver-manager
UpgradeStatus: Upgraded to focal on 2020-03-06 (38 days ago)

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


** Tags: amd64 apport-bug focal
-- 
kubuntu-driver-manager: nvidia driver version switch fails
https://bugs.launchpad.net/bugs/1872551
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to software-properties in Ubuntu.

-- 
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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2020-04-13 Thread ironincoder
I have been trying to get ALC298 working for a while now and wanted to
share my findings. This issue exist on all distros and is an ALSA
problem (not pulseaudio). Verified it when found a fix for the headphone
by using the kernel's early patching feature. To use this feature, write
a simple patch (instructions here
https://www.kernel.org/doc/html/v5.0/sound/hd-audio/notes.html):

[codec]
0x10ec0298 0x144dc169 0

[model]
auto

[verb]
0x1a 0x707 0xc5

and save it as /lib/firmware/alc298-sound-patch.fw then save:

options snd-hda-intel patch=alc298-sound-patch.fw,alc298-sound-
patch.fw,alc298-sound-patch.fw,alc298-sound-patch.fw

to /etc/modprobe.d/alc298-sound-patch.conf

Then reboot the machine and try your headphones. Next speakers!
unfortunately all three mixer pins in the hda codec are set to mute and
I'm working like a maniac to find a way of unmuting them, hoping that
would fix the speakers. Hope this helps someone.

Went from web development to system development over this issue. Some
may call that progress!

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: 

[Touch-packages] [Bug 1868246] Re: No network after subiquity LPAR installation on s390x with VLAN

2020-04-13 Thread Michael Hudson-Doyle
So we believe this bug is now fixed but can you confirm Frank?

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

Title:
  No network after subiquity LPAR installation on s390x with VLAN

Status in cloud-init:
  Invalid
Status in subiquity:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I tried today an subiquity LPAR installation using the latest ISO (March 19) 
that includes the latest 20.03 subiquity.
  The installation itself completed fine, but after the post-install reboot the 
system didn't had a network active - please note that the LPAR is connected to 
a VLAN.

  $ ip a   
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000   
  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 
  
  inet 127.0.0.1/8 scope host lo
  
 valid_lft forever preferred_lft forever
  
  inet6 ::1/128 scope host  
  
 valid_lft forever preferred_lft forever
  
  2: encc000:  mtu 1500 qdisc noop state DOWN group 
default q
  len 1000  
  
  link/ether a2:8d:91:85:12:e3 brd ff:ff:ff:ff:ff:ff
  
  3: enP1p0s0:  mtu 1500 qdisc noop state DOWN group 
default 
  qlen 1000 
  
  link/ether 82:0c:2d:0c:b8:70 brd ff:ff:ff:ff:ff:ff
  
  4: enP1p0s0d1:  mtu 1500 qdisc noop state DOWN group 
defaul
  t qlen 1000   
  
  link/ether 82:0c:2d:0c:b8:71 brd ff:ff:ff:ff:ff:ff
  
  5: enP2p0s0:  mtu 1500 qdisc noop state DOWN group 
default 
  qlen 1000 
  
  link/ether 82:0c:2d:0c:b7:00 brd ff:ff:ff:ff:ff:ff
  
  6: enP2p0s0d1:  mtu 1500 qdisc noop state DOWN group 
defaul
  t qlen 1000   
  
  link/ether 82:0c:2d:0c:b7:01 brd ff:ff:ff:ff:ff:ff   

  Wanting to have a look at the netplan config it turned out that there is no 
yaml file:
  $ ls -l /etc/netplan/
  total 0  

  Adding one manually and applying it worked fine.

  So looks like the installer does not properly generate or copy a
  01-netcfg.yaml to /etc/netplan.

  Please see below the entire steps as well as a compressed file with
  the entire content of /var/log

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1868246/+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 1870930] Re: systemctl crashed with SIGSEGV

2020-04-13 Thread Brian Murray
** Tags removed: apport-failed-retrace

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  New

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  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.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870930/+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 1872215] Re: There should be a GUI option to install non-security packages too

2020-04-13 Thread Balint Reczey
** Changed in: unattended-upgrades (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  There should be a GUI option to install non-security packages too

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  The Software & Updates program lacks the option for the user to allow
  Ubuntu to automatically install non-security packages. It only
  supports security packages.

  I know Unattended-upgrades supports automatic upgrading of other
  packages but it might be too complicated for new users. There should
  be an easier way.

  Consider that Windows also deals with software updates "unattended" by
  default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1872215/+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 1864558] Re: Printer adds automatically at boot with notification or if printer deleted

2020-04-13 Thread Mark Richards
The bug referenced above #1725955 goes back to 2017. This issue I
describe has only started with focal 20.04 (I don't get the issue on
19.10 or any earlier release with the same laptop/network/printer
setup). Even if I don't remove the printer I still get the notification
that a my HP Envy wireless printer has been added each time I reboot,
popping up on the Ubuntu logon/greeter screen. If I can help by
providing more info or further testing please ask.

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

Title:
  Printer adds automatically at boot with notification or if printer
  deleted

Status in cups package in Ubuntu:
  New

Bug description:
  When booting 20.04 I get a notification on the logon screen each time
  advising that my wireless printer has been setup. If I remove the
  printer via settings, then as soon as it's removed, it gets re-added
  and I see the same notification as I do on the logon screen about the
  printer having been setup. I've attached a screenshot of this
  notification.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.35.91-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 24 21:49:43 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-02-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+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 1870930] StacktraceSource.txt

2020-04-13 Thread Apport retracing service
** Attachment added: "StacktraceSource.txt"
   
https://bugs.launchpad.net/bugs/1870930/+attachment/5353471/+files/StacktraceSource.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/1870930

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  New

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  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.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870930/+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 1870930] Stacktrace.txt

2020-04-13 Thread Apport retracing service
** Attachment added: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1870930/+attachment/5353470/+files/Stacktrace.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/1870930

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  New

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  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.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870930/+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 1870930] ThreadStacktrace.txt

2020-04-13 Thread Apport retracing service
** Attachment added: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1870930/+attachment/5353472/+files/ThreadStacktrace.txt

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1870930/+attachment/5347081/+files/CoreDump.gz

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  New

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  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.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870930/+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 1870930] systemctl crashed with SIGSEGV

2020-04-13 Thread Apport retracing service
StacktraceTop:
 ?? ()
 bus_wait_for_units_clear (d=0x565151b0be80) at 
../src/shared/bus-wait-for-units.c:94
 bus_wait_for_units_clear (d=d@entry=0x565151b0be80) at 
../src/shared/bus-wait-for-units.c:83
 match_disconnected (m=0x565151b11ae0, userdata=0x565151b0be80, 
error=) at ../src/shared/bus-wait-for-units.c:109
 bus_match_run (bus=bus@entry=0x565151b07c10, node=0x565151b0bf40, 
m=m@entry=0x565151b11ae0) at ../src/libsystemd/sd-bus/bus-match.c:319

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  New

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  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.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870930/+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 1870585] Re: Not cleaning /var/tmp by default

2020-04-13 Thread Dan Streetman
Also, might I suggest that the sosreport package includes its own
systemd tmpfiles.d config?  Something like:

# Remove sosreport files on each boot
r! /var/tmp/sosreport-*


or if the policy should be age-based instead of (or in addition to) removing 
each boot, something like:


# Remove sosreports after 60 days
e /var/tmp/sosreport-* - - - 60d

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

Title:
  Not cleaning /var/tmp by default

Status in systemd package in Ubuntu:
  New

Bug description:
  1) 20.04
  2) 245.2-1ubuntu2
  3) I expect /var/tmp to be cleaned up in some way.
  4) It's commented out per 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773313

  In sosreport was comparing the difference between /tmp (Ubuntu/Debian)
  and /var/tmp (RH) and determined that as long as /var/tmp gets cleaned
  on a regular basis we would prefer /var/tmp.

  The  bug that appears to have prompted the disabling was fixed a long
  time ago, can we have this 30d delete re-enabled by default?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870585/+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 1870585] Re: Not cleaning /var/tmp by default

2020-04-13 Thread Dan Streetman
> 4) It's commented out per https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=773313

no, that's regarding a bug with the related x entries; the difference in
behavior from upstream originates from https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=675422

To be clear:

upstream behavior:
/tmp:
 -by default, /tmp is a tmpfs (via tmp.mount service), so everything under it 
is lost each boot
 -however, if the tmp.mount service is disabled/removed, a 'normal' /tmp dir is 
created
 -with tmp.mount disabled, /tmp is *not* cleaned each boot - items are 
persistent
 -/tmp content is cleaned with 10d aging time
/var/tmp: 
 -there is no corresponding tmp.mount for /var/tmp, so it is just a normal 
(temp) dir
 -it is *not* cleaned each boot - items are persistent (this is correct per FHS)
 -/var/tmp content is cleaned with 30d aging time

debian/ubuntu behavior:
/tmp
 -debian removes (actually, moves) the tmp.mount service so it is not available 
(by default)
 -/tmp is thus a 'normal' (temp) dir
 -debian changes the tmp.conf entry for /tmp to be 'D' instead of 'q'
 -because it is 'D', all its content is removed each boot
 -debian removes the aging time so /tmp is *not* cleaned by age!
/var/tmp
 -debian removes this tmpfiles.d entry completely, so this dir is NOT managed 
by tmpfiles
 -the dir is not created by systemd, but by 'base-files' pkg
 -/var/tmp content is *never cleaned up by systemd ever*
 -as a specific exception, /var/tmp/systemd-private-* content is configured 
separately as R!, which removes just those dirs, only at boot

There is also a minor difference in that default upstream uses 'q' which
(according to the docs) only has a meaningful difference for systems
with a btrfs / fs.

> In sosreport was comparing the difference between /tmp (Ubuntu/Debian)
and /var/tmp (RH) and determined that as long as /var/tmp gets cleaned
on a regular basis we would prefer /var/tmp.

Also note that, except Debian/Ubuntu, systems using systemd will, by
default, have /tmp configured as tmpfs, so dropping really large
sosreports in there may not be good.


Personally, I think there are really 3 changes to consider here, and they 
should be considered first for Debian and then for Ubuntu:

1. should /tmp change to a tmpfs, as upstream systemd defaults to?
2. should files under /tmp be removed with 10-day aging, as upstream systemd 
defaults to?
3. should files under /var/tmp be removed with 30-day aging, as upstream 
systemd defaults to?

Again, personally, I think #1 is a significant policy change and I don't
really see a strong reason to change our default behavior.

For #2, since it's configured to be cleaned out each boot, I think a
age-based cleaning policy isn't as important.  A 10-day aging policy
probably makes more sense when matched with upstream's default of using
tmpfs.

However, for #3, as /var/tmp is persistent storage, I tend to think
*some* kind of age-based cleanup does make sense.  I don't know if 30
days is the right number to move to from our current never-clean, but
personally I think some finite cleanup policy would be good to set by
default.

Have you opened a Debian bug?


** Bug watch added: Debian Bug tracker #773313
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773313

** Bug watch added: Debian Bug tracker #675422
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675422

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

Title:
  Not cleaning /var/tmp by default

Status in systemd package in Ubuntu:
  New

Bug description:
  1) 20.04
  2) 245.2-1ubuntu2
  3) I expect /var/tmp to be cleaned up in some way.
  4) It's commented out per 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773313

  In sosreport was comparing the difference between /tmp (Ubuntu/Debian)
  and /var/tmp (RH) and determined that as long as /var/tmp gets cleaned
  on a regular basis we would prefer /var/tmp.

  The  bug that appears to have prompted the disabling was fixed a long
  time ago, can we have this 30d delete re-enabled by default?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870585/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-13 Thread Steven Jay Cohen
Thank you for the testing link.

https://www.ssllabs.com/ssltest/analyze.html?d=shibboleth.nyu.edu=on

This server supports weak Diffie-Hellman (DH) key exchange parameters.
This server does not support Forward Secrecy with the reference browsers.
This server supports TLS 1.0 and TLS 1.1.

So, you are saying that unless the University upgrades on their end, I
cannot connect from 20.04, correct?

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1872485] Re: virtualbox-guest-utils fails to install on 20.04

2020-04-13 Thread Balint Reczey
** Also affects: virtualbox (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: Debian Bug tracker #956577
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956577

** Also affects: virtualbox (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956577
   Importance: Unknown
   Status: Unknown

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

Title:
  virtualbox-guest-utils fails to install on 20.04

Status in systemd package in Ubuntu:
  Triaged
Status in virtualbox package in Ubuntu:
  New
Status in virtualbox package in Debian:
  Unknown

Bug description:
  Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on
  ubuntu:focal (20.04) produces a broken state. Debug of `apt-get
  install virtualbox-guest-utils` below.

  Steps to reproduce:

  1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 
test-container)
  2. lxc exec test-container bash
  3. apt update
  4. apt full-upgrade
  5. apt-get install virtualbox-guest-utils

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

  The following packages have unmet dependencies:
   glib-networking : Depends: gsettings-desktop-schemas but it is not going to 
be installed
   init : PreDepends: systemd-sysv but it is not going to be installed

  
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 59
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 59 as a solution to systemd:amd64 59
Or group remove for systemd:amd64
  Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23
Removing libpam-systemd:amd64 rather than change systemd:amd64
  Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 

[Touch-packages] [Bug 1872517] [NEW] video quality is low, also couldn't switch to nvidia video-card

2020-04-13 Thread Yerdos
Public bug reported:

~$ sudo apt-get install xserver-xorg-video-intel

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

The following packages have unmet dependencies:
 xserver-xorg-video-intel : Depends: xorg-video-abi-23
Depends: xserver-xorg-core (>= 2:1.18.99.901)
E: Unable to correct problems, you have held broken packages.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 23:47:34 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:1331]
 NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:1332]
InstallationDate: Installed on 2020-04-02 (11 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0408:a061 Quanta Computer, Inc. 
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 004: ID 8087:0029 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Nitro AN515-54
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=2e2c213b-e6db-4fe8-aec4-f4e8a886b4d8 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.28
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Octavia_CFS
dmi.board.vendor: CFL
dmi.board.version: V1.28
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.28
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.28:bd03/09/2020:svnAcer:pnNitroAN515-54:pvrV1.28:rvnCFL:rnOctavia_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28:
dmi.product.family: Nitro 5
dmi.product.name: Nitro AN515-54
dmi.product.sku: 
dmi.product.version: V1.28
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
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

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


** Tags: amd64 apport-bug bionic 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/1872517

Title:
  video quality is low, also couldn't switch to nvidia video-card

Status in xorg package in Ubuntu:
  New

Bug description:
  ~$ sudo apt-get install xserver-xorg-video-intel

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

  The following packages have unmet dependencies:
   xserver-xorg-video-intel : Depends: xorg-video-abi-23
  Depends: xserver-xorg-core (>= 2:1.18.99.901)
  E: Unable to correct problems, you have held broken packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 23:47:34 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 

[Touch-packages] [Bug 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-13 Thread Steven Jay Cohen
My University Account (NYU) uses Shibboleth. I was able to add that
account to Online Accounts in 19.10 but it fails with this error in
20.04.

Are you saying that the minimal level of crypto changed between 19.10
and 20.04?

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-13 Thread Tom Reynolds
There is no easy way to gracefully handle weak crypto. It has been known
for more than five years that 1024 bit (or rather <2048 bit) DH primes
need to be considered weak and should not be used - https://weakdh.org/
- GnuTLS > 3.2 does the right thing in having services which still have
not taken action to use contemporary (non weak) crypto fail by default,
so that users will become aware of the fact they are (were) connecting
insecurely, and these services can be more easily identified and fixed.

In some cases, using clients (and software versions of client) which
support higher TLS protocol versions can work around this problem (if
remote servers support strong ciphers on higher TLS protocol versions;
example:
https://www.ssllabs.com/ssltest/analyze.html?d=mail.nhs.net=on
).

It *may* be possible to continue to allow for insecure connections by
setting the GnuTLS priority string to include LEGACY as per
https://gnutls.org/manual/html_node/Priority-Strings.html

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Confirmed

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: evolution (Ubuntu)
   Status: New => Confirmed

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1872485] Re: virtualbox-guest-utils fails to install on 20.04

2020-04-13 Thread Steve Langasek
The bug is in systemd-timesyncd, which has added a Conflicts: against
virtualbox-guest-utils and virtualbox-guest-utils-hwe forcing their
uninstallation when this is not intended.  This has been corrected
already in Debian in commit 02e27e24e4f84335f360c085d1e8c3f11bd12349
which we should cherry-pick.

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

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  virtualbox-guest-utils fails to install on 20.04

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on
  ubuntu:focal (20.04) produces a broken state. Debug of `apt-get
  install virtualbox-guest-utils` below.

  Steps to reproduce:

  1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 
test-container)
  2. lxc exec test-container bash
  3. apt update
  4. apt full-upgrade
  5. apt-get install virtualbox-guest-utils

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

  The following packages have unmet dependencies:
   glib-networking : Depends: gsettings-desktop-schemas but it is not going to 
be installed
   init : PreDepends: systemd-sysv but it is not going to be installed

  
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 59
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 59 as a solution to systemd:amd64 59
Or group remove for systemd:amd64
  Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23
Removing libpam-systemd:amd64 rather than change systemd:amd64
  Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libnss-systemd:amd64 Depends on 

[Touch-packages] [Bug 1872485] [NEW] virtualbox-guest-utils fails to install on 20.04

2020-04-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on
ubuntu:focal (20.04) produces a broken state. Debug of `apt-get install
virtualbox-guest-utils` below.

Steps to reproduce:

1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 
test-container)
2. lxc exec test-container bash
3. apt update
4. apt full-upgrade
5. apt-get install virtualbox-guest-utils


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

The following packages have unmet dependencies:
 glib-networking : Depends: gsettings-desktop-schemas but it is not going to be 
installed
 init : PreDepends: systemd-sysv but it is not going to be installed


Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none 
-> 6.1.4-dfsg-2 @un puN >
  Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
  Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR 
>
  Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
  Added systemd-timesyncd:amd64 to the remove list
Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
  Considering openntpd:amd64 0 as a solution to systemd:amd64 59
  Added openntpd:amd64 to the remove list
  Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
  Fixing systemd:amd64 via keep of openntpd:amd64
Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none 
-> 6.1.4-dfsg-2 @un puN >
  Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
  Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR 
>
  Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
  Added systemd-timesyncd:amd64 to the remove list
Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
  Considering openntpd:amd64 0 as a solution to systemd:amd64 59
  Added openntpd:amd64 to the remove list
  Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
  Fixing systemd:amd64 via keep of openntpd:amd64
Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < none 
-> 6.1.4-dfsg-2 @un puN >
  Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 59
  Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mR 
>
  Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59
Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
  Considering openntpd:amd64 59 as a solution to systemd:amd64 59
  Or group remove for systemd:amd64
Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > 
(= 245.4-2ubuntu1)
  Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23
  Removing libpam-systemd:amd64 rather than change systemd:amd64
Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > 
(= 245.4-2ubuntu1)
  Considering systemd:amd64 59 as a solution to libnss-systemd:amd64 14
  Removing libnss-systemd:amd64 rather than change systemd:amd64
Investigating (3) plymouth:amd64 < 0.9.4git20200323-0ubuntu6 @ii mK Ib >
Broken plymouth:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (>= 
232-8~)
  Considering systemd:amd64 59 as a solution to plymouth:amd64 12
  Removing plymouth:amd64 rather than change systemd:amd64
Investigating (3) plymouth-theme-ubuntu-text:amd64 < 0.9.4git20200323-0ubuntu6 
@ii mK Ib >
Broken plymouth-theme-ubuntu-text:amd64 Depends on plymouth:amd64 < 
0.9.4git20200323-0ubuntu6 @ii mR > (= 0.9.4git20200323-0ubuntu6)
  Considering plymouth:amd64 59 as a solution to 
plymouth-theme-ubuntu-text:amd64 11
  Removing plymouth-theme-ubuntu-text:amd64 rather than change plymouth:amd64
Investigating (3) netplan.io:amd64 < 

[Touch-packages] [Bug 1860461] Re: libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with error "Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acc

2020-04-13 Thread Steven Jay Cohen
** Also affects: gnome-online-accounts (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client
  with error "Error performing TLS handshake: The Diffie-Hellman prime
  sent by the server is not acceptable (not long enough)."

Status in evolution package in Ubuntu:
  New
Status in gnome-online-accounts package in Ubuntu:
  New
Status in gnutls28 package in Ubuntu:
  Confirmed

Bug description:
  After upgrade to 20.04 package libgnutls30 broke pulseUI VPN client
  with the following error:

  "Error performing TLS handshake: The Diffie-Hellman prime sent by the
  server is not acceptable (not long enough)."

  I had to revert the package to the 19.10 version (3.6.9-5ubuntu1) and
  to install 19.10 dependency libhogweed4 3.4.1-1 to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgnutls30 3.6.9-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Tue Jan 21 17:48:39 2020
  InstallationDate: Installed on 2017-06-21 (943 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: gnutls28
  UpgradeStatus: Upgraded to focal on 2020-01-10 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1860461/+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 1872485] Re: virtualbox-guest-utils fails to install on 20.04

2020-04-13 Thread Robert C Jennings
systemd-timesyncd is conflicting with virtualbox-guest-utils but
virtualbox-guest-utils isn't providing time-daemon... debian/control in
virtualbox contains:

Package: virtualbox-guest-utils
Architecture: amd64 i386
Depends: adduser,
 pciutils,
 virtualbox-guest-dkms (= ${source:Version}) | virtualbox-guest-source 
(= ${source:Version}) | virtualbox-guest-modules,
 ${misc:Depends},
 ${shlibs:Depends}
#Conflicts: time-daemon, ntp
#Provides: time-daemon
#Replaces: time-daemon



** No longer affects: apt (Ubuntu)

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

Title:
  virtualbox-guest-utils fails to install on 20.04

Status in virtualbox package in Ubuntu:
  Triaged

Bug description:
  Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on
  ubuntu:focal (20.04) produces a broken state. Debug of `apt-get
  install virtualbox-guest-utils` below.

  Steps to reproduce:

  1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 
test-container)
  2. lxc exec test-container bash
  3. apt update
  4. apt full-upgrade
  5. apt-get install virtualbox-guest-utils

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

  The following packages have unmet dependencies:
   glib-networking : Depends: gsettings-desktop-schemas but it is not going to 
be installed
   init : PreDepends: systemd-sysv but it is not going to be installed

  
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 59
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 59 as a solution to systemd:amd64 59
Or group remove for systemd:amd64
  Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23
Removing libpam-systemd:amd64 rather than change systemd:amd64
  Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken 

[Touch-packages] [Bug 1872485] Re: virtualbox-guest-utils fails to install on 20.04

2020-04-13 Thread Dimitri John Ledkov
** Changed in: apt (Ubuntu)
   Status: New => Invalid

** Changed in: virtualbox (Ubuntu)
   Status: New => Triaged

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

Title:
  virtualbox-guest-utils fails to install on 20.04

Status in virtualbox package in Ubuntu:
  Triaged

Bug description:
  Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on
  ubuntu:focal (20.04) produces a broken state. Debug of `apt-get
  install virtualbox-guest-utils` below.

  Steps to reproduce:

  1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 
test-container)
  2. lxc exec test-container bash
  3. apt update
  4. apt full-upgrade
  5. apt-get install virtualbox-guest-utils

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

  The following packages have unmet dependencies:
   glib-networking : Depends: gsettings-desktop-schemas but it is not going to 
be installed
   init : PreDepends: systemd-sysv but it is not going to be installed

  
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 59
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 59 as a solution to systemd:amd64 59
Or group remove for systemd:amd64
  Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23
Removing libpam-systemd:amd64 rather than change systemd:amd64
  Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libnss-systemd:amd64 14
Removing libnss-systemd:amd64 rather than change systemd:amd64
  Investigating (3) plymouth:amd64 < 0.9.4git20200323-0ubuntu6 @ii mK Ib >
  Broken plymouth:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (>= 
232-8~)
Considering systemd:amd64 59 as 

[Touch-packages] [Bug 1800965] Re: Browsers don't display Devanagari script correctly

2020-04-13 Thread Gunnar Hjalmarsson
Closing the "fontconfig (Ubuntu)" task, since I have the experience that
upstream is disinclined to change /etc/fonts/conf.avail/65-nonlatin.conf
at the request of a distro, and carrying patches for the purpose is
inconvenient.

** Changed in: fontconfig (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  Browsers don't display Devanagari script correctly

Status in fontconfig package in Ubuntu:
  Won't Fix
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In the file /etc/fonts/conf.avail/65-nonlatin.conf the "Raghindi" font family 
is specified for devanagari script in Serif and Sans-serif style while "Lohit 
Hindi" in monospace. On the other hand, the Raghindi font is not installed by 
default. Because of this, the web browsers including Chrome and Firefox don't 
display the script correctly. A lot of people struggle to correct it by 
manually changing the settings in the browsers and partially succeed.
  The problem can be completely solved by replacing "Raghindi" in 
/etc/fonts/conf.avail/65-nonlatin.conf with "Lohit Hindi" or any other 
pre-installed font.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: fontconfig-config 2.13.0-5ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 07:38:12 2018
  InstallationDate: Installed on 2018-10-22 (9 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.fonts.conf.avail.65-nonlatin.conf: 
2018-10-26T14:54:05.700607

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1800965/+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 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable

2020-04-13 Thread Steven Jay Cohen
*** This bug is a duplicate of bug 1860461 ***
https://bugs.launchpad.net/bugs/1860461

** Also affects: gnome-online-accounts (Ubuntu)
   Importance: Undecided
   Status: New

** This bug has been marked a duplicate of bug 1860461
   libgnutls30 3.6.11.1-2ubuntu2 (Ubuntu 20.04) breaks pulseui client with 
error "Error performing TLS handshake: The Diffie-Hellman prime sent by the 
server is not acceptable (not long enough)."

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

Title:
  The Diffie-Hellman prime sent by the server is not acceptable

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I can no longer connect to my ISP mail server.
  Works in previous version 19.10

  "The reported error was “Failed to get capabilities: Error performing
  TLS handshake: The Diffie-Hellman prime sent by the server is not
  acceptable (not long enough).”."

  I've tried finding a workaround but so far no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evolution 3.35.92-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:07:01 2020
  InstallationDate: Installed on 2020-03-03 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+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 1872502] [NEW] There is no installable python package on Focal

2020-04-13 Thread Panos Asproulis
Public bug reported:

There is no installable "python" package on Focal. An attempt to install
it produces the following error:

$ sudo apt install python
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package python is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  python2-minimal:i386 python2:i386 python2-minimal python2 python-is-python2 
2to3 python-is-python3

E: Package 'python' has no installation candidate

This breaks the installation of many other software packages which have
the "python" package as a dependency.

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


** Tags: focal python

** Tags added: python

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

Title:
  There is no installable python package on Focal

Status in python-defaults package in Ubuntu:
  New

Bug description:
  There is no installable "python" package on Focal. An attempt to
  install it produces the following error:

  $ sudo apt install python
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Package python is not available, but is referred to by another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source
  However the following packages replace it:
python2-minimal:i386 python2:i386 python2-minimal python2 python-is-python2 
2to3 python-is-python3

  E: Package 'python' has no installation candidate

  This breaks the installation of many other software packages which
  have the "python" package as a dependency.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1872502/+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 1872485] Re: virtualbox-guest-utils fails to install on 20.04

2020-04-13 Thread Robert C Jennings
** Tags added: champagne

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

Title:
  virtualbox-guest-utils fails to install on 20.04

Status in apt package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New

Bug description:
  Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on
  ubuntu:focal (20.04) produces a broken state. Debug of `apt-get
  install virtualbox-guest-utils` below.

  Steps to reproduce:

  1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 
test-container)
  2. lxc exec test-container bash
  3. apt update
  4. apt full-upgrade
  5. apt-get install virtualbox-guest-utils

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

  The following packages have unmet dependencies:
   glib-networking : Depends: gsettings-desktop-schemas but it is not going to 
be installed
   init : PreDepends: systemd-sysv but it is not going to be installed

  
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 59
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 59 as a solution to systemd:amd64 59
Or group remove for systemd:amd64
  Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23
Removing libpam-systemd:amd64 rather than change systemd:amd64
  Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libnss-systemd:amd64 14
Removing libnss-systemd:amd64 rather than change systemd:amd64
  Investigating (3) plymouth:amd64 < 0.9.4git20200323-0ubuntu6 @ii mK Ib >
  Broken plymouth:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (>= 
232-8~)
Considering systemd:amd64 59 as a solution to plymouth:amd64 12
Removing plymouth:amd64 

[Touch-packages] [Bug 1870824] Re: Errors in script /usr/lib/avahi/avahi-daemon-check-dns.sh

2020-04-13 Thread Launchpad Bug Tracker
This bug was fixed in the package avahi - 0.7-4ubuntu7

---
avahi (0.7-4ubuntu7) focal; urgency=medium

  * Remove avahi-daemon-check-dns.sh hack, the feature is provided by
libnss-mdns now (lp: #1870824)
  * debian/patches/local-only-services-support.patch:
- replaced by the upstream commited version, part of the code which
  was there to workaround a ippusbxd issue has been removed since
  the problem has been resolved in cups now

 -- Sebastien Bacher   Wed, 08 Apr 2020 13:43:27
+0200

** Changed in: avahi (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Errors in script /usr/lib/avahi/avahi-daemon-check-dns.sh

Status in avahi package in Ubuntu:
  Fix Released

Bug description:
  In line 42 and 46 Command Substitution is used wrongly because the
  shell expects to execute what it returns.  See attached patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1870824/+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 1872485] Re: virtualbox-guest-utils fails to install on 20.04

2020-04-13 Thread Brian Murray
** Also affects: apt (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: focal rls-ff-incoming

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

Title:
  virtualbox-guest-utils fails to install on 20.04

Status in apt package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New

Bug description:
  Attempting to install virtualbox-guest-utils 6.1.4-dfsg-2 on
  ubuntu:focal (20.04) produces a broken state. Debug of `apt-get
  install virtualbox-guest-utils` below.

  Steps to reproduce:

  1. pull a fresh 20.04 image for testing (ex: lxc launch ubuntu-daily:20.04 
test-container)
  2. lxc exec test-container bash
  3. apt update
  4. apt full-upgrade
  5. apt-get install virtualbox-guest-utils

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

  The following packages have unmet dependencies:
   glib-networking : Depends: gsettings-desktop-schemas but it is not going to 
be installed
   init : PreDepends: systemd-sysv but it is not going to be installed

  
  Starting pkgProblemResolver with broken count: 1
  Starting 2 pkgProblemResolver with broken count: 1
  Investigating (0) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (1) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (1) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 14
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (2) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 14 as a solution to systemd:amd64 59
Added systemd-timesyncd:amd64 to the remove list
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 0 as a solution to systemd:amd64 59
Added openntpd:amd64 to the remove list
Fixing systemd:amd64 via keep of systemd-timesyncd:amd64
Fixing systemd:amd64 via keep of openntpd:amd64
  Investigating (2) systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd-timesyncd:amd64 Conflicts on virtualbox-guest-utils:amd64 < 
none -> 6.1.4-dfsg-2 @un puN >
Considering virtualbox-guest-utils:amd64 9998 as a solution to 
systemd-timesyncd:amd64 59
Removing systemd-timesyncd:amd64 rather than change 
virtualbox-guest-utils:amd64
  Investigating (3) systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken systemd:amd64 Depends on systemd-timesyncd:amd64 < 245.4-2ubuntu1 @ii 
mR >
Considering systemd-timesyncd:amd64 9998 as a solution to systemd:amd64 59
  Broken systemd:amd64 Depends on time-daemon:amd64 < none @un H >
Considering openntpd:amd64 59 as a solution to systemd:amd64 59
Or group remove for systemd:amd64
  Investigating (3) libpam-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libpam-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libpam-systemd:amd64 23
Removing libpam-systemd:amd64 rather than change systemd:amd64
  Investigating (3) libnss-systemd:amd64 < 245.4-2ubuntu1 @ii mK Ib >
  Broken libnss-systemd:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR 
> (= 245.4-2ubuntu1)
Considering systemd:amd64 59 as a solution to libnss-systemd:amd64 14
Removing libnss-systemd:amd64 rather than change systemd:amd64
  Investigating (3) plymouth:amd64 < 0.9.4git20200323-0ubuntu6 @ii mK Ib >
  Broken plymouth:amd64 Depends on systemd:amd64 < 245.4-2ubuntu1 @ii mR > (>= 
232-8~)

[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution

2020-04-13 Thread Launchpad Bug Tracker
This bug was fixed in the package libxml2 - 2.9.10+dfsg-5

---
libxml2 (2.9.10+dfsg-5) unstable; urgency=medium

  * Team upload.

  [ Mattia Rizzolo ]
  * d/rules:
+ Drop --disable-silent-rules, already passed by dh_auto_configure.
+ Drop --parallel, now default with debhelper compat > 10.
+ Use dh_installdocs and dh_installexamples to install docs and examples.
+ Use dh_missing --fail-missing (and add the relevant d/not-installed).
+ Minimize indep build to build only the docs.
  * d/watch: fix an option to avoid a warning message.
  * d/control:
+ Move most of the build-deps to Build-Depends-Arch.
+ Use ${python:Depends} also for python-libxml2-dbg.
  * Add a lintian override for
debian-rules-uses-supported-python-versions-without-python-all-build-depends

  [ Gunnar Hjalmarsson ]
  * d/p/python3-unicode-errors.patch:
Fix segfault issue with itstool and py3.  LP: #1869814

 -- Mattia Rizzolo   Fri, 10 Apr 2020 14:53:23 +0200

** Changed in: libxml2 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu-docs build failure - possible solution

Status in libxml2:
  New
Status in libxml2 package in Ubuntu:
  Fix Released
Status in ubuntu-docs package in Ubuntu:
  Fix Released

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+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 1872474] Re: Missing gpgme-json prevents use of popular Mailvelope browser extension

2020-04-13 Thread Peter J. Mello
Task on upstream Phabricator: https://dev.gnupg.org/T4820 (appears
resolved)

** Bug watch added: Debian Bug tracker #911189
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911189

** Also affects: gpgme1.0 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911189
   Importance: Unknown
   Status: Unknown

** Changed in: gpgme1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Missing gpgme-json prevents use of popular Mailvelope browser
  extension

Status in gpgme1.0 package in Ubuntu:
  Confirmed
Status in gpgme1.0 package in Debian:
  Unknown

Bug description:
  As described at the Mailvelope GitHub repository wiki here
   users are able to use their local GPG keyring via gpgme-
  json (rather than the included Openpgp.js library) with several
  popular webmail services, provided that the gpgme-json binary is
  available to the browser process. I reviewed the file lists for the
  binary packages produced from this source package and found no mention
  of it. Upon closer inspection of the packaging files, the d/rules has
  an override for dh_missing for the file and a note in the changelog
  from 2018, but there was no mention of what the circumstances were
  that necessitated that decision.

  If it's possible to correct the conditions that led to the file's
  exclusion I think it would be well worth pursuing as e-mail becomes
  evermore commercialized on top of an infrastructure that never did
  place much of a premium on privacy.

  I'm running the dev release of Kubuntu 20.04 LTS "Focal Fossa" with
  version 1.13.1-7ubuntu2 of the libgpgme11 package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1872474/+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 1872474] [NEW] Missing gpgme-json prevents use of popular Mailvelope browser extension

2020-04-13 Thread Peter J. Mello
Public bug reported:

As described at the Mailvelope GitHub repository wiki here
 users are able to use their local GPG keyring via gpgme-
json (rather than the included Openpgp.js library) with several popular
webmail services, provided that the gpgme-json binary is available to
the browser process. I reviewed the file lists for the binary packages
produced from this source package and found no mention of it. Upon
closer inspection of the packaging files, the d/rules has an override
for dh_missing for the file and a note in the changelog from 2018, but
there was no mention of what the circumstances were that necessitated
that decision.

If it's possible to correct the conditions that led to the file's
exclusion I think it would be well worth pursuing as e-mail becomes
evermore commercialized on top of an infrastructure that never did place
much of a premium on privacy.

I'm running the dev release of Kubuntu 20.04 LTS "Focal Fossa" with
version 1.13.1-7ubuntu2 of the libgpgme11 package.

** Affects: gpgme1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: packaging

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

Title:
  Missing gpgme-json prevents use of popular Mailvelope browser
  extension

Status in gpgme1.0 package in Ubuntu:
  New

Bug description:
  As described at the Mailvelope GitHub repository wiki here
   users are able to use their local GPG keyring via gpgme-
  json (rather than the included Openpgp.js library) with several
  popular webmail services, provided that the gpgme-json binary is
  available to the browser process. I reviewed the file lists for the
  binary packages produced from this source package and found no mention
  of it. Upon closer inspection of the packaging files, the d/rules has
  an override for dh_missing for the file and a note in the changelog
  from 2018, but there was no mention of what the circumstances were
  that necessitated that decision.

  If it's possible to correct the conditions that led to the file's
  exclusion I think it would be well worth pursuing as e-mail becomes
  evermore commercialized on top of an infrastructure that never did
  place much of a premium on privacy.

  I'm running the dev release of Kubuntu 20.04 LTS "Focal Fossa" with
  version 1.13.1-7ubuntu2 of the libgpgme11 package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1872474/+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 1393502] Re: [MacBookPro11, 3, Cirrus Logic CS4208, Pink Mic] Combo jack not recognized.

2020-04-13 Thread Andrew Hyatt
I am also experiencing this issue, MacbookPro11,5

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

Title:
  [MacBookPro11,3, Cirrus Logic CS4208, Pink Mic] Combo jack not
  recognized.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New Macbook comes with a four-conductor TRRS jack for headset.

  With headset plugged in the microfone is recognized on Mac os-x.
  Ubuntu recognizes the external headphones but not the microphone.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mikaelb2403 F pulseaudio
   /dev/snd/controlC0:  mikaelb2403 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 17 18:58:35 2014
  InstallationDate: Installed on 2014-10-20 (28 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Pink Mic, N/A
  Symptom_Type: No auto-switch between inputs
  Title: [MacBookPro11,3, Cirrus Logic CS4208, Pink Mic, N/A] No autoswitch
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/12/2014
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP112.88Z.0138.B07.1402121134
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-2BD1B31983FE1663
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,3
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-2BD1B31983FE1663
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP112.88Z.0138.B07.1402121134:bd02/12/2014:svnAppleInc.:pnMacBookPro11,3:pvr1.0:rvnAppleInc.:rnMac-2BD1B31983FE1663:rvrMacBookPro11,3:cvnAppleInc.:ct10:cvrMac-2BD1B31983FE1663:
  dmi.product.name: MacBookPro11,3
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-11-10T22:25:45.211791

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1393502/+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 1872327] Re: OLED brightness control on Intel Iris Plus Graphics G7

2020-04-13 Thread Daniel Blatter
I found a workaround using a script that is triggered by inotify.

I created the script called brightness in /usr/local/bin:

sudo nano /usr/local/bin/brightness

content:
--
#!/bin/sh

path=/sys/class/backlight/intel_backlight

luminance() {
read -r level < "$path"/actual_brightness
printf %.10f\\n "$((100 * level/max))e-2"
}

read -r max < "$path"/max_brightness
xrandr --output eDP-1 --brightness "$(luminance)"

inotifywait -me modify --format '' "$path"/actual_brightness | while read FILE
do 
echo $(luminance)
xrandr --output eDP-1 --brightness "$(luminance)"
done
--

chmod 755 /usr/local/bin/brightness

Remarks:
- The script waits for change in 
/sys/class/backlight/intel_backlight/actual_brightness.
- "intel_backlight" might be replaced the corresponding directory name in  
/sys/class/backlight according to your installation.
- eDP-1 may be replaced by the display name (might be eDP1 or different). Check 
the correct display name using the xrandr command. 

Add the script to the in the system setting to be executed at login.

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

Title:
  OLED brightness control on Intel Iris Plus Graphics G7

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi

  I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
  The hotkeys to adjust the OLED brightness do not work.

  Adjusting the display brightness editing the file brightness in
  /sys/class/backlight/intel_backlight doesn't work either. At
  /etc/default/grub I already added "acpi_backlight=vendor"

  I found an article, that fits to the topic:
  
http://reddit.com/r/linux/comments/cmf0vi/the_state_of_oled_brightness_on_linux

  Regards Daniel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Apr 12 18:42:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
  InstallationDate: Installed on 2020-04-03 (8 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=61d60ac7-8b29-4729-a6a0-e3b0300dba97 ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8KZ06EA#UUZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/xorg/+bug/1872327/+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 1872471] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()

2020-04-13 Thread Apport retracing service
*** This bug is a duplicate of bug 1870843 ***
https://bugs.launchpad.net/bugs/1870843

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1870843, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1872471/+attachment/5353318/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1872471/+attachment/5353320/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1872471/+attachment/5353323/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1872471/+attachment/5353324/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1872471/+attachment/5353325/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872471/+attachment/5353326/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1872471/+attachment/5353327/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1870843
   ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()

Status in ibus package in Ubuntu:
  New

Bug description:
  I don't known other issue

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30
  Uname: Linux 5.4.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 12 20:37:09 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-12 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f3fe6985f7b : orq
$0x0,(%rsp)
   PC (0x7f3fe6985f7b) ok
   source "$0x0" ok
   destination "(%rsp)" (0x7ffe7295dd30) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872471/+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 1872327] Re: OLED brightness control on Intel Iris Plus Graphics G7

2020-04-13 Thread Daniel Blatter
** Summary changed:

- OLED brightness control on Intel Iris Plus Graphics G7 on 20.4 beta
+ OLED brightness control on Intel Iris Plus Graphics G7

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

Title:
  OLED brightness control on Intel Iris Plus Graphics G7

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi

  I'm testing kubuntu 20.4 with my HP spectre x360 13 aw0720nz.
  The hotkeys to adjust the OLED brightness do not work.

  Adjusting the display brightness editing the file brightness in
  /sys/class/backlight/intel_backlight doesn't work either. At
  /etc/default/grub I already added "acpi_backlight=vendor"

  I found an article, that fits to the topic:
  
http://reddit.com/r/linux/comments/cmf0vi/the_state_of_oled_brightness_on_linux

  Regards Daniel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Sun Apr 12 18:42:36 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 
[VGA controller])
     Subsystem: Hewlett-Packard Company Iris Plus Graphics G7 [103c:86fa]
  InstallationDate: Installed on 2020-04-03 (8 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: HP HP Spectre x360 Convertible 13-aw0xxx
  ProcEnviron:
   LANGUAGE=de_CH:de
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=de_CH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=UUID=61d60ac7-8b29-4729-a6a0-e3b0300dba97 ro rootflags=subvol=@ quiet 
splash acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2020
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.46
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd03/02/2020:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.46:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8KZ06EA#UUZ
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/xorg/+bug/1872327/+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 1871487] Re: anon_inode:[eventfd] leaked on vgs invocation inside lxd container

2020-04-13 Thread Dan Watkins
Thanks!

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

Title:
  anon_inode:[eventfd] leaked on vgs invocation inside lxd container

Status in lvm2 package in Ubuntu:
  Invalid
Status in lxd package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  $ lxc launch ubuntu-daily:f reproducer
  $ lxc shell reproducer
  $ vgs

  Expected behaviour:

No output (the behaviour on an EC2 instance with no VGs).

  Actual behaviour:

Outputs "File descriptor 25 (anon_inode:[eventfd]) leaked on vgs
  invocation. Parent PID 283: -bash"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-1028.29~18.04.1-gcp 5.0.21
  Uname: Linux 5.0.0-1028-gcp x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_0_0_1028_29_gcp_65 
lkp_Ubuntu_5_0_0_1028_29_gcp_64 nf_tables lkp_Ubuntu_5_0_0_1028_29_gcp_63 
ebtable_filter ebtables ufs msdos xfs binfmt_misc veth ip6t_MASQUERADE 
ip6table_nat nf_nat_ipv6 ipt_MASQUERADE xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat nf_nat_ipv4 nf_nat iptable_mangle bridge stp llc zfs zunicode zavl 
icp zcommon znvpair spl ip6table_filter ip6_tables iptable_filter bpfilter 
nls_iso8859_1 input_leds serio_raw sch_fq_codel ib_iser rdma_cm iw_cm ib_cm 
ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 
crypto_simd cryptd glue_helper virtio_net net_failover failover psmouse
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  Date: Tue Apr  7 20:19:14 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1871487/+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 1872443] Re: /etc/securetty missing: dovecot not working

2020-04-13 Thread Dr. Uwe Meyer-Gruhl
At least, in 18.04, the file /etc/securetty was in package login...

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

Title:
  /etc/securetty missing: dovecot not working

Status in shadow package in Ubuntu:
  New

Bug description:
  With Ubuntu 20.04 Focal Fossa, /etc/securetty is missing from the
  "login" package (4.8.1-1ubuntu4).

  This leads to errors such as in /var/log/mail.log when a dovecot auth
  is tried:

  Apr 13 13:08:17 venus dovecot[10588]: imap-login: Login: user=, 
method=PLAIN,
  rip=192.168.123.1, lip=192.168.123.188, mpid=12200, TLS, TLSv1.2 with cipher 
ECDHE-E
  CDSA-AES256-GCM-SHA384 (256/256 bits)
  Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open 
/etc/secure
  tty: No such file or directory
  Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open 
/etc/secure
  tty: No such file or directory
  Apr 13 13:08:18 venus dovecot[10588]: imap-login: Login: user=, 
method=PLAIN,
  rip=192.168.123.1, lip=192.168.123.188, mpid=12202, TLS, TLSv1.2 with cipher 
ECDHE-E
  CDSA-AES256-GCM-SHA384 (256/256 bits)

  It seems that pam_unix still needs /etc/securetty, but login no longer
  provides it.

  There was a similar bug in debian that seems to be related:

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

  To my understanding, this is a problem between pam and login packages
  in 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1872443/+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 1800965] Re: Browsers don't display Devanagari script correctly

2020-04-13 Thread Launchpad Bug Tracker
This bug was fixed in the package language-selector - 0.204

---
language-selector (0.204) focal; urgency=medium

  * fontconfig/64-language-selector-prefer.conf:
- Add "Lohit Devanagari" since "Raghindi" (stated in
  65-nonlatin.conf) is not installed by default (LP: #1800965).
  * Translations from Launchpad

 -- Gunnar Hjalmarsson   Mon, 13 Apr 2020 01:42:00
+0200

** Changed in: language-selector (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Browsers don't display Devanagari script correctly

Status in fontconfig package in Ubuntu:
  Confirmed
Status in language-selector package in Ubuntu:
  Fix Released

Bug description:
  In the file /etc/fonts/conf.avail/65-nonlatin.conf the "Raghindi" font family 
is specified for devanagari script in Serif and Sans-serif style while "Lohit 
Hindi" in monospace. On the other hand, the Raghindi font is not installed by 
default. Because of this, the web browsers including Chrome and Firefox don't 
display the script correctly. A lot of people struggle to correct it by 
manually changing the settings in the browsers and partially succeed.
  The problem can be completely solved by replacing "Raghindi" in 
/etc/fonts/conf.avail/65-nonlatin.conf with "Lohit Hindi" or any other 
pre-installed font.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: fontconfig-config 2.13.0-5ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 07:38:12 2018
  InstallationDate: Installed on 2018-10-22 (9 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: fontconfig
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.fonts.conf.avail.65-nonlatin.conf: 
2018-10-26T14:54:05.700607

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1800965/+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 1872452] [NEW] Boot into black screen without power supply (Kubuntu on AMD / Thinkpad T495)

2020-04-13 Thread snow
Public bug reported:

Always when I turn on my Lenovo Thinkpad T495 (AMD CPU)- without the
power supply connected - the laptop  boots correctly at the beginning,
but then just before going to the login screen it gets black. It can
only be restarted. When I attach the power supply before the laptop boot
everything works correctly. I see this behavior only on Kubuntu (with
KDE desktop). On Ubuntu 20.04 everything works fine.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: KDE
Date: Mon Apr 13 14:20:17 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Picasso [17aa:5125]
InstallationDate: Installed on 2020-04-02 (10 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
MachineType: LENOVO 20NKS01Y00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=d6957960-70a9-45a8-98b1-b0a14d07b829 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/28/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R12ET46W(1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NKS01Y00
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.modalias: 
dmi:bvnLENOVO:bvrR12ET46W(1.16):bd10/28/2019:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T495
dmi.product.name: 20NKS01Y00
dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495
dmi.product.version: ThinkPad T495
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
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

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


** Tags: amd64 apport-bug focal fonts kubuntu 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/1872452

Title:
  Boot into black screen without power supply (Kubuntu on AMD / Thinkpad
  T495)

Status in xorg package in Ubuntu:
  New

Bug description:
  Always when I turn on my Lenovo Thinkpad T495 (AMD CPU)- without the
  power supply connected - the laptop  boots correctly at the beginning,
  but then just before going to the login screen it gets black. It can
  only be restarted. When I attach the power supply before the laptop
  boot everything works correctly. I see this behavior only on Kubuntu
  (with KDE desktop). On Ubuntu 20.04 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Apr 13 14:20:17 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Picasso [17aa:5125]
  InstallationDate: Installed on 2020-04-02 (10 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  MachineType: LENOVO 20NKS01Y00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=d6957960-70a9-45a8-98b1-b0a14d07b829 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R12ET46W(1.16 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NKS01Y00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  

[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

2020-04-13 Thread Rocko
My Ubuntu 20.04 installation just did this - something changed the
org.gnome.desktop.lockdown disable-lock-screen to true and also the
blank screen to never (did an update do this?).

But there's nothing I can see in gnome-control-center to modify this
value, making this bug pretty obscure when it happens. Wouldn't a
setting in g-c-c make a lot of sense if you can actually disable the
screen lock completely?

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

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+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 1872418] Re: Fatal GPU issue

2020-04-13 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1872418

Title:
  Fatal GPU issue

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu installs fine but only main screen remains functional and only
  at low resolution. This can be fixed by adding "iommu=soft" as a
  kernel parameter.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 11:03:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] [1002:0b36]
  InstallationDate: Installed on 2020-04-12 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=b176eadc-ca87-4fa9-b9a5-0512e889d77c ro iommu=soft ipv6.disable=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/31/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2007
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF B450-PRO GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2007:bd12/31/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450-PROGAMING:rvrRevX.0x: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
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 
20.0.4+git2004041407.4c2c6e6119b~f~mesarc1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/xorg/+bug/1872418/+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 1872418] [NEW] Fatal GPU issue

2020-04-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Ubuntu installs fine but only main screen remains functional and only at
low resolution. This can be fixed by adding "iommu=soft" as a kernel
parameter.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 13 11:03:57 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 
5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 
OEM/5600 XT / 5700/5700 XT] [1002:0b36]
InstallationDate: Installed on 2020-04-12 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=b176eadc-ca87-4fa9-b9a5-0512e889d77c ro iommu=soft ipv6.disable=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/31/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2007
dmi.board.asset.tag: Default string
dmi.board.name: TUF B450-PRO GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2007:bd12/31/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFB450-PROGAMING:rvrRevX.0x: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
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-1
version.libgl1-mesa-dri: libgl1-mesa-dri 
20.0.4+git2004041407.4c2c6e6119b~f~mesarc1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
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

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


** Tags: amd64 apport-bug focal third-party-packages ubuntu
-- 
Fatal GPU issue
https://bugs.launchpad.net/bugs/1872418
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 
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 1872443] [NEW] /etc/securetty missing: dovecot not working

2020-04-13 Thread Dr. Uwe Meyer-Gruhl
Public bug reported:

With Ubuntu 20.04 Focal Fossa, /etc/securetty is missing from the
"login" package (4.8.1-1ubuntu4).

This leads to errors such as in /var/log/mail.log when a dovecot auth is
tried:

Apr 13 13:08:17 venus dovecot[10588]: imap-login: Login: user=, 
method=PLAIN,
rip=192.168.123.1, lip=192.168.123.188, mpid=12200, TLS, TLSv1.2 with cipher 
ECDHE-E
CDSA-AES256-GCM-SHA384 (256/256 bits)
Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open 
/etc/secure
tty: No such file or directory
Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open 
/etc/secure
tty: No such file or directory
Apr 13 13:08:18 venus dovecot[10588]: imap-login: Login: user=, 
method=PLAIN,
rip=192.168.123.1, lip=192.168.123.188, mpid=12202, TLS, TLSv1.2 with cipher 
ECDHE-E
CDSA-AES256-GCM-SHA384 (256/256 bits)

It seems that pam_unix still needs /etc/securetty, but login no longer
provides it.

There was a similar bug in debian that seems to be related:

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

To my understanding, this is a problem between pam and login packages in
20.04.

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


** Tags: dovecot login pam securetty

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

Title:
  /etc/securetty missing: dovecot not working

Status in shadow package in Ubuntu:
  New

Bug description:
  With Ubuntu 20.04 Focal Fossa, /etc/securetty is missing from the
  "login" package (4.8.1-1ubuntu4).

  This leads to errors such as in /var/log/mail.log when a dovecot auth
  is tried:

  Apr 13 13:08:17 venus dovecot[10588]: imap-login: Login: user=, 
method=PLAIN,
  rip=192.168.123.1, lip=192.168.123.188, mpid=12200, TLS, TLSv1.2 with cipher 
ECDHE-E
  CDSA-AES256-GCM-SHA384 (256/256 bits)
  Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open 
/etc/secure
  tty: No such file or directory
  Apr 13 13:08:18 venus auth[12195]: pam_unix(dovecot:auth): Couldn't open 
/etc/secure
  tty: No such file or directory
  Apr 13 13:08:18 venus dovecot[10588]: imap-login: Login: user=, 
method=PLAIN,
  rip=192.168.123.1, lip=192.168.123.188, mpid=12202, TLS, TLSv1.2 with cipher 
ECDHE-E
  CDSA-AES256-GCM-SHA384 (256/256 bits)

  It seems that pam_unix still needs /etc/securetty, but login no longer
  provides it.

  There was a similar bug in debian that seems to be related:

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

  To my understanding, this is a problem between pam and login packages
  in 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1872443/+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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

2020-04-13 Thread Andrew Welham
mm, see you have got tot he same stage as me after the changes removing
the rw to the some directories

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

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+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 387657] Re: aa-logprof: doesn't handle large logs

2020-04-13 Thread Christian Boltz
In the meantime (actually nearly a year ago), log parsing was rewritten
and now does de-duplication instantly. This should reduce memory usage a
lot - my experience is that especially large lots have lots of
duplication included.

I also removed some intermediate steps in the chain from logfile to aa-
logprof questions, which means less intermediate variables/arrays that
eat quite some memory.

The new log parsing is currently only in git master (not in 2.13.x). It
will be included in the next major release (probably 3.0).

Processing / asking about the log events one by one (instead of reading
the whole log first) would in theory save even more memory. However,
IMHO it would make the user experience worse because it would also mean
loosing the ability to sort the questions aa-logprof asks by profile and
rule type.

Therefore I'm closing this bug as "mostly fixed" ;-) - if you still see
aa-logprof eating too much memory, feel free to open a new bug.

** Changed in: apparmor
   Status: Triaged => Fix Committed

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

Title:
  aa-logprof: doesn't handle large logs

Status in AppArmor:
  Fix Committed
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: apparmor

  Ubuntu 8.04.2
  Package: apparmor-utils
  Version: 2.1+1075-0ubuntu9.2

  My first experience with AppArmor was finding a kernel log file that
  was full of 800 MB of AppArmor warnings from Samba and CUPS. I'm not
  sure what suddenly enabled AppArmor on this LTS system, but while
  fixing the problem I noticed

  aa-logprof, while processing an 800 MB log file, drove the load
  average up into the high 40's. I suspect it was trying to load the
  whole thing into memory (on a system with 1 GB of RAM). I'd recommend
  revising the architecture so that it processes the lines as it sees
  them.

  I worked around the problem by splitting the file into a dozen 75MB
  chunks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/387657/+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 1617564] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is

2020-04-13 Thread Rik Mills
** Changed in: kaccounts-providers (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  [master] package kaccounts-providers (not installed) failed to
  install/upgrade: trying to overwrite '/etc/signon-ui/webkit-
  options.d/www.facebook.com.conf', which is also in package account-
  plugin-facebook 0.12+16.04.20160126-0ubuntu1

Status in One Hundred Papercuts:
  Confirmed
Status in account-plugins package in Ubuntu:
  Confirmed
Status in kaccounts-providers package in Ubuntu:
  Won't Fix

Bug description:
  showing this error when installing kde environment in ubuntu 16.04. it
  say kaccounts  niot installed. so i think it may cause some security
  issue

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: kaccounts-providers (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Sat Aug 27 18:11:18 2016
  DuplicateSignature:
   package:kaccounts-providers:(not installed)
   Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb
 (--unpack):
    trying to overwrite '/usr/share/accounts/services/google-im.service', which 
is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1
  ErrorMessage: trying to overwrite 
'/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in 
package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  InstallationDate: Installed on 2016-08-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: kaccounts-providers
  Title: package kaccounts-providers (not installed) failed to install/upgrade: 
trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', 
which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1617564/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2020-04-13 Thread Dirk Heumann
Sorry, should put my reading glasses on, 20:04beta's version 2.64.1-1 is
newer than 19.10's version 2.62.4-1.

I wished, I could correct messages here, unless someone else is on the
top ;-)

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in glib2.0 package in Ubuntu:
  New

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

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1872286/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2020-04-13 Thread full name
I attached the Realtek dump with my headphones plugged into the jack for
comparison.

** Attachment added: "RtHDDump.txt.headphonesInJack"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5353097/+files/RtHDDump.txt.headphonesInJack

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 06:20:08 2019
  InstallationDate: Installed on 2019-11-03 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   

[Touch-packages] [Bug 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2020-04-13 Thread Dirk Heumann
Checked the (working) Ubuntu 19.04 package:

$ apt-cache policy libglib2.0-bin
libglib2.0-bin:
  Installed: 2.62.4-1~ubuntu19.10.2
  Candidate: 2.62.4-1~ubuntu19.10.2
  Version table:
 *** 2.62.4-1~ubuntu19.10.2 500
500 http://de.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages
100 /var/lib/dpkg/status
 2.62.1-1 500
500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

It seems, that the package is newer at Ubuntu 19.10???

$ lsb_release -rd
Description:Ubuntu 19.10
Release:19.10

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in glib2.0 package in Ubuntu:
  New

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

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1872286/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2020-04-13 Thread Dirk Heumann
Opened

[https://gitlab.gnome.org/GNOME/glib/-/issues/2090](https://gitlab.gnome.org/GNOME/glib/-/issues/2090)

as requested, with additional comments that it works in Ubuntu 19.10 up
to kernel 5.6.3 (I use both Ubuntu and newest linux kernel).

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2090
   https://gitlab.gnome.org/GNOME/glib/-/issues/2090

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in glib2.0 package in Ubuntu:
  New

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

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1872286/+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 1872415] Re: Laptop/Tablet lose trackpad on flipping to tablet mode.

2020-04-13 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (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/1872415

Title:
  Laptop/Tablet lose trackpad on flipping to tablet mode.

Status in xorg package in Ubuntu:
  New

Bug description:
  I am on a Lenovo Flex 14 laptop that includes a 360-degree hinge for
  flipping the screen to tablet mode. Upon flipping the screen to tablet
  mode the trackpad seems to be disabled but after returning the screen
  to 90 degrees or laptop mode the trackpad is not re-enabled.

  The only way the trackpad seems to be able to be re-enabled is by
  restarting the system. Logging out and back does not fix the problem.

  The laptop keyboard and touchscreen still work after flipping to
  360-degrees and back to 90 degrees/laptop, but, again, the trackpad is
  not working after doing this operation of flipping the screen.

  Tested on Xubuntu 20.04 and Ubuntu 20.04, which are both in beta.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Apr 13 03:19:05 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:398c]
 Subsystem: Lenovo GM108M [GeForce MX130] [17aa:398c]
  InstallationDate: Installed on 2020-04-07 (5 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200407)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 174f:2426 Syntek Integrated Camera
   Bus 001 Device 003: ID 0bda:b023 Realtek Semiconductor Corp. Bluetooth Radio 
   Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81EM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=f33b718b-a02d-47b1-9d8a-a0704da0f02d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7QCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad FLEX 6-14IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr7QCN43WW:bd11/28/2019:svnLENOVO:pn81EM:pvrLenovoideapadFLEX6-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoideapadFLEX6-14IKB:
  dmi.product.family: ideapad FLEX 6-14IKB
  dmi.product.name: 81EM
  dmi.product.sku: LENOVO_MT_81EM_BU_idea_FM_ideapad FLEX 6-14IKB
  dmi.product.version: Lenovo ideapad FLEX 6-14IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  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/xorg/+bug/1872415/+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 1824916] Re: Wallpaper corruption after waking from sleep

2020-04-13 Thread Jimsheri Maziashvili
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407

Same problem on Ubuntu 20.04 too.

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

Title:
  Wallpaper corruption after waking from sleep

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I upgraded to Dingo today, and I'm having a new issue with waking from
  sleep on my Dell XPS 9560. When I wake my laptop, the wallpaper
  becomes corrupted (screenshot attached), and it doesn't go away until
  I restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Uname: Linux 5.0.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 15 23:06:37 2019
  DistUpgraded: 2019-04-15 19:46:05,884 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-11-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:07be]
 Subsystem: Dell GP107M [GeForce GTX 1050 Mobile] [1028:07be]
  InstallationDate: Installed on 2018-10-28 (170 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0c45:6713 Microdia 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-11-generic 
root=UUID=9f074e0b-7e2f-475a-9cae-48d43abd3345 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-15 (0 days ago)
  dmi.bios.date: 10/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd10/02/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.product.sku: 07BE
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  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/xorg/+bug/1824916/+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 1872415] [NEW] Laptop/Tablet lose trackpad on flipping to tablet mode.

2020-04-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I am on a Lenovo Flex 14 laptop that includes a 360-degree hinge for
flipping the screen to tablet mode. Upon flipping the screen to tablet
mode the trackpad seems to be disabled but after returning the screen to
90 degrees or laptop mode the trackpad is not re-enabled.

The only way the trackpad seems to be able to be re-enabled is by
restarting the system. Logging out and back does not fix the problem.

The laptop keyboard and touchscreen still work after flipping to
360-degrees and back to 90 degrees/laptop, but, again, the trackpad is
not working after doing this operation of flipping the screen.

Tested on Xubuntu 20.04 and Ubuntu 20.04, which are both in beta.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Apr 13 03:19:05 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:398c]
   Subsystem: Lenovo GM108M [GeForce MX130] [17aa:398c]
InstallationDate: Installed on 2020-04-07 (5 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200407)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 174f:2426 Syntek Integrated Camera
 Bus 001 Device 003: ID 0bda:b023 Realtek Semiconductor Corp. Bluetooth Radio 
 Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81EM
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=f33b718b-a02d-47b1-9d8a-a0704da0f02d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/28/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: 7QCN43WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad FLEX 6-14IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr7QCN43WW:bd11/28/2019:svnLENOVO:pn81EM:pvrLenovoideapadFLEX6-14IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoideapadFLEX6-14IKB:
dmi.product.family: ideapad FLEX 6-14IKB
dmi.product.name: 81EM
dmi.product.sku: LENOVO_MT_81EM_BU_idea_FM_ideapad FLEX 6-14IKB
dmi.product.version: Lenovo ideapad FLEX 6-14IKB
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
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

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


** Tags: amd64 apport-bug focal ubuntu
-- 
Laptop/Tablet lose trackpad on flipping to tablet mode.
https://bugs.launchpad.net/bugs/1872415
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 
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 1749546] Re: Booting a live session is slow - fontconfig regenerates its font cache

2020-04-13 Thread Bug Watch Updater
** Changed in: fontconfig
   Status: Unknown => New

** Changed in: fontconfig
   Importance: Medium => Unknown

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

Title:
  Booting a live session is slow - fontconfig regenerates its font cache

Status in Fontconfig:
  New
Status in fontconfig package in Ubuntu:
  Fix Released
Status in fontconfig source package in Bionic:
  Fix Released

Bug description:
  On Bionic Ubuntu Desktop booting to a live session is slow. It takes
  roughly 2 min on my test machine to boot from the "Try or Install
  Ubuntu" boot menu to a usable session.

  It also takes 1 minute to logout and 17s to log in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: casper 1.388
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:43:19 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: casper
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/1749546/+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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones

2020-04-13 Thread full name
Exactly the same problem with Samsung Notebook 9 Pro (np930mbe-k04us)
which also has an ALC298.

Headphones are working with model=mono-speakers.

I attached my Realtek dump.

I'm also soliciting the arch forum for help (I'm running arch):

https://bbs.archlinux.org/viewtopic.php?pid=1897858

** Attachment added: "RtHDDump.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5353056/+files/RtHDDump.txt

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

Title:
  [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on
  internal speakers, very very quiet on headphones

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've been googling this issue for 10's of hours and tried many things.

  Relase of Ubuntu: 19.10

  Expected outcome: Music plays on the internal speakers and headphones.

  Actual outcome: I can barely hear audio using headphones with volume
  turned up to 150%.  Absolutely nothing comes out of the speakers. (The
  speakers sound great under Windows 10.)

  Complete alsa-info output is attached, but here are some snippets:

  !!DMI Information
  !!---

  Manufacturer:  SAMSUNG ELECTRONICS CO., LTD.
  Product Name:  950SBE/951SBE
  Product Version:   P06RES
  Firmware Version:  P06RES.075.190529.SP
  Board Vendor:  SAMSUNG ELECTRONICS CO., LTD.
  Board Name:NP950SBE-K01US

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-19-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes


  !!ALSA Version
  !!

  Driver version: k5.3.0-19-generic
  Library version:1.1.9
  Utilities version:  1.1.9

  
  !!Loaded ALSA modules
  !!---

  snd_hda_intel

  
  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

   0 [PCH]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0x604b118000 irq 177

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP
  High Definition Audio Controller (rev 11)

  
  !!Advanced information - PCI Vendor/Device/Subsystem ID's
  !!---

  00:1f.3 0401: 8086:9dc8 (rev 11)
  DeviceName: Onboard - Sound

  
  !!HDA-Intel Codec information
  !!---
  --startcollapse--

  Codec: Realtek ALC298
  Address: 0
  AFG Function Id: 0x1 (unsol 1)
  Vendor Id: 0x10ec0298
  Subsystem Id: 0x144dc812
  Revision Id: 0x100103
  No Modem Function Group found
  Default PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
  Default Amp-In caps: N/A
  Default Amp-Out caps: N/A
  State of AFG node 0x01:
Power states:  D0 D1 D2 D3 D3cold CLKSTOP EPSS
Power: setting=D0, actual=D0
  GPIO: io=8, o=0, i=0, unsolicited=1, wake=0
IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Headphone Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Device: name="ALC298 Analog", type="Audio", device=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x00 0x00]
Converter: stream=1, channel=0
PCM:
  rates [0x60]: 44100 48000
  bits [0xe]: 16 20 24
  formats [0x1]: PCM
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0
  Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out
Control: name="Speaker Playback Volume", index=0, device=0
  ControlAmp: chs=3, dir=Out, idx=0, ofs=0
Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0
Amp-Out vals:  [0x7f 0x7f]
Converter: stream=1, channel=0

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin 1383 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  6 06:20:08 2019
  

[Touch-packages] [Bug 1870975] Re: No audio devices appear except "Dummy Output" when I close my laptop lid while audio is playing and then open it back up.

2020-04-13 Thread Sebastien Bacher
** Package changed: gnome-control-center (Ubuntu) => pulseaudio (Ubuntu)

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => New

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

Title:
   No audio devices appear except "Dummy Output" when I close my laptop
  lid while audio is playing and then open it back up.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
  ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  Date: Sun Apr  5 15:00:42 2020
  InstallationDate: Installed on 2020-04-04 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+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 1872286] Re: gio - cifs mount smb not possible "Location is not mountable"

2020-04-13 Thread Sebastien Bacher
Thank you for your bug report, could report it upstream as well on
https://gitlab.gnome.org/GNOME/glib ?

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

Title:
  gio - cifs mount smb not possible "Location is not mountable"

Status in glib2.0 package in Ubuntu:
  New

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

  2) Package
  $ apt-cache policy libglib2.0-bin
  libglib2.0-bin:
Installed: 2.64.1-1
Candidate: 2.64.1-1
Version table:
   *** 2.64.1-1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3) Expected to happen
  The path should be mounted at
  /run/user/1000/gvfs/smb-share:server=192.168.178.1,share=PathName/

  4) What happened instead:
  Error Message:
  gio: smb://192.168.178.1/PathName/: Location is not mountable

  5) Long description / explanation
  Since some years, I mount a Windows drive with

  gio mount smb://192.168.178.1/PathName

  After upgrading from 19.04 to 20.04 beta, this does not work any more,
  I get the error message

  gio: smb://192.168.178.1/PathName/: Location is not mountable

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-bin 2.64.1-1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Apr 12 12:43:53 2020
  InstallationDate: Installed on 2019-02-17 (420 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: glib2.0
  UpgradeStatus: Upgraded to focal on 2020-04-05 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1872286/+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 1849714] Re: failure to install repos for raspberry pi

2020-04-13 Thread Troy
Err:3 http://ppa.launchpad.net/ubuntu-raspi2/ppa/ubuntu focal Release  
  404  Not Found [IP: 91.189.95.83 80]


E: The repository 'http://ppa.launchpad.net/ubuntu-raspi2/ppa/ubuntu focal 
Release' does not have a Release file.

I'm having the same issue, but I'm on "Ubuntu Focal Fossa (development
branch) aarch64"

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

Title:
  failure to install repos for raspberry pi

Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  following the directions about 1/5 down the page of
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo add-apt-repository ppa:ubuntu-raspi2/ppa
  Cannot add PPA: 'ppa:~ubuntu-raspi2/ubuntu/ppa'.
  ERROR: '~ubuntu-raspi2' user or team does not exist.

  This seems like a failure to me.

  shire:~(13) lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1849714/+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 1870975] [NEW] No audio devices appear except "Dummy Output" when I close my laptop lid while audio is playing and then open it back up.

2020-04-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When I closed my laptop lid while sound was playing in Audacity and then
opened the lid back up, the device woke up from sleep. However, my
headphones were plugged in at the time, and Ubuntu acted as if the audio
resumed.

However, I was not hearing audio. So I went to the Audio section of
Settings and found there was only one sound device: Dummy Device,
instead of seeing the speakers built into the laptop and the headphones.

Description: Ubuntu 18.04.4 LTS
Release: 18.04

I am forced to reboot my machine as a workaround.

gnome-control-center:
  Installed: 1:3.28.2-0ubuntu0.18.04.6
  Candidate: 1:3.28.2-0ubuntu0.18.04.6
  Version table:
 *** 1:3.28.2-0ubuntu0.18.04.6 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:3.28.1-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6
ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
Date: Sun Apr  5 15:00:42 2020
InstallationDate: Installed on 2020-04-04 (1 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pulseaudio (Ubuntu)
 Importance: Low
 Status: New


** Tags: amd64 apport-bug bionic
-- 
 No audio devices appear except "Dummy Output" when I close my laptop lid while 
audio is playing and then open it back up.
https://bugs.launchpad.net/bugs/1870975
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio in Ubuntu.

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