date:20200506

It was flaky and now resolved in proposed migration.
But I'd want to understand why we fail 4/5 times.

So the debugging tests in the bileto ticket [1] will go on for a bit.

[1]: https://bileto.ubuntu.com/#/ticket/4049

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

Title:
  chrony autopkgtest fails on armhf (groovy)

Status in chrony package in Ubuntu:
  New
Status in libcap2 package in Ubuntu:
  Confirmed

Bug description:
  Test fails on armhf only:
running chronyc makestepERROR
checking chronyc output OK
running chronyc trimrtc ERROR
checking chronyc output OK
running chronyc writertcERROR

  This might be a new twist on 
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1863590
  as it is libcap2 again.

  This reproduces through a bunch of retries
  http://autopkgtest.ubuntu.com/packages/c/chrony/groovy/armhf
  But as I said is armfh only:
  http://autopkgtest.ubuntu.com/packages/chrony

  Flagging update-excuse, but I won't be able to get to it immediately
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+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 1877219] [NEW] dozens of empty grilo-plugin-cache folders polluting /tmp

2020-05-06 Thread Forest

Public bug reported:

My /tmp folder has dozens of empty folders with names like grilo-plugin-
cache-ABCDEF. I don't know anything about grilo-plugins, but surely they
can do their job without leaving endless garbage directories behind when
they're done?

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename:   eoan

$ dpkg-query --show grilo-plugins-0.3-base
grilo-plugins-0.3-base:amd640.3.9-1ubuntu1

** Affects: grilo-plugins (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  My /tmp folder has dozens of empty folders with names like grilo-plugin-
  cache-ABCDEF. I don't know anything about grilo-plugins, but surely they
  can do their job without leaving endless garbage directories behind when
  they're done?
+ 
+ $ lsb_release -a
+ No LSB modules are available.
+ Distributor ID:   Ubuntu
+ Description:  Ubuntu 19.10
+ Release:  19.10
+ Codename: eoan
+ 
+ $ dpkg-query --show grilo-plugins-0.3-base
+ grilo-plugins-0.3-base:amd64  0.3.9-1ubuntu1

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

Title:
  dozens of empty grilo-plugin-cache folders polluting /tmp

Status in grilo-plugins package in Ubuntu:
  New

Bug description:
  My /tmp folder has dozens of empty folders with names like grilo-
  plugin-cache-ABCDEF. I don't know anything about grilo-plugins, but
  surely they can do their job without leaving endless garbage
  directories behind when they're done?

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  $ dpkg-query --show grilo-plugins-0.3-base
  grilo-plugins-0.3-base:amd64  0.3.9-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1877219/+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 1877194] Re: Selected audio output device not persistent between reboots (Resets to USB-device)

2020-05-06 Thread Daniel van Vugt

We configure PulseAudio by default to automatically choose hotplugged
devices so it might be thinking booting with USB counts as hotplugging.
To avoid this you should just be able to comment out:

  load-module module-switch-on-connect

from /etc/pulse/default.pa


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

Title:
  Selected audio output device not persistent between reboots (Resets to
  USB-device)

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877194/+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 1877216] [NEW] [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all

2020-05-06 Thread ernestrayb...@hotmail.com

Public bug reported:

Problem keeps appearing when video is played. video keeps playing but no
sound is heard thru headphones.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  ernest 1095 F pulseaudio
 /dev/snd/controlC1:  ernest 1095 F pulseaudio
 /dev/snd/controlC0:  ernest 1095 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May  7 09:55:52 2020
InstallationDate: Installed on 2020-04-25 (11 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  ernest 1095 F pulseaudio
 /dev/snd/controlC1:  ernest 1095 F pulseaudio
 /dev/snd/controlC0:  ernest 1095 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/28/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: B.10
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B450M PRO-VDH MAX (MS-7A38)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 8.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 8.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB.10:bd08/28/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr8.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHMAX(MS-7A38):rvr8.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr8.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A38
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 8.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug focal

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

Title:
  [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Problem keeps appearing when video is played. video keeps playing but
  no sound is heard thru headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ernest 1095 F pulseaudio
   /dev/snd/controlC1:  ernest 1095 F pulseaudio
   /dev/snd/controlC0:  ernest 1095 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  7 09:55:52 2020
  InstallationDate: Installed on 2020-04-25 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ernest 1095 F pulseaudio
   /dev/snd/controlC1:  ernest 1095 F pulseaudio
   /dev/snd/controlC0:  ernest 1095 F pulseaudio
  Symptom_Jack: Green Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [MS-7A38, Realtek ALC892, Green Headphone Out, Front] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B450M PRO-VDH MAX (MS-7A38)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 8.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 8.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB.10:bd08/28/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A38:pvr8.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MPRO-VDHMAX(MS-7A38):rvr8.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr8.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A38
  dmi.product.sku: To be filled by O.E.M.

[Touch-packages] [Bug 1877115] Re: Corruption of default wallpaper

2020-05-06 Thread Daniel van Vugt

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1867668, so it 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. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1867668
   Visual artifacts in Gnome Shell when using the 'intel' Xorg driver

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

Title:
  Corruption of default wallpaper

Status in xorg package in Ubuntu:
  New

Bug description:
  If the "Tearfree" Xorg option for Intel graphics is turned on,
  painting the default wallpaper is corrupted. See attached screenshot.

  My X11 change from default for the "Tearfree" option is:

  Section "Device"
 Identifier  "Intel Graphics"
 Driver  "intel"
 Option  "TearFree""true"
  EndSection

  as /etc/X11/xorg.conf.d/20-intel.conf

  Copying the wallpaper to My Pictures and setting as wallpaper doesn't
  show the corruption. Using other wallpapers including included
  wallpapers shows no corruption.

  Removing the "tearfree" option then logoff/logon doesn't show the
  wallpaper corruption (but gives me screen tearing when playing videos,
  which I don't like. Using the Wayland option shows no wallpaper
  corruption.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 14:06:30 2020
  DistUpgraded: 2020-05-02 16:18:39,153 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:07e6]
  InstallationDate: Installed on 2018-08-09 (636 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=ff06b612-9a9b-4692-bd35-9dc3a5e65fef ro mem_sleep_default=deep quiet 
splash drm_kms_helper.edid_firmware=edid/1920x1080_50.00.bin vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-05-02 (3 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0F6P3V
  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:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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/1877115/+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 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade

2020-05-06 Thread warrenc5

This is something to do with linux 5 kernel api

You need to manually downgrade systemd - well - that's what I did.

when you boot with grub or refind - edit default entry and change the
init=/bin/init to init=/bin/bash

That will bypass systemd starting up and drop you straight into a shell.

mount -o remount /
mount /usr
mount /var
mount /dev/sdc1 /mnt 
dpkg -i /mnt/systemd_241-7~deb10u3_amd64.deb


On a system that works or download a previous version somehow.

dpkg -l systemd
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  systemd245.5-2  amd64system and service manager
root@leet:/home/wozza# apt-cache policy systemd
systemd:
  Installed: 245.5-2
  Candidate: 245.5-2
  Version table:
 *** 245.5-2 500
500 http://ftp.iinet.net.au/debian/debian bullseye/main amd64 Packages
100 /var/lib/dpkg/status
 241-7~deb10u3 500
500 http://ftp.iinet.net.au/debian/debian stable/main amd64 Packages
root@leet:/home/wozza# apt-get download systemd=241-7~deb10u3
Get:1 http://ftp.iinet.net.au/debian/debian stable/main amd64 systemd amd64 
241-7~deb10u3 [3,495 kB]
Fetched 3,495 kB in 11s (321 kB/s)
W: Download is performed unsandboxed as root as file 
'/home/wozza/systemd_241-7~deb10u3_amd64.deb' couldn't be accessed by user 
'_apt'. - pkgAcquire::Run (13: Permission denied)
root@leet:/home/wozza# ll systemd_241-7~deb10u3_amd64.deb
-rw-r--r-- 1 root root 3495428 Jan 31 15:11 systemd_241-7~deb10u3_amd64.deb
root@leet:/home/wozza# mount /dev/sdc1 /mnt
root@leet:/home/wozza# cp systemd_241-7~deb10u3_amd64.deb /mnt/
root@leet:/home/wozza# cd /mnt/
root@leet:/mnt# mkdir unpack
root@leet:/mnt# cd unpack/
root@leet:/mnt/unpack# dpkg-deb -R ../systemd_241-7~deb10u3_amd64.deb  .

worst comes to worse can copy the files across from unpack directory -
good luck.

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

Title:
  Kernel panic booting after 18.04 to 20.04 upgrade

Status in libseccomp package in Ubuntu:
  New

Bug description:
  Upgraded Ubuntu 18.04 to 20.04.  Following the upgrade, booting was not 
possible.  The error messages is:
  /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: 
undefined symbol: seccomp_api_get
  [4.608900] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  See also attached photograph of screen during boot.

  Upgrade followed steps from here: 
https://help.ubuntu.com/community/FocalUpgrades/Kubuntu
  With the excpetion that The -d flag was used for the do-release-upgrade:
  sudo do-release-upgrade -d -m desktop

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Prior to upgrade: Ubuntu 18.04.4
  After upgrade (but never booted): Ubuntu (Kubuntu) 20.04
  Note that Ubuntu had originally be installed, but kubuntu-desktop was 
recently installed to change to Kubuntu, but no booting problems were 
experienced before updating to 20.04.

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in 
  Unknown -- Package version may have changed when upgrading to 20.04.

  3) What you expected to happen
  Boot without kernel panic.

  4) What happened instead
  Could not boot.  Even selecting safe mode from grub could not boot.  Had to 
restore system from backups.  Will not attempt upgrade again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+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 1872560] Re: integer overflow in whoopsie 0.2.69

2020-05-06 Thread Seong-Joong Kim

Sure. This issue is also reproducible with pre-compiled version of
0.2.62ubuntu0.4.

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

Title:
integer overflow in whoopsie 0.2.69

Status in whoopsie package in Ubuntu:
Confirmed

Bug description:
Hi,

I have found a security issue on whoopsie 0.2.69 and earlier.

## Vulnerability in whoopsie
- whoopsie 0.2.69 and earlier have a heap-based buffer overflow
vulnerability.
- An attacker can cause a denial of service (memory corruption and
application crash) via a crafted .crash file.

## Basic
When a program has been crashed, Linux system tries to create a '.crash' file
on '/var/crash/' directory with python script located in
'/usr/share/apport/apport'.
The file contains a series of system crash information including core dump,
syslog, stack trace, memory map info, etc.
After the creation of '.crash' file, whoopsie extracts the above information
from the '.crash' file and encodes it into binary json (bson) format.
Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error
Report system.

## Vulnerability
Unfortunately, we have found a heap-based buffer overflow vulnerability
during the encoding, when whoopsie attempts to bsonify with crafted crash file.
The data in '.crash' file is stored in key-value form and the whoopsie
separately measures the length of 'key' and 'value' to allocate memory region
during the encoding.
A heap-based buffer overflow can occur when an integer overflow happens on a
variable that contains length of 'key'.
FYI, a issue to that raised by 'value' is well covered by performing
exception handling.

@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]

const uint32_t len = strlen( name ) + 1;

- Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value.
- Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.

@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]

b->data = bson_realloc( b->data, new_size );

- Unexpected small memory region is allocated due to above integer
overflow.

@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]

bson_append( b, name, len );

- Memory corruption happens when unexpected small memory region is
allocated.

## Attack Scenario
1) Create a fake.crash file
- '.crash' file is composed of the following format: 'key : value'.
- To cause the overflow attack, the size of 'key' should be in double amount
of INT32_MAX.
- The size of 'value' doesn’t matter, but not zero length.

$ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
$ cat fake.crash
AAA … AA : B

2) Trigger the whoopsie to read the fake.crash file
- Just create 'fake.upload' file by touch command.
- Or launch apport-gtk gui or apport-bug cli application.

3) Check out the result
- After a while, the whoopsie has been killed by segmentation fault.

Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1877194] Re: Selected audio output device not persistent between reboots (Resets to USB-device)

** Description changed:

  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
  
  Only difference is that it does not reset to HDMI output, but to one of
  my USB-outputs. It does not respect the change I made after reboot.
+ 
+ In short:
+ 1. Boot system
+ 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
+ 3. Reboot.
+ 4 Output device is now back to "Analogue Output - RODE NT-USB".
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  Selected audio output device not persistent between reboots (Resets to
  USB-device)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877194/+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 1876125] Autopkgtest regression report (evolution-data-server/3.36.2-0ubuntu1)

2020-05-06 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted evolution-data-server (3.36.2-0ubuntu1) 
for focal have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/1:6.4.3-0ubuntu0.20.04.1 (ppc64el, armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#evolution-data-server

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  SRU the current 3.36.2 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1876125/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

2020-05-06 Thread Kai Groner

In the generic kernel CONFIG_RT_GROUP_SCHED is still enabled.  It was
only disabled for the lowlatency kernel.

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in rtkit package in Ubuntu:
  Confirmed

Bug description:
  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1877194] Re: Selected audio output device not persistent between reboots (Resets to USB-device)

** Description changed:

  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
  
  Only difference is that it does not reset to HDMI output, but to one of
  my USB-outputs. It does not respect the change I made after reboot.
- 
- (Notice that I swapped out my username with $USER in the text below)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  $USER 1604 F pulseaudio
-  /dev/snd/controlC0:  $USER 1604 F pulseaudio
-  /dev/snd/controlC1:  $USER 1604 F pulseaudio
-  /dev/snd/pcmC1D0c:   $USER 1604 F...m pulseaudio
+  /dev/snd/controlC2:  marcus 1604 F pulseaudio
+  /dev/snd/controlC0:  marcus 1604 F pulseaudio
+  /dev/snd/controlC1:  marcus 1604 F pulseaudio
+  /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  Selected audio output device not persistent between reboots (Resets to
  USB-device)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877194/+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 1872560] Re: integer overflow in whoopsie 0.2.69

2020-05-06 Thread Marc Deslauriers

Sorry, I meant "Are you able to reproduce the issue with the pre-
compiled version of Whoopsie that comes with it?"

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

Title:
integer overflow in whoopsie 0.2.69

Status in whoopsie package in Ubuntu:
Confirmed

Bug description:
Hi,

I have found a security issue on whoopsie 0.2.69 and earlier.

@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]

const uint32_t len = strlen( name ) + 1;

- Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value.
- Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.

@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]

b->data = bson_realloc( b->data, new_size );

- Unexpected small memory region is allocated due to above integer
overflow.

@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]

bson_append( b, name, len );

- Memory corruption happens when unexpected small memory region is
allocated.

$ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
$ cat fake.crash
AAA … AA : B

2) Trigger the whoopsie to read the fake.crash file
- Just create 'fake.upload' file by touch command.
- Or launch apport-gtk gui or apport-bug cli application.

3) Check out the result
- After a while, the whoopsie has been killed by segmentation fault.

Sincerely,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1872560/+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 1877194] Re: Selected audio output device not persistent between reboots (Resets to USB-device)

** Description changed:

  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
  
- Only difference is that it does not reset to and HDMI output, but to one
- of my USB-outputs. It does not respect the change I made after reboot.
+ Only difference is that it does not reset to HDMI output, but to one of
+ my USB-outputs. It does not respect the change I made after reboot.
  
  (Notice that I swapped out my username with $USER in the text below)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  $USER 1604 F pulseaudio
   /dev/snd/controlC0:  $USER 1604 F pulseaudio
   /dev/snd/controlC1:  $USER 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   $USER 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

Title:
  Selected audio output device not persistent between reboots (Resets to
  USB-device)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  (Notice that I swapped out my username with $USER in the text below)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  $USER 1604 F pulseaudio
   /dev/snd/controlC0:  $USER 1604 F pulseaudio
   /dev/snd/controlC1:  $USER 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   $USER 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877194/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

2020-05-06 Thread DaveTickem

Attached is the output from journalctl -b 0, where the error occurs.

Apologies - no vagrant skills here, but I can confirm Kai's replication
method -  kvm qemu clean 20.04 server install, then add pulseaudio,
docker.io, reboot and the issue occurs.


** Attachment added: "20.04 boot log showing rtkit-daemon failing to enable RT 
scheduling."
   
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+attachment/5367552/+files/ubuntu-20.04-server-rtkit-failing-bootlog.txt

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in rtkit package in Ubuntu:
  Confirmed

Bug description:
  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1877194] [NEW] Selected audio output device not persistent between reboots (Resets to USB-device)

Public bug reported:

Similar to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

Only difference is that it does not reset to HDMI output, but to one of
my USB-outputs. It does not respect the change I made after reboot.

(Notice that I swapped out my username with $USER in the text below)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  $USER 1604 F pulseaudio
 /dev/snd/controlC0:  $USER 1604 F pulseaudio
 /dev/snd/controlC1:  $USER 1604 F pulseaudio
 /dev/snd/pcmC1D0c:   $USER 1604 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May  6 23:40:08 2020
InstallationDate: Installed on 2020-05-06 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/27/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3703
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII HERO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal

** Description changed:

  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
  
  Only difference is that it does not reset to and HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC2:  marcus 1604 F pulseaudio
-  /dev/snd/controlC0:  marcus 1604 F pulseaudio
-  /dev/snd/controlC1:  marcus 1604 F pulseaudio
-  /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  $USER 1604 F pulseaudio
+  /dev/snd/controlC0:  $USER 1604 F pulseaudio
+  /dev/snd/controlC1:  $USER 1604 F pulseaudio
+  /dev/snd/pcmC1D0c:   $USER 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

** Description changed:

  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
  
  Only difference is that it does not reset to and HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.
+ 
+ (Notice that I swapped out my username with $USER in the text below)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  $USER 1604 F pulseaudio
   /dev/snd/controlC0:  $USER 1604

[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2020-05-06 Thread Ryan Moore

I"ve had this problem on a clean install of 20.04 on a new laptop, with
two headsets that support both profiles.

```
Name: Soundcore Life 2
Alias: Soundcore Life 2
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
```
Name: OnePlus Bullets Wireless 2
Alias: OnePlus Bullets Wireless 2
Class: 0x00240418
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Serial Port   (1101--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: Battery Service   (180f--1000-8000-00805f9b34fb)
Modalias: bluetooth:v000Apd
```

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

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

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

seems like from the other bug that it got turn off again in -26.30 which
is the revision in use by the report here according to the apport
report?

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in rtkit package in Ubuntu:
  Confirmed

Bug description:
  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1873920] Re: default vi on focal emits escape sequences unrecognized by bionic's terminal?

2020-05-06 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  default vi on focal emits escape sequences unrecognized by bionic's
  terminal?

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  On ubuntu 18.04, opening the default terminal (gnome-terminal
  3.28.2-1ubuntu1~18.04.1), ssh'ing to an up-to-date ubuntu 20.04
  system, running 'vi', and pressing 'i' shows the unwelcome garbage ESC
  [>4;m.  Pressing ESC emits more garbage: ESC [>4;2m

  Focal's default vi is provided by vim.tiny via alternatives.  Oddly,
  when running vim.tiny by itself, or if you install vim and let it
  provide vi, the garbage does not appear.

  Evidently focal's vim.tiny is confused about what escape sequences
  ubu1804's Terminal accepts.

  TERM is xterm-256color.  The problem also occurs if TERM is xterm.

  There is no .vimrc.

  If I use xterm on ubuntu 18.04, all is well.  Evidently xterm accepts
  ESC[>4;m and gnome-terminal doesn't?

  I captured a session using 'script' and dumped typescript via hexdump -C. 
  In this session, I typed i, Q, and escape. Here's an excerpt
  showing the end of vi's welcome message, followed by five escape sequences
  and then the Q I typed.  The unrecognized ESC > 4;m is visible in the dump,
  followed by ESC[?25l (CURSOR OFF)

  1070  66 61 75 6c 74 1b 5b 33  34 6d 3c 45 6e 74 65 72  |fault.[34m.[m for info on|
  1090  20 74 68 69 73 1b 5b 31  3b 31 48 1b 5b 3f 32 35  | this.[1;1H.[?25|
  10a0  68 1b 5b 3f 32 30 30 34  6c 1b 5b 3e 34 3b 6d 1b  |h.[?2004l.[>4;m.|
  10b0  5b 3f 32 35 6c 51 1b 5b  38 3b 34 37 48 1b 5b 31  |[?25lQ.[8;47H.[1|

  The mystery sequence ESC [ > 4;m appears to be "Set/reset key modifier 
options, xterm",
  per https://invisible-island.net/xterm/ctlseqs/ctlseqs.html.  So it's trying
  to modify function keys, or something.

  ssh'ing in from a mac worked fine (TERM there was also xterm-256color),
  as did ssh'ing from an ubuntu 19.04 system with gnome-terminal.
  ssh'ing from another ubuntu 18.04 system exhibited the same problem.

  So it's a little family squabble between focal's vim.tiny and ubuntu
  18.04/bionic's gnome-terminal...?

  Given how long 18.04's going to be supported, this seems worth
  resolving somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: vim-tiny 2:8.1.2269-1ubuntu5 [modified: 
usr/share/vim/vim81/doc/help.txt usr/share/vim/vim81/doc/tags]
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Uname: Linux 5.4.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr 20 09:27:50 2020
  InstallationDate: Installed on 2020-01-27 (83 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1873920/+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 1877129] Re: jackd won't run in realtime

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

** This bug has been marked a duplicate of bug 1875665
   rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after 
upgrade to 20.04

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

Title:
  jackd won't run in realtime

Status in jackd2 package in Ubuntu:
  Incomplete

Bug description:
  Was using jackd2 for ages, never had this issue. The usual limits.conf
  tweaks are present. Jackd won't run in realtime even as root. It's
  very easy to reproduce in Focal.

  Before upgrade, was working:
  Ubuntu 18.04.4 LTS
  uname -r
  kernel 5.3.0-51-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  After upgrade:
  Ubuntu 20.04 LTS
  uname -r
  5.4.0-29-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  
  Simple test:
  jackd -R -d dummy -r192000 -p2048

  jackdmp 1.9.12
  Copyright 2001-2005 Paul Davis and others.
  Copyright 2004-2016 Grame.
  Copyright 2016-2017 Filipe Coelho.
  jackdmp comes with ABSOLUTELY NO WARRANTY
  This is free software, and you are welcome to redistribute it
  under certain conditions; see the file COPYING for details
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  JACK server starting in realtime mode with priority 10
  self-connect-mode is "Don't restrict self connect requests"
  Cannot use real-time scheduling (RR/10)(1: Operation not permitted)
  AcquireSelfRealTime error

  I'm guessing that it's not jack itself (package ver. seems to be the
  same as bionic, without new feats), smth is missing in the kernel
  config. I would try RT kernel, but it usually does not boot at all
  thanks to Nvidia blob on that system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1877129/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-05-06 Thread Jamie Strandboge

FYI, there is a pending update that will go out either tomorrow or early
next week. Please base your next upload on this update.

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1872902] Re: Upgrade to Focal now removes chrony

I retested the armhf autopkgtest failures and update-manager and update-
notifier have now both passed.

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

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in germinate package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in germinate source package in Focal:
  New
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Fix Committed

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
    MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
     Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  Test Case
  -
  1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package 
chrony
  2) Run do-release-upgrade with the appropriate switches
  3) Observe that chrony is marked for deletion

  With the version of dist-upgrader from -proposed (accessed with the -p
  switch) chrony is no longer marked for deletion.

  Regression Potential
  
  Given that Dimitri's change is now ignoring the tasks minimal and standard 
(which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious 
and test desktop upgrades and ensure that packages in those tasks are not 
marked for removal.

  Regression Test
  ---
  1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system
  2) Record the list of packages marked for removal

  Compare the list of packages marked for removal with the release-
  upgrader from -proposed from Focal.

  Original Description
  
  I'd ask you to revise the dependencies that got changes in systemd 
245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as 
that was an opt-in chances are quite high people would want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1877182] Re: Blank screen timer does not work

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:

  apport-collect 1877182

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  Blank screen timer does not work

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  It just does not work if I set it to never or to 15 MIN it does not
  work it is stuck at one min

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-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  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 22:43:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d3d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d3d]
  InstallationDate: Installed on 2020-05-02 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f2:b3fd Chicony Electronics Co., Ltd HD WebCam 
(Asus N-series)
   Bus 001 Device 005: ID 0b05:17ac ASUSTek Computer, Inc. ASUS Laser GAMING 
MOUSE
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. G551VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7fb860e1-6845-4a22-9fde-4c8435d52aba ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G551VW.209
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G551VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG551VW.209:bd02/19/2016:svnASUSTeKCOMPUTERINC.:pnG551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G551VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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/gnome-shell/+bug/1877182/+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-05-06 Thread Launchpad Bug Tracker

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

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/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:
  Confirmed

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 1877183] [NEW] segfault in mysql_server_end() from libmysqlclient.so.21

2020-05-06 Thread JonHurst

Public bug reported:

libmysqlclient.so.21 causes a segfault on shutdown.

Test case attached ==> "Removed database" will not be reported.

Backtrace:
#0  0x714c330f in ?? () from /lib/x86_64-linux-gnu/libmysqlclient.so.21
#1  0x714c8823 in ?? () from /lib/x86_64-linux-gnu/libmysqlclient.so.21
#2  0x71466243 in mysql_server_end () from 
/lib/x86_64-linux-gnu/libmysqlclient.so.21
#3  0x71b4d0ee in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so
#4  0x71b4d10d in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so
#5  0x778e55fb in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5
#6  0x778e588e in QSqlDatabase::~QSqlDatabase() () from 
/lib/x86_64-linux-gnu/libQt5Sql.so.5
#7  0x778e5d9c in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5
#8  0x5579 in cause_segfault () at main.cpp:16
#9  0x5729 in main (argc=1, argv=0x7fffeb18) at main.cpp:23

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libqt5sql5-mysql 5.12.8+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed May  6 21:40:58 2020
InstallationDate: Installed on 2020-04-27 (9 days ago)
InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: qtbase-opensource-src
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Attachment added: "Test case"
   https://bugs.launchpad.net/bugs/1877183/+attachment/5367528/+files/main.cpp

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

Title:
  segfault in mysql_server_end() from libmysqlclient.so.21

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  libmysqlclient.so.21 causes a segfault on shutdown.

  Test case attached ==> "Removed database" will not be reported.

  Backtrace:
  #0  0x714c330f in ?? () from 
/lib/x86_64-linux-gnu/libmysqlclient.so.21
  #1  0x714c8823 in ?? () from 
/lib/x86_64-linux-gnu/libmysqlclient.so.21
  #2  0x71466243 in mysql_server_end () from 
/lib/x86_64-linux-gnu/libmysqlclient.so.21
  #3  0x71b4d0ee in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so
  #4  0x71b4d10d in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/sqldrivers/libqsqlmysql.so
  #5  0x778e55fb in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5
  #6  0x778e588e in QSqlDatabase::~QSqlDatabase() () from 
/lib/x86_64-linux-gnu/libQt5Sql.so.5
  #7  0x778e5d9c in ?? () from /lib/x86_64-linux-gnu/libQt5Sql.so.5
  #8  0x5579 in cause_segfault () at main.cpp:16
  #9  0x5729 in main (argc=1, argv=0x7fffeb18) at main.cpp:23

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libqt5sql5-mysql 5.12.8+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Wed May  6 21:40:58 2020
  InstallationDate: Installed on 2020-04-27 (9 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1877183/+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 1877182] [NEW] Blank screen timer does not work

2020-05-06 Thread mohamed moursi

Public bug reported:

It just does not work if I set it to never or to 15 MIN it does not work
it is stuck at one min

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-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  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May  6 22:43:44 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d3d]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d3d]
InstallationDate: Installed on 2020-05-02 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 04f2:b3fd Chicony Electronics Co., Ltd HD WebCam (Asus 
N-series)
 Bus 001 Device 005: ID 0b05:17ac ASUSTek Computer, Inc. ASUS Laser GAMING MOUSE
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. G551VW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=7fb860e1-6845-4a22-9fde-4c8435d52aba ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 02/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G551VW.209
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G551VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG551VW.209:bd02/19/2016:svnASUSTeKCOMPUTERINC.:pnG551VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG551VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G551VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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+git20200226-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

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

Title:
  Blank screen timer does not work

Status in xorg package in Ubuntu:
  New

Bug description:
  It just does not work if I set it to never or to 15 MIN it does not
  work it is stuck at one min

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-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  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 22:43:44 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.6, 5.4.0-29-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel

[Touch-packages] [Bug 1877181] [NEW] package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2020-05-06 Thread Thomas

Public bug reported:

Happening while trying to upgrade from 18.04 to 20.04.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6
ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed May  6 14:26:11 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2014-03-10 (2249 days ago)
InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Happening while trying to upgrade from 18.04 to 20.04.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed May  6 14:26:11 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-03-10 (2249 days ago)
  InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release 
amd64 (20140204)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1877181/+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 1877181] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2020-05-06 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.136ubuntu6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Happening while trying to upgrade from 18.04 to 20.04.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
  Uname: Linux 5.3.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed May  6 14:26:11 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2014-03-10 (2249 days ago)
  InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release 
amd64 (20140204)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1877181/+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 1872902] Re: Upgrade to Focal now removes chrony

Testing on an Ubuntu 18.04 LTS system with ubuntu-desktop and chrony
installed.

bdmurray@clean-bionic-amd64:/tmp/u-r-u-proposed$ apt-cache policy chrony
chrony:
  Installed: 3.5-6ubuntu6
  Candidate: 3.5-6ubuntu6
  Version table:
 *** 3.5-6ubuntu6 500
500 http://192.168.10.7/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
bdmurray@clean-bionic-amd64:/tmp/u-r-u-proposed$ apt-cache policy 
systemd-timesyncd
systemd-timesyncd:
  Installed: (none)
  Candidate: 245.4-4ubuntu3
  Version table:
 245.4-4ubuntu3 500
500 http://192.168.10.7/ubuntu focal/main amd64 Packages
bdmurray@clean-bionic-amd64:/tmp/u-r-u-proposed$ head 
/var/log/dist-upgrade/main.log 
2020-05-06 12:26:14,373 INFO Using config files '['./DistUpgrade.cfg.bionic']'
2020-05-06 12:26:14,373 INFO uname information: 'Linux clean-bionic-amd64 
4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64'
2020-05-06 12:26:14,733 INFO apt version: '1.6.12'
2020-05-06 12:26:14,733 INFO python version: '3.6.9 (default, Apr 18 2020, 
01:56:04) 
[GCC 8.4.0]'
2020-05-06 12:26:14,737 INFO release-upgrader version '20.04.19' started
2020-05-06 12:26:14,740 INFO locale: 'en_US' 'UTF-8'
2020-05-06 12:26:14,805 DEBUG Using 'DistUpgradeViewText' view
2020-05-06 12:26:14,843 DEBUG enable dpkg --force-overwrite
2020-05-06 12:26:14,870 DEBUG creating statefile: 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'

I had the same results with tasksel as I did with the lxc container
upgrade.

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

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in germinate package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in germinate source package in Focal:
  New
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Fix Committed

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
    MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
     Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  Test Case
  -
  1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package 
chrony
  2) Run do-release-upgrade with the appropriate switches
  3) Observe that chrony is marked for deletion

  With the version of dist-upgrader from -proposed (accessed with the -p
  switch) chrony is no longer marked for deletion.

  Regression Potential
  
  Given that Dimitri's change is now ignoring the tasks minimal and standard 
(which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious 
and test desktop upgrades and ensure that packages in those tasks are not 
marked for removal.

  Regression Test
  ---
  1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system
  2) Record the list of packages marked for removal

  Compare the list of packages marked for removal with the release-
  upgrader from -proposed from Focal.

  Original Description
  
  I'd ask you to revise the dependencies that got changes in systemd 
245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as 
that was an opt-in chances are quite high people would want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1862232] Re: Long hostname causes networking setup to fail

on xenial, additional fix is needed for bug 1877176 for complete fix for
this bug, but this patch introduces no regressions and allows networkd
to continue requesting the lease for invalid hostnames.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  Long hostname causes networking setup to fail

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  networkd fails to bring up networking on systems with long hostname

  [test case]

  setting the hostname:

  $ sudo hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  then reboot and check the networking.

  [regression potential]

  as this adjusts logging and certain error handling while performing
  dhcp, any regression would likely cause dhcp failure.

  [scope]

  this is fixed by upstream commit
  a8494759b4f14af5337391727ba295ab708b92f9 (along with some associated
  commits around it), which is included starting in v240, so this is
  included already in Eoan and later.

  This is needed in Bionic and Xenial.

  [other info]

  the problem around this is that Linux sets HOST_NAME_MAX to 64, but
  RFC 1035 limits DNS labels to 63 characters, so any host with a max-
  length single-label hostname (i.e. a 64 character hostname with no
  dots) will be "valid" from Linux's perspective, but will violate RFC
  1035 and thus systemd will consider it invalid and won't pass it to
  the dhcp server.

  Also note that a 64-character hostname that is *not* single-label
  (i.e. a hostname with at least 1 dot) will not cause this problem.

  The systemd patches continue to reject sending the invalid hostname to
  the dhcp server, but do not prevent networkd from finishing setting up
  networking.

  [original description]

  1) ubuntu version
  # lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  2) package version
  # apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.31
    Candidate: 237-3ubuntu10.31
    Version table:
   *** 237-3ubuntu10.31 500
  500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
  es
  100 /var/lib/dpkg/status
   237-3ubuntu10.29 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages

  3) I expect the network to come online correctly regardless of how
  long the hostname is. This is what happens with both 14.0 and 19.0 (I
  tested the same behavior with both of them).

  4) the external network interface fails to be configured and is stuck
  in a (pending) state as reported by networkctl status -a

  setting the hostname:

  # hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  after rebooting the machine, it no longer has network access.

  # journalctl
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: 
Starting Wait for Network to be Configured...
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: Link state is up-to-date
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: found matching network 
'/run/systemd/network/10-netplan-eth0.network'
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: sd-netlink: callback failed: Invalid argument
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: lo: Link state is up-to-date

  # networkctl status -a:
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1

  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: off (pending)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: Virtio network device
    HW Address: ae:4d:91:1c:e8:86
   DNS: 67.207.67.3
    67.207.67.2

  and to bring up the network correctly, set the hostname to something
  shorter

  # hostnamectl set-hostname asdf
  # systemctl restart systemd-networkd
  # networkctl status -a
  ● 1: lo
     Link File:

[Touch-packages] [Bug 1877176] [NEW] 64-char hostname causes dhcp server to reject lease

Public bug reported:

[impact]

a systemd with a 64-character hostname (the maximum hostname length for
Linux) will cause a dhcp server to reject its dhcp lease due to passing
the invalid hostname in the dhcp lease request.

[test case]

$ cat /etc/systemd/network/10-ens3.network
[Match]
Name=ens3

[Network]
DHCP=yes


set hostname to 64-char name, e.g.:

$ sudo hostnamectl set-hostname
a123456789b123456789c123456789d123456789e123456789f123456789g123

restart networkd:

$ sudo systemctl restart systemd-networkd

check logs:

root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# 
journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error'
May 06 19:01:30 
a123456789b123456789c123456789d123456789e123456789f123456789g123 
systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument

[scope]

this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which
is included in Bionic and later.  This is needed only for Xenial.

[other info]

this is a follow on to bug 1862232, which corrected sd-dhcp-client.c to
continue networkd dhcp even if the hostname is invalid, however the
older code in Xenial doesn't correctly detect the invalid hostname, so
this additional patch is needed.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Ubuntu Xenial)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Also affects: systemd (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

** Changed in: systemd (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  64-char hostname causes dhcp server to reject lease

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress

Bug description:
  [impact]

  a systemd with a 64-character hostname (the maximum hostname length
  for Linux) will cause a dhcp server to reject its dhcp lease due to
  passing the invalid hostname in the dhcp lease request.

  [test case]

  $ cat /etc/systemd/network/10-ens3.network
  [Match]
  Name=ens3

  [Network]
  DHCP=yes

  
  set hostname to 64-char name, e.g.:

  $ sudo hostnamectl set-hostname
  a123456789b123456789c123456789d123456789e123456789f123456789g123

  restart networkd:

  $ sudo systemctl restart systemd-networkd

  check logs:

  root@a123456789b123456789c123456789d123456789e123456789f123456789g123:~# 
journalctl -b -u systemd-networkd --no-pager | grep 'DHCP error'
  May 06 19:01:30 
a123456789b123456789c123456789d123456789e123456789f123456789g123 
systemd-networkd[737]: ens3: DHCP error: Client failed: Invalid argument

  [scope]

  this is fixed by commit 9740eae694e93b06658ff3b3045b22b591561e7c which
  is included in Bionic and later.  This is needed only for Xenial.

  [other info]

  this is a follow on to bug 1862232, which corrected sd-dhcp-client.c
  to continue networkd dhcp even if the hostname is invalid, however the
  older code in Xenial doesn't correctly detect the invalid hostname, so
  this additional patch is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877176/+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] Re: /proc/sys/kernel/random/boot_id rule missing from abstractions/nameservice

2020-05-06 Thread Simon Déziel

The missing rule for boot_id was added to Apparmor 2.13
(https://gitlab.com/apparmor/apparmor/-/blob/apparmor-2.13/profiles/apparmor.d/abstractions/nameservice#L35)
and was later refined in the master branch. As such, marking as fix
committed.


** Changed in: apparmor (Ubuntu)
   Status: New => 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/1872564

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

Status in apparmor package in Ubuntu:
  Fix Committed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564/+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 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable

2020-05-06 Thread Simon Déziel

On 2020-05-06 2:49 p.m., Andreas Hasenack wrote:
> There are many alternatives here.

IIRC, `chmod -x` snippets from /etc/update-motd.d/ was the way to go a
few releases ago when it was consumed by run-parts.

> I think fixing this doesn't warrant an SRU, but should be considered for
> the devel release of ubuntu (groovy at the moment).

It's merely to avoid harmless surprise and keep the old sysadmins happy,
certainly not worth a SRU.

Thanks,
Simon

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

Title:
  motd-news.service scheduled even when /etc/update-motd.d/50-motd-news
  is not executable

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  update-motd(5) says:

   Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as 
the root user at each
   login, and this information is concatenated in /run/motd.dynamic.  The order 
of  script  execu‐
   tion is determined by the run-parts(8) --lsbsysinit option (basically 
alphabetical order, with
   a few caveats).

  So sysadmins are used to "chmod -x" motd fragments from /etc/update-
  motd.d/ to prevent their execution. When doing so for /etc/update-
  motd.d/50-motd-news, I noticed that motd-news.timer was still trying
  to execute the motd-news.service unit which then logged a failure:

   systemd[3704]: motd-news.service: Failed to execute command: Permission 
denied
   systemd[3704]: motd-news.service: Failed at step EXEC spawning 
/etc/update-motd.d/50-motd-news:
    Permission denied
   systemd[1]: motd-news.service: Main process exited, code=exited, 
status=203/EXEC
   systemd[1]: motd-news.service: Failed with result 'exit-code'.
   systemd[1]: Failed to start Message of the Day.

  The motd-news.service unit looks like this:

  $ systemctl cat motd-news.service
  # /lib/systemd/system/motd-news.service
  [Unit]
  Description=Message of the Day
  After=network-online.target
  Documentation=man:update-motd(8)

  [Service]
  Type=oneshot
  ExecStart=/etc/update-motd.d/50-motd-news --force

  This problem was observed on a Bionic system:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  $ apt-cache policy base-files
  base-files:
    Installed: 10.1ubuntu2.3
    Candidate: 10.1ubuntu2.3
    Version table:
   *** 10.1ubuntu2.3 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   10.1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   10.1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  But the problem also exist in Disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1803601/+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 1818548] Re: namei -l incorrect error message

2020-05-06 Thread Seth Arnold

Yay, this appears to have been fixed in focal:

$ namei -l /etc/ssl/private/ssl-cert-snakeoil.key
f: /etc/ssl/private/ssl-cert-snakeoil.key
drwxr-xr-x root root /
drwxr-xr-x root root etc
drwxr-xr-x root root ssl
drwx--x--- root ssl-cert private
 ssl-cert-snakeoil.key - Permission denied

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

Title:
  namei -l incorrect error message

Status in util-linux package in Ubuntu:
  New

Bug description:
  Hello, namei -l gives incorrect error messages if a directory is not
  readable:

  $ namei -l /etc/ssl/private/ssl-cert-snakeoil.key
  f: /etc/ssl/private/ssl-cert-snakeoil.key
  drwxr-xr-x root root /
  drwxr-xr-x root root etc
  drwxr-xr-x root root ssl
  drwx--x--- root ssl-cert private
   ssl-cert-snakeoil.key - No such file or directory
  $ cat /etc/ssl/private/ssl-cert-snakeoil.key
  cat: /etc/ssl/private/ssl-cert-snakeoil.key: Permission denied
  $ ls -l /etc/ssl/private/
  ls: cannot open directory '/etc/ssl/private/': Permission denied

  
  "No such file or directory" is a poor error message for this case. The 
correct error message (as shown by cat) is "Permission denied".

  Incorrect error messages make this tool much less useful.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: util-linux 2.31.1-0.4ubuntu3.3
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Mon Mar  4 09:00:12 2019
  InstallationDate: Installed on 2012-10-18 (2328 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (306 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1818548/+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 1872902] Re: Upgrade to Focal now removes chrony

Testing in an Ubuntu 18.04 LTS lxc container.

root@bionic:/tmp/u-r-u-proposed# apt-cache policy chrony
chrony:
  Installed: 3.5-6ubuntu6
  Candidate: 3.5-6ubuntu6
  Version table:
 *** 3.5-6ubuntu6 500
500 http://192.168.10.7/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
root@bionic:/tmp/u-r-u-proposed# apt-cache policy systemd-timesyncd
systemd-timesyncd:
  Installed: (none)
  Candidate: 245.4-4ubuntu3
  Version table:
 245.4-4ubuntu3 500
500 http://192.168.10.7/ubuntu focal/main amd64 Packages
root@bionic:/tmp/u-r-u-proposed# head /var/log/dist-upgrade/main.log 
2020-05-06 18:53:45,805 INFO Using config files '['./DistUpgrade.cfg.bionic']'
2020-05-06 18:53:45,805 INFO uname information: 'Linux bionic 5.4.0-26-generic 
#30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64'
2020-05-06 18:53:46,054 INFO apt version: '1.6.12'
2020-05-06 18:53:46,054 INFO python version: '3.6.9 (default, Apr 18 2020, 
01:56:04) 
[GCC 8.4.0]'
2020-05-06 18:53:46,058 INFO release-upgrader version '20.04.19' started
2020-05-06 18:53:46,063 WARNING can't import view 'DistUpgradeViewGtk3' 
(Namespace Vte not available)
2020-05-06 18:53:46,104 WARNING can't import view 'DistUpgradeViewKDE' (No 
module named 'PyQt4')

Additionally, I ran 'tasksel install standard' and 'tasksel install
minimal' to ensure that no packages in either task were removed and none
were. (Although doing that installed systemd-timesyncd.)

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

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in germinate package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in germinate source package in Focal:
  New
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Fix Committed

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
    MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
     Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  Test Case
  -
  1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package 
chrony
  2) Run do-release-upgrade with the appropriate switches
  3) Observe that chrony is marked for deletion

  With the version of dist-upgrader from -proposed (accessed with the -p
  switch) chrony is no longer marked for deletion.

  Regression Potential
  
  Given that Dimitri's change is now ignoring the tasks minimal and standard 
(which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious 
and test desktop upgrades and ensure that packages in those tasks are not 
marked for removal.

  Regression Test
  ---
  1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system
  2) Record the list of packages marked for removal

  Compare the list of packages marked for removal with the release-
  upgrader from -proposed from Focal.

  Original Description
  
  I'd ask you to revise the dependencies that got changes in systemd 
245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as 
that was an opt-in chances are quite high people would want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable

2020-05-06 Thread Andreas Hasenack

There are many alternatives here. What you describe is one, and you
could then also add a systemd override with that exec check. A bit
cumbersome, though.

Another one is specific to this service, and that is to set ENABLED=0 in
/etc/default/motd-news.

I think fixing this doesn't warrant an SRU, but should be considered for
the devel release of ubuntu (groovy at the moment).

** Changed in: base-files (Ubuntu)
   Status: New => Triaged

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

Title:
  motd-news.service scheduled even when /etc/update-motd.d/50-motd-news
  is not executable

Status in base-files package in Ubuntu:
  Triaged

Bug description:
  update-motd(5) says:

   Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as 
the root user at each
   login, and this information is concatenated in /run/motd.dynamic.  The order 
of  script  execu‐
   tion is determined by the run-parts(8) --lsbsysinit option (basically 
alphabetical order, with
   a few caveats).

  So sysadmins are used to "chmod -x" motd fragments from /etc/update-
  motd.d/ to prevent their execution. When doing so for /etc/update-
  motd.d/50-motd-news, I noticed that motd-news.timer was still trying
  to execute the motd-news.service unit which then logged a failure:

   systemd[3704]: motd-news.service: Failed to execute command: Permission 
denied
   systemd[3704]: motd-news.service: Failed at step EXEC spawning 
/etc/update-motd.d/50-motd-news:
    Permission denied
   systemd[1]: motd-news.service: Main process exited, code=exited, 
status=203/EXEC
   systemd[1]: motd-news.service: Failed with result 'exit-code'.
   systemd[1]: Failed to start Message of the Day.

  
  The motd-news.service unit looks like this:

  $ systemctl cat motd-news.service
  # /lib/systemd/system/motd-news.service
  [Unit]
  Description=Message of the Day
  After=network-online.target
  Documentation=man:update-motd(8)

  [Service]
  Type=oneshot
  ExecStart=/etc/update-motd.d/50-motd-news --force

  
  This problem was observed on a Bionic system:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  $ apt-cache policy base-files
  base-files:
    Installed: 10.1ubuntu2.3
    Candidate: 10.1ubuntu2.3
    Version table:
   *** 10.1ubuntu2.3 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   10.1ubuntu2.2 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   10.1ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  But the problem also exist in Disco.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1803601/+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 1776654] Re: systemd upstream sysusers tests fails

This was fixed in Debian at version 244.2-1, which is earlier than the
version in focal, so this is fix released for focal.

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

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

Title:
  systemd upstream sysusers tests fails

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  TEST-21-SYSUSERS autopkgtest fails

  [test case]

  see original description

  [regression potential]

  any regression would be limited to incorrect pass/fail of
  TEST-21-SYSUSERS

  [scope]

  TEST-21-SYSUSERS does not exist in Xenial, it is first contained in
  Bionic.  This is needed for B, E, and F.

  [original description]

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-cosmic-canonical-kernel-team-
  bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz

  == TEST-21-SYSUSERS ==
  make: Entering directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  TEST CLEANUP: Sysuser-related tests
  TEST SETUP: Sysuser-related tests
  TEST RUN: Sysuser-related tests
  *** Running test-1.input
  *** Running test-2.input
  *** Running test-3.input
  *** Running test-4.input
  *** Running test unhappy-1.input
  --- /var/tmp/systemd-test.TjNA7s/tmp/err  2018-06-13 00:22:12.805061468 
+
  +++ unhappy-1.expected-err2018-01-28 15:58:17.0 +
  @@ -1 +1 @@
  -Creating user xxx (n/a) with uid 312 and gid 310.
  +Failed to parse UID: '99': Numerical result out of range
   Unexpected error output for unhappy-1.input
  Creating user xxx (n/a) with uid 312 and gid 310.
  make: *** [run] Error 1
  Makefile:4: recipe for target 'run' failed
  make: Leaving directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'

  FAILED TESTS:  test/TEST-21-SYSUSERS
  autopkgtest [00:22:13]: test upstream: ---]
  upstream FAIL non-zero exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1776654] Re: systemd upstream sysusers tests fails

TEST-21 did not fail for any arch for autopkgtests on bionic and eoan.


** Tags removed: verification-needed verification-needed-bionic 
verification-needed-eoan
** Tags added: verification-done verification-done-bionic verification-done-eoan

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

Title:
  systemd upstream sysusers tests fails

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Invalid
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  TEST-21-SYSUSERS autopkgtest fails

  [test case]

  see original description

  [regression potential]

  any regression would be limited to incorrect pass/fail of
  TEST-21-SYSUSERS

  [scope]

  TEST-21-SYSUSERS does not exist in Xenial, it is first contained in
  Bionic.  This is needed for B, E, and F.

  [original description]

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-cosmic-canonical-kernel-team-
  bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz

  == TEST-21-SYSUSERS ==
  make: Entering directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'
  TEST CLEANUP: Sysuser-related tests
  TEST SETUP: Sysuser-related tests
  TEST RUN: Sysuser-related tests
  *** Running test-1.input
  *** Running test-2.input
  *** Running test-3.input
  *** Running test-4.input
  *** Running test unhappy-1.input
  --- /var/tmp/systemd-test.TjNA7s/tmp/err  2018-06-13 00:22:12.805061468 
+
  +++ unhappy-1.expected-err2018-01-28 15:58:17.0 +
  @@ -1 +1 @@
  -Creating user xxx (n/a) with uid 312 and gid 310.
  +Failed to parse UID: '99': Numerical result out of range
   Unexpected error output for unhappy-1.input
  Creating user xxx (n/a) with uid 312 and gid 310.
  make: *** [run] Error 1
  Makefile:4: recipe for target 'run' failed
  make: Leaving directory 
'/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS'

  FAILED TESTS:  test/TEST-21-SYSUSERS
  autopkgtest [00:22:13]: test upstream: ---]
  upstream FAIL non-zero exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+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 1872902] Re: Upgrade to Focal now removes chrony

I also tested upgrading an 19.10 Ubuntu desktop install with chrony
installed to 20.04 LTS and chrony remained installed.

bdmurray@clean-eoan-amd64:/tmp/u-r-u-proposed$ apt-cache policy chrony
chrony:
  Installed: 3.5-6ubuntu6
  Candidate: 3.5-6ubuntu6
  Version table:
 *** 3.5-6ubuntu6 500
500 http://192.168.10.7/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
bdmurray@clean-eoan-amd64:/tmp/u-r-u-proposed$ apt-cache policy 
systemd-timesyncd
systemd-timesyncd:
  Installed: (none)
  Candidate: 245.4-4ubuntu3
  Version table:
 245.4-4ubuntu3 500
500 http://192.168.10.7/ubuntu focal/main amd64 Packages
bdmurray@clean-eoan-amd64:/tmp/u-r-u-proposed$ head 
/var/log/dist-upgrade/main.log 
2020-05-06 11:12:55,719 INFO Using config files '['./DistUpgrade.cfg']'
2020-05-06 11:12:55,719 INFO uname information: 'Linux clean-eoan-amd64 
5.3.0-51-generic #44-Ubuntu SMP Wed Apr 22 21:09:44 UTC 2020 x86_64'
2020-05-06 11:12:56,050 INFO apt version: '1.9.4'
2020-05-06 11:12:56,051 INFO python version: '3.7.5 (default, Apr 19 2020, 
20:18:17) 
[GCC 9.2.1 20191008]'
2020-05-06 11:12:56,053 INFO release-upgrader version '20.04.19' started
2020-05-06 11:12:56,056 INFO locale: 'en_US' 'UTF-8'
2020-05-06 11:12:56,118 DEBUG Using 'DistUpgradeViewText' view
2020-05-06 11:12:56,151 DEBUG enable dpkg --force-overwrite
2020-05-06 11:12:56,182 DEBUG creating statefile: 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'

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

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in germinate package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in germinate source package in Focal:
  New
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Fix Committed

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
    MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
     Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  Test Case
  -
  1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package 
chrony
  2) Run do-release-upgrade with the appropriate switches
  3) Observe that chrony is marked for deletion

  With the version of dist-upgrader from -proposed (accessed with the -p
  switch) chrony is no longer marked for deletion.

  Regression Potential
  
  Given that Dimitri's change is now ignoring the tasks minimal and standard 
(which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious 
and test desktop upgrades and ensure that packages in those tasks are not 
marked for removal.

  Regression Test
  ---
  1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system
  2) Record the list of packages marked for removal

  Compare the list of packages marked for removal with the release-
  upgrader from -proposed from Focal.

  Original Description
  
  I'd ask you to revise the dependencies that got changes in systemd 
245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as 
that was an opt-in chances are quite high people would want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1870589] Re: test-seccomp fails test_restrict_suid_sgid on arm64 on Bionic

autopkgtest now passes on arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200428_033750_621b2@/log.gz

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic

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

Title:
  test-seccomp fails test_restrict_suid_sgid on arm64 on Bionic

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  RestrictSUIDSGID (backported to Bionic in security CVE) fails 100% of
  the time on arm64, and testcase failure indicates this as well.

  [test case]

  check autopkgtest logs, e.g.
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200401_09_34f60@/log.gz

  /* test_restrict_suid_sgid */
  Failed to add suid/sgid rule for architecture arm64, skipping: Numerical 
argument out of domain
  Assertion 'chmod(path, 0775 | S_ISUID) < 0 && errno == EPERM' failed at 
../src/test/test-seccomp.c:823, function test_restrict_suid_sgid(). Aborting.
  suidsgidseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("suidsgidseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:889, function 
test_restrict_suid_sgid(). Aborting.
  FAIL: test-seccomp (code: 134)
  Aborted (core dumped)

  [regression potential]

  this improves the function that (tries to) install seccomp suid/sgid
  filters, so and regression would involve failure to restrict suid/sgid
  with seccomp filters; however on arm64, the this functionality already
  fails 100% of the time (which is what the failed test case was
  pointing out).

  [scope]

  this fails only in Bionic, and this specific feature and testcase was
  backported in patches for CVE-2019-384x.  It does not appear that the
  backported feature, or its testcase, ever passed in Bionic on arm64.

  [other info]

  systemd bionic arm64 autopkgtests have failed forever, but we should
  fix that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870589/+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 1870811] Re: compile auto test failure, and root-unittest failure, is extremely noisy

no build failures to verify this bug with, but manually adding build
test failure shows both bionic and eoan correctly display the build test
failure summary:

bionic:

OK:   233
FAIL:   1
SKIP:  20
TIMEOUT:0


The output from the failed tests:

 50/254 test-networkFAIL 0.79 s

--- command ---
SYSTEMD_KBD_MODEL_MAP='/build/lp1870811/systemd-237/src/locale/kbd-model-map' 
SYSTEMD_LANGUAGE_FALLBACK_MAP='/build/lp1870811/systemd-237/src/locale/language-fallback-map'
 
PATH='/build/lp1870811/systemd-237/build-deb:/home/ubuntu/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin'
 /build/lp1870811/systemd-237/build-deb/test-network
--- stderr ---
Assertion '1 == 0' failed at ../src/network/test-network.c:65, function 
test_deserialize_dhcp_routes(). Aborting.
---


eoan:

Ok:  505
Expected Fail: 0
Fail:  1
Unexpected Pass:   0
Skipped:  13
Timeout:   0


The output from the failed tests:

284/519 test-networkFAIL 0.62 s (killed
by signal 6 SIGABRT)

--- command ---
SYSTEMD_KBD_MODEL_MAP='/build/lp1870811/systemd-242/src/locale/kbd-model-map' 
SYSTEMD_LANGUAGE_FALLBACK_MAP='/build/lp1870811/systemd-242/src/locale/language-fallback-map'
 
PATH='/build/lp1870811/systemd-242/build-deb:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin'
 /build/lp1870811/systemd-242/build-deb/test-network
--- stderr ---
Assertion '1 == 0' failed at ../src/network/test-network.c:49, function 
test_deserialize_dhcp_routes(). Aborting.
---


** Tags removed: verification-needed verification-needed-bionic 
verification-needed-eoan
** Tags added: verification-done verification-done-bionic verification-done-eoan

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

Title:
  compile auto test failure, and root-unittest failure, is extremely
  noisy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Eoan:
  Fix Committed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  failure in the compile-time tests (also run from the root-unittest
  autopkgtest) prints out the entire meson testlog.txt, which shows the
  output of all tests, including passed ones, not just the failed test
  output.  This makes it extremely difficult to find the output of the
  failed test(s) and creates a massive log to download.

  [test case]

  see any failed build, e.g.
  
https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz

  [regression potential]

  any regression would likely occur during test failure, likely
  resulting in lack of details of the test failure; or, a regression
  caused by the additional meson parameter could cause build failure.

  [scope]

  Xenial does not use meson, so can not be adjusted.  This is needed in
  Bionic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870811/+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 1877159] Re: netlink: 'systemd-network': attribute type 5 has an invalid length.

2020-05-06 Thread Balint Reczey

** Also affects: systemd (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  netlink: 'systemd-network': attribute type 5 has an invalid length.

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  This morning, our 2 Bionic machine configured with the wireguard's PPA
  and using systemd-networkd to configure the wireguard tunnel started
  misbehaving. Why this started just now is unclear ATM but their dmesg
  was filled with this:

  validate_nla: 100 callbacks suppressed
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.

  Folks in #systemd mentioned
  https://github.com/systemd/systemd/issues/11575 which points to 2
  commits missing from Bionic's systemd version:

  
https://github.com/systemd/systemd/commit/7d0b26a027118ca063780421cb31c74e9d2664ee
  
https://github.com/systemd/systemd/commit/624a47694cad4c87b2e807c32db656f3e9d679c5

  Focal's systemd have the above commits. Would it be possible to
  backport those 2 commits to Bionic?

  
  Additional information:

  # uname -a
  Linux noc-eu1 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  # apt-cache policy systemd wireguard{,-tools,-dkms}
  systemd:
Installed: 237-3ubuntu10.39
Candidate: 237-3ubuntu10.39
Version table:
   *** 237-3ubuntu10.39 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10.38 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  wireguard:
Installed: 1.0.20200319-1ubuntu1~18.04
Candidate: 1.0.20200319-1ubuntu1~18.04
Version table:
   *** 1.0.20200319-1ubuntu1~18.04 500
  500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main 
amd64 Packages
  500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main 
i386 Packages
  100 /var/lib/dpkg/status
  wireguard-tools:
Installed: 1.0.20200319-1ubuntu1~18.04
Candidate: 1.0.20200319-1ubuntu1~18.04
Version table:
   *** 1.0.20200319-1ubuntu1~18.04 500
  500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status
  wireguard-dkms:
Installed: 1.0.20200429-2~18.04
Candidate: 1.0.20200429-2~18.04
Version table:
   *** 1.0.20200429-2~18.04 500
  500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main 
amd64 Packages
  500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main 
i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1877159/+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 1872902] Re: Upgrade to Focal now removes chrony

I tested upgrading an lxc container with chrony installed by downloading
the tarball from http://archive.ubuntu.com/ubuntu/dists/focal-
proposed/main/dist-upgrader-all/current/ as the meta-release files have
not been updated for Focal. During the upgrade process chrony was kept
and systemd-timesyncd was not installed. Additionally, I ran 'tasksel
install standard' and 'tasksel install minimal' to ensure that no
packages in either task were removed and none were. (Although doing that
installed systemd-timesyncd.)

root@welcomed-cow:/tmp/u-r-u# head /var/log/dist-upgrade/main.log
2020-05-06 17:51:12,543 INFO Using config files '['./DistUpgrade.cfg']'
2020-05-06 17:51:12,543 INFO uname information: 'Linux welcomed-cow 
5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64'
2020-05-06 17:51:12,750 INFO apt version: '1.9.4'
2020-05-06 17:51:12,750 INFO python version: '3.7.5 (default, Apr 19 2020, 
20:18:17)
[GCC 9.2.1 20191008]'
2020-05-06 17:51:12,753 INFO release-upgrader version '20.04.19' started

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

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in germinate package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in germinate source package in Focal:
  New
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Fix Committed

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
    MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
     Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  Test Case
  -
  1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package 
chrony
  2) Run do-release-upgrade with the appropriate switches
  3) Observe that chrony is marked for deletion

  With the version of dist-upgrader from -proposed (accessed with the -p
  switch) chrony is no longer marked for deletion.

  Regression Potential
  
  Given that Dimitri's change is now ignoring the tasks minimal and standard 
(which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious 
and test desktop upgrades and ensure that packages in those tasks are not 
marked for removal.

  Regression Test
  ---
  1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system
  2) Record the list of packages marked for removal

  Compare the list of packages marked for removal with the release-
  upgrader from -proposed from Focal.

  Original Description
  
  I'd ask you to revise the dependencies that got changes in systemd 
245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as 
that was an opt-in chances are quite high people would want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1877167] Re: package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers looping, abandoned

2020-05-06 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  New

Bug description:
  upgrade from 18.04.4 to 20.04 server

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: dbus 1.12.16-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed May  6 18:02:25 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2020-05-05 (1 days ago)
  InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: dbus
  Title: package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1877167/+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 1877165] Re: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to install/upgrade: triggers looping, abandoned

2020-05-06 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to
  install/upgrade: triggers looping, abandoned

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  upgrade from 18.04.4 to 20.04 server

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed May  6 18:02:25 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2020-05-05 (1 days ago)
  InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1877165/+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 1858412] Re: systemd vacuuming does not work for remote journals

xenial:

ubuntu@lp1858412-x:~$ dpkg -l systemd|grep systemd
ii  systemd229-4ubuntu21.27 amd64system and service manager
ubuntu@lp1858412-x:~$ du -sh /var/log/journal/remote
65M /var/log/journal/remote
ubuntu@lp1858412-x:~$ sudo journalctl -D /var/log/journal/remote 
--vacuum-size=10M
ubuntu@lp1858412-x:~$ du -sh /var/log/journal/remote
65M /var/log/journal/remote


ubuntu@lp1858412-x:~$ dpkg -l systemd|grep systemd
ii  systemd229-4ubuntu21.28 amd64system and service manager
ubuntu@lp1858412-x:~$ du -sh /var/log/journal/remote
65M /var/log/journal/remote
ubuntu@lp1858412-x:~$ sudo journalctl -D /var/log/journal/remote 
--vacuum-size=10M
Deleted archived journal 
/var/log/journal/remote/system@2cd50be57af347e1a473974288f23b15-0001-0005a4fe64b79740.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@2cd50be57af347e1a473974288f23b15-047d-0005a4fe7e0e6b7b.journal
 (8.0M).
Vacuuming done, freed 16.0M of archived journals on disk.
ubuntu@lp1858412-x:~$ du -sh /var/log/journal/remote
49M /var/log/journal/remote


** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

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

Title:
  systemd vacuuming does not work for remote journals

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  attempting to vacuum journals using -D with the 'root' (in journald
  terms) journal directory fails to perform any vacuuming.  This can
  lead to journal files continually increasing in size and filling up
  the filesystem.

  [test case]

  see original description below.

  [regession potential]

  this removes a check in the code when iterating journal directories
  during vacuuming, so any regression would likely occur during
  vacuuming, possibly causing failure to vacuum.

  [scope]

  this is fixed upstream by commit
  c488660e6edb3c1375ab62514a8df035c3d712bf which is included starting in
  version 244, so this is already included in Focal.  This is needed for
  Eoan, Bionic, and Xenial.

  [original description]

  systemd has an issue in regard to vacuuming remote journals:
  https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as
  this version still has this problem.

  Steps to reproduce on "Description: Ubuntu 18.04.3 LTS":

  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/
  root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M
  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/

  Would it be possible to backport this trivial patch
  https://github.com/systemd/systemd/pull/13924 into 18.04?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+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 1877165] [NEW] package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to install/upgrade: triggers looping, abandoned

2020-05-06 Thread Carsten Roters

Public bug reported:

upgrade from 18.04.4 to 20.04 server

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3
ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
Uname: Linux 4.15.0-99-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed May  6 18:02:25 2020
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2020-05-05 (1 days ago)
InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: gdk-pixbuf
Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to 
install/upgrade: triggers looping, abandoned
UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal uec-images

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

Title:
  package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to
  install/upgrade: triggers looping, abandoned

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  upgrade from 18.04.4 to 20.04 server

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed May  6 18:02:25 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2020-05-05 (1 days ago)
  InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1877165/+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 1877167] [NEW] package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers looping, abandoned

2020-05-06 Thread Carsten Roters

Public bug reported:

upgrade from 18.04.4 to 20.04 server

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: dbus 1.12.16-2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
Uname: Linux 4.15.0-99-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed May  6 18:02:25 2020
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2020-05-05 (1 days ago)
InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2
SourcePackage: dbus
Title: package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago)

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


** Tags: amd64 apport-package focal uec-images

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

Title:
  package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

Status in dbus package in Ubuntu:
  New

Bug description:
  upgrade from 18.04.4 to 20.04 server

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: dbus 1.12.16-2ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
  Uname: Linux 4.15.0-99-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed May  6 18:02:25 2020
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2020-05-05 (1 days ago)
  InstallationMedia: Ubuntu-Server 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: dbus
  Title: package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1877167/+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 1728093] Re: [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize Devices

2020-05-06 Thread Luciano Leveroni

After many hours of tinkering around, I made the headset with microphone
to be fully recognized and working on Dell Latitude 7389! The
combination was to set pin 0x21 to "Headphones" as Jeff metioned using
hdajackretask. Then, setting the ALSA config to model "alc256-asus-mic"
adding "options snd-hda-intel model=alc256-asus-mic" to /etc/modeprobe
/alsa-base.conf. Unfortunately, this brakes the internal mic support,
which was previously working... Hope someone finds a way to make both
things work at the same time.

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

Title:
  [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize
  Devices

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh installation of Ubuntu 16.04 on a Dell Latitude 5289
  Ultrabook that has a single 3.5mm jack for both input and output. This
  installation is in a dual-boot situation with Windows 10. This device
  has UEFI secure boot enabled.

  The combo jack works perfectly in Windows 10, however, when I plug in
  a headset or headphone of any kind, it does not register that anything
  has been plugged in. The laptop is connected to a Dell dock via USB-C,
  so there is also USB Audio (Output only) available on the dock, but
  that also does not work. It worked for one session yesterday on my
  dock at work, however it does not work at my dock that I have at home.
  The internal speakers and the microphone built into the lid work fine.
  The Combo jack also does not work disconnected from the dock.

  I have installed gnome and gnome-shell, but it does not work in either
  gnome or unity (I continue to use lightdm so that I can switch back
  and forth).

  Neither Unity nor Gnome bring up any kind of "What Did You Plug In"
  dialog.

  alsamixer does not have a headphone option as expected

  pavucontrol does not allow me to select "Headphones" under the Built-
  in Audio Analog Stereo Port

  I have attempted to tweak settings in hdajackretask to no success

  I have attempted to add:

  options snd_hda_intel model=dell-headset-multi(dell-headset-dock,
  generic, auto, headset-mic, etc) to no success

  I have also tried updating my kernel to 4.13.10, to no success.

  I also tried 17.10 to no success.

  Outputs:
  --
  uname -sr
  Linux 4.10.0-37-generic
  --
  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Audio [USB Audio], device 0: USB Audio [USB Audio]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Audio [USB Audio], device 1: USB Audio [USB Audio #1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  
  cat /proc/asound/car*/co* | grep Codec
  Codec: Realtek ALC3253
  Codec: Intel Kabylake HDMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1728093/+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 1858412] Re: systemd vacuuming does not work for remote journals

bionic:


ubuntu@lp1858412-b:~$ dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.39 amd64system and service manager
ubuntu@lp1858412-b:~$ du -sh /var/log/journal/remote
417M/var/log/journal/remote
ubuntu@lp1858412-b:~$ sudo journalctl -D /var/log/journal/remote/ 
--vacuum-size=10M
ubuntu@lp1858412-b:~$ du -sh /var/log/journal/remote
417M/var/log/journal/remote


ubuntu@lp1858412-b:~$ dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.40 amd64system and service manager
ubuntu@lp1858412-b:~$ du -sh /var/log/journal/remote
417M/var/log/journal/remote
ubuntu@lp1858412-b:~$ sudo journalctl -D /var/log/journal/remote/ 
--vacuum-size=10M
Deleted archived journal 
/var/log/journal/remote//remote-127.0.0.1@5a01d9e8d4804c69a55a151a95b0313b-0001-0005a4f9330068c4.journal
 (128.0M).
Deleted archived journal 
/var/log/journal/remote//remote-127.0.0.1@5a01d9e8d4804c69a55a151a95b0313b-000267dd-0005a4f9337fd2bf.journal
 (128.0M).
Deleted archived journal 
/var/log/journal/remote//remote-127.0.0.1@5a01d9e8d4804c69a55a151a95b0313b-00046581-0005a4fa0f7fe771.journal
 (128.0M).
Vacuuming done, freed 384.0M of archived journals from /var/log/journal/remote/.
ubuntu@lp1858412-b:~$ du -sh /var/log/journal/remote
33M /var/log/journal/remote

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

Title:
  systemd vacuuming does not work for remote journals

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  attempting to vacuum journals using -D with the 'root' (in journald
  terms) journal directory fails to perform any vacuuming.  This can
  lead to journal files continually increasing in size and filling up
  the filesystem.

  [test case]

  see original description below.

  [regession potential]

  this removes a check in the code when iterating journal directories
  during vacuuming, so any regression would likely occur during
  vacuuming, possibly causing failure to vacuum.

  [scope]

  this is fixed upstream by commit
  c488660e6edb3c1375ab62514a8df035c3d712bf which is included starting in
  version 244, so this is already included in Focal.  This is needed for
  Eoan, Bionic, and Xenial.

  [original description]

  systemd has an issue in regard to vacuuming remote journals:
  https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as
  this version still has this problem.

  Steps to reproduce on "Description: Ubuntu 18.04.3 LTS":

  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/
  root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M
  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/

  Would it be possible to backport this trivial patch
  https://github.com/systemd/systemd/pull/13924 into 18.04?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+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 1858412] Re: systemd vacuuming does not work for remote journals

sorry, i missed that it was already verified for bionic

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

Title:
  systemd vacuuming does not work for remote journals

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  attempting to vacuum journals using -D with the 'root' (in journald
  terms) journal directory fails to perform any vacuuming.  This can
  lead to journal files continually increasing in size and filling up
  the filesystem.

  [test case]

  see original description below.

  [regession potential]

  this removes a check in the code when iterating journal directories
  during vacuuming, so any regression would likely occur during
  vacuuming, possibly causing failure to vacuum.

  [scope]

  this is fixed upstream by commit
  c488660e6edb3c1375ab62514a8df035c3d712bf which is included starting in
  version 244, so this is already included in Focal.  This is needed for
  Eoan, Bionic, and Xenial.

  [original description]

  systemd has an issue in regard to vacuuming remote journals:
  https://github.com/systemd/systemd/issues/2376 - this affects 18.04 as
  this version still has this problem.

  Steps to reproduce on "Description: Ubuntu 18.04.3 LTS":

  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/
  root@1:~# journalctl -D /var/log/journal/remote --vacuum-size=100M
  root@1:~# du -hs /var/log/journal/remote/
  8.6G  /var/log/journal/remote/

  Would it be possible to backport this trivial patch
  https://github.com/systemd/systemd/pull/13924 into 18.04?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858412/+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 1872902] Autopkgtest regression report (ubuntu-release-upgrader/1:20.04.19)

2020-05-06 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted ubuntu-release-upgrader (1:20.04.19) 
for focal have finished running.
The following regressions have been reported in tests triggered by the package:

update-manager/1:20.04.10 (armhf)
update-notifier/3.192.30 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#ubuntu-release-upgrader

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in germinate package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in germinate source package in Focal:
  New
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Fix Committed

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
    MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
     Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  Test Case
  -
  1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package 
chrony
  2) Run do-release-upgrade with the appropriate switches
  3) Observe that chrony is marked for deletion

  With the version of dist-upgrader from -proposed (accessed with the -p
  switch) chrony is no longer marked for deletion.

  Regression Potential
  
  Given that Dimitri's change is now ignoring the tasks minimal and standard 
(which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious 
and test desktop upgrades and ensure that packages in those tasks are not 
marked for removal.

  Regression Test
  ---
  1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system
  2) Record the list of packages marked for removal

  Compare the list of packages marked for removal with the release-
  upgrader from -proposed from Focal.

  Original Description
  
  I'd ask you to revise the dependencies that got changes in systemd 
245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as 
that was an opt-in chances are quite high people would want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all

2020-05-06 Thread bcander...@cableone.net

Just upgraded to 20.04LTS and the problem has not changed.

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

Title:
  [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at
  all

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Built-in speakers work fine. When testing headphones in sound
  settings, The sound indicator bar in Pulse-Audio moves.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 12:05:57 2019
  InstallationDate: Installed on 2019-05-16 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  root   8064 F pulseaudio
galactic  13345 F pulseaudio
   /dev/snd/pcmC0D0p:   galactic  13345 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: No sound at all
  Title: [GL703VD, Realtek ALC295, Black Headphone Out, Left] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL703VD.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL703VD
  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.:bvrGL703VD.308:bd08/15/2018:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL703VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+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 1875644] Re: motd-news complains that curl is missing

2020-05-06 Thread Launchpad Bug Tracker

This bug was fixed in the package base-files - 11ubuntu7

---
base-files (11ubuntu7) groovy; urgency=medium

  [ Simon Deziel ]
  * motd/50-motd-news: abort early if curl is missing (LP: #1875644)

 -- Andreas Hasenack   Wed, 06 May 2020 09:25:15
-0300

** Changed in: base-files (Ubuntu)
   Status: New => Fix Released

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

Title:
  motd-news complains that curl is missing

Status in base-files package in Ubuntu:
  Fix Released

Bug description:
  Description:

  motd-news complains that curl is missing on every run. motd-news.timer
  firing every ~12 hours, this useless message ends up in the logs
  regularly.

  Steps to reproduce:

  $ lxc launch images:ubuntu/focal motd
  Creating motd
  Starting motd
  $ lxc exec motd -- /etc/update-motd.d/50-motd-news --force
  dpkg-query: no packages found matching curl

  This should output nothing.

  Additional information:

  # lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  # apt-cache policy base-files
  base-files:
Installed: 11ubuntu5
Candidate: 11ubuntu5
Version table:
   *** 11ubuntu5 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/ubuntu/+source/base-files/+bug/1875644/+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 931368] Re: PCI/internal sound card seems to be detected, but is not available

2020-05-06 Thread Bjorn Helgaas

This issue should be resolved by
https://git.kernel.org/linus/1dace0116d0b, which appeared in v4.2.  If
the kernel contains that commit, the "pci=use_crs" boot parameter should
not be needed.

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

Title:
  PCI/internal sound card seems to be detected, but is not available

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  In my PC is a VT8237A/VT8251 HDA Controller from VIA Technologies, Inc.
  When I open the sound preferences, I only see a dummy output.
  I tried a lot of commands to figure out the pronblem. It seems that the PCI 
sound controller is found.
  Somehow it is not recognized as an audio device.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic i686
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 2012-02-13 11:37 seq
   crw-rw+ 1 root audio 116, 33 2012-02-13 11:37 timer
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices: aplay: device_list:240: no soundcards found...
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  ArecordDevices: arecord: device_list:240: no soundcards found...
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Mon Feb 13 12:04:02 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: K8M890-8237A
  dmi.board.vendor: Foxconn
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/23/2007:svnFoxconn:pnOEM:pvr:rvnFoxconn:rnK8M890-8237A:rvr:cvnOEM:ct3:cvr:
  dmi.product.name: OEM
  dmi.sys.vendor: Foxconn

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/931368/+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 1877159] [NEW] netlink: 'systemd-network': attribute type 5 has an invalid length.

2020-05-06 Thread Simon Déziel

Public bug reported:

This morning, our 2 Bionic machine configured with the wireguard's PPA
and using systemd-networkd to configure the wireguard tunnel started
misbehaving. Why this started just now is unclear ATM but their dmesg
was filled with this:

validate_nla: 100 callbacks suppressed
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.
netlink: 'systemd-network': attribute type 5 has an invalid length.

Folks in #systemd mentioned
https://github.com/systemd/systemd/issues/11575 which points to 2
commits missing from Bionic's systemd version:

https://github.com/systemd/systemd/commit/7d0b26a027118ca063780421cb31c74e9d2664ee
https://github.com/systemd/systemd/commit/624a47694cad4c87b2e807c32db656f3e9d679c5

Focal's systemd have the above commits. Would it be possible to backport
those 2 commits to Bionic?


Additional information:

# uname -a
Linux noc-eu1 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

# apt-cache policy systemd wireguard{,-tools,-dkms}
systemd:
  Installed: 237-3ubuntu10.39
  Candidate: 237-3ubuntu10.39
  Version table:
 *** 237-3ubuntu10.39 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 237-3ubuntu10.38 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 237-3ubuntu10 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
wireguard:
  Installed: 1.0.20200319-1ubuntu1~18.04
  Candidate: 1.0.20200319-1ubuntu1~18.04
  Version table:
 *** 1.0.20200319-1ubuntu1~18.04 500
500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main 
amd64 Packages
500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main 
i386 Packages
100 /var/lib/dpkg/status
wireguard-tools:
  Installed: 1.0.20200319-1ubuntu1~18.04
  Candidate: 1.0.20200319-1ubuntu1~18.04
  Version table:
 *** 1.0.20200319-1ubuntu1~18.04 500
500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main 
amd64 Packages
100 /var/lib/dpkg/status
wireguard-dkms:
  Installed: 1.0.20200429-2~18.04
  Candidate: 1.0.20200429-2~18.04
  Version table:
 *** 1.0.20200429-2~18.04 500
500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main 
amd64 Packages
500 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main 
i386 Packages
100 /var/lib/dpkg/status

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

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

Title:
  netlink: 'systemd-network': attribute type 5 has an invalid length.

Status in systemd package in Ubuntu:
  New

Bug description:
  This morning, our 2 Bionic machine configured with the wireguard's PPA
  and using systemd-networkd to configure the wireguard tunnel started
  misbehaving. Why this started just now is unclear ATM but their dmesg
  was filled with this:

  validate_nla: 100 callbacks suppressed
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.
  netlink: 'systemd-network': attribute type 5 has an invalid length.

  Folks in #systemd mentioned
  https://github.com/systemd/systemd/issues/11575 which points to 2
  commits missing from Bionic's systemd version:

  
https://github.com/systemd/systemd/commit/7d0b26a027118ca063780421cb31c74e9d2664ee
  
https://github.com/systemd/systemd/commit/624a47694cad4c87b2e807c32db656f3e9d679c5

  Focal's systemd have the above commits. Would it be possible to
  backport those 2 commits to Bionic?

  
  Additional information:

  # uname -a
  Linux noc-eu1 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  # apt-cache policy systemd

[Touch-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages

2020-05-06 Thread Ken VanDine

** Description changed:

- When you download a DEB file within 20.04 Ubuntu Beta and you double
- click it the file is opened by the archive manager.  I would expect the
- installer to open the file just like in previous versions of Ubuntu.
+ [Impact]
+ 
+  * When a deb is downloaded the default handler is not capable of
+ installing on 20.04.
+ 
+ [Test Case]
+ 
+  We should perform this test on Ubuntu 20.04 as well as some flavors to
+ ensure we do not regress.
+ 
+  * Download any deb in firefox, double click on the downloaded file
+- On Ubuntu this should open "Ubuntu Software"
+- On flavors it should open whatever their default app for handling debs is
+ 
+ [Regression Potential]
+ 
+  * For Ubuntu, very low, rarely would a user expect to open a deb with
+ file-roller
+ 
+  * Other flavors of ubuntu are overriding this default and should not be
+ affected.  We do need to test this on other flavors to ensure their
+ defaults are still honored.

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

Title:
  Deb Files are not associated with an application that manages packages

Status in desktop-file-utils package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Invalid
Status in desktop-file-utils source package in Focal:
  Confirmed
Status in gdebi source package in Focal:
  Invalid

Bug description:
  [Impact]

   * When a deb is downloaded the default handler is not capable of
  installing on 20.04.

  [Test Case]

   We should perform this test on Ubuntu 20.04 as well as some flavors
  to ensure we do not regress.

   * Download any deb in firefox, double click on the downloaded file
 - On Ubuntu this should open "Ubuntu Software"
 - On flavors it should open whatever their default app for handling debs is

  [Regression Potential]

   * For Ubuntu, very low, rarely would a user expect to open a deb with
  file-roller

   * Other flavors of ubuntu are overriding this default and should not
  be affected.  We do need to test this on other flavors to ensure their
  defaults are still honored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+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 1877154] [NEW] [Nvidia HDMI] After suspend to ram sound output device changes from HDMI to S/PDIF

2020-05-06 Thread Jaroslaw Ilgiewicz

Public bug reported:

After suspend to RAM sound device changes from default HDMI to S/PDIF. After 
changing it again to HDMI right speaker stops to respond. I can hear only the 
sound from left speaker during sound test from the settings menu.
After the first wake from suspend you can find in messages from dmesg:
[   68.362807] pcieport :00:01.3: PME: Spurious native interrupt!
[   68.527845] nvme nvme0: 15/0/0 default/read/poll queues
[   68.533836] snd_hda_intel :0a:00.1: spurious response 0x8000:0x0, 
last cmd=0x6f2f03

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jaroslaw   2972 F pulseaudio
 /dev/snd/controlC1:  jaroslaw   2972 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May  6 18:32:10 2020
InstallationDate: Installed on 2020-05-03 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_Type: None of the above
Title: [AB350N-Gaming WIFI, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F50a
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug focal

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

Title:
  [Nvidia HDMI] After suspend to ram sound output device changes from
  HDMI to S/PDIF

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After suspend to RAM sound device changes from default HDMI to S/PDIF. After 
changing it again to HDMI right speaker stops to respond. I can hear only the 
sound from left speaker during sound test from the settings menu.
  After the first wake from suspend you can find in messages from dmesg:
  [   68.362807] pcieport :00:01.3: PME: Spurious native interrupt!
  [   68.527845] nvme nvme0: 15/0/0 default/read/poll queues
  [   68.533836] snd_hda_intel :0a:00.1: spurious response 0x8000:0x0, 
last cmd=0x6f2f03

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaroslaw   2972 F pulseaudio
   /dev/snd/controlC1:  jaroslaw   2972 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 18:32:10 2020
  InstallationDate: Installed on 2020-05-03 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [AB350N-Gaming WIFI, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] 
Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F50a
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350N-Gaming WIFI-CF

[Touch-packages] [Bug 1877129] Re: jackd won't run in realtime

2020-05-06 Thread Igor Sakulin

Please see attached systemd log

** Attachment added: "jrn"
   
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1877129/+attachment/5367437/+files/jrn

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

Title:
  jackd won't run in realtime

Status in jackd2 package in Ubuntu:
  Incomplete

Bug description:
  Was using jackd2 for ages, never had this issue. The usual limits.conf
  tweaks are present. Jackd won't run in realtime even as root. It's
  very easy to reproduce in Focal.

  Before upgrade, was working:
  Ubuntu 18.04.4 LTS
  uname -r
  kernel 5.3.0-51-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  After upgrade:
  Ubuntu 20.04 LTS
  uname -r
  5.4.0-29-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  
  Simple test:
  jackd -R -d dummy -r192000 -p2048

  jackdmp 1.9.12
  Copyright 2001-2005 Paul Davis and others.
  Copyright 2004-2016 Grame.
  Copyright 2016-2017 Filipe Coelho.
  jackdmp comes with ABSOLUTELY NO WARRANTY
  This is free software, and you are welcome to redistribute it
  under certain conditions; see the file COPYING for details
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  JACK server starting in realtime mode with priority 10
  self-connect-mode is "Don't restrict self connect requests"
  Cannot use real-time scheduling (RR/10)(1: Operation not permitted)
  AcquireSelfRealTime error

  I'm guessing that it's not jack itself (package ver. seems to be the
  same as bionic, without new feats), smth is missing in the kernel
  config. I would try RT kernel, but it usually does not boot at all
  thanks to Nvidia blob on that system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1877129/+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 1728093] Re: [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize Devices

2020-05-06 Thread Luciano Leveroni

I can confirm this still occurs in Ubuntu 20.04 on my Dell Latitude 7389 (also 
using ALC3253). 
On a fresh install, the audio jack does not even recognize when a headset is 
connected at all. After following Jeff Conner suggestion on comment #5, it now 
recognizes them and sound output works as expected. However, mic of the headset 
is NOT working. I've tried a lot of combinations on hdajackretask 
unsucessfully. This is really a big issue for me, as headset usage is important 
on my daily work. I'm willing to help debbuging or anything to help make it 
work.

Thank you!

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

Title:
  [16.04, ALC3253] Dell Latitude 5289 Combo Jack Does Not Recognize
  Devices

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a fresh installation of Ubuntu 16.04 on a Dell Latitude 5289
  Ultrabook that has a single 3.5mm jack for both input and output. This
  installation is in a dual-boot situation with Windows 10. This device
  has UEFI secure boot enabled.

  The combo jack works perfectly in Windows 10, however, when I plug in
  a headset or headphone of any kind, it does not register that anything
  has been plugged in. The laptop is connected to a Dell dock via USB-C,
  so there is also USB Audio (Output only) available on the dock, but
  that also does not work. It worked for one session yesterday on my
  dock at work, however it does not work at my dock that I have at home.
  The internal speakers and the microphone built into the lid work fine.
  The Combo jack also does not work disconnected from the dock.

  I have installed gnome and gnome-shell, but it does not work in either
  gnome or unity (I continue to use lightdm so that I can switch back
  and forth).

  Neither Unity nor Gnome bring up any kind of "What Did You Plug In"
  dialog.

  alsamixer does not have a headphone option as expected

  pavucontrol does not allow me to select "Headphones" under the Built-
  in Audio Analog Stereo Port

  I have attempted to tweak settings in hdajackretask to no success

  I have attempted to add:

  options snd_hda_intel model=dell-headset-multi(dell-headset-dock,
  generic, auto, headset-mic, etc) to no success

  I have also tried updating my kernel to 4.13.10, to no success.

  I also tried 17.10 to no success.

  Outputs:
  --
  uname -sr
  Linux 4.10.0-37-generic
  --
  aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Audio [USB Audio], device 0: USB Audio [USB Audio]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  card 1: Audio [USB Audio], device 1: USB Audio [USB Audio #1]
    Subdevices: 1/1
    Subdevice #0: subdevice #0
  
  cat /proc/asound/car*/co* | grep Codec
  Codec: Realtek ALC3253
  Codec: Intel Kabylake HDMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1728093/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

2020-05-06 Thread Kai Groner

Enabling, but not configuring CONFIG_RT_GROUP_SCHED seems likely to be the 
cause of this:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=master-next=9b039fc517876d312e7fa0955571101a299c91f5

Some discussion of this WRT lowlatency kernel is here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in rtkit package in Ubuntu:
  Confirmed

Bug description:
  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1876670] Re: nfs does not mount at boot with bridge

2020-05-06 Thread Jonathan Van den Broeck

Same probleme with the modification you suggest.

root@bowser:~# cat /etc/systemd/system/mnt-nas.mount
[Unit]
Description=NAS devices
After=network-online.target

[Mount]
What=192.168.1.20:/volume2/media
Where=/mnt/nas
Type=nfs
Options=_netdev,auto

[Install]
WantedBy=multi-user.target
root@bowser:~# systemctl status mnt-nas.mount

● mnt-nas.mount - NAS devices
 Loaded: loaded (/etc/systemd/system/mnt-nas.mount; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Wed 2020-05-06 17:35:46 CEST; 
4min 59s ago
  Where: /mnt/nas
   What: 192.168.1.20:/volume2/media

May 06 17:35:45 bowser systemd[1]: Mounting NAS devices...
May 06 17:35:46 bowser mount[751]: mount.nfs: Network is unreachable
May 06 17:35:46 bowser systemd[1]: mnt-nas.mount: Mount process exited, 
code=exited, status=32/n/a
May 06 17:35:46 bowser systemd[1]: mnt-nas.mount: Failed with result 
'exit-code'.
May 06 17:35:46 bowser systemd[1]: Failed to mount NAS devices.

I also have done some more test. I only have this problem on a bare
metal installation (Lenovo M720q). If I do the same configuration on a
virtual machine, I do not have the problem. I do not have the problem
with a fedora server installation on bare metal.

I do not have enough knowledge to troubleshoot this problem but I am
fully available if you have some commands you want me to try.

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

Title:
  nfs does not mount at boot with bridge

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I am running a Ubuntu 20.04 server with lxd and kvm/qemu. 
  I try to connect a nfs share at boot. It is working while I do not configure 
any bridge with netplan. I am creating directly a systemd service for the NFS 
mount but I have the same problem if I edit the fstab file.

  #/etc/systemd/system/mnt-nas.mount
  [Unit]
  Description=NAS devices
  After=network.target

  [Mount]
  What=192.168.1.20:/volume2/media
  Where=/mnt/nas
  Type=nfs
  Options=_netdev,auto

  [Install]
  WantedBy=multi-user.target

  ## TEST WITHOUT BRIDGE

  #/etc/netplan/01-netcfg.yaml 
  network:
version: 2
renderer: networkd
ethernets:
  eno1:
dhcp4: yes

  root@bowser:~# ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default 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: eno1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether f8:75:a4:00:be:ad brd ff:ff:ff:ff:ff:ff
  inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic eno1
 valid_lft 86244sec preferred_lft 86244sec
  inet6 fe80::fa75:a4ff:fe00:bead/64 scope link 
 valid_lft forever preferred_lft forever
  3: wlp1s0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 60:f2:62:38:d7:c2 brd ff:ff:ff:ff:ff:ff

  root@bowser:~# journalctl -b
  ...
  May 04 08:58:08 bowser systemd-networkd[535]: eno1: Gained carrier
  May 04 08:58:08 bowser kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: None
  May 04 08:58:08 bowser kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link 
becomes ready
  May 04 08:58:08 bowser systemd[1]: systemd-rfkill.service: Succeeded.
  May 04 08:58:08 bowser set-cpufreq[795]: Setting powersave scheduler for all 
CPUs
  May 04 08:58:08 bowser systemd[1]: ondemand.service: Succeeded.
  May 04 08:58:08 bowser systemd[1]: dmesg.service: Succeeded.
  May 04 08:58:09 bowser systemd-networkd[535]: eno1: Gained IPv6LL
  May 04 08:58:09 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-networkd[535]: eno1: DHCPv4 address 
192.168.1.100/24 via 192.168.1.1
  May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-networkd-wait-online[611]: managing: eno1
  May 04 08:58:10 bowser systemd[1]: Finished Wait for Network to be Configured.
  May 04 08:58:10 bowser systemd[1]: Reached target Network is Online.
  May 04 08:58:10 bowser systemd[1]: Condition check resulted in Login to 
default iSCSI targets being skipped.
  May 04 08:58:10 bowser systemd[1]: Reached target Remote File Systems (Pre).
  May 04 08:58:10 bowser systemd[1]: Mounting NAS devices...
  May 04 08:58:10 bowser systemd[1]: Starting Availability of block devices...
  May 04 08:58:10 bowser systemd[1]: Condition check resulted in Pollinate to 
seed the

[Touch-packages] [Bug 1858412] Re: systemd vacuuming does not work for remote journals

eoan:

ubuntu@lp1858412-e:~$ dpkg -l systemd|grep systemd
ii  systemd242-7ubuntu3.7 amd64system and service manager
ubuntu@lp1858412-e:~$ du -sh /var/log/journal/remote
273M/var/log/journal/remote
ubuntu@lp1858412-e:~$ sudo journalctl -D /var/log/journal/remote 
--vacuum-size=10M
ubuntu@lp1858412-e:~$ du -sh /var/log/journal/remote
273M/var/log/journal/remote


ubuntu@lp1858412-e:~$ dpkg -l systemd|grep systemd
ii  systemd242-7ubuntu3.8 amd64system and service manager
ubuntu@lp1858412-e:~$ du -sh /var/log/journal/remote
273M/var/log/journal/remote
ubuntu@lp1858412-e:~$ sudo journalctl -D /var/log/journal/remote 
--vacuum-size=10M
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-0001-0005a4f93261040f.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/user-1000@63c462cb3bfe42d8aae1a91b4d2711a6-0435-0005a4f935a960b5.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-13e8-0005a4fb05e4c7ef.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-13ec-0005a4fb092ed6af.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/user-1000@63c462cb3bfe42d8aae1a91b4d2711a6-14fe-0005a4fb271141e0.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1941-0005a4fb29d41b99.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/user-1000@63c462cb3bfe42d8aae1a91b4d2711a6-1993-0005a4fbc19b8de5.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1ca3-0005a4fbc267c680.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1dd8-0005a4fbc464346b.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/user-1000@0110cef9e4a8457ba44cf2e309034570-1de1-0005a4fbc5523608.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1df2-0005a4fbc93c71d7.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1df4-0005a4fbf7e6a339.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1df7-0005a4fc2dbe7958.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1dfe-0005a4fc2f8efc30.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1dff-0005a4fc4181be1d.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1e02-0005a4fc7bce3298.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1e06-0005a4fc7dddc828.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1e09-0005a4fc91a3f7ed.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1e10-0005a4fc9373a53e.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1e11-0005a4fca1309488.journal
 (8.0M).
Deleted archived journal 
/var/log/journal/remote/system@106304fba7e24f4eaa633c524dee66e4-1e6e-0005a4fca379da83.journal
 (8.0M).
Vacuuming done, freed 168.0M of archived journals from /var/log/journal/remote.
ubuntu@lp1858412-e:~$ du -sh /var/log/journal/remote
105M/var/log/journal/remote



** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  systemd vacuuming does not work for remote journals

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  attempting to vacuum journals using -D with the 'root' (in journald
  terms) journal directory fails to perform any vacuuming.  This can
  lead to journal files continually increasing in size and filling up
  the filesystem.

  [test case]

  see original description below.

  [regession potential]

  this removes a check in the code when iterating journal directories
  during vacuuming, so any regression would likely occur during
  vacuuming, possibly causing failure to vacuum.

  [scope]

  this is fixed upstream by commit

[Touch-packages] [Bug 1872902] Re: Upgrade to Focal now removes chrony

2020-05-06 Thread Łukasz Zemczak

Hello Christian, or anyone else affected,

Accepted ubuntu-release-upgrader into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:20.04.19 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-release-upgrader (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-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/1872902

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in germinate package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in germinate source package in Focal:
  New
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Fix Committed

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
    MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
     Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  Test Case
  -
  1) On a system running Ubuntu 19.10 or Ubuntu 18.04 LTS install the package 
chrony
  2) Run do-release-upgrade with the appropriate switches
  3) Observe that chrony is marked for deletion

  With the version of dist-upgrader from -proposed (accessed with the -p
  switch) chrony is no longer marked for deletion.

  Regression Potential
  
  Given that Dimitri's change is now ignoring the tasks minimal and standard 
(which are handled by _keepBaseMetaPkgsInstalled) we should still be cautious 
and test desktop upgrades and ensure that packages in those tasks are not 
marked for removal.

  Regression Test
  ---
  1) Run do-release-upgrade on an Ubuntu 19.10 or Ubuntu 18.04 LTS system
  2) Record the list of packages marked for removal

  Compare the list of packages marked for removal with the release-
  upgrader from -proposed from Focal.

  Original Description
  
  I'd ask you to revise the dependencies that got changes in systemd 
245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays installed as 
that was an opt-in chances are quite high people would want to keep it that way.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872902/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

Could you add a 'journalctl -b 0' log from a session having the issue?

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

Title:
  rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted
  after upgrade to 20.04

Status in rtkit package in Ubuntu:
  Confirmed

Bug description:
  These errors started right after upgrading to 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: rtkit 0.12-4
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 10:31:43 2020
  InstallationDate: Installed on 2019-06-18 (315 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rtkit
  UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1875665/+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 1877129] Re: jackd won't run in realtime

Thank you for your bug report, bug #1875665 has similar warnings

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

Title:
  jackd won't run in realtime

Status in jackd2 package in Ubuntu:
  Incomplete

Bug description:
  Was using jackd2 for ages, never had this issue. The usual limits.conf
  tweaks are present. Jackd won't run in realtime even as root. It's
  very easy to reproduce in Focal.

  Before upgrade, was working:
  Ubuntu 18.04.4 LTS
  uname -r
  kernel 5.3.0-51-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  After upgrade:
  Ubuntu 20.04 LTS
  uname -r
  5.4.0-29-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  
  Simple test:
  jackd -R -d dummy -r192000 -p2048

  jackdmp 1.9.12
  Copyright 2001-2005 Paul Davis and others.
  Copyright 2004-2016 Grame.
  Copyright 2016-2017 Filipe Coelho.
  jackdmp comes with ABSOLUTELY NO WARRANTY
  This is free software, and you are welcome to redistribute it
  under certain conditions; see the file COPYING for details
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  JACK server starting in realtime mode with priority 10
  self-connect-mode is "Don't restrict self connect requests"
  Cannot use real-time scheduling (RR/10)(1: Operation not permitted)
  AcquireSelfRealTime error

  I'm guessing that it's not jack itself (package ver. seems to be the
  same as bionic, without new feats), smth is missing in the kernel
  config. I would try RT kernel, but it usually does not boot at all
  thanks to Nvidia blob on that system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1877129/+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 1877129] Re: jackd won't run in realtime

Could you add a 'journalctl -b 0' log from a session having the issue?

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

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

Title:
  jackd won't run in realtime

Status in jackd2 package in Ubuntu:
  Incomplete

Bug description:
  Was using jackd2 for ages, never had this issue. The usual limits.conf
  tweaks are present. Jackd won't run in realtime even as root. It's
  very easy to reproduce in Focal.

  Before upgrade, was working:
  Ubuntu 18.04.4 LTS
  uname -r
  kernel 5.3.0-51-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  After upgrade:
  Ubuntu 20.04 LTS
  uname -r
  5.4.0-29-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  
  Simple test:
  jackd -R -d dummy -r192000 -p2048

  jackdmp 1.9.12
  Copyright 2001-2005 Paul Davis and others.
  Copyright 2004-2016 Grame.
  Copyright 2016-2017 Filipe Coelho.
  jackdmp comes with ABSOLUTELY NO WARRANTY
  This is free software, and you are welcome to redistribute it
  under certain conditions; see the file COPYING for details
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  JACK server starting in realtime mode with priority 10
  self-connect-mode is "Don't restrict self connect requests"
  Cannot use real-time scheduling (RR/10)(1: Operation not permitted)
  AcquireSelfRealTime error

  I'm guessing that it's not jack itself (package ver. seems to be the
  same as bionic, without new feats), smth is missing in the kernel
  config. I would try RT kernel, but it usually does not boot at all
  thanks to Nvidia blob on that system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1877129/+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 1876915] Re: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade: installed cups-daemon package post-installation script subprocess returned error exit status 1

2020-05-06 Thread Matthew Kuler

No i have not changed anything i just pulled my laptop out of sleep mode
and i got the error

On Wed, May 6, 2020 at 4:02 AM Sebastien Bacher 
wrote:

> Thank you for your bug report, the log has
>
> Failed to restart cups.service: Unit -.mount is masked.
>
> Did you do any change to the cups system service?
>
> ** Changed in: cups (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1876915
>
> Title:
>   package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade:
>   installed cups-daemon package post-installation script subprocess
>   returned error exit status 1
>
> Status in cups package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Im not sure what caused this problem
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 19.10
>   Package: cups-daemon 2.2.12-2ubuntu1.1
>   ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
>   Uname: Linux 5.3.0-46-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu8.8
>   Architecture: amd64
>   Date: Sat May  2 11:27:39 2020
>   DpkgHistoryLog:
>Start-Date: 2020-05-02  11:27:19
>Commandline: /usr/bin/unattended-upgrade
>Upgrade: libcups2:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1),
> libcups2:i386 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1),
> cups-server-common:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1),
> cups-common:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-bsd:amd64
> (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-core-drivers:amd64
> (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-daemon:amd64 (2.2.12-2ubuntu1,
> 2.2.12-2ubuntu1.1), libcupsimage2:amd64 (2.2.12-2ubuntu1,
> 2.2.12-2ubuntu1.1), cups:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1),
> cups-client:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1),
> cups-ipp-utils:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1)
>   ErrorMessage: installed cups-daemon package post-installation script
> subprocess returned error exit status 1
>   InstallationDate: Installed on 2020-03-30 (35 days ago)
>   InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
>   Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat:
> No destinations added.
>   MachineType: ASUSTeK COMPUTER INC. Q500A
>   Papersize: letter
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
> root=UUID=d1314bd9-a342-4a79-ba05-fd27f747bc14 ro quiet splash vt.handoff=7
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
> root=UUID=d1314bd9-a342-4a79-ba05-fd27f747bc14 ro quiet splash vt.handoff=7
>   Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal,
> 3.7.5-1
>   PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal,
> 2.7.17-1
>   RelatedPackageVersions:
>dpkg 1.19.7ubuntu2
>apt  1.9.4
>   SourcePackage: cups
>   Title: package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade:
> installed cups-daemon package post-installation script subprocess returned
> error exit status 1
>   UpgradeStatus: Upgraded to eoan on 2020-04-02 (32 days ago)
>   dmi.bios.date: 08/17/2012
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: Q500A.205
>   dmi.board.asset.tag: ATN12345678901234567
>   dmi.board.name: Q500A
>   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.:bvrQ500A.205:bd08/17/2012:svnASUSTeKCOMPUTERINC.:pnQ500A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ500A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
>   dmi.product.family: Q
>   dmi.product.name: Q500A
>   dmi.product.sku: ASUS-NotebookSKU
>   dmi.product.version: 1.0
>   dmi.sys.vendor: ASUSTeK COMPUTER INC.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1876915/+subscriptions
>

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

Title:
  package cups-daemon 2.2.12-2ubuntu1.1 failed to install/upgrade:
  installed cups-daemon package post-installation script subprocess
  returned error exit status 1

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Im not sure what caused this problem

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: cups-daemon 2.2.12-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Sat May  2 11:27:39 2020
  DpkgHistoryLog:
   Start-Date: 2020-05-02  11:27:19
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: libcups2:amd64 (2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), libcups2:i386 
(2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-server-common:amd64 
(2.2.12-2ubuntu1, 2.2.12-2ubuntu1.1), cups-common:amd64 (2.2.12-2ubuntu1,

[Touch-packages] [Bug 1876886] Re: chrony autopkgtest fails on armhf (groovy)

I have restarted it again on LP in case it was a flaky network after
all.

At the same time I have added some debug statements and prepare a bileto
ticket to run the tests there as well.

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

Title:
  chrony autopkgtest fails on armhf (groovy)

Status in chrony package in Ubuntu:
  New
Status in libcap2 package in Ubuntu:
  Confirmed

Bug description:
  Test fails on armhf only:
running chronyc makestepERROR
checking chronyc output OK
running chronyc trimrtc ERROR
checking chronyc output OK
running chronyc writertcERROR

  This might be a new twist on 
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1863590
  as it is libcap2 again.

  This reproduces through a bunch of retries
  http://autopkgtest.ubuntu.com/packages/c/chrony/groovy/armhf
  But as I said is armfh only:
  http://autopkgtest.ubuntu.com/packages/chrony

  Flagging update-excuse, but I won't be able to get to it immediately
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+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 1203235] Re: [H87N-WIFI, Realtek ALC892, Green Line Out, Rear] Underruns, dropouts or crackling sound

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [H87N-WIFI, Realtek ALC892, Green Line Out, Rear] Underruns, dropouts
  or crackling sound

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Out of the box, ubuntu has intermittent crackling sounds on this
  hardware. I've tried turning off other sound devices, switching fully
  to ALSA, tweaking config files with stuff described here:
  https://wiki.ubuntu.com/Audio/PositionReporting and various other
  things. Nothing seems to alleviate the issues of crackling sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2
  Uname: Linux 3.8.0-26-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  brian  1732 F pulseaudio
   /dev/snd/controlC1:  brian  1732 F pulseaudio
   /dev/snd/controlC0:  brian  1732 F pulseaudio
  Date: Fri Jul 19 23:22:05 2013
  InstallationDate: Installed on 2013-07-15 (4 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [H87N-WIFI, Realtek ALC892, Green Line Out, Rear] Underruns, dropouts 
or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/07/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H87N-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd05/07/2013:svnGigabyteTechnologyCo.,Ltd.:pnH87N-WIFI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: H87N-WIFI
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1203235/+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 1877129] [NEW] jackd won't run in realtime

2020-05-06 Thread Igor Sakulin

Public bug reported:

Was using jackd2 for ages, never had this issue. The usual limits.conf
tweaks are present. Jackd won't run in realtime even as root. It's very
easy to reproduce in Focal.

Before upgrade, was working:
Ubuntu 18.04.4 LTS
uname -r
kernel 5.3.0-51-generic
jackd --version
jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

After upgrade:
Ubuntu 20.04 LTS
uname -r
5.4.0-29-generic
jackd --version
jackdmp version 1.9.12 tmpdir /dev/shm protocol 8


Simple test:
jackd -R -d dummy -r192000 -p2048

jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
Cannot use real-time scheduling (RR/10)(1: Operation not permitted)
AcquireSelfRealTime error

I'm guessing that it's not jack itself (package ver. seems to be the
same as bionic, without new feats), smth is missing in the kernel
config. I would try RT kernel, but it usually does not boot at all
thanks to Nvidia blob on that system.

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

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

Title:
  jackd won't run in realtime

Status in jackd2 package in Ubuntu:
  New

Bug description:
  Was using jackd2 for ages, never had this issue. The usual limits.conf
  tweaks are present. Jackd won't run in realtime even as root. It's
  very easy to reproduce in Focal.

  Before upgrade, was working:
  Ubuntu 18.04.4 LTS
  uname -r
  kernel 5.3.0-51-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  After upgrade:
  Ubuntu 20.04 LTS
  uname -r
  5.4.0-29-generic
  jackd --version
  jackdmp version 1.9.12 tmpdir /dev/shm protocol 8

  
  Simple test:
  jackd -R -d dummy -r192000 -p2048

  jackdmp 1.9.12
  Copyright 2001-2005 Paul Davis and others.
  Copyright 2004-2016 Grame.
  Copyright 2016-2017 Filipe Coelho.
  jackdmp comes with ABSOLUTELY NO WARRANTY
  This is free software, and you are welcome to redistribute it
  under certain conditions; see the file COPYING for details
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  Cannot create RT messagebuffer thread: Operation not permitted (1)
  Retrying messagebuffer thread without RT scheduling
  Messagebuffer not realtime; consider enabling RT scheduling for user
  no message buffer overruns
  JACK server starting in realtime mode with priority 10
  self-connect-mode is "Don't restrict self connect requests"
  Cannot use real-time scheduling (RR/10)(1: Operation not permitted)
  AcquireSelfRealTime error

  I'm guessing that it's not jack itself (package ver. seems to be the
  same as bionic, without new feats), smth is missing in the kernel
  config. I would try RT kernel, but it usually does not boot at all
  thanks to Nvidia blob on that system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1877129/+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 1224099] Re: [Satellite P200, Realtek ALC268, Black Headphone Out, Front] No sound at all

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [Satellite P200, Realtek ALC268, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  front headphones work perfect in ubuntu 12.04 LTS. after a fresh
  instllation of 13.04 - no sound comming out of headphones only front
  speakers are working.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ilan   4270 F pulseaudio
ilan   6673 F pulseaudio
   /dev/snd/controlC0:  ilan   4270 F pulseaudio
ilan   6673 F pulseaudio
  Date: Wed Sep 11 23:12:43 2013
  InstallationDate: Installed on 2013-09-11 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ilan   4270 F pulseaudio
ilan   6673 F pulseaudio
   /dev/snd/controlC0:  ilan   4270 F pulseaudio
ilan   6673 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [Satellite P200, Realtek ALC268, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2007
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.90
  dmi.board.name: ISRAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.90:bd10/23/2007:svnTOSHIBA:pnSatelliteP200:pvrPSPB6E-10M04NEN:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: Satellite P200
  dmi.product.version: PSPB6E-10M04NEN
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1224099/+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 1168206] Re: UnicodeDecodeError raised from attach_hardware()

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

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

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

Title:
  UnicodeDecodeError raised from attach_hardware()

Status in apport package in Ubuntu:
  Invalid
Status in xdiagnose package in Ubuntu:
  Fix Released

Bug description:
  As seen on bugs #1164623 and #1162151:

  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in 
_run_hook
  symb['add_info'](report, ui)
    File "/usr/share/apport/package-hooks/source_xserver-xorg-video-intel.py", 
line 660, in add_info
  attach_hardware(report)
    File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 246, in 
attach_hardware
  attach_dmi(report)
    File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 201, in 
attach_dmi
  value = fd.read().strip()
    File "/usr/lib/python3.3/codecs.py", line 300, in decode
  (result, consumed) = self._buffer_decode(data, self.errors, final)
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xff in position 0: 
invalid start byte

  attach_dmi() is an apport call.  The dmi info's sometimes useful but
  not crucial to have in X bug reports, so if it's erroring we can
  safely skip its inclusion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1168206/+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 1876886] Re: chrony autopkgtest fails on armhf (groovy)

Ha, that was a good red-herring

It doesn't fail at this test despite all the error messages thrown out.
It does
1. build chrony without root (works with tests skipped as it isn't root)
2. passes other tests as it ERRORs but detects that the environment is the 
reason for that

The actual error is:
autopkgtest [15:12:44]: test upstream-simulation-test-suite: 
[---
make: Entering directory '/tmp/autopkgtest.VV9dfn/autopkgtest_tmp'
make: *** No targets specified and no makefile found.  Stop.
make: Leaving directory '/tmp/autopkgtest.VV9dfn/autopkgtest_tmp'
autopkgtest [15:12:56]: test upstream-simulation-test-suite: 
---]

Which in the past was:
autopkgtest [15:59:37]: test upstream-simulation-test-suite: 
[---
make: Entering directory '/tmp/autopkgtest.msuU3S/autopkgtest_tmp'
cc -O2 -Wall -g -fPIC -DGETTIMEOFDAY_VOID  -c -o client.o client.c
cc -O2 -Wall -g -fPIC -shared -o clknetsim.so client.o  -ldl -lm

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

Title:
  chrony autopkgtest fails on armhf (groovy)

Status in chrony package in Ubuntu:
  New
Status in libcap2 package in Ubuntu:
  Confirmed

Bug description:
  Test fails on armhf only:
running chronyc makestepERROR
checking chronyc output OK
running chronyc trimrtc ERROR
checking chronyc output OK
running chronyc writertcERROR

  This might be a new twist on 
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1863590
  as it is libcap2 again.

  This reproduces through a bunch of retries
  http://autopkgtest.ubuntu.com/packages/c/chrony/groovy/armhf
  But as I said is armfh only:
  http://autopkgtest.ubuntu.com/packages/chrony

  Flagging update-excuse, but I won't be able to get to it immediately
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+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 581773] Re: snd-virmidi should by default blocked to become default card

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  snd-virmidi should by default blocked to become default card

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: alsa-base

  loading snd-virmidi with the default settings can lead to lots of audio 
trouble as it can become the default card (index 0).
  It is very unlikely that anyone ever wants the virtual midi device as card 0.
  I recommend adding the following line to /etc/modprobe.d/alsa-base.conf to 
prevent this to happen:

  # Keep snd-virmidi from being loaded as first soundcard
  options snd-virmidi index=-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/581773/+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 1876886] Re: chrony autopkgtest fails on armhf (groovy)

At the actual build time it is skipped for being "non-root".
But I think this is as easy as now trying to set HW-time in a container.

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

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

Title:
  chrony autopkgtest fails on armhf (groovy)

Status in chrony package in Ubuntu:
  New
Status in libcap2 package in Ubuntu:
  Confirmed

Bug description:
  Test fails on armhf only:
running chronyc makestepERROR
checking chronyc output OK
running chronyc trimrtc ERROR
checking chronyc output OK
running chronyc writertcERROR

  This might be a new twist on 
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1863590
  as it is libcap2 again.

  This reproduces through a bunch of retries
  http://autopkgtest.ubuntu.com/packages/c/chrony/groovy/armhf
  But as I said is armfh only:
  http://autopkgtest.ubuntu.com/packages/chrony

  Flagging update-excuse, but I won't be able to get to it immediately
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+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 479365] Re: assertion failure

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

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

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

Title:
  assertion failure

Status in apport package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: squid

  Ubuntu 9.10
  squid version 2.7.STABLE6-2ubuntu2

  Som when I start up Ubuntu, I have an outstanding failure, which I try
  to report, but then I get a dialog box titled "Problem in squid" that
  says, "The problem cannot be reported: The program crashed on an
  assertion failure, but the message could not be retrieved. Apport does
  not support reporting these crashes."

  ProblemType: Bug
  Architecture: i386
  Date: Mon Nov  9 13:01:37 2009
  DistroRelease: Ubuntu 9.10
  Package: squid 2.7.STABLE6-2ubuntu2
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: squid
  Uname: Linux 2.6.31-14-generic i686
  XsessionErrors:
   (gnome-settings-daemon:2050): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (gnome-settings-daemon:2050): GLib-CRITICAL **: g_propagate_error: assertion 
`src != NULL' failed
   (polkit-gnome-authentication-agent-1:2103): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (nautilus:2074): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed
   (nautilus:2529): Eel-CRITICAL **: eel_preferences_get_boolean: assertion 
`preferences_is_initialized ()' failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/479365/+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 1201112] Re: 64-bit GRUB refuses to Install

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

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

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

Title:
  64-bit GRUB refuses to Install

Status in grub2 package in Ubuntu:
  Invalid
Status in ucf package in Ubuntu:
  Triaged

Bug description:
  On an attempt to install Saucy from 13.04 (Kubuntu), an error occurs
  in /usr/bin/ucfq on line 529. Initially, I fixed it by editing the
  file to directly call `Cwd::abs_path` and let the application
  continue. It didn't solve the problem (and I've redacted such
  changes).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: grub-efi-amd64 2.00-15ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.10.2-0ubuntu4
  Architecture: amd64
  Date: Sun Jul 14 09:58:53 2013
  EcryptfsInUse: Yes
  MarkForUpload: True
  SourcePackage: grub2
  UpgradeStatus: Upgraded to saucy on 2013-07-14 (0 days ago)

  The error from /usr/bin/ucfq was:

  Undefined subroutine ::abs_path called at /usr/bin/ucfq line
  529,  line 21.

  The upgrade to Saucy was done using the executable `kubuntu-devel-
  release-upgrade`.

  I've attached a ppa.tar.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1201112/+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 1876886] Re: chrony autopkgtest fails on armhf (groovy)

It is the build phase that fails.
Reproduced in armhf container on canonistack.

1. get the source and build deps
2. build that until it breaks
3. re-run via 
  $ cd ~/chrony-3.5/test/system
  $ ./run -i 20 -m 2

In this repro environment I get two extra fails at:
005-scfilter   Testing system call filter:
  non-default settings:
extra_chronyd_options=-F -1
  starting chronyd  ERROR
FAIL
  stopping chronyd  ERROR


But also the actual issues:
007-cmdmon   Testing chronyc commands:
  starting chronyd  OK
  running chronyc makestep  ERROR
  checking chronyc output   OK
  running chronyc trimrtc   ERROR
  checking chronyc output   OK
  running chronyc writertc  ERROR
  checking chronyc output   OK
  stopping chronyd  OK

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

Title:
  chrony autopkgtest fails on armhf (groovy)

Status in chrony package in Ubuntu:
  New
Status in libcap2 package in Ubuntu:
  Confirmed

Bug description:
  Test fails on armhf only:
running chronyc makestepERROR
checking chronyc output OK
running chronyc trimrtc ERROR
checking chronyc output OK
running chronyc writertcERROR

  This might be a new twist on 
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1863590
  as it is libcap2 again.

  This reproduces through a bunch of retries
  http://autopkgtest.ubuntu.com/packages/c/chrony/groovy/armhf
  But as I said is armfh only:
  http://autopkgtest.ubuntu.com/packages/chrony

  Flagging update-excuse, but I won't be able to get to it immediately
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1876886/+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 1191898] Re: [USB-Audio - USB Sound Blaster HD, playback] fails after reboot

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [USB-Audio - USB Sound Blaster HD, playback] fails after reboot

Status in PulseAudio:
  New
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  To get the sound card to work, I have to go through this complicated
  process of:

  1) Starting the computer without the card plugged in;
  2) Plugging it in;
  3) At this point, it does NOT work. I have to select it in the audio 
settings, try to make it lay a test sound, which it fails, and then select the 
on-board sound;
  4) Reboot with onboard sound selected. Just logging out does NOT work;
  5) After reboot, select USB Analogue Output, and it will work, however
  6) After a subsequent reboot, it will fail again, and I have to unplug the 
card and reboot again, starting the whole cycle over.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.9.0-6.13-generic 3.9.6
  Uname: Linux 3.9.0-6-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vasco  2151 F pulseaudio
   /dev/snd/controlC1:  vasco  2151 F pulseaudio
   /dev/snd/pcmC1D0p:   vasco  2151 F...m pulseaudio
  Date: Mon Jun 17 18:57:29 2013
  InstallationDate: Installed on 2012-01-20 (514 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB Sound Blaster HD - USB Sound Blaster HD
  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - USB Sound Blaster HD, playback] fails after a while
  UpgradeStatus: Upgraded to raring on 2013-05-06 (42 days ago)
  dmi.bios.date: 05/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W240EU/W250EUQ/W270EUQ
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: V3.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/24/2012:svnCLEVOCO.:pnW240EU/W250EUQ/W270EUQ:pvrNotApplicable:rvnCLEVOCO.:rnW240EU/W250EUQ/W270EUQ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: W240EU/W250EUQ/W270EUQ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1191898/+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 1200925] Re: [USB-Audio - USB Audio, playback] Playback problem Playback only at maximum level, if the volume is turned down just a little no sound is played.

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [USB-Audio - USB Audio, playback] Playback problem Playback only at
  maximum level, if the volume is turned down just a little no sound is
  played.

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  The headphones worked with 10.04 at any volume level.
  Now the headphones work only at maximum volume level (tested with 11.10, 
12.04 13.04) if the volume is turned down just a little no sound is played.

  lsb_release -rd:
  Description:  Ubuntu 12.04.2 LTS
  Release:  12.04

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46
  Uname: Linux 3.2.0-49-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ulrich 8418 F pulseaudio
   /dev/snd/controlC0:  ulrich 8418 F pulseaudio
   /dev/snd/pcmC0D0c:   ulrich 8418 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfd80 irq 50'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:11060448,15585130,0010 
HDA:80862804,15585130,0010'
 Controls  : 38
 Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'Audio'/'USB Audio at usb-:00:1a.0-1.1.1, full speed'
 Mixer name : 'USB Mixer'
 Components : 'USB0d8c:0006'
 Controls  : 12
 Simple ctrls  : 7
  Date: Sat Jul 13 15:08:49 2013
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=de_AT:de
   TERM=xterm
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio failed
  Symptom_Card: Storm HP-USB500 5.1 Headset - USB Audio
  Symptom_Type: None of the above
  Title: [USB-Audio - USB Audio, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: B5130M
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd08/27/2010:svnCLEVOCO.:pnB5130M:pvrNotApplicable:rvnCLEVOCO.:rnB5130M:rvrNotApplicable:cvnNoEnclosure:ct9:cvrN/A:
  dmi.product.name: B5130M
  dmi.product.version: Not Applicable
  dmi.sys.vendor: CLEVO CO.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1200925/+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 1183361] Re: emu10k1: unhandled interrupt: 0x00400000

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  emu10k1: unhandled interrupt: 0x0040

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  hi there,

  i have just pluged a pair of stereo speakers to the "rear" output of
  my Audigy 2 Value card, and inmediately log got flooded by the above
  statement. PC became unresponsive and i had to power it off and on
  again using power button (for more than 4 seconds, impossible to shut
  down via ACPI shutdown)

  When i power on again, with speakers plugged in, all works correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  Uname: Linux 3.9.2-030902-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  Date: Thu May 23 15:48:41 2013
  InstallationDate: Installed on 2012-02-27 (450 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: Upgraded to raring on 2013-01-13 (129 days ago)
  dmi.bios.date: 01/13/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.20F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.20F:bd01/13/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.name: MS-7616
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1183361/+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 1181828] Re: macbook air 2,1 no sound

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  macbook air 2,1 no sound

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Hello,

  I installed Ubuntu raring 13.04 on a Macbook Air 2,1 and I have no
  sound. The card is recognized by alsamixer and pulseaudio. I put the
  volume to the maximum, put all the mixer unmute in alsamixer, no sound
  at all.

  Thanks for your help.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8
  Uname: Linux 3.8.0-21-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rom1   1493 F pulseaudio
  CurrentDmesg: [8.408776] NVRM: GPU at :02:00: 
GPU-e1116370-0337-a0c6-6dce-80e73ebd884a
  Date: Sun May 19 20:29:36 2013
  InstallationDate: Installed on 2013-05-19 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA21.88Z.0075.B03.0811141325
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-F42D88C8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F42D88C8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA21.88Z.0075.B03.0811141325:bd11/14/08:svnAppleInc.:pnMacBookAir2,1:pvr1.0:rvnAppleInc.:rnMac-F42D88C8:rvr:cvnAppleInc.:ct10:cvrMac-F42D88C8:
  dmi.product.name: MacBookAir2,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1181828/+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 1180593] Re: no sound from speakers [OptiPlex 320, Analog Devices AD1983, Green Line Out, Rear] No sound at all

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  no sound from speakers [OptiPlex 320, Analog Devices AD1983, Green
  Line Out, Rear] No sound at all

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  I just switched to ubuntu this is all new to me.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu3.1
  ProcVersionSignature: Ubuntu 3.5.0-28.48-generic 3.5.7.9
  Uname: Linux 3.5.0-28-generic i686
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  twoblue2372 F pulseaudio
  Date: Wed May 15 19:10:22 2013
  InstallationDate: Installed on 2013-05-14 (1 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful
  Symptom_Card: Built-in Audio - HDA ATI SB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  twoblue2372 F pulseaudio
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [OptiPlex 320, Analog Devices AD1983, Green Line Out, Rear] No sound 
at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/10/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.9
  dmi.board.name: 0TY915
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.9:bd07/10/2007:svnDellInc.:pnOptiPlex320:pvr:rvnDellInc.:rn0TY915:rvr:cvnDellInc.:ct7:cvr:
  dmi.product.name: OptiPlex 320
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1180593/+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 1178825] Re: [USB-Audio - Plantronics GameCom 780] Terrible support for this headset

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [USB-Audio - Plantronics GameCom 780] Terrible support for this
  headset

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Today I bought a Plantronics GameCom 780 headset, I pluged into the
  USB port whishing it would work out of the box, but it didn't
  properly. First of all, I'm using Kubuntu 13.04, Linux Kernel version
  is 3.8.0-19, and, for example, I can't hear nothing if volume is less
  than 24%, if I put it at 20% I won't hear anything, it gets muted.
  Micprohone is working quite well, but the function "Loudness" isn't
  working, I typed Alsamixer and I selected the soundcard of the
  headset, Loudness appears there but it appears desactivated, and I
  can't enable it :/

  My problems seems to be similar to this:
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/961481

  Do you know if this will be solved in future versions of the Linux
  Kernel? maybe with a new PulseAudio version? what about Alsamixer? I'm
  new in Linux, and this kind of problems are terrible, I know it's not
  Linux fault, it's GameCom fault, they should make better support for
  Linux...

  Thank you (sorry for my bad English)

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1178825/+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 989800] Re: Error alert stops appearing for the same crash after a while

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

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

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

Title:
  Error alert stops appearing for the same crash after a while

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Invalid

Bug description:
  apport 2.0.1-0ubuntu6, Ubuntu 12.04

  1. Encounter a particular crash.
  2. Encounter the same crash again.
  3. Encounter the same crash again.

  What happens:
  1. An error alert appears explaining what happened.
  2. An error alert appears explaining what happened.
  3. Nothing.

  What should happen:
  3. An error alert appears explaining what happened.

  The primary purpose of the error alert, as far as the user is
  concerned, is to explain what has just gone wrong. This purpose does
  not change no matter how often the error occurs.

  For fair comparison of error rates between Ubuntu versions, it may be
  necessary to flag these previously-suppressed errors as ones that
  wouldn't have been reported "by X standards".

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/989800/+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 1172015] Re: Sydney timezone is in the wrong location

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

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

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

Title:
  Sydney timezone is in the wrong location

Status in One Hundred Papercuts:
  Confirmed
Status in libtimezonemap package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  In ubiquity, the timezone marker points at least 500km away from
  sydney. it seems to be in the ACT(canberra) rather than new south
  wales.

  This occurs when choosing the location in the drop down list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1172015/+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 581650] Re: Total deciBel gain incorrectly reported

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Total deciBel gain incorrectly reported

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: pulseaudio

  This report relates to the gnome-volume-control panel applet, which reports 
the
  total audio gain as a percentage and in deciBels whenever the user performs a
  mouse-over.

  The dB gain reported seems to assume that "all sliders at max" is the zero dB 
reference level. However, this is not always the case. For example, on my 
system, 
  Master ranges from -46.5dB to 0dB but
  PCM ranges from -34.5dB to +12dB,
  so if these are both set to maximum the total gain will be +12dB, not 0dB as 
indicated. This is important because if I use those maximum settings and play 
any audio which peaks above -12dB, the output will clip and sound distorted.
  [i.e. For clean audio, sliders should be set to 0dB, not 100%].

  This bug was initially reported against gnome-media here:-
  https://bugzilla.gnome.org/show_bug.cgi?id=618551
  However, a Gnome developer says the erroneous dB value shown in the tooltip 
comes from the pulse function pa_sw_volume_to_dB().

  Cheers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/581650/+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 1170714] Re: colord is activated during ubiquity-dm installation session, is it really needed?

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

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

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

Title:
  colord is activated during ubiquity-dm installation session, is it
  really needed?

Status in colord package in Ubuntu:
  New
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  Recently I started seeing this in syslog when launching ubiquity installer:
  Apr 10 10:51:27 ubuntu dbus[1094]: [system] Activating service 
name='org.freedesktop.ColorManager' (using servicehelper)
  Apr 10 10:51:27 ubuntu colord: Using config file /etc/colord.conf
  Apr 10 10:51:27 ubuntu colord: Using mapping database file 
/var/lib/colord/mapping.db
  Apr 10 10:51:27 ubuntu colord: Using device database file 
/var/lib/colord/storage.db
  Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_camera.so
  Apr 10 10:51:27 ubuntu colord: plugin 
/usr/lib/colord-plugins/libcd_plugin_sane.so not loaded: plugin refused to load
  Apr 10 10:51:27 ubuntu colord: loaded plugin libcd_plugin_scanner.so
  Apr 10 10:51:27 ubuntu colord: Daemon ready for requests
  Apr 10 10:51:27 ubuntu ubiquity[3150]: Ubiquity 2.14.1
  Apr 10 10:51:27 ubuntu dbus[1094]: [system] Successfully activated service 
'org.freedesktop.ColorManager'
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-f5cf9cb1331928471dbcd67d7229aff5
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-d3ee37ff47fcdf614fb5cb62fb3e16a7
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-612c87ff43ce187a724c1c4354428d5c
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-e1818e5a6f09a1cf9984b3752d306ff5
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-b8009c7e612e5ed5ddbd42dcb6eb349c
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-ae0f19a77ff01ea1932ef5fd9609ef9d
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-6590422afc1260c68d531b8de865eda1
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-9282466ab15c12d62ce889610bc427bd
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-068a2ad86446468c029a0d55c061e46c
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-de6232cfa581f3ce8c9c2548f3ac308f
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-adb5ebe2a14b98599a170cd3ab54fe76
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-29f7c3bb18648f967e9cc450f5b0821e
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-0ef971da00dac3a46e0c86550c54d5ad
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-e7ecfce2d984c9f0c90f4ef1cdc9ac7e
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-798efa4314bbd0274499de21fdf4ee5e
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-c191d7b963b91ae51c83722957430c9c
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-709099b11b3ec2828a314682a3c09f75
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-cecd8af52a99dfe8b57b9cd0f4e41ab0
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-ea21dae0f2e604aba058541c1972b7f1
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-aaa3a8cf35289974339049bc4cff354d
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-819072bc37e0ea0042b6c3b28ce8da1a
  Apr 10 10:51:27 ubuntu colord: Profile added: 
icc-578e8c43d0440cff3239ced4417c691a
  Apr 10 10:51:28 ubuntu colord: Profile added: 
icc-f844a65e79050c828a5f8381a0798e49
  Apr 10 10:51:28 ubuntu colord: Device added: xrandr-default

  Is colord really needed in the bare-minimal "install ubuntu" session?
  It was not loaded previously (e.g. early raring and previous
  releases). Or is it really necessary to load that now?

  It would interesting to trace what does activate it. I am randomly
  guessing gnome-settings-daemon ;-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1170714/+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 1168592] Re: Sound not working on tyan S7025, Alsa detects, and activates controller, but no sound

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Sound not working on tyan S7025, Alsa detects, and activates
  controller, but no sound

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  It works under ubuntu 10.04, and windows.

  The card is detected by the system, alsa and is activated (Intel
  Corporation 82801JI (ICH10 Family) HD Audio Controller)

  I've unmuted everything. 
  I can't test the digital port (so I don't know if that is sending anything), 
since I have nothing to plug into it.

  Here is the information dump.

  http://www.alsa-
  project.org/db/?f=7b6cd11ab958f0116538916043508c9cc05b98ce

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1168592/+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 1160441] Re: Calendar is still in English despite French is selected as the Language during the installation

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

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

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

Title:
  Calendar is still in English despite French is selected as the
  Language during the installation

Status in Indicator Date and Time:
  In Progress
Status in evolution package in Ubuntu:
  In Progress
Status in evolution-data-server package in Ubuntu:
  In Progress
Status in localechooser package in Ubuntu:
  Triaged
Status in ubiquity package in Ubuntu:
  Invalid
Status in evolution source package in Raring:
  Won't Fix
Status in evolution-data-server source package in Raring:
  Won't Fix
Status in localechooser source package in Raring:
  Won't Fix
Status in ubiquity source package in Raring:
  Won't Fix

Bug description:
  When London is selected as the location and language is selected as
  French, the calendar entries are shown in English. The calendar shows
  correct London date and time but presents them in English. One would
  expect that the calendar entries would be shown in French as it used
  to be the case.

  This occurs in installations with and without network, with and
  without live session and on both amd64 and i386 of 20130326 images.
  When Paris is selected as the location, the calendar entries are shown
  in French.

  Incomplete language support dialog pops up (for networkless
  installations) after the reboot but updating the language does not
  solve the issue.

  Steps to reproduce:

  1. Boot the usb with todays image (20130326)
  2. Select French language for installation
  3. Continue with default settings except the location setting, which should 
be set to London
  4. Finish the installation and reboot.
  5. Check the calendar entries

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: ubiquity 2.13.17
  ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
  Uname: Linux 3.8.0-14-generic i686
  ApportVersion: 2.9.2-0ubuntu4
  Architecture: i386
  CasperVersion: 1.330
  Date: Tue Mar 26 15:20:47 2013
  LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130326)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1160441/+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 997238] Re: [CA0106 - CA0106, playback] No sound at all since upgrade to 12.04

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [CA0106 - CA0106, playback] No sound at all since upgrade to 12.04

Status in PulseAudio:
  New
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  The title sums it it up pretty well. Since I upgraded to 12.04, I have
  no sound anymore...

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julien 1740 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'CA0106'/'Audigy SE [SB0570] at 0xec00 irq 20'
 Mixer name : 'CA0106'
 Components : ''
 Controls  : 35
 Simple ctrls  : 18
  CurrentDmesg:
   [2.066528] microsoft 0003:045E:00DB.0002: input,hidraw1: USB HID v1.11 
Keyboard [Microsoft Natural\xffc2\xffae\xffae Ergonomic Keyboard 
4000] on usb-:00:1d.0-2/input0
   [2.096177] input: Microsoft Natural\xffc2\xffae\xffae 
Ergonomic Keyboard 4000 as 
/devices/pci:00/:00:1d.0/usb5/5-2/5-2:1.1/input/input4
   [2.096902] microsoft 0003:045E:00DB.0003: input,hidraw2: USB HID v1.11 
Device [Microsoft Natural\xffc2\xffae\xffae Ergonomic Keyboard 
4000] on usb-:00:1d.0-2/input1
   [4.910980] skge :05:04.0: eth1: Link is up at 100 Mbps, full duplex, 
flow control both
   [   13.760021] eth1: no IPv6 routers present
  Date: Wed May  9 19:37:07 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed
  Symptom_Card: CA0106 Soundblaster - CA0106
  Symptom_DevicesInUse:
   1740  julienF pulseaudio
   PID ACCESS COMMAND
  Symptom_Type: No sound at all
  Title: [CA0106 - CA0106, playback] No sound at all
  UpgradeStatus: Upgraded to precise on 2012-05-09 (0 days ago)
  dmi.bios.date: 12/22/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1901
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Commando
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1901:bd12/22/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCommando:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/997238/+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 960314] Re: Unnecessary languages listed but not installed after install

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

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

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

Title:
  Unnecessary languages listed but not installed after install

Status in accountsservice package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  Testing Precise ISO build 20120319.

  Steps:
  1) Boot it from a usb/cd live and click on Try Ubuntu with English language.
  2) Click on Install icon on the desktop, connected or not to the net (it's 
the same)
  3) After reboot, the language selector shows as screenshot-19 and 
screenshot-20 (regional format)

  English variants and Chinese are grey in the list, the only installed
  language (checked in install/remove languages...) is English.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/960314/+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 1876600] Re: cookie overruns can cause org.freedesktop.systemd1 dbus to hang

** Tags removed: sts-sponsor
** Tags added: sts-sponsor-ddstreet

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

Title:
  cookie overruns can cause org.freedesktop.systemd1 dbus to hang

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Long-running services overflow the sd_bus->cookie counter, causing further 
communication with org.freedesktop.systemd1 to stall.

  [Description]
  Systemd dbus messages include a "cookie" value to uniquely identify them in 
their bus context. This value is obtained from the bus header, and incremented 
for each exchanged message in the same bus object. For services that run for 
longer periods of time and keep communicating through dbus, it's possible to 
overflow the cookie value, causing further messages to the 
org.freedesktop.systemd1 dbus to fail. This can lead to these services becoming 
unresponsive, as they get stuck trying to communicate with invalid bus cookie 
values.

  This issue has been fixed upstream by the commit below:
  -  sd-bus: deal with cookie overruns (1f82f5bb4237)

  $ git describe --contains 1f82f5bb4237
  v242-rc1~228

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.27 | xenial-security | source, ...
   systemd | 229-4ubuntu21.27 | xenial-updates  | source, ...
   systemd | 229-4ubuntu21.28 | xenial-proposed | source, ...
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.38 | bionic-security | source, ...
   systemd | 237-3ubuntu10.39 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.40 | bionic-proposed | source, ... <
   systemd | 242-7ubuntu3 | eoan| source, ...

  Releases starting with Eoan already have this fix.

  [Test Case]
  There doesn't seem to be an easy test case for this, as the cookie values 
start at zero and won't overflow until (1<<32). There have been reports from 
users hitting this on Kubernetes clusters continuously running for longer 
periods (~5 months).
  Using GDB, we can construct an artificial test case to test the cookie 
overflow. The test case below performs the following steps:

  1. Create a new system bus object through sd_bus_default_system()
  2. Allocate and append a new method_call message to the bus
  3. Send the message through sd_bus_call()
  4. Handle the response message and free up the message objects

  It's essentially the example code from the
  sd_bus_message_new_method_call() manpage, with minor modifications:
  this is done continuously, to keep incrementing the bus cookie value.
  We step in with GDB when it reaches 0x1, and set its value to
  0xff00 which then causes the test program to fail shortly
  afterwards. An example test run of an impacted system:

  ubuntu@bionic:~$ gcc -Wall test.c -o cookie -lsystemd -g
  ubuntu@bionic:~$ gdb --batch --command=test.gdb --args ./cookie
  Breakpoint 1 at 0xe61: file test.c, line 38.
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  (16s) cookie: 0x0001reply-cookie: 0x0001

  Breakpoint 1, print_unit_path (bus=0x55757290) at test.c:38
  38  r = sd_bus_message_new_method_call(bus, ,
  $1 = 0x1
  $2 = 0xff00
  Call failed: Operation not supported
  Sleeping and retrying...
  Call failed: Invalid argument
  Assertion 'm->n_ref > 0' failed at 
../src/libsystemd/sd-bus/bus-message.c:934, function sd_bus_message_unref(). 
Aborting.

  Program received signal SIGABRT, Aborted.
  __GI_raise (sig=sig@entry=0x6) at ../sysdeps/unix/sysv/linux/raise.c:51
  51  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.

  To compile and debug the test case above, libsystemd-dev and 
libsystemd0-dbgsym are required.
  Both test.c and test.gdb source code are attached to this LP bug.

  [Regression Potential]
  This fix introduces some changes in the way cookie incrementation is handled. 
We now have a reduced number of available values, since the patch makes use of 
a high order bit to indicate whether we have overflowed or not. Potential 
issues could arise from two distinct messages repeating the cookie value, or 
from us not handling the cookie reuse properly. In practice, this shouldn't 
cause serious problems as most dbus messages should not stall long enough for a 
possible overlap in the 2^31 space. The patch has been present in other stable 
Ubuntu Series and upstream, and has been validated and tested through the 
systemd test suite and autopkgtests.

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

-- 
Mailing list:

[Touch-packages] [Bug 975221] Re: [OptiPlex 745, Analog Devices AD1983, Green Line Out, Rear] No sound on some applications

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  [OptiPlex 745, Analog Devices AD1983, Green Line Out, Rear] No sound
  on some applications

Status in ALSA driver:
  Unknown
Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  I was unable to play the BBC Music player on live material ( previous
  programs ran OK ) and the Application "TuneIn" would not run.  I have
  been unable to install VLC from Snyptic or the software center, lists
  a million unsatisfied dependancies.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1754 F pulseaudio
  Date: Fri Apr  6 10:52:52 2012
  InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 
(20110720.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   1754/dev/snd/controlC0:  dennisF pulseaudio
   AND
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [OptiPlex 745, Analog Devices AD1983, Green Line Out, Rear] No sound 
at all
  UpgradeStatus: Upgraded to precise on 2012-04-05 (1 days ago)
  dmi.bios.date: 11/04/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.3
  dmi.board.name: 0HR330
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.3:bd11/04/2009:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0HR330:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 745
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/975221/+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 957177] Re: support multiple crashdbs

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

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

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

Title:
  support multiple crashdbs

Status in apport package in Ubuntu:
  Invalid
Status in whoopsie package in Ubuntu:
  Confirmed
Status in apport source package in Raring:
  Won't Fix
Status in whoopsie source package in Raring:
  Won't Fix

Bug description:
  Right now Apport only supports sending reports to one crashdb.

  With whoopsie we actually have two now, which we want to send reports
  to at the same time. whoopsie support is currently bolted on at the
  side, but it would be more elegant to create an actual whoopsie
  CrashDB backend, and then change /etc/apport/crashdb.conf to send to
  multiple DBs at the same time (e. g. launchpad+whoopsie during
  development, and just whoopsie post-release).

  I just discussed the addition of a new "problem_types" CrashDB option
  with Evan, which is a list of "ProblemType" values this crashdb
  accepts. So e. g. after release, the launchpad DB could say
  "problem_types: ['Bug', 'Package']" if we don't want LP bug reports
  for crashes any more.

  If we have that, ui.py could then check if any of the active CrashDBs
  takes that particular ProblemType, and present the report. If no
  crashdb takes it, it wouldn't show the report at all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/957177/+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 1251370] Re: apport-gtk opens too many windows to be useful

2020-05-06 Thread Paul White

Further to above comment also closing Papercuts task.

** Changed in: hundredpapercuts
   Status: New => Invalid

** Changed in: hundredpapercuts
   Importance: Undecided => Medium

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

Title:
  apport-gtk opens too many windows to be useful

Status in One Hundred Papercuts:
  Invalid
Status in apport package in Ubuntu:
  Invalid

Bug description:
  For regular users, windows are a burden, and more than one appearing
  that is not the result of something they asked for is a terrible
  experience. It's scary, intimidating, and turns their machine into a
  useless heap and makes them feel helpless until they can clean away
  the mess. It damages their trust in the machine.

  A single window is manageable. They can take that effort. That can be
  digested.

  Apport UI should open a single window, regardless of how many reports
  it wishes to send.  If I have a wonky hardware device or a long-
  running machine, getting all the scheduled reports at once is almost
  useless.

  This should be a good 100 Papercuts bug to fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1251370/+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 948015] Re: OS crash alert unnecessarily includes Ubuntu version number

This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.

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

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

Title:
  OS crash alert unnecessarily includes Ubuntu version number

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Invalid

Bug description:
  apport 1.94-0ubuntu1
  apport 1.95-0ubuntu1

  1. Invoke an internal error.

  What happens: An alert appears with the primary text "Sorry, Ubuntu
  12.04 has experienced an internal error.".

  What should happen: An alert appears with the primary text "Sorry,
  Ubuntu has experienced an internal error.".
  

  The Ubuntu version number isn't relevant to the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/948015/+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 1369258] Re: [USB-Audio - USB Device 0x47f:0xad01, playback] volume slider problem