[Touch-packages] [Bug 1873164] [NEW] my Bug Report

[Hrishikesh Sathaye]

Public bug reported:

I am using Lenovo Ideapad D330 2 in 1 Laptop. It has Intel UHD Graphics
600. and its a touchscreen laptop. The Problem is i'm facing with g
sensor and screen orientation

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 16 11:08:58 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 605 [17aa:39ff]
InstallationDate: Installed on 2020-04-16 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
MachineType: LENOVO 81H3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=c7483622-a4a6-415a-9767-7aa10bb670db ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: 8NCN37WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55724 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 32
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad D330-10IGM
dmi.modalias: 
dmi:bvnLENOVO:bvr8NCN37WW:bd10/30/2019:svnLENOVO:pn81H3:pvrLenovoideapadD330-10IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct32:cvrLenovoideapadD330-10IGM:
dmi.product.family: ideapad D330-10IGM
dmi.product.name: 81H3
dmi.product.sku: LENOVO_MT_81H3_BU_idea_FM_ideapad D330-10IGM
dmi.product.version: Lenovo ideapad D330-10IGM
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.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+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  my Bug Report

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using Lenovo Ideapad D330 2 in 1 Laptop. It has Intel UHD
  Graphics 600. and its a touchscreen laptop. The Problem is i'm facing
  with g sensor and screen orientation

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 16 11:08:58 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 605 [17aa:39ff]
  InstallationDate: Installed on 2020-04-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 81H3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=c7483622-a4a6-415a-9767-7aa10bb670db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8NCN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55724 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 32
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad D330-10IGM
  dmi.modalias: 
dmi:bvnLENOVO:bvr8NCN37WW:bd10/30/2019:svnLENOVO:pn81H3:pvrLenovoideapadD330-10IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct32:cvrLenovoideapadD330-10IGM:
  dmi.product.family: ideapad D330-10IGM
  dmi.product.name: 81H3
  dmi.product.sku: LENOVO_MT_81H3_BU_idea_FM_ideapad D330-10IGM
  dmi.product.version: Lenovo ideapad D330-10IGM
  dmi.sys.vendor: LENOVO
  

[Touch-packages] [Bug 1845797]

[jon.reeve]

This issue persists even after the latest (March 2020) BIOS update from
Lenovo. I posted about this here on the Lenovo forums:

https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/After-latest-
BIOS-update-audio-not-working-on-Yoga-C930/m-p/5009564

Is our only hope getting the Lenovo BIOS devs to release a fix? Can we
fix this in the BIOS ourselves?

I rate the probability of ever hearing from Lenovo about this at around
0%.

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1808864] Re: Poor translation of zh_CN gpasswd(1) man page

[LYF]

Hello,

Since the file is so large, I only looked over the diff of po/zh_CN.po
that was submitted on Jun 16, 2018 by LionNatsu. Here are a few
suggestions/questions I have:

L862, R855
Link: 
https://github.com/shadow-maint/shadow/commit/cba31b52b39e5ad1df2c4f0d9c684bd4615b92e9#diff-464912b277c8ce74ecad8c785c503facR855

The string "display faillog records more recent than DAYS" is better
translated to this: "显示比 DAYS 天更近的登录失败记录". The current translation is
more along the lines of "display faillog records from DAYS ago".

L1707, R1688
Link: 
https://github.com/shadow-maint/shadow/commit/cba31b52b39e5ad1df2c4f0d9c684bd4615b92e9#diff-464912b277c8ce74ecad8c785c503facR1688

The string "duplicate password entry" was correctly translated to
"重复的密码项" but the updated Chinese translation (in green) is wrong. It
says "duplicate user entry" "重复的用户条目"

L1762, R1743
Link: 
https://github.com/shadow-maint/shadow/commit/cba31b52b39e5ad1df2c4f0d9c684bd4615b92e9#diff-464912b277c8ce74ecad8c785c503facL1762

The new translation for the string "duplicate shadow password entry",
"重复的用户影子条目" says "duplicate shadow user entry", so it is incorrect. A
correct translation would be "重复的密码影子条目"

L2381, R2354
Link: 
https://github.com/shadow-maint/shadow/commit/cba31b52b39e5ad1df2c4f0d9c684bd4615b92e9#diff-464912b277c8ce74ecad8c785c503facR2354

What does the notation "$s" mean? What is the purpose?

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

Title:
  Poor translation of zh_CN gpasswd(1) man page

Status in Ubuntu Translations:
  New
Status in language-pack-zh-hans package in Ubuntu:
  New
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  man -l /usr/share/man/zh_CN/man1/gpasswd.1.gz

  The zh_CN version of gpasswd(1) not only is partially done, but also
  contains an error in the first sentence. The translator confused the
  verb "administer" with the person "administrator." The section
  heading, originally "Notes (noun) about group passwords," was
  translated as "Please note (verb) the group passwords." Even Google
  translate does better!

  Translation errors
  ==
  gpasswd - administer /etc/group and /etc/gshadow
  gpasswd - 管理员 /etc/group 和 /etc/gshadow
^^ 管理员 -- administrator
   管理 -- administer

  Notes about group passwords
  请注意组密码
  ^^ 请注意…… -- please note (v.)
 关于……的说明 -- notes (n.) about

  Typos
  =
  -h, --help
  Display help message and exit.

  -h, --help
  现实帮助信息并退出。
   显示 Xiǎnshì -- display
   现实 Xiànshí -- reality

  Correct Google translate results (this but unironically)
  
  "gpasswd - administer /etc/group and /etc/gshadow"
  "gpasswd - 管理 /etc/group 和 /etc/gshadow"

  "Notes about group passwords"
  "关于组密码的说明"

  "Display help message and exit."
  "显示帮助消息并退出。"

  Notes about my system
  =
  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  $ apt-cache policy passwd
  passwd:
Installed: 1:4.5-1ubuntu1
Candidate: 1:4.5-1ubuntu1
Version table:
   *** 1:4.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1808864/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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

[Simon Déziel]

Scratch that. Using 'owner' on a root-owned but world readable file is
probably ill-advised in an abstraction. It seems plausible for an
application to do NSS lookup for user/group while running as non-root.

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

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

Status in apparmor package in Ubuntu:
  New

Bug description:
  # Description

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

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

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

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

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

  # Steps to reproduce

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

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

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

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

  
  Step 4, should not return anything. Because systemd is involved in the 
user/group 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

[Touch-packages] [Bug 1873086] Re: sound stutters when playing on a bluetooth receiver

[Daniel van Vugt]

The main fix for Bluetooth audio stutter is one that you already have,
released in pulseaudio 1:11.1-1ubuntu7.1 (bug 405294). People generally
don't report problems since then so any remaining issues are likely to
be hardware-specific or environment-specific.

Please run these commands:

  lsusb > lsusb.txt
  lspci -k > lspci.txt

and then attach the resulting two files.

Please also test with:

  * wifi disabled completely; and
  * using a 5GHz network instead of 2.4GHz


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

** Tags added: a2dp-skip

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

Title:
  sound stutters when playing on a bluetooth receiver

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I can play via bluetooth from my laptop or my mobile phone. I have a
  set of bluetooth headphones and bluetooth speakers.

  Any combination of output with the smartphone as the player works,
  which is as it should be.

  Any combination of output with the laptop as the player is miserable:
  sound stutters, sometimes randomly, sometimes seemingly when I touch
  the laptop or come close to it...had similar or identical problems
  with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad
  shape.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  laptop Dell XPS 9370

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tna2174 F pulseaudio
   /dev/snd/pcmC0D0p:   tna2174 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 22:55:05 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (706 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1873086] Re: sound stutters when playing on a bluetooth receiver

[Daniel van Vugt]

Also I notice your kernel log mentions ath10k so bug 1746164 might be
relevant.

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

Title:
  sound stutters when playing on a bluetooth receiver

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I can play via bluetooth from my laptop or my mobile phone. I have a
  set of bluetooth headphones and bluetooth speakers.

  Any combination of output with the smartphone as the player works,
  which is as it should be.

  Any combination of output with the laptop as the player is miserable:
  sound stutters, sometimes randomly, sometimes seemingly when I touch
  the laptop or come close to it...had similar or identical problems
  with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad
  shape.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  laptop Dell XPS 9370

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tna2174 F pulseaudio
   /dev/snd/pcmC0D0p:   tna2174 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 22:55:05 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (706 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1873086] Re: sound stutters when playing on a bluetooth receiver

[Daniel van Vugt]

** Tags added: a2dp

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

Title:
  sound stutters when playing on a bluetooth receiver

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I can play via bluetooth from my laptop or my mobile phone. I have a
  set of bluetooth headphones and bluetooth speakers.

  Any combination of output with the smartphone as the player works,
  which is as it should be.

  Any combination of output with the laptop as the player is miserable:
  sound stutters, sometimes randomly, sometimes seemingly when I touch
  the laptop or come close to it...had similar or identical problems
  with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad
  shape.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  laptop Dell XPS 9370

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tna2174 F pulseaudio
   /dev/snd/pcmC0D0p:   tna2174 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 22:55:05 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (706 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1872970] Re: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device

[Daniel van Vugt]

** Bug watch added: Red Hat Bugzilla #1818883
   https://bugzilla.redhat.com/show_bug.cgi?id=1818883

** Also affects: pulseaudio (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1818883
   Importance: Unknown
   Status: Unknown

** Tags added: fixed-in-13.99.2 fixed-upstream focal

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail
  device

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio package in Fedora:
  Unknown

Bug description:
  I install ubuntu focal, no sound on my Cherry trail device, it has a es8316 
sound card.
  downgrade pulseaudio_13.0-1ubuntu1.1 sound work.

  https://bugzilla.redhat.com/show_bug.cgi?id=1818883
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/276/

  please build next pulseaudio include patch, ucm: fix the port / ucm device 
activation on boot
  alsa sink/source: fix the mixer initialization

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

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

[Touch-packages] [Bug 1873005] Re: [Bluetooth Bose Headphones, playback] Sound plays exclusively from laptop speakers even when headset is selected as output device

[Daniel van Vugt]

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

Note that:

 * after you delete ~/.config/pulse you at least need to log out and in
again.

 * even if deleting ~/.config/pulse doesn't work then we should use bug
1866194 still. The workaround is also not confirmed to work in that bug,
but it's the same bug.

** This bug has been marked a duplicate of bug 1866194
   External audio device shows up in the sound output options but the sound 
keeps being emitted from the internal laptop speaker, or none at all.

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

Title:
  [Bluetooth Bose Headphones, playback] Sound plays exclusively from
  laptop speakers even when headset is selected as output device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The computer will not send any sound output to the headset, and
  instead does all playback through the built in speakers. If headphones
  are connected by AUX sound will be sent there.

  Bluetooth media buttons work - I can pause music by tapping the
  bluetooth headset.

  If I change bluetooth audio quality the headset makes a notification
  sound, but playback continues as before through computer speakers.

  Audio tests (front left, front right) are also channelled through
  computer speakers.

  The same headset with the same setup worked flawlessly in 19.10.

  Thank you so much for your work! 20.04 is a joy to use.

  Edit: I tried deleting .config/pulse. This didn't make any difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steinarne   1509 F pulseaudio
   /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 16:30:16 2020
  InstallationDate: Installed on 2019-08-08 (251 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: LE-Bose NC 700 Headphones
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steinarne   1509 F pulseaudio
   /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [LE-Bose NC 700 Headphones, playback] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-04-13 (2 days ago)
  dmi.bios.date: 05/05/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET56W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LS0017MX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET56W(1.33):bd05/05/2019:svnLENOVO:pn20LS0017MX:pvrThinkPadL480:rvnLENOVO:rn20LS0017MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LS0017MX
  dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1864274] Re: [iris regression] gfx corruption

[Bug Watch Updater]

** Changed in: mesa
   Status: New => Fix Released

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

Title:
  [iris regression] gfx corruption

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Focal:
  Confirmed

Bug description:
  Hello, after upgrading firefox (and many other packages) on focal
  today, I've got some video artifacts in firefox.

  When typing in text boxes and text fields, the new character is drawn
  very slowly, pixel-by-pixel, and isn't complete until the cursor has
  moved on. When larger portions of the screen are updated, it looks a
  lot like the entire window is being run through a video codec or you
  can see parts of the video memory from other processes. (But it looks
  more deliberate and predictable than either of these descriptions.)

  So far Firefox is the only application I've found that is affected.
  urxvt, libreoffice, xfontsel, glxgears all seem to work as expected.

  I did get cairo package update today, but the changelog is just:

  pango1.0 (1.44.7-1ubuntu2) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
   -- Matthias Klose   Sat, 08 Feb 2020 11:15:23 +

  And an xorg update:

  xorg (1:7.7+19ubuntu14) focal; urgency=medium
* No-change rebuild with fixed binutils on arm64.
   -- Matthias Klose   Sat, 08 Feb 2020 11:21:28 +

  
  So I don't believe these are involved.

  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620
  (rev 07)

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 73.0.1+build1-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  AddonCompatCheckDisabled: False
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sarnold3296 F pulseaudio
   /dev/snd/controlC0:  sarnold3296 F pulseaudio
  BuildID: 20200217142647
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 144'
 Mixer name : 'Realtek ALC285'
 Components : 'HDA:10ec0285,17aa225c,0012 
HDA:8086280b,80860101,0010'
 Controls  : 53
 Simple ctrls  : 15
  Card1.Amixer.info:
   Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at 
usb-:00:14.0-4.2.4, high speed'
 Mixer name : 'USB Mixer'
 Components : 'USB17ef:306f'
 Controls  : 9
 Simple ctrls  : 4
  Channel: Unavailable
  Date: Sat Feb 22 05:41:10 2020
  ForcedLayersAccel: False
  IncompatibleExtensions:
   Pentadactyl - pentadac...@dactyl.googlecode.com
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  IpRoute:
   default via 192.168.0.1 dev enp0s31f6 proto dhcp metric 100 
   10.23.231.0/24 dev lxdbr0 proto kernel scope link src 10.23.231.1 
   192.168.0.0/24 dev enp0s31f6 proto kernel scope link src 192.168.0.34 metric 
100 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  MostRecentCrashID: bp-ea952d4d-f25a-4ced-893c-8cabb2160112
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:737
  PrefSources: prefs.js
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=73.0.1/20200217142647 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: Upgraded to focal on 2020-01-24 (28 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET69W (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1872853] Re: Keys stuck on repeat when key triggers sound, and output device is ClearOne Chat 50

[Daniel van Vugt]

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

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

Title:
  Keys stuck on repeat when key triggers sound, and output device is
  ClearOne Chat 50

Status in gnome-shell package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I am typing in a gnome terminal, any time I press a key that
  triggers a sound (e.g., hitting "backspace" when already at the
  beginning of the command line, hitting "tab" for tab completion when
  there are multiple possible completion options), the key gets stuck on
  repeat. The sound plays over and over. If I move the mouse to other
  windows and focus on them, the repeated key continues there. (I have
  focus-follows-mouse enabled, if that matters.)

  This is 100% reproducible. But I have tracked it down to only occuring
  when I go into Settings->Sounds, select the "Output" tab, and choose
  the "Analog Output - Chat 50" device for sound output.

  I do have a ClearOne Chat 50 plugged into my computer via USB. It
  seems to be operating correctly for both input and output sound
  (ignoring the key repeat issue).

  Before figuring out that changing the sound output to be something
  other than the Chat 50, I ruled out the keyboard being the problem by
  swapping in a different model of USB keyboard. I also rebooted the
  system, and that made no difference either.

  I saw other bugs about repeating keys, such as bug #124406. I did try
  disabling repeat with "xset r off". This seems to stop the repeated
  key from taking effect in, say, Gnome terminal. But the repeating key
  is probably still being issued somewhere in the system because when I
  then trigger the bug the keyboard becomes unusable until I unplug it
  and plug it back in again.

  In all cases, unplugging the USB keyboard and plugging it back in
  again eliminates the stuck repeating key.

  I apologize for not selecting a particular package for this bug. This
  bug does only seem to occur when the ClearOne Chat 50 is selected as
  the output sound device, but I'm completely unclear about how an
  output sound device could case key presses to operate incorrectly. I
  does not seem like the sound device should be able to cause a keypress
  to repeat even if the sound driver is buggy.

  
  Ubuntu 18.04.4 LTS.
  Linux mal 4.15.0-96-generic #97-Ubuntu SMP Wed Apr 1 03:25:46 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872853/+subscriptions

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

[Touch-packages] [Bug 1817496] Re: Login always shows partitions to be fsck-ed, even after reboot.

[Serge Hallyn]

You should be able to manually do

fsck /dev/sda5

If the filesystem on sda5 is listed in /etc/fstab, then sixth fstab
field for that filesystem should be '2'.  If it is 0, then indeed it
won't be fsck'd on reboot.

fstab is owned by util-linux, but system bringup belongs to systemd, so
I'm assigning this to the systemd package.  However I suspect fstab
lists '0' for the sixth field, and the system is doing what it is told.

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

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

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

Title:
  Login always shows partitions to be fsck-ed, even after reboot.

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This system reports /dev/sda5 will be checked on the next reboot.
  Maybe it is (it's EXT4 on as SSD drive, so it could be too fast to
  notice), but the message persists even after such a reboot.

  I would expect it to go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Sun Feb 24 17:27:50 2019
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1817496] Re: Login always shows partitions to be fsck-ed, even after reboot.

[Serge Hallyn]

Please show the results of 'mount | grep sda5' and the contents of
/etc/fstab.

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

Title:
  Login always shows partitions to be fsck-ed, even after reboot.

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This system reports /dev/sda5 will be checked on the next reboot.
  Maybe it is (it's EXT4 on as SSD drive, so it could be too fast to
  notice), but the message persists even after such a reboot.

  I would expect it to go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Sun Feb 24 17:27:50 2019
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1872146] Re: Audio on Headphones stopped working

[Daniel van Vugt]

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

OK, we can track this as a duplicate of bug 1866194 then, until proven
otherwise.

** This bug has been marked a duplicate of bug 1866194
   External audio device shows up in the sound output options but the sound 
keeps being emitted from the internal laptop speaker, or none at all.

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

Title:
  Audio on Headphones stopped working

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio via my headphones worked yesterday, Today no such luck.

  When I plug in my headphone, Plasma picks it up but no sound.

  Bluetooth headset still works.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Apr 10 23:03:09 2020
  InstallationDate: Installed on 2020-04-05 (5 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1808864] Re: Poor translation of zh_CN gpasswd(1) man page

[Serge Hallyn]

Would you mind comparing this to the new version at

https://github.com/shadow-maint/shadow/blob/master/po/zh_CN.po

?  I looked for the 'administrator' one, and that seems fixed.  Any
other updates you have which you could post as pull requests against the
upstream project would be greatly appreciated.

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

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

Title:
  Poor translation of zh_CN gpasswd(1) man page

Status in Ubuntu Translations:
  New
Status in language-pack-zh-hans package in Ubuntu:
  New
Status in shadow package in Ubuntu:
  Incomplete

Bug description:
  man -l /usr/share/man/zh_CN/man1/gpasswd.1.gz

  The zh_CN version of gpasswd(1) not only is partially done, but also
  contains an error in the first sentence. The translator confused the
  verb "administer" with the person "administrator." The section
  heading, originally "Notes (noun) about group passwords," was
  translated as "Please note (verb) the group passwords." Even Google
  translate does better!

  Translation errors
  ==
  gpasswd - administer /etc/group and /etc/gshadow
  gpasswd - 管理员 /etc/group 和 /etc/gshadow
^^ 管理员 -- administrator
   管理 -- administer

  Notes about group passwords
  请注意组密码
  ^^ 请注意…… -- please note (v.)
 关于……的说明 -- notes (n.) about

  Typos
  =
  -h, --help
  Display help message and exit.

  -h, --help
  现实帮助信息并退出。
   显示 Xiǎnshì -- display
   现实 Xiànshí -- reality

  Correct Google translate results (this but unironically)
  
  "gpasswd - administer /etc/group and /etc/gshadow"
  "gpasswd - 管理 /etc/group 和 /etc/gshadow"

  "Notes about group passwords"
  "关于组密码的说明"

  "Display help message and exit."
  "显示帮助消息并退出。"

  Notes about my system
  =
  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  $ apt-cache policy passwd
  passwd:
Installed: 1:4.5-1ubuntu1
Candidate: 1:4.5-1ubuntu1
Version table:
   *** 1:4.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1808864/+subscriptions

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

[Touch-packages] [Bug 1811893] Re: In Ubuntu on Virtualbox, the screen is blank after sign-in

[Serge Hallyn]

Thanks for reporting this bug.  This looks to be a bug with either
xubuntu login manager or xubuntu default X11 session, so I'm reassigning
it to lightdm.

** Package changed: shadow (Ubuntu) => lightdm (Ubuntu)

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

Title:
  In Ubuntu on Virtualbox, the screen is blank after sign-in

Status in lightdm package in Ubuntu:
  New

Bug description:
  I installed xubuntu in my Windows box using the latest VBOX (6.0). It
  installed perfectly however after I log in the screen kind of freezes.
  I see the background however the icons and title bar do not appear.
  Also mouse inputs like right click do not work. Function keys do not
  work either like alt F2.

  Xubuntu system is updated and the guest addons are installed.

  I have tried disbling the 3d acceleration however that did not work.

  The only way I can get this to load the icons is to go to Devices ->
  Insert Guest Additions CD Image. Once I click on Insert Guest
  Additions the icons and title bar load and everything works fine.

  I checked online for solutions but have not found any that work.

  This also seems to be a problem with other versions of Ubuntu and
  other Linux distributions.

  xubuntu 10.04.1

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jan 15 15:20:31 2019
  InstallationDate: Installed on 2019-01-15 (0 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Simon Déziel]

On all my machines and using various daemons, the denial messages always
have fsuid==ouid. As such, I believe it would be OK to use the 'owner'
specifier like this:

  owner @{PROC}/sys/kernel/random/boot_id r,

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

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

Status in apparmor package in Ubuntu:
  New

Bug description:
  # Description

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

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

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

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

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

  # Steps to reproduce

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

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

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

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

  
  Step 4, should not return anything. Because systemd is involved in the 
user/group 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

[Touch-packages] [Bug 1873104] Re: Defaults to USB audio after every reboot

[Hui Wang]

You could temporarily remove the module-switch-on-connect from the
/etc/pulse/default.pa, reboot and redo the test.

To check if switch-on-connect is loaded or not, run "pactl list modules
| grep connect"

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

Title:
  Defaults to USB audio after every reboot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I manually set my audio output to the Line Out. Every reboot this
  settings is lost and the system defaults back to the USB output. I
  have several other distros to test - Ubuntu and its flavors are the
  only ones that have this problem. Something changed in 19.04 or 19.10
  that broke this, and it continues to be an issue in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  caleb  1778 F pulseaudio
   /dev/snd/controlC3:  caleb  1778 F pulseaudio
   /dev/snd/controlC1:  caleb  1778 F pulseaudio
   /dev/snd/controlC0:  caleb  1778 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Wed Apr 15 19:32:36 2020
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.name: 8437
  dmi.board.vendor: HP
  dmi.board.version: 1.3
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Omen
  dmi.product.name: OMEN by HP Desktop PC 880-p1xx
  dmi.product.sku: 2TB61AV
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1872443] Re: /etc/securetty missing: dovecot not working

[Serge Hallyn]

This was a decision made by the debian package (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771675 ).

Would you mind raising a bug against pam and shadow in debian bringing
this up? Perhaps the libpam-modules package should supply it alongside
the pam_securetty.so.

Please let us know if you're not comfortable doing that.


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

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

Title:
  /etc/securetty missing: dovecot not working

Status in shadow package in Ubuntu:
  New

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1872926] Re: font scaling

[Daniel van Vugt]

Thanks for the bug report.

It is the responsibility of the graphics toolkit used by an app, or the
app itself, to honour font scaling settings. So please report this issue
to each application. It looks like Chrome (Chromium) is already covered
by bug 1316847?

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

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

Title:
  font scaling

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  i use font scaling at 1.20 an it doesn't work on skype, chrome,
  discord whatsdesk etc

  i need to edit all the launcher to use it

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/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 Apr 15 10:43:40 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:5036]
  InstallationDate: Installed on 2020-04-09 (6 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Lsusb:
   Bus 001 Device 002: ID 8087:8001 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 04f2:b449 Chicony Electronics Co., Ltd Integrated 
Camera
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20BWS3MG00
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=e64bf22d-6dd2-4ba5-9de7-df6dbf8d2dc4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BWS3MG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BWS3MG00:pvrThinkPadT450s:rvnLENOVO:rn20BWS3MG00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BWS3MG00
  dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~sdeziel/ubuntu/+source/rsyslog/+git/rsyslog/+merge/382344

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  In Progress
Status in rsyslog source package in Disco:
  In Progress
Status in rsyslog source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * rsyslog ships with a (Default disable) apparmor profile.
   * Security sensitive users are in general encouraged to enable such
     profiles but unfortunately due to slightly new behavior of the program
     the profile prevents its usage.
   * Allow the program to map/read its binary to get this working again

  [Test Case]

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  [Regression Potential]

   * This is just opening up the apparmor profile a bit. Therefore the only
     regression it could cause IMHO is a security issue. But then what it
     actually allows is reading (not writing!) its own binary which should
     be very safe.
   * Thinking further it came to my mind that package updates (independent 
 to the change) might restart services and that means if there is any 
 issue e.g. in a local config that worked but now fails (not by this 
 change but in general) then the upgrade will not cause, but trigger 
 this. This is a general regression risk for any upload, but in this 
 case worth to mention as it is about log handling - which if broken - 
 makes large scale systems hard to debug.

  [Other Info]

   * n/a

  ---

  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  Workaround:

    echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog

  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1872971] Re: Xorg crash

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (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/1872971

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

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

  apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  I was running the game Into the Breach
  (https://store.steampowered.com/app/590380/Into_the_Breach/) through
  Steam Play (Proton 5.0-5). When I continue my game and mouse over a
  character which has been placed on the play field, my session crashes
  and I am returned to the login screen. This consistently happens every
  time I load my game and perform the mouseover.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: 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.82  Wed Apr  1 20:04:33 
UTC 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Apr 15 13:38:42 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.82, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0819]
 Subsystem: Dell GM108M [GeForce MX130] [1028:0819]
  InstallationDate: Installed on 2020-04-09 (6 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Dell Inc. Latitude 5591
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=595cdefb-5445-4df8-99e9-6a60485a8c97 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0DVVG1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd01/11/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5591
  dmi.product.sku: 0819
  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-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  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+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1872971/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1871972] Re: Update pango for Unicode 13.0

[Launchpad Bug Tracker]

This bug was fixed in the package pango1.0 - 1.44.7-2ubuntu3

---
pango1.0 (1.44.7-2ubuntu3) focal; urgency=medium

  [ Laurent Bigonville ]
  * debian/control.in: Add libcairo2-doc, libgtk-3-doc and libharfbuzz-doc
to BDI to fix more links between gtk-doc files

  [ Jeremy Bicha ]
  * Cherry-pick Update-pango-emoji-table.h-to-Unicode-Emoji-Data-13.0.patch:
- Prepare for Unicode 13.0 (LP: #1871972)

 -- Jeremy Bicha   Thu, 09 Apr 2020 21:27:07 -0400

** Changed in: pango1.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Update pango for Unicode 13.0

Status in pango1.0 package in Ubuntu:
  Fix Released

Bug description:
  Unicode 13 was released a month ago. The Pango library needs to be
  updated for the new emoji sequences for emoji that are implemented by
  multiple emoji in sequence to appear as a single character instead of
  as separate parts. For instance, https://emojipedia.org/black-cat/

  By doing this update for Ubuntu 20.04 LTS now, it will be easier to
  get full Unicode 13 support once Ubuntu's color emoji font (fonts-
  noto-color-emoji) is released with Unicode 13 support in a few months.

  I don't believe a freeze exception is necessary for this improvement
  now.

  https://gitlab.gnome.org/GNOME/pango/-/commit/06aab3539

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1871972/+subscriptions

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

[Touch-packages] [Bug 1872967] Re: Xorg crash

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (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/1872967

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Screen freezes when using LibreOffice writer, then crashes.

  After around a minute, the X session restarts and presents me with the
  login prompt.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 13:56:21 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:8a52] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:08b0]
  InstallationDate: Installed on 2019-12-02 (134 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash i915.enable_psr=0 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.9
  dmi.board.name: 06CDVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd08/02/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1872967/+subscriptions

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

[Touch-packages] [Bug 998816] Re: Login password is shown in plaintext

[Serge Hallyn]

Note this was wishlist in shadow, but i can't find wishlist in the list
of options any more.

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

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

Title:
  Login password is shown in plaintext

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  This bug was originally posted on kernel.org but it was closed because
  it seems to be a non-related kernel bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=21272

  I'm currently using Ubuntu 12.10 dev and the bug still exists there.

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

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

[Touch-packages] [Bug 998816] Re: Login password is shown in plaintext

[Serge Hallyn]

This is actually a bug in getty, which accepts the username and then
starts login.

** Package changed: shadow (Ubuntu) => util-linux (Ubuntu)

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

Title:
  Login password is shown in plaintext

Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  This bug was originally posted on kernel.org but it was closed because
  it seems to be a non-related kernel bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=21272

  I'm currently using Ubuntu 12.10 dev and the bug still exists there.

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

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

[Touch-packages] [Bug 600653] Re: passwd man mistake minage -m should be -n

[Serge Hallyn]

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

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

Title:
  passwd man mistake minage -m should  be -n

Status in shadow package in Ubuntu:
  Fix Released

Bug description:
  root@XX:/etc/pam.d# cat /etc/issue
  Ubuntu 8.10 \n \l

  root@X:/etc/pam.d# man passwd | grep min
 -m, --mindays MIN_DAYS
 Set the minimum number of days between password changes to
 of the last password change. The next four fields are the minimum
  root@onmsip02:/etc/pam.d# passwd -m 1 root
  passwd: invalid option -- 'm'
  Usage: passwd [options] [LOGIN]

  Options:
-a, --all report password status on all accounts
-d, --delete  delete the password for the named account
-e, --expire  force expire the password for the named 
account
-h, --helpdisplay this help message and exit
-k, --keep-tokens change password only if expired
-i, --inactive INACTIVE   set password inactive after expiration
  to INACTIVE
-l, --locklock the named account
-n, --mindays MIN_DAYSset minimum number of days before password
  change to MIN_DAYS
-q, --quiet   quiet mode
-r, --repository REPOSITORY   change password in REPOSITORY repository
-S, --status  report password status on the named account
-u, --unlock  unlock the named account
-w, --warndays WARN_DAYS  set expiration warning days to WARN_DAYS
-x, --maxdays MAX_DAYSset maximim number of days before password
  change to MAX_DAYS

  
  root@X:/etc/pam.d# passwd -n 1 root && echo $?
  Password changed.
  0
  root@:/etc/pam.d#

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

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

[Touch-packages] [Bug 1873104] [NEW] Defaults to USB audio after every reboot

[Caleb McKay]

Public bug reported:

I manually set my audio output to the Line Out. Every reboot this
settings is lost and the system defaults back to the USB output. I have
several other distros to test - Ubuntu and its flavors are the only ones
that have this problem. Something changed in 19.04 or 19.10 that broke
this, and it continues to be an issue in 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  caleb  1778 F pulseaudio
 /dev/snd/controlC3:  caleb  1778 F pulseaudio
 /dev/snd/controlC1:  caleb  1778 F pulseaudio
 /dev/snd/controlC0:  caleb  1778 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Wed Apr 15 19:32:36 2020
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: USB sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/06/2018
dmi.bios.vendor: AMI
dmi.bios.version: F.30
dmi.board.name: 8437
dmi.board.vendor: HP
dmi.board.version: 1.3
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr:
dmi.product.family: 103C_53311M HP Omen
dmi.product.name: OMEN by HP Desktop PC 880-p1xx
dmi.product.sku: 2TB61AV
dmi.sys.vendor: HP

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

Title:
  Defaults to USB audio after every reboot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I manually set my audio output to the Line Out. Every reboot this
  settings is lost and the system defaults back to the USB output. I
  have several other distros to test - Ubuntu and its flavors are the
  only ones that have this problem. Something changed in 19.04 or 19.10
  that broke this, and it continues to be an issue in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  caleb  1778 F pulseaudio
   /dev/snd/controlC3:  caleb  1778 F pulseaudio
   /dev/snd/controlC1:  caleb  1778 F pulseaudio
   /dev/snd/controlC0:  caleb  1778 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Wed Apr 15 19:32:36 2020
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: USB sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.30
  dmi.board.name: 8437
  dmi.board.vendor: HP
  dmi.board.version: 1.3
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53311M HP Omen
  dmi.product.name: OMEN by HP Desktop PC 880-p1xx
  dmi.product.sku: 2TB61AV
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 837285] Re: lightdm assert failure: lightdm: pam_mount.c:417: modify_pm_count: Assertion `user != ((void *)0)' failed.

[Bug Watch Updater]

** Changed in: libpam-mount (Debian)
   Status: New => Fix Released

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

Title:
  lightdm assert failure: lightdm: pam_mount.c:417: modify_pm_count:
  Assertion `user != ((void *)0)' failed.

Status in lightdm package in Ubuntu:
  Fix Released
Status in libpam-mount package in Debian:
  Fix Released

Bug description:
  Logged in with GNOME as session.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  AssertionMessage: lightdm: pam_mount.c:417: modify_pm_count: Assertion `user 
!= ((void *)0)' failed.
  CrashCounter: 1
  Date: Tue Aug 30 12:18:08 2011
  ExecutablePath: /usr/sbin/lightdm
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcCmdline: lightdm
  ProcEnviron: PATH=(custom, no user)
  Signal: 6
  SourcePackage: lightdm
  StacktraceTop:
   __GI___assert_fail (assertion=0x7f0c2294a63c "user != ((void *)0)", 
file=, line=417, function=) at assert.c:81
   ?? () from /lib/security/pam_mount.so
   pam_sm_close_session () from /lib/security/pam_mount.so
   ?? () from /lib/x86_64-linux-gnu/libpam.so.0
   ?? ()
  Title: lightdm assert failure: lightdm: pam_mount.c:417: modify_pm_count: 
Assertion `user != ((void *)0)' failed.
  UpgradeStatus: Upgraded to oneiric on 2011-08-19 (10 days ago)
  UserGroups:

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

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

[Touch-packages] [Bug 1871952] Re: Ubuntu falsely claims via a notification that I have broken packages, even though I am using a fresh install without updating any packages yet.

[Brian Murray]

** Summary changed:

- Ubuntu falsely claims via a notificat ion that I have broken packages, even 
though I am using a fresh install without updating any packages yet.
+ Ubuntu falsely claims via a notification that I have broken packages, even 
though I am using a fresh install without updating any packages yet.

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

Title:
  Ubuntu falsely claims via a notification that I have broken packages,
  even though I am using a fresh install without updating any packages
  yet.

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  After logging into Ubuntu after installing the beta, I changed the
  update settings to allow proposed updates and backports. I then
  refreshed the cache and checked for updates. APT said no errors.
  However, on the menu bar, I received a notifcation saying
  brokenPackages > 0, even though that is not true and my system is
  working without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  Date: Thu Apr  9 18:13:10 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperMD5CheckResult: skip
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: apt 2.0.1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1873017] Re: Error when install lvm2 on ubuntu 20.04

[Yiu Man Ho]

That log on this page's top is show on the third install and just the
install part, not include the remove part.

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

Title:
  Error when install lvm2 on ubuntu 20.04

Status in lvm2 package in Ubuntu:
  New

Bug description:
  I am using chinese so some log will use chinese.
  These is the logs that i found on terminal:

  解開 lvm2 (2.03.07-1ubuntu1) 中...
  設定 lvm2 (2.03.07-1ubuntu1) ...
  update-initramfs: deferring update (trigger activated)
  Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked.
  invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed.
  ● lvm2-lvmpolld.service - LVM2 poll daemon
   Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; 
vendor p
  reset: enabled)
   Active: inactive (dead)
     Docs: man:lvmpolld(8)
  dpkg: error processing package lvm2 (--configure):
   installed lvm2 package post-installation script 子進程傳回了 1 錯誤退出狀態碼
  執行 systemd (245.4-2ubuntu1) 的觸發程式……
  執行 man-db (2.9.1-1) 的觸發程式……
  執行 ureadahead (0.100.0-21) 的觸發程式……
  ureadahead will be reprofiled on next reboot
  執行 initramfs-tools (0.136ubuntu6) 的觸發程式……
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  I: The initramfs will attempt to resume from /dev/sda6
  I: (UUID=52eb06e0-e84e-4146-be3b-e07513046207)
  I: Set the RESUME variable to override this.
  Warning: Not updating LILO; /etc/lilo.conf not found!
  處理時發生錯誤：
   lvm2
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:17:22 2020
  InstallationDate: Installed on 2020-02-08 (67 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to focal on 2020-04-12 (3 days ago)

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

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

[Touch-packages] [Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

[Simon Déziel]

The 1st SRU for Bionic failed because I typo'ed the path to the binary (rsyslog 
!= rsyslogd).
Focal is fixed and Bionic is left with a 'bad' package in bionic-proposed. I 
don't think redoing the SRU for Bionic is worth it, it's a default *disabled* 
profile after all.

I'd leave things as is or maybe delete the bionic-proposed package as
cleanup if that's easy.

Thanks Rafael!

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  In Progress
Status in rsyslog source package in Disco:
  In Progress
Status in rsyslog source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * rsyslog ships with a (Default disable) apparmor profile.
   * Security sensitive users are in general encouraged to enable such
     profiles but unfortunately due to slightly new behavior of the program
     the profile prevents its usage.
   * Allow the program to map/read its binary to get this working again

  [Test Case]

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  [Regression Potential]

   * This is just opening up the apparmor profile a bit. Therefore the only
     regression it could cause IMHO is a security issue. But then what it
     actually allows is reading (not writing!) its own binary which should
     be very safe.
   * Thinking further it came to my mind that package updates (independent 
 to the change) might restart services and that means if there is any 
 issue e.g. in a local config that worked but now fails (not by this 
 change but in general) then the upgrade will not cause, but trigger 
 this. This is a general regression risk for any upload, but in this 
 case worth to mention as it is about log handling - which if broken - 
 makes large scale systems hard to debug.

  [Other Info]

   * n/a

  ---

  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  Workaround:

    echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog

  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1873017] Re: Error when install lvm2 on ubuntu 20.04

[Yiu Man Ho]

This error show three times:

1. I want to install GnuGo from gnome-software
2. I want to continue the lvm2 install manually
3. I want to re-install lvm2 manually

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

Title:
  Error when install lvm2 on ubuntu 20.04

Status in lvm2 package in Ubuntu:
  New

Bug description:
  I am using chinese so some log will use chinese.
  These is the logs that i found on terminal:

  解開 lvm2 (2.03.07-1ubuntu1) 中...
  設定 lvm2 (2.03.07-1ubuntu1) ...
  update-initramfs: deferring update (trigger activated)
  Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked.
  invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed.
  ● lvm2-lvmpolld.service - LVM2 poll daemon
   Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; 
vendor p
  reset: enabled)
   Active: inactive (dead)
     Docs: man:lvmpolld(8)
  dpkg: error processing package lvm2 (--configure):
   installed lvm2 package post-installation script 子進程傳回了 1 錯誤退出狀態碼
  執行 systemd (245.4-2ubuntu1) 的觸發程式……
  執行 man-db (2.9.1-1) 的觸發程式……
  執行 ureadahead (0.100.0-21) 的觸發程式……
  ureadahead will be reprofiled on next reboot
  執行 initramfs-tools (0.136ubuntu6) 的觸發程式……
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  I: The initramfs will attempt to resume from /dev/sda6
  I: (UUID=52eb06e0-e84e-4146-be3b-e07513046207)
  I: Set the RESUME variable to override this.
  Warning: Not updating LILO; /etc/lilo.conf not found!
  處理時發生錯誤：
   lvm2
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:17:22 2020
  InstallationDate: Installed on 2020-02-08 (67 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to focal on 2020-04-12 (3 days ago)

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

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

[Touch-packages] [Bug 1872162] Re: crash report fail to submit

[Brian Murray]

apport does create or use a submit.log file.

** Package changed: apport (Ubuntu) => firefox (Ubuntu)

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

Title:
  crash report fail to submit

Status in firefox package in Ubuntu:
  New

Bug description:
  Since 2020-03-19, firefox crashed about 17 times (it did not crash 1,5
  years before). Though, all crash reports failed to submit. My firefox
  crash report submit.log reads:

  [Mo 17 Dez 2018 00:14:42 CET] Crash report submitted successfully
  [Do 19 Mär 2020 00:06:24 CET] Crash report submission failed: Couldn't 
connect to server
  [Sa 21 Mär 2020 15:14:19 CET] Crash report submission failed: Couldn't 
connect to server
  [Di 24 Mär 2020 23:22:51 CET] Crash report submission failed: Couldn't 
connect to server
  [Mi 25 Mär 2020 14:22:41 CET] Crash report submission failed: Couldn't 
connect to server
  [Do 26 Mär 2020 17:40:46 CET] Crash report submission failed: Couldn't 
connect to server
  [Sa 28 Mär 2020 10:59:32 CET] Crash report submission failed: Couldn't 
connect to server
  [Mo 30 Mär 2020 01:03:56 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 01 Apr 2020 16:01:11 CEST] Crash report submission failed: Couldn't 
connect to server
  [Do 02 Apr 2020 20:39:29 CEST] Crash report submission failed: Couldn't 
connect to server
  [Fr 03 Apr 2020 21:07:53 CEST] Crash report submission failed: Couldn't 
connect to server
  [So 05 Apr 2020 22:38:08 CEST] Crash report submission failed: Couldn't 
connect to server
  [Di 07 Apr 2020 21:40:43 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 08 Apr 2020 13:05:39 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 08 Apr 2020 20:16:28 CEST] Crash report submission failed: Couldn't 
connect to server
  [Mi 08 Apr 2020 22:27:58 CEST] Crash report submission failed: Couldn't 
connect to server
  [Do 09 Apr 2020 23:36:31 CEST] Crash report submission failed: Couldn't 
connect to server
  [Fr 10 Apr 2020 20:07:48 CEST] Crash report submission failed: Couldn't 
connect to server

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

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

[Touch-packages] [Bug 1872875] Re: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

[Raymond Kimathi]

Thank you for the workaround (learning a lot by participating in Ubuntu
Beta testing week!)


libva info: VA-API version 1.7.0
libva info: User environment variable requested driver 'i965'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.7 (libva 2.6.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Gemini Lake - 2.4.0
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileH264MultiviewHigh  : VAEntrypointVLD
  VAProfileH264MultiviewHigh  : VAEntrypointEncSlice
  VAProfileH264StereoHigh : VAEntrypointVLD
  VAProfileH264StereoHigh : VAEntrypointEncSlice
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileVP8Version0_3  : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointEncSlice
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointEncSlice
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile0: VAEntrypointEncSlice
  VAProfileVP9Profile2: VAEntrypointVLD

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

Title:
  [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

Status in Libva:
  Unknown
Status in libva package in Ubuntu:
  Confirmed
Status in obs-studio package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  System selects wrong intel driver (iris_drv_video.so). Therefore cannot use 
vaapi hardware decoding

  vainfo:

  libva info: VA-API version 1.7.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

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

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

[Touch-packages] [Bug 1872875] Re: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

[Horst Schirmeier]

OBS Studio error message w/o the workaround, to help others find the
aforementioned temporary solution: "Starting the output failed. Please
check the log for details."

info: [FFMPEG VAAPI encoder: 'streaming_h264'] settings:
device:   /dev/dri/renderD128
rate_control: CBR
profile:  578
level:40
qp:   0
bitrate:  2500
maxrate:  2500
keyint:   60
width:1920
height:   1080
b-frames: 0

[h264_vaapi @ 0x55bae7f246c0] Driver does not support any RC mode compatible 
with selected options (supported modes: CQP).
warning: [FFMPEG VAAPI encoder: 'streaming_h264'] Failed to open VAAPI codec: 
Invalid argument

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

Title:
  [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

Status in Libva:
  Unknown
Status in libva package in Ubuntu:
  Confirmed
Status in obs-studio package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  System selects wrong intel driver (iris_drv_video.so). Therefore cannot use 
vaapi hardware decoding

  vainfo:

  libva info: VA-API version 1.7.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

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

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

[Touch-packages] [Bug 1872875] Re: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

[Horst Schirmeier]

This also affects OBS Studio (focal package obs-studio), which fails to
record using VAAPI hardware encoding due to this bug.

Workaround: Start obs with the LIBVA_DRIVER_NAME environment variable
set to the driver matching your Intel hardware, e.g. the following for
my Intel Skylake CPU.

LIBVA_DRIVER_NAME=i965 obs

** Also affects: libva via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956281
   Importance: Unknown
   Status: Unknown

** Also affects: obs-studio (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

Status in Libva:
  Unknown
Status in libva package in Ubuntu:
  Confirmed
Status in obs-studio package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04
  System selects wrong intel driver (iris_drv_video.so). Therefore cannot use 
vaapi hardware decoding

  vainfo:

  libva info: VA-API version 1.7.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

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

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

[Touch-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends

[Jeremy Bicha]

@AsciiWorld, unless things changed in Ubuntu 20.04 LTS, you can use the
Software app to install GNOME Shell extensions.

chrome-gnome-shell is in universe. It needs to be in main before it can
be installed by default in the Canonical-supported flavors. See
https://wiki.ubuntu.com/MainInclusionProcess and bug 1695565

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

Title:
  Add chrome-gnome-shell to ubuntu-desktop recommends

Status in One Hundred Papercuts:
  Opinion
Status in chrome-gnome-shell package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Opinion

Bug description:
  Please, consider adding the chrome-gnome-shell package as a
  recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The
  chrome-gnome-shell package provides GNOME Shell integration
  (connector) for Firefox, Chrome, Chromium and other web browsers that
  is necessary for users to be able to manage GNOME Shell extensions
  using a extensions.gnome.org website. Since the Shell Extensions
  support was removed from gnome-software since 3.36 and the replacement
  Extensions application cannot be used to find and install new
  extensions, there is not any user friendly way to install new Shell
  Extensions without having the chrome-gnome-shell package installed.

  More information:
  https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome

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

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

[Touch-packages] [Bug 1856407] Re: nvidia-435 is in eoan, linux-restricted-modules only builds against 430, ubiquity gives me the self-signed modules experience instead of using the Canonical-signed m

[dann frazier]

The ubuntu-drivers-common task here appears to be to change it to prefer
the pre-built/signed drivers (linux-modules-nvidia-*) over the DKMS
counterparts. I'd recommend at that point that we start seeding linux-
modules-nvidia-[0-9]+-generic onto the desktop ISO instead of the DKMS
counterparts, so the offline install experiences matches.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  nvidia-435 is in eoan, linux-restricted-modules only builds against
  430, ubiquity gives me the self-signed modules experience instead of
  using the Canonical-signed modules

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  New
Status in linux source package in Eoan:
  Fix Released
Status in linux-restricted-modules source package in Eoan:
  Fix Released
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed
Status in ubuntu-meta source package in Eoan:
  New

Bug description:
  SRU Justification

  Impact: The nvidia-435 drivers are missing from linux-restricted-
  modules in eoan. On install ubuntu-drivers picks 435 as the newest
  version, and users must use self-signed dkms drivers and enroll a MOK.

  Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.

  Test Case: A test build is available in ppa:sforshee/test-builds.
  Verify that signed drivers for nvidia-435 can be installed for eoan
  via the linux-modules-nvidia-435-{generic,lowlatency} packages.

  Regression Potential: The nvidia-435 l-r-m drivers are new packages
  built from the same source as the nvidia-435 dkms driver, so
  regressions are unlikely.

  ---

  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of
  having to locally self-sign and enroll a signing key through MOK.  But
  lrm in eoan is only building driver packages for nvidia 390 and 430,
  and nvidia 435 is present in eoan.

  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.

  We should never allow the archive to get into this situation.  We
  should be enforcing that any version of the nvidia driver that we
  expect ubuntu-drivers to install by default on any hardware is
  integrated into linux-restricted-modules, and we should ensure that
  ubuntu-drivers always prefers the signed drivers over other options.

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

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

[Touch-packages] [Bug 1872875] Re: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

[Horst Schirmeier]

Related (and fixed in Debian?): https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=956281

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

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

Title:
  [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

Status in libva package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04
  System selects wrong intel driver (iris_drv_video.so). Therefore cannot use 
vaapi hardware decoding

  vainfo:

  libva info: VA-API version 1.7.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

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

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

[Touch-packages] [Bug 1872875] Re: [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

[Launchpad Bug Tracker]

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

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

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

Title:
  [Focal] Intel libva va_openDriver() returns -1 (VA-API broken)

Status in libva package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04
  System selects wrong intel driver (iris_drv_video.so). Therefore cannot use 
vaapi hardware decoding

  vainfo:

  libva info: VA-API version 1.7.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iris_drv_video.so
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit

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

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

[Touch-packages] [Bug 1867029] Re: Package ifupdown breaks network configuration by cloud-init

[Chad Smith]

** Changed in: cloud-init
   Status: In Progress => Fix Committed

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

Title:
  Package ifupdown breaks network configuration by cloud-init

Status in cloud-init:
  Fix Committed
Status in ifupdown package in Ubuntu:
  New

Bug description:
  It appears the `ifupdown` package breaks networking configuration that
  cloud-init would normally handle (?) on both providers. The result, if
  you image an instance with the `ifupdown` package installed, is that
  the image is not bootable by Azure/AWS. I'm not familiar with how
  Azure/AWS/etc use cloud-init for network start up however. I'm filing
  here for now, in case `cloud-init` needs to be more defensive against
  `ifupdown`.

  To reproduce with Packer (I confirmed this method):

  * Add necessary Azure subscription env vars from `ifupdown-bug.json`
  * `packer build ifupdown-bug.json`
  * Try to boot an instance with resulting image
  * Instance will never boot -- more specifically, networking never comes up. 
See `boot.log` for an example boot

  To reproduce manually (only a guess, I did not confirm):

  * Boot 18.04 ubuntu instance
  * Install ifupdown
  * Image the instance
  * Try to boot instance using new image
  * Instance won't boot

  I hit this with Packer, creating new images for booting instances in
  scaling groups -- `ifupdown` is brought in by `salt`. If this is
  reproducible via manual installation, there could be some backup
  images/snapshots that are unable to boot though.

  This appears to be because cloud-init network start up operations are
  broken by whatever `ifupdown` sysv/systemd scripts perform on boot.
  With `ifupdown` installed on Azure, `eth0` does not get an IP address,
  the instance never fully boots according to Azure, and it will enter
  an error state. On AWS, the instance boots, but network operations
  like SSH fail.

  The `boot.log` is from Azure. Eventually `cloud-init` gives an
  exception (see `exception.log`), but this seems like a secondary issue
  related to networking being down.

  I did try to upgrade cloud-init using nightly PPAs (version 20.1 I
  believe), but no luck. This is on Ubuntu 18.04 instances from Azure
  marketplace and AWS Canonical AMI, cloud-init version
  `19.4-33-gbb4131a2-0ubuntu1~18.04.1`.

  Related: https://github.com/Azure/WALinuxAgent/issues/1612

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1867029/+subscriptions

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

[Touch-packages] [Bug 1872124] Re: Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

[Lee Trager]

MAAS contains a way to automatically install drivers. Every region has a
file, /etc/maas/drivers.yaml, which specifies drivers which should be
automatically installed. I don't have access to any test hardware but I
*think* this should work. One thing I noticed is there isn't a meta
package for the nVidia driver which points to the latest version for
each Ubuntu release. We would need that before adding this to MAAS.

diff --git a/drivers-orig.yaml b/drivers.yaml
index 2d3724c..97a4eb2 100644
--- a/drivers-orig.yaml
+++ b/drivers.yaml
@@ -82,3 +82,10 @@ drivers:
   repository: http://downloads.linux.hpe.com/SDR/repo/ubuntu-hpdsa
   series:
 - trusty
+- blacklist: nouveau
+  comment: nVidia driver
+  modaliases:
+  - 'pci:v10DEd*sv*sd*bc03sc02i00*'
+  - 'pci:v10DEd*sv*sd*bc03sc00i00*'
+  - module: nvidia
+  - package: nvidia-headless-440

** Changed in: maas
   Status: New => Triaged

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

Title:
  Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in subiquity:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Could subiquity provide an option in the UI to install and execute
  ubuntu-drivers-common on the target? The use case I'm interested in is
  an "on-rails" installation of Nvidia drivers for servers being
  installed for deep learning workloads.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1872124/+subscriptions

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

[Touch-packages] [Bug 1873086] [NEW] sound stutters when playing on a bluetooth receiver

[Tomislav]

Public bug reported:

I can play via bluetooth from my laptop or my mobile phone. I have a set
of bluetooth headphones and bluetooth speakers.

Any combination of output with the smartphone as the player works, which
is as it should be.

Any combination of output with the laptop as the player is miserable:
sound stutters, sometimes randomly, sometimes seemingly when I touch the
laptop or come close to it...had similar or identical problems with a
previous Ubuntu laptop. Bluetooth audio seems to be in very bad shape.

$ lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04

laptop Dell XPS 9370

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.4
ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tna2174 F pulseaudio
 /dev/snd/pcmC0D0p:   tna2174 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 15 22:55:05 2020
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
InstallationDate: Installed on 2018-05-10 (706 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago)
dmi.bios.date: 12/11/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
dmi.board.name: 0W970W
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9370
dmi.product.sku: 07E6
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  sound stutters when playing on a bluetooth receiver

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I can play via bluetooth from my laptop or my mobile phone. I have a
  set of bluetooth headphones and bluetooth speakers.

  Any combination of output with the smartphone as the player works,
  which is as it should be.

  Any combination of output with the laptop as the player is miserable:
  sound stutters, sometimes randomly, sometimes seemingly when I touch
  the laptop or come close to it...had similar or identical problems
  with a previous Ubuntu laptop. Bluetooth audio seems to be in very bad
  shape.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  laptop Dell XPS 9370

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.4
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tna2174 F pulseaudio
   /dev/snd/pcmC0D0p:   tna2174 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 22:55:05 2020
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-05-10 (706 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to bionic on 2020-03-04 (42 days ago)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA05:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1873085] [NEW] initramfs keyboard layout back to qwerty after upgrade

[Alexandre Iooss]

Public bug reported:

After initial installation of Ubuntu 20.04 beta two days ago, I was able
to unlock my disk at boot with an AZERTY keyboard.

Since afternoon upgrade, my initramfs is now in QWERTY and so I need to
input my password in QWERTY which is inconvenient.

This is my APT log from my last upgrade :

```
Start-Date: 2020-04-15  22:51:43
Commandline: apt upgrade
Requested-By: erdnaxe (1000)
Install: appstream:amd64 (0.12.10-2, automatic)
Upgrade: ubuntu-desktop-minimal:amd64 (1.447, 1.448), libdrm-nouveau2:amd64 
(2.4.101-1, 2.4.101-2), libdrm-nouveau2:i386 (2.4.101-1, 2.4.101-2), 
libllvm9:amd64 (1:9.0.1-11ubuntu1, 1:9.0.1-12), libllvm9:i386 
(1:9.0.1-11ubuntu1, 1:9.0.1-12), libsystemd0:amd64 (245.4-2ubuntu1, 
245.4-4ubuntu1), grub-common:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), 
ubuntu-standard:amd64 (1.447, 1.448), ubuntu-desktop:amd64 (1.447, 1.448), 
python-matplotlib-data:amd64 (3.1.2-1ubuntu3, 3.1.2-1ubuntu4), 
python-apt-common:amd64 (1.9.10, 2.0.0), grub2-common:amd64 (2.04-1ubuntu24, 
2.04-1ubuntu25), udev:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), 
python3-matplotlib:amd64 (3.1.2-1ubuntu3, 3.1.2-1ubuntu4), 
nautilus-extension-gnome-terminal:amd64 (3.35.91-0ubuntu1, 3.36.1.1-1ubuntu1), 
grub-pc:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), libudev1:amd64 (245.4-2ubuntu1, 
245.4-4ubuntu1), libudev1:i386 (245.4-2ubuntu1, 245.4-4ubuntu1), 
systemd-timesyncd:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), grub-pc-bin:amd64 
(2.04-1ubuntu24, 2.04-1ubuntu25), ubuntu-minimal:amd64 (1.447, 1.448), 
libdrm-amdgpu1:amd64 (2.4.101-1, 2.4.101-2), libdrm-amdgpu1:i386 (2.4.101-1, 
2.4.101-2), grub-efi-amd64-bin:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), 
python-is-python3:amd64 (3.8.2-3, 3.8.2-4), systemd-sysv:amd64 (245.4-2ubuntu1, 
245.4-4ubuntu1), gnome-shell-common:amd64 (3.36.1-4ubuntu1, 3.36.1-5ubuntu1), 
libpam-systemd:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), libdrm2:amd64 
(2.4.101-1, 2.4.101-2), libdrm2:i386 (2.4.101-1, 2.4.101-2), systemd:amd64 
(245.4-2ubuntu1, 245.4-4ubuntu1), libsdl2-2.0-0:amd64 (2.0.10+dfsg1-2ubuntu5, 
2.0.10+dfsg1-3), libnss-systemd:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), 
grub-efi-amd64-signed:amd64 (1.140+2.04-1ubuntu24, 1.141+2.04-1ubuntu25), 
gnome-terminal-data:amd64 (3.35.91-0ubuntu1, 3.36.1.1-1ubuntu1), 
unattended-upgrades:amd64 (2.2, 2.3), libdrm-intel1:amd64 (2.4.101-1, 
2.4.101-2), libdrm-intel1:i386 (2.4.101-1, 2.4.101-2), gnome-shell:amd64 
(3.36.1-4ubuntu1, 3.36.1-5ubuntu1), libdrm-radeon1:amd64 (2.4.101-1, 
2.4.101-2), libdrm-radeon1:i386 (2.4.101-1, 2.4.101-2), apport-symptoms:amd64 
(0.22, 0.23), gnome-terminal:amd64 (3.35.91-0ubuntu1, 3.36.1.1-1ubuntu1), 
python3-apt:amd64 (1.9.10, 2.0.0), libdrm-common:amd64 (2.4.101-1, 2.4.101-2)
End-Date: 2020-04-15  22:55:07
```

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 15 23:17:43 2020
InstallationDate: Installed on 2020-04-13 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/zsh
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1873085

Title:
  initramfs keyboard layout back to qwerty after upgrade

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After initial installation of Ubuntu 20.04 beta two days ago, I was
  able to unlock my disk at boot with an AZERTY keyboard.

  Since afternoon upgrade, my initramfs is now in QWERTY and so I need
  to input my password in QWERTY which is inconvenient.

  This is my APT log from my last upgrade :

  ```
  Start-Date: 2020-04-15  22:51:43
  Commandline: apt upgrade
  Requested-By: erdnaxe (1000)
  Install: appstream:amd64 (0.12.10-2, automatic)
  Upgrade: ubuntu-desktop-minimal:amd64 (1.447, 1.448), libdrm-nouveau2:amd64 
(2.4.101-1, 2.4.101-2), libdrm-nouveau2:i386 (2.4.101-1, 2.4.101-2), 
libllvm9:amd64 (1:9.0.1-11ubuntu1, 1:9.0.1-12), libllvm9:i386 
(1:9.0.1-11ubuntu1, 1:9.0.1-12), libsystemd0:amd64 (245.4-2ubuntu1, 
245.4-4ubuntu1), grub-common:amd64 (2.04-1ubuntu24, 2.04-1ubuntu25), 
ubuntu-standard:amd64 (1.447, 1.448), ubuntu-desktop:amd64 (1.447, 1.448), 
python-matplotlib-data:amd64 (3.1.2-1ubuntu3, 3.1.2-1ubuntu4), 
python-apt-common:amd64 (1.9.10, 2.0.0), grub2-common:amd64 (2.04-1ubuntu24, 
2.04-1ubuntu25), udev:amd64 (245.4-2ubuntu1, 245.4-4ubuntu1), 
python3-matplotlib:amd64 (3.1.2-1ubuntu3, 3.1.2-1ubuntu4), 

[Touch-packages] [Bug 1872124] Re: ubuntu-drivers-common integration

[Dimitri John Ledkov]

I don't think that implementing just subiquity is enough. Ubiquity was
the last piece of ubuntu-drivers integration on the Desktop, as update-
manager continiously was already checking for any new drivers that are
available for the systems' hardware, and continiously providing
notifications to install / switch between new alternatives / dismiss
installing drivers, on continuous basis post-install / post-upgrade.
Doing this during install, simply moved that step from post-install to
pre-install.

Ubuntu Server currently does not have ubuntu-drivers integration with
motd, unattanded upgrades, and apt output to notify users of the newly
available driver implementations, and how to opt into them.

Command line tooling exists, but currently only used non-interactively
by cloud-init on some compatible public clouds.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-drivers-common (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: maas
   Importance: Undecided
   Status: New

** Summary changed:

- ubuntu-drivers-common integration
+ Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

** Also affects: cloud-init
   Importance: Undecided
   Status: New

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

Title:
  Please integrate ubuntu-drivers --gpgpu into Ubuntu Server

Status in cloud-init:
  New
Status in MAAS:
  New
Status in subiquity:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Could subiquity provide an option in the UI to install and execute
  ubuntu-drivers-common on the target? The use case I'm interested in is
  an "on-rails" installation of Nvidia drivers for servers being
  installed for deep learning workloads.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1872124/+subscriptions

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

[Touch-packages] [Bug 1759247] Re: lxc-copy forgets to change /etc/hostname and /etc/hosts

[Serge Hallyn]

Tested this in eoan - hostname had the new name.

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

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

Title:
  lxc-copy forgets to change /etc/hostname and /etc/hosts

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  LXC 2.x behaved like this when cloning containers: it wrote the new
  hostname into /etc/hostname of the new container, and changed
  /etc/hosts accordingly. LXC 3.0.0.beta3 no longer does it.

  root@zh1cn:/var/lib/lxc# lxc-create -t download -n ubuntu-1604-new -- -d 
ubuntu -a amd64 -r xenial
  Setting up the GPG keyring
  Downloading the image index
  Downloading the rootfs
  Downloading the metadata
  The image cache is now ready
  Unpacking the rootfs

  ---
  You just created an Ubuntu container (release=xenial, arch=amd64, 
variant=default)

  To enable sshd, run: apt-get install openssh-server

  For security reason, container images ship without user accounts
  and without a root password.

  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.


  root@zh1cn:/var/lib/lxc# cat ubuntu-1604-new/config 
  # Template used to create this container: 
/usr/share/lxc/templates/lxc-download
  # Parameters passed to the template: -d ubuntu -a amd64 -r xenial
  # Template script checksum (SHA-1): 5f6cea9c51537459a7ab5f81e2c1eac6a94b5e08
  # For additional config options, please look at lxc.container.conf(5)

  # Uncomment the following line to support nesting containers:
  #lxc.include = /usr/share/lxc/config/nesting.conf
  # (Be aware this has security implications)

  
  # Distribution configuration
  lxc.include = /usr/share/lxc/config/common.conf
  lxc.arch = x86_64

  # Container specific configuration
  lxc.rootfs.path = dir:/var/lib/lxc/ubuntu-1604-new/rootfs
  lxc.uts.name = ubuntu-1604-new

  # Network configuration
  lxc.net.0.type = veth
  lxc.net.0.link = lxcbr0
  lxc.net.0.flags = up
  lxc.net.0.hwaddr = 00:16:3e:65:85:6b


  root@zh1cn:/var/lib/lxc# cat ubuntu-1604-new/rootfs/etc/hostname 
  ubuntu-1604-new


  root@zh1cn:/var/lib/lxc# lxc-copy -n ubuntu-1604-new -N
  ubuntu-1604-new1


  root@zh1cn:/var/lib/lxc# cat ubuntu-1604-new1/config
  # Template used to create this container: 
/usr/share/lxc/templates/lxc-download
  # Parameters passed to the template: -d ubuntu -a amd64 -r xenial
  # Template script checksum (SHA-1): 5f6cea9c51537459a7ab5f81e2c1eac6a94b5e08
  # For additional config options, please look at lxc.container.conf(5)
  # Uncomment the following line to support nesting containers:
  #lxc.include = /usr/share/lxc/config/nesting.conf
  # (Be aware this has security implications)
  # Distribution configuration
  lxc.include = /usr/share/lxc/config/common.conf
  lxc.arch = x86_64
  # Container specific configuration
  # Network configuration
  lxc.net.0.type = veth
  lxc.net.0.link = lxcbr0
  lxc.net.0.flags = up
  lxc.net.0.hwaddr = 00:16:3e:ec:9a:54
  lxc.rootfs.path = dir:/var/lib/lxc/ubuntu-1604-new1/rootfs
  lxc.uts.name = ubuntu-1604-new1


  root@zh1cn:/var/lib/lxc# cat ubuntu-1604-new1/rootfs/etc/hostname 
  ubuntu-1604-new

  I would expect ubuntu-1604-new1 here, or maybe no such file at all (so
  that lxc.uts.name applies from the config).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lxc 3.0.0~beta3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  Date: Tue Mar 27 19:21:21 2018
  InstallationDate: Installed on 2018-01-25 (61 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180120)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm
   SHELL=/bin/bash
   PATH=(custom, no user)
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.net.0.type = veth
   lxc.net.0.link = lxcbr0
   lxc.net.0.flags = up
   lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx

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

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

[Touch-packages] [Bug 1872970] Re: pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail device

[Sebastien Bacher]

Thank you for the bug report

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

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

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

Title:
  pulseaudio (1:13.99.1-1ubuntu2) no sound on Bay and Cherry trail
  device

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  I install ubuntu focal, no sound on my Cherry trail device, it has a es8316 
sound card.
  downgrade pulseaudio_13.0-1ubuntu1.1 sound work.

  https://bugzilla.redhat.com/show_bug.cgi?id=1818883
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/276/

  please build next pulseaudio include patch, ucm: fix the port / ucm device 
activation on boot
  alsa sink/source: fix the mixer initialization

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

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

[Touch-packages] [Bug 1873072] [NEW] nmcli setting wrong value for username in config file

[Mark]

Public bug reported:

If you try to set the username for an openvpn VPN connection via the cli
with the nmcli command, it will set the wrong value in the network
manager system-connections config file.

command example:

nmcli connection modify vpn_name vpn.user-name my.username

the file
/etc/NetworkManager/system-connections/vpn_name.nmconnection

will have the value vpn.user-name set to my.username

This value is not used by network manager or openvpn when trying to
create the VPN connection, the correct value is vpn.username. This is
the value set by the GUI editor.

This appears to be this exact bug reported to Redhat back in 2014.

https://bugzilla.redhat.com/show_bug.cgi?id=1060460

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: network-manager 1.20.4-2ubuntu2.2
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 15 16:29:36 2020
InstallationDate: Installed on 2020-02-13 (62 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
IpRoute:
 default via 192.168.1.1 dev enx98e743e4fd54 proto dhcp metric 100 
 default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
 169.254.0.0/16 dev wlo1 scope link metric 1000 
 192.168.1.0/24 dev enx98e743e4fd54 proto kernel scope link src 192.168.1.192 
metric 100 
 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.193 metric 600
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug eoan

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

Title:
  nmcli setting wrong value for username in config file

Status in network-manager package in Ubuntu:
  New

Bug description:
  If you try to set the username for an openvpn VPN connection via the
  cli with the nmcli command, it will set the wrong value in the network
  manager system-connections config file.

  command example:

  nmcli connection modify vpn_name vpn.user-name my.username

  the file
  /etc/NetworkManager/system-connections/vpn_name.nmconnection

  will have the value vpn.user-name set to my.username

  This value is not used by network manager or openvpn when trying to
  create the VPN connection, the correct value is vpn.username. This is
  the value set by the GUI editor.

  This appears to be this exact bug reported to Redhat back in 2014.

  https://bugzilla.redhat.com/show_bug.cgi?id=1060460

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 16:29:36 2020
  InstallationDate: Installed on 2020-02-13 (62 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev enx98e743e4fd54 proto dhcp metric 100 
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev enx98e743e4fd54 proto kernel scope link src 192.168.1.192 
metric 100 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.193 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1872980] Re: Add field for PresentationIdentity in Online Accounts GUI

[Steven Jay Cohen]

Will do!

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

Title:
  Add field for PresentationIdentity in Online Accounts GUI

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

Bug description:
  Version: focal,now 3.36.0-1ubuntu1 amd64

  ~/.config/goa-1.0/accounts.conf has a field called
  PresentationIdentity. When setting up a Google Account for example,
  that field gets set to the email address. This field is used in places
  like Nautilus to show which accounts something is connected to. If the
  addresses are similar (and long) this can be a bit confusing.

  Example:

  johnjacobjingleheilmerschm...@gmail.com
  johnjacob...@school.edu

  If there were an option in the GUI to set the name (to Gmail and
  School in this example), there would be less confusion in places like
  Nautilus.

  Visual Example:

  __|
  johnjacobj|
  johnjacobj|
  __|

  Becomes:

  __|
  Gmail |
 School |
  __|

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1872980/+subscriptions

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

[Touch-packages] [Bug 1321854] Re: useradd doesn't add the default shell to /etc/passwd entry

[Serge Hallyn]

Tested this in eoan.  New user got the SHELL=zsh which I specified in
/etc/default/useradd

** Changed in: shadow (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  useradd doesn't add the default shell to /etc/passwd entry

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Trusty:
  Triaged

Bug description:
  useradd is not honoring the default shell listed in
  /etc/defaults/useradd when creating new users.

  useradd -D showing the defaults. SHELL=/bin/bash

  # useradd -D
  GROUP=100
  HOME=/home
  INACTIVE=-1
  EXPIRE=
  SHELL=/bin/bash
  SKEL=/etc/skel
  CREATE_MAIL_SPOOL=no

  Using useradd to create user test1. The /etc/passwd entry has a blank
  shell field:

  # useradd test1
  # grep test1 /etc/passwd
  test1:x:2080:2080::/home/test1:

  Using useradd -s does populate the shell field:
  # useradd -s /bin/bash test2
  #grep test2 /etc/passwd
  test2:x:2081:2081::/home/test2:/bin/bash

  Why useradd instead of adduser: puppet uses useradd to do user
  creation.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: passwd 1:4.1.5.1-1ubuntu9
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Wed May 21 17:51:57 2014
  Ec2AMI: ami-42dc302a
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: m3.large
  Ec2Kernel: aki-919dcaf8
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: shadow
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.default.useradd: 2014-05-21T17:36:05.208686

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

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

[Touch-packages] [Bug 1869447] Re: python-is-python3 & python-is-python2 do not Provides: python

[Liz Fong-Jones]

what-is-python (4) solves this.

** Changed in: what-is-python (Ubuntu)
   Status: New => Fix Released

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

Title:
  python-is-python3 & python-is-python2 do not Provides: python

Status in python-defaults package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Invalid
Status in what-is-python package in Ubuntu:
  Fix Released

Bug description:
  This is a bug in Focal prerelease.

  Third-party packages like Steam currently appear to Depend: upon
  python, but nothing Provides: python, only Conflicts: python.

  I believe that python-is-... should Provide: python so that packages
  that expect to use /usr/bin/python aren't surprised.

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

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

[Touch-packages] [Bug 1869447] Re: python-is-python3 & python-is-python2 do not Provides: python

[Liz Fong-Jones]

Solved by what-is-python (4)

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

Title:
  python-is-python3 & python-is-python2 do not Provides: python

Status in python-defaults package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Invalid
Status in what-is-python package in Ubuntu:
  Fix Released

Bug description:
  This is a bug in Focal prerelease.

  Third-party packages like Steam currently appear to Depend: upon
  python, but nothing Provides: python, only Conflicts: python.

  I believe that python-is-... should Provide: python so that packages
  that expect to use /usr/bin/python aren't surprised.

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

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

[Touch-packages] [Bug 185165] Re: Ubuntu does not open MS Windows internet shortcuts with 'url' extension

[alexdd]

Is interoperability an official goal of ubuntu? Anybody know?

If yes, this should get fixed. Was reported 12 years ago.

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

Title:
  Ubuntu does not open MS Windows internet shortcuts with 'url'
  extension

Status in Ayatana Design:
  Fix Committed
Status in Gnome Mime-Data:
  Fix Released
Status in One Hundred Papercuts:
  Invalid
Status in gnome-mime-data package in Ubuntu:
  Fix Released
Status in mime-support package in Ubuntu:
  Triaged
Status in shared-mime-info package in Ubuntu:
  Triaged

Bug description:
  Ubuntu will not open standard internet shortcuts created in Microsoft
  Windows.  This makes interoperability very poor, and will prevent many
  people from migrating to Ubuntu.

  Copy any 'filename.url' from a Microsoft Windows machine, or create a
  file with the following contents:

  [DEFAULT]
  BASEURL=http://www.ubuntu.com
  [InternetShortcut]
  URL=http://www.ubuntu.com

  and name it 'ubuntu.url'.

  Double click in Nautilus to launch.  Nothing happens.  It should
  launch in the same manner as a 'desktop' internet shortcut.

  Note: a workaround has been developed -
  http://ubuntuforums.org/showthread.php?p=3281092.  This should be
  provided by default Ubuntu installation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/185165/+subscriptions

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

[Touch-packages] [Bug 1872917] Re: Laptop does not recognize it's charging

[Sebastien Bacher]

Thank you for your bug report, could you include the 'upower -d' output
at the time of the issue?

** Package changed: gnome-power-manager (Ubuntu) => upower (Ubuntu)

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

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

Title:
  Laptop does not recognize it's charging

Status in upower package in Ubuntu:
  Incomplete

Bug description:
  I'm using a pretty new Lenovo Thinkpad X1 Extreme G2. Since a few
  days, the laptop does not recognize that its charging all the time.
  It's showing the battery icon and a percent number. This must be
  broken a couple of days or weeks ago, this was working when I
  installed Ubuntu 19.10.

  It does not depend from dock or directly connecting the AC adapter.

  Incredibly long battery life time is shown, see screenshot. (laptop
  was connected to AC during this)

  This is a problem because for example firmware upgrades does not work
  because they require "AC-connected state".

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

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

[Touch-packages] [Bug 1862925] Re: libtool-doc gives dpkg error on install

[Sebastien Bacher]

The issue has been fixed in that update,
https://launchpad.net/ubuntu/+source/libtool/2.4.6-14

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

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

Title:
  libtool-doc gives dpkg error on install

Status in libtool package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 20.04 development branch with kernel 5.4.0-12-generic system up
  to date @ 12/2/2020

  Installing libtool-doc gives a dpkg error on install:

  lotuspsychje @ RooTBoX: ~ $ sudo apt install libtool-doc
  Package lists are read ... Ready
  Tree of requirements is being built
  The status information is read ... Ready
  The following NEW packages will be installed:
libtool doc
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  0 B / 232 kB of archives must be retrieved.
  After this operation, an additional 1,072 kB of disk space will be used.
  (Database is being read ... 247912 files and folders currently installed
  .)
  Unpacking ... / libtool-doc_2.4.6-12_all.deb is being prepared ...
  Unpacking libtool-doc (2.4.6-12) ...
  dpkg: Error processing archive /var/cache/apt/archives/libtool-doc_2.4.6-1
  2_all.deb (--unpack):
   attempt to overwrite '/ usr / share / doc / libtool / AUTHORS', whatever in 
package
  t libtool 2.4.6-12
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors found while processing:
   /var/cache/apt/archives/libtool-doc_2.4.6-12_all.deb
  E: Sub-process / usr / bin / dpkg returned an error code (1)

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

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

[Touch-packages] [Bug 1863356] Re: libtool and libtool-doc 2.4.6-12 both contain /usr/share/doc/libtool/AUTHORS causing upgrade failures

[Sebastien Bacher]

The issue has been fixed in that update,
https://launchpad.net/ubuntu/+source/libtool/2.4.6-14

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

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

Title:
  libtool and libtool-doc 2.4.6-12 both contain
  /usr/share/doc/libtool/AUTHORS causing upgrade failures

Status in libtool package in Ubuntu:
  Fix Released
Status in libtool package in Debian:
  Fix Released

Bug description:
  Unpacking libtool-doc (2.4.6-12) over (2.4.6-11) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-tTUGeR/289-libtool-doc_2.4.6-12_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libtool/AUTHORS', which is also in 
package libtool 2.4.6-12
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libtool 2.4.6-12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: i3
  Date: Fri Feb 14 09:04:32 2020
  InstallationDate: Installed on 2017-12-15 (790 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libtool
  UpgradeStatus: Upgraded to focal on 2019-09-23 (144 days ago)

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

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

[Touch-packages] [Bug 1872980] Re: Add field for PresentationIdentity in Online Accounts GUI

[Sebastien Bacher]

Thank you for the bug report, it seems like a request better placed
upstream, could you submit it on https://gitlab.gnome.org/GNOME/gnome-
online-accounts/-/issues ?

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Add field for PresentationIdentity in Online Accounts GUI

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

Bug description:
  Version: focal,now 3.36.0-1ubuntu1 amd64

  ~/.config/goa-1.0/accounts.conf has a field called
  PresentationIdentity. When setting up a Google Account for example,
  that field gets set to the email address. This field is used in places
  like Nautilus to show which accounts something is connected to. If the
  addresses are similar (and long) this can be a bit confusing.

  Example:

  johnjacobjingleheilmerschm...@gmail.com
  johnjacob...@school.edu

  If there were an option in the GUI to set the name (to Gmail and
  School in this example), there would be less confusion in places like
  Nautilus.

  Visual Example:

  __|
  johnjacobj|
  johnjacobj|
  __|

  Becomes:

  __|
  Gmail |
 School |
  __|

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1872980/+subscriptions

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

[Touch-packages] [Bug 1872917] [NEW] Laptop does not recognize it's charging

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm using a pretty new Lenovo Thinkpad X1 Extreme G2. Since a few days,
the laptop does not recognize that its charging all the time. It's
showing the battery icon and a percent number. This must be broken a
couple of days or weeks ago, this was working when I installed Ubuntu
19.10.

It does not depend from dock or directly connecting the AC adapter.

Incredibly long battery life time is shown, see screenshot. (laptop was
connected to AC during this)

This is a problem because for example firmware upgrades does not work
because they require "AC-connected state".

** Affects: upower (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: battery charging power
-- 
Laptop does not recognize it's charging
https://bugs.launchpad.net/bugs/1872917
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to upower in Ubuntu.

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

[Touch-packages] [Bug 1740159] Re: Can't sync iPod (touch 2G): device recognized by file manager but not by media players / managers

[Sebastien Bacher]

Thank you for your bug report, looks like you are using elementary OS,
not Ubuntu, please report the issue to them

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

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

Title:
  Can't sync iPod (touch 2G): device recognized by file manager but not
  by media players / managers

Status in libimobiledevice package in Ubuntu:
  Invalid

Bug description:
  Can't sync iPod (touch 2G): when mounting in file manager, the access
  address afc://[device uuid] appends a ":3" at the end, so it turns to
  afc://[uuid]:3, which the file manager shows as an empty location.

  There are 2 devices / mount points after connecting the iPod and opening a 
file manager:
  -"iPod"; when clicking "properties", the protocol used for it is gphoto2:// 
(?)
  -"iPod Documentation"; this mount point is opened via afc://[device uuid], 
and should show the iPod's root file system. 
  Removing the ":3" at the end and entering afc://[device uuid] manually shows 
the iPod's root filesystem, which could in theory be managed by gtkpod, 
Rhythmbox or Banshee.

  However, I can't seem to find a way to disable the arbitrary ":3" added 
automatically by the mounter.
  This behaviour began after updating the library (it has worked fine before, 
in the same OS in 2 different machines, being able to transfer music files).

  I've googled for a week looking for a similar problem reported, and none was 
found so far, hence the bug report.
  Please let me know what other culprit there may be, to begin pinpointing the 
cause somewhere else, if necessary.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: libimobiledevice6 1.2.0+dfsg-3~ubuntu0.2 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Tue Dec 26 14:38:47 2017
  InstallationDate: Installed on 2017-09-24 (93 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
  SourcePackage: libimobiledevice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1872153] Re: gsd-usb-protection crashed with SIGSEGV in g_source_set_ready_time()

[Sebastien Bacher]

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: gnome-settings-daemon (Ubuntu)
   Importance: Low => High

** Package changed: gnome-settings-daemon (Ubuntu) => glib2.0 (Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2091
   https://gitlab.gnome.org/GNOME/glib/-/issues/2091

** Also affects: glib via
   https://gitlab.gnome.org/GNOME/glib/-/issues/2091
   Importance: Unknown
   Status: Unknown

** Summary changed:

- gsd-usb-protection crashed with SIGSEGV in g_source_set_ready_time()
+ SIGSEGV in g_source_set_ready_time()

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

Title:
  SIGSEGV in g_source_set_ready_time()

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  cuando abro software ubuntu ma  aparece tramsparente sin fondo iconos
  solos

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-settings-daemon 3.36.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 19:48:54 2020
  ExecutablePath: /usr/libexec/gsd-usb-protection
  InstallationDate: Installed on 2020-04-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/gsd-usb-protection
  ProcEnviron:
   LANG=es_AR.UTF-8
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7faa5f4a2bf3 :   cmp
0x10(%rax),%rbp
   PC (0x7faa5f4a2bf3) ok
   source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
   destination "%rbp" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-settings-daemon
  StacktraceTop:
   g_source_set_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gsd-usb-protection crashed with SIGSEGV in g_source_set_ready_time()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  separator:

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

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

[Touch-packages] [Bug 1740159] Re: Can't sync iPod (touch 2G): device recognized by file manager but not by media players / managers

[indigocat]

Any news?

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

Title:
  Can't sync iPod (touch 2G): device recognized by file manager but not
  by media players / managers

Status in libimobiledevice package in Ubuntu:
  New

Bug description:
  Can't sync iPod (touch 2G): when mounting in file manager, the access
  address afc://[device uuid] appends a ":3" at the end, so it turns to
  afc://[uuid]:3, which the file manager shows as an empty location.

  There are 2 devices / mount points after connecting the iPod and opening a 
file manager:
  -"iPod"; when clicking "properties", the protocol used for it is gphoto2:// 
(?)
  -"iPod Documentation"; this mount point is opened via afc://[device uuid], 
and should show the iPod's root file system. 
  Removing the ":3" at the end and entering afc://[device uuid] manually shows 
the iPod's root filesystem, which could in theory be managed by gtkpod, 
Rhythmbox or Banshee.

  However, I can't seem to find a way to disable the arbitrary ":3" added 
automatically by the mounter.
  This behaviour began after updating the library (it has worked fine before, 
in the same OS in 2 different machines, being able to transfer music files).

  I've googled for a week looking for a similar problem reported, and none was 
found so far, hence the bug report.
  Please let me know what other culprit there may be, to begin pinpointing the 
cause somewhere else, if necessary.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: libimobiledevice6 1.2.0+dfsg-3~ubuntu0.2 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  NonfreeKernelModules: nvidia_uvm wl nvidia
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Tue Dec 26 14:38:47 2017
  InstallationDate: Installed on 2017-09-24 (93 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814)
  SourcePackage: libimobiledevice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1865300] Re: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from deep_count_more_files_callback()

[Sebastien Bacher]

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2643
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643

** Also affects: gnome-shell via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2643
   Importance: Unknown
   Status: Unknown

** Tags added: apport-request-retrace

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

Title:
  gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from deep_count_more_files_callback()

Status in GNOME Shell:
  Unknown
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/b6069e75f805530e3c7722835d567cfdb84f2fec
  https://errors.ubuntu.com/problem/2edf29b9677e3de0d55d2114024f39c4c52b45e9

  ---

  Happened during normal use of the desktop.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.34.3-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 19:51:58 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  InstallationDate: Installed on 2020-01-25 (35 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117)
  ProcCmdline: /usr/lib/gnome-shell/gnome-shell-hotplug-sniffer
  RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
  SegvAnalysis:
   Segfault happened at: 0x7f5f54fa6444 : movsbl (%rdi),%eax
   PC (0x7f5f54fa6444) ok
   source "(%rdi)" (0x) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: gnome-shell-hotplug-sniffer crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1865300/+subscriptions

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

[Touch-packages] [Bug 1872153] [NEW] gsd-usb-protection crashed with SIGSEGV in g_source_set_ready_time()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

cuando abro software ubuntu ma  aparece tramsparente sin fondo iconos
solos

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-settings-daemon 3.36.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Greeter:GNOME
Date: Fri Apr 10 19:48:54 2020
ExecutablePath: /usr/libexec/gsd-usb-protection
InstallationDate: Installed on 2020-04-09 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcCmdline: /usr/libexec/gsd-usb-protection
ProcEnviron:
 LANG=es_AR.UTF-8
 LANGUAGE=es_AR:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7faa5f4a2bf3 : cmp
0x10(%rax),%rbp
 PC (0x7faa5f4a2bf3) ok
 source "0x10(%rax)" (0x0010) not located in a known VMA region (needed 
readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_source_set_ready_time () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gsd-usb-protection crashed with SIGSEGV in g_source_set_ready_time()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
separator:

** Affects: glib2.0 (Ubuntu)
 Importance: High
 Status: In Progress


** Tags: amd64 apport-crash focal
-- 
gsd-usb-protection crashed with SIGSEGV in g_source_set_ready_time()
https://bugs.launchpad.net/bugs/1872153
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to glib2.0 in Ubuntu.

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

[Touch-packages] [Bug 1058191] Re: file doesn't recognise all "Linux make config build file[s]"

[Ken Sharp]

Changed again. I guess this will be a never-ending task.

$ file -i /boot/config*
/boot/config-5.3.0-42-generic: text/plain; charset=us-ascii
/boot/config-5.3.0-45-generic: text/plain; charset=us-ascii
/boot/config-5.3.0-46-generic: text/plain; charset=us-ascii

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

Title:
  file doesn't recognise all "Linux make config build file[s]"

Status in file package in Ubuntu:
  Fix Committed

Bug description:
  $ file /boot/config*
  /boot/config-2.6.38-16-generic: Linux make config build file
  /boot/config-2.6.38-8-generic:  Linux make config build file
  /boot/config-3.2.0-30-generic:  ASCII text
  /boot/config-3.2.0-31-generic:  ASCII text

  $ file -i /boot/config*
  /boot/config-2.6.38-16-generic: text/plain; charset=us-ascii
  /boot/config-2.6.38-8-generic:  text/plain; charset=us-ascii
  /boot/config-3.2.0-30-generic:  text/plain; charset=us-ascii
  /boot/config-3.2.0-31-generic:  text/plain; charset=us-ascii

  The files are practically identical.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: file 5.09-2
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.0.1-0ubuntu13
  Architecture: amd64
  Date: Fri Sep 28 17:04:17 2012
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

[Rafael David Tinoco]

Simon,

Could you please help identifying the current status of this bug ? Your
original merge requests were postponed to the next SRU for rsyslog in
Bionic, Disco and Eoan, correct ?

During verification time you discovered the difference between "bin" and
"sbin" for the apparmor rule, is that it ? Than the verifications have
been marked as failed.

>From @paelzers comments I see that Focal is good. Should we re-try a SRU
for *at least* Bionic here in this bug ? Or just let it hang for
documentation purposes if others face this (since SRU is too small to be
accepted directly) ?

Any thoughts ?

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  In Progress
Status in rsyslog source package in Disco:
  In Progress
Status in rsyslog source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * rsyslog ships with a (Default disable) apparmor profile.
   * Security sensitive users are in general encouraged to enable such
     profiles but unfortunately due to slightly new behavior of the program
     the profile prevents its usage.
   * Allow the program to map/read its binary to get this working again

  [Test Case]

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  [Regression Potential]

   * This is just opening up the apparmor profile a bit. Therefore the only
     regression it could cause IMHO is a security issue. But then what it
     actually allows is reading (not writing!) its own binary which should
     be very safe.
   * Thinking further it came to my mind that package updates (independent 
 to the change) might restart services and that means if there is any 
 issue e.g. in a local config that worked but now fails (not by this 
 change but in general) then the upgrade will not cause, but trigger 
 this. This is a general regression risk for any upload, but in this 
 case worth to mention as it is about log handling - which if broken - 
 makes large scale systems hard to debug.

  [Other Info]

   * n/a

  ---

  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  Workaround:

    echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog

  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

[Rafael David Tinoco]

Marking as Fix Released for Disco:

+rsyslog (8.32.0-1ubuntu7.1) disco; urgency=medium
+
+  [ Simon Deziel ]
+  * d/usr.sbin.rsyslogd: allow reading/mmap'ing rsyslog binary
+This is required for usage inside containers (LP: #1827253)
+
+ -- Christian Ehrhardt   Mon, 14 Oct 2019 
08:53:03 +0200

Marking as Fix Released for Bionic:

+rsyslog (8.32.0-1ubuntu4.1) bionic; urgency=medium
+
+  [ Simon Deziel ]
+  * d/usr.sbin.rsyslogd: allow reading/mmap'ing rsyslog binary
+This is required for usage inside containers (LP: #1827253)
+
+ -- Christian Ehrhardt   Mon, 14 Oct 2019 
08:54:45 +0200
+


** Changed in: rsyslog (Ubuntu Bionic)
   Status: Triaged => Fix Released

** Changed in: rsyslog (Ubuntu Disco)
   Status: Triaged => Fix Released

** Changed in: rsyslog (Ubuntu Eoan)
   Status: Triaged => In Progress

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

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

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  In Progress
Status in rsyslog source package in Disco:
  In Progress
Status in rsyslog source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * rsyslog ships with a (Default disable) apparmor profile.
   * Security sensitive users are in general encouraged to enable such
     profiles but unfortunately due to slightly new behavior of the program
     the profile prevents its usage.
   * Allow the program to map/read its binary to get this working again

  [Test Case]

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  [Regression Potential]

   * This is just opening up the apparmor profile a bit. Therefore the only
     regression it could cause IMHO is a security issue. But then what it
     actually allows is reading (not writing!) its own binary which should
     be very safe.
   * Thinking further it came to my mind that package updates (independent 
 to the change) might restart services and that means if there is any 
 issue e.g. in a local config that worked but now fails (not by this 
 change but in general) then the upgrade will not cause, but trigger 
 this. This is a general regression risk for any upload, but in this 
 case worth to mention as it is about log handling - which if broken - 
 makes large scale systems hard to debug.

  [Other Info]

   * n/a

  ---

  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  Workaround:

    echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog

  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1868892] Re: initramfs-tools/hooks/udev for network *.link really sucks

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/382329

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

Title:
  initramfs-tools/hooks/udev for network *.link really sucks

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  [impact]

  If the /{etc,lib}/systemd/network directory itself is a symlink, the find
  command will not actually find any of the files in the dir it links to.

  [test case]

  $ sudo touch /etc/systemd/network/lp1868892.link
  $ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  ...
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  usr/lib/systemd/network/lp1868892.link
  $ sudo mv /etc/systemd/network /etc/systemd/network.abc
  $ sudo ln -s network.abc /etc/systemd/network
  $ sudo update-initramfs -u
  $ sudo lsinitramfs /boot/initrd.img-5.4.0-21-generic | grep lp1868892
  $ 

  [regression potential]

  this adjusts how link files are included in the initramfs, so
  regressions would likely occur when creating new initramfs, such as
  failure to create initramfs at all, or failure to properly copy link
  files into the initramfs, causing network setup failure.

  [scope]

  this is a Debian/Ubuntu specific file, and the Debian MR was just
  opened, so this is needed for Debian and all releases of Ubuntu.

  [other info]

  This bug likely has a very limited impact, as it is uncommon to
  symlink either the /lib/systemd/network or /etc/systemd/network dirs.

  [original description]

  If one creates e.g. /etc/systemd/network.cu and
  /etc/systemd/network.fc and symlinks  /etc/systemd/network to one of
  them, network setup will fail on reboot, because /usr/share/initramfs-
  tools/hooks/udev does a very poor job: it simply checks for a
  directory instead of the link files and therefore skips copying
  required files to the ram image. Another poor job is done when copying
  the files to the ram image: instead of following symlinks it copies
  them as which in turn makes them useless, because it does not copy the
  related dirs and thus the symlinks point to nothing. So keeping the
  system in an consistent state which such poor scripts is very hard,
  asking for trouble.

  Suggested fix is attached.

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

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

[Touch-packages] [Bug 1872146] Re: Audio on Headphones stopped working

[Shaun]

After I removed it works, but the problems comes back afetr a few hours.

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

Title:
  Audio on Headphones stopped working

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio via my headphones worked yesterday, Today no such luck.

  When I plug in my headphone, Plasma picks it up but no sound.

  Bluetooth headset still works.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Apr 10 23:03:09 2020
  InstallationDate: Installed on 2020-04-05 (5 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1872242] Re: HDA Intel PCH on samsung laptop: Headphones not working, speakers are ok

[Launchpad Bug Tracker]

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

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  HDA Intel PCH on samsung laptop: Headphones not working, speakers are
  ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Speakers in my samsung laptop are ok, but headphones don't work (no
  sound). Using Ubuntu 18.04 defaults.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sartojr1936 F pulseaudio
   /dev/snd/controlC0:  sartojr1936 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 16:47:32 2020
  InstallationDate: Installed on 2020-01-14 (88 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1377 F pulseaudio
    sartojr1936 F pulseaudio
   /dev/snd/controlC0:  gdm1377 F pulseaudio
    sartojr1936 F pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [760XBE, Realtek ALC256, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02REZ.040.190610.FL
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP760XBE-XW1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 7 Series
  dmi.product.name: 760XBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ
  dmi.product.version: P02REZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083

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

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

[Touch-packages] [Bug 1563110]

[lionelmiquel]

Hello,
  I know this issue is closed, but should I post
in this thread if I got a problem with my microp
hone on a E200HA, Ubuntu 18.04, custom kernel bas
ed on 5.6.3 with cx2072x support compiled in and 
right UCM files ?
Or should I create a bug report ?

Thanks.

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

Status in ALSA driver:
  Fix Released
Status in alsa-driver package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I've recently bought an Asus e200ha.
  Sound in this laptop doesn't work.
  The sound card is an intel sst with codec conexant cx2072x

  aplay -l:
  aplay: device_list:268: no soundcard found...
  in the sound setting there is a "Dummy output"
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a
  InstallationDate: Installed on 2016-03-28 (0 days ago)
  InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105
  Lsusb:
   Bus 002 Device 002: ID 0781:5583 SanDisk Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3496 IMC Networks 
   Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. E200HA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic 
root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E200HA.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E200HA
  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.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E200HA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1863356] Re: libtool and libtool-doc 2.4.6-12 both contain /usr/share/doc/libtool/AUTHORS causing upgrade failures

[Bug Watch Updater]

** Changed in: libtool (Debian)
   Status: Unknown => Fix Released

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

Title:
  libtool and libtool-doc 2.4.6-12 both contain
  /usr/share/doc/libtool/AUTHORS causing upgrade failures

Status in libtool package in Ubuntu:
  Confirmed
Status in libtool package in Debian:
  Fix Released

Bug description:
  Unpacking libtool-doc (2.4.6-12) over (2.4.6-11) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-tTUGeR/289-libtool-doc_2.4.6-12_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libtool/AUTHORS', which is also in 
package libtool 2.4.6-12
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libtool 2.4.6-12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: i3
  Date: Fri Feb 14 09:04:32 2020
  InstallationDate: Installed on 2017-12-15 (790 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libtool
  UpgradeStatus: Upgraded to focal on 2019-09-23 (144 days ago)

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

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

[Touch-packages] [Bug 1827857] Re: Stuck on applying package profile for servers running 18.04

[Simon Poirier]

The issue was fixed in python-apt =2.0.0

** Changed in: python-apt (Ubuntu)
   Status: New => Fix Released

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

Title:
  Stuck on applying package profile for servers running 18.04

Status in landscape-client package in Ubuntu:
  Fix Committed
Status in python-apt package in Ubuntu:
  Fix Released

Bug description:
  When I apply a package profile to a server, the activity is stuck on
  'in progress'. It only happens for servers running on 18.04 LTS. It
  works for servers running on 14.04 LTS.

  I can verify that this is not a connection issue by:
  * Manually installing the packages contained in the package profile
  * Installing the package profile directly using apt-get.

  The landscape server is hosted on-premise using version 18.01.
  The 18.04 server is running:
* The latest version of landscape-client, 18.01-0ubuntu3.3.
* Ubuntu Server 18.04.02 LTS using 4.15.x kernel.
* Python version: 3.6.7

  Maybe relevant log files:

  package-changer.log 
  2019-05-06 11:59:55,977 WARNING  [MainThread] Package data not yet 
synchronized with server (...)

  package-reporter.log
  2019-05-06 12:00:07,581 ERROR[MainThread] None
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb2 in position 29: 
invalid start byte

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1827857/+subscriptions

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

[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

[Dan Streetman]

** Description changed:

- requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in 
+ [impact]
+ 
+ the networkd UseRoutes parameter allowed ignoring all routes provided by
+ a dhcp4 server, including the route via the dhcp4-provided gateway.
+ This was the behavior of networkd until recently, and in Focal the
+ UseRoutes parameter does *not* prevent networkd from adding the route
+ via the dhcp4-provided gateway.  This is now controlled with a new
+ parameter, UseGateway.
+ 
+ The systemd in Focal unfortunately has part of the upstream code; it no
+ longer ignores the gateway route when UseRoutes=false is specified, but
+ also it does not include the UseGateway parameter.
+ 
+ [test case]
+ 
+ bug 1872589 has a good test case netplan config, but a very quick test
+ can be done with the networkd config:
+ 
+ [Match]
+ Name=eth0
+ 
+ [Network]
+ DHCP=ipv4
+ LinkLocalAddressing=ipv6
+ 
+ [DHCP]
+ RouteMetric=100
+ UseMTU=true
+ UseRoutes=false
+ 
+ 
+ this results in the system incorrectly setting a route via the default 
gateway:
+ 
+ root@lp1867375-f:~# ip r
+ default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100 
+ 10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86 
+ 10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100 
+ 
+ [regression potential]
+ 
+ tbd
+ 
+ [other info]
+ 
+ to properly support separation of 'routes' and 'gateways' received via
+ dhcp4, SRU releases should also support the UseGateway parameter, which
+ is what this bug was originally opened requesting.
+ 
+ [original description]
+ 
+ requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

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

** Also affects: netplan.io (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: netplan.io (Ubuntu Bionic)
   Status: New => Invalid

** Changed in: netplan.io (Ubuntu Eoan)
   Status: New => Invalid

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Confirmed
Status in netplan.io source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  [test case]

  bug 1872589 has a good test case netplan config, but a very quick test
  can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

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

  
  this results in the system incorrectly setting a route via the default 
gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100 
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86 
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100 

  [regression potential]

  tbd

  [other info]

  to properly support separation of 'routes' and 'gateways' received via
  dhcp4, SRU releases should also support the UseGateway parameter,
  which is what this bug was originally opened requesting.

  [original description]

  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1867375/+subscriptions

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

[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

[Dan Streetman]

** Also affects: netplan.io (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/1867375

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  New
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Eoan:
  New
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in 
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1867375/+subscriptions

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

[Touch-packages] [Bug 1873038] Re: Merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main)

[Sebastien Bacher]

Thank you for your bug report, the Debian maintainers have included most
of the git fixes in the .17 package, what fixes do you want to see
landing?

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Incomplete

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main)

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Please merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main)

  Sorry, I can't work on this merge myself. It fixes bugs in Wayland.

  https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS

  Overview of Changes in GTK+ 3.24.18
  ===

  * Wayland:
   - Fix more sizing regressions in Epiphany and LibreOffice
 menus, and popups in general

  * Build:
   - Make resource build reproducible

  * Translation updates
   Basque
   Latvian

  Explanation of the Ubuntu delta:
* Update to the current stable version (based on Debian)

  Changelog entries since current focal version 3.24.17-3ubuntu1:

  gtk+3.0 (3.24.18-1) unstable; urgency=medium

* Team upload
* New upstream release
  - Fix remaining XInclude failure in documentation (Closes: #672369)
* d/copyright: Update
* d/patches: Drop patches that came from upstream

   -- Simon McVittie   Fri, 10 Apr 2020 15:47:07 +0100

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

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

[Touch-packages] [Bug 1807759] Re: Can not type file path in file open dialog, also can not turn on always-use-location-entry

[Amr Ibrahim]

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

** This bug has been marked a duplicate of bug 1863157
   Petition to bring back file name copy/paste functionality in GTK file chooser

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

Title:
  Can not type file path in file open dialog, also can not turn on
  always-use-location-entry

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  after upgrading to 16.04 from 14.04, I found that all file open dialog
  lost the address bar (location entry). The only thing to navigate
  between folders is the breadcrumb bar. Every path change requires a
  dozen of clicking, while before I could just paste the path and done.
  This is a big inconvenience.

  after googling, I found tons of reports to restore the location entry
  using the below command

  gsettings set org.gnome.nautilus.preferences always-use-location-entry true
   or
  dconf write /org/gnome/nautilus/preferences/always-use-location-entry true

  however, this fails to work on my system, I got

  fangq@taote:~$ gsettings set org.gnome.nautilus.preferences always-
  use-location-entry true

  (process:11686): dconf-WARNING **: failed to commit changes to dconf:
  
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code4:
  Failed to rename file '/home/users/fangq/.config/dconf/user.SO58SZ' to
  '/home/users/fangq/.config/dconf/user': g_rename() failed: No such
  file or directory

  I would like to get a workaround to revert to the previous setting
  (either location entry is displayed by default, or can be re-enabled
  by clicking a button on the dialog). Also, I would suggest the
  developers to consider adding this feature back. For people who use
  Linux a lot, clicking is just not fast enough!

  
  Links to similar complains:

  
https://unix.stackexchange.com/questions/154106/show-address-bar-w-full-path-in-nautilus-instead-of-breadcrumbs-bar
  
https://www.howtogeek.com/189777/how-to-show-the-location-entry-instead-of-the-breadcrumb-bar-in-nautilus-in-ubuntu-14.04/
  
https://askubuntu.com/questions/547688/default-to-showing-and-using-pathbar-in-ubuntu-file-dialogs
  https://community.linuxmint.com/tutorial/view/65
  https://blog.tersmitten.nl/restore-the-location-bar-in-nautilus.html
  
https://askubuntu.com/questions/324064/use-path-bar-and-address-bar-in-nautilus

  and many more

  https://www.google.com/search?q=nautilus+always_use_location_entry

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

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

[Touch-packages] [Bug 1851128] Re: Stylus Use leads to Crash Application in Wayland Sessions

[Amr Ibrahim]

** Changed in: gtk+3.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Stylus Use leads to Crash Application in Wayland Sessions

Status in gtk+3.0 package in Ubuntu:
  Fix Released

Bug description:
  There is an issue in gtk. In Wayland sessions the use of a stylus
  leads to crash of the application. It is apparently fixed in Gnome
  gtk.

  When asking what should I do I got the answer that I should ask the
  ubuntu gtk maintainers to  backport <
  https://gitlab.gnome.org/GNOME/gtk/merge_requests/1121> and
  , which I do
  here and now.

  Best regards

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

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

[Touch-packages] [Bug 1870843] Re: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_call_sync()

[baslow]

I am affected by the same bug. I just checked the time stamp of
/var/crash/_usr_libexec_ibus-ui-gtk3.1000.crash and found that it
corresponds to the time I first logged in this morning, not last night's
shutdown:

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

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

Status in ibus package in Ubuntu:
  Incomplete

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

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 13:03:51 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   LANGUAGE=es_AR:es
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_AR.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fee4f4e8f5b : orq
$0x0,(%rsp)
   PC (0x7fee4f4e8f5b) ok
   source "$0x0" ok
   destination "(%rsp)" (0x7ffe02368d40) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1873038] [NEW] Merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main)

[Amr Ibrahim]

Public bug reported:

Please merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main)

Sorry, I can't work on this merge myself. It fixes bugs in Wayland.

https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS

Overview of Changes in GTK+ 3.24.18
===

* Wayland:
 - Fix more sizing regressions in Epiphany and LibreOffice
   menus, and popups in general

* Build:
 - Make resource build reproducible

* Translation updates
 Basque
 Latvian

Explanation of the Ubuntu delta:
  * Update to the current stable version (based on Debian)

Changelog entries since current focal version 3.24.17-3ubuntu1:

gtk+3.0 (3.24.18-1) unstable; urgency=medium

  * Team upload
  * New upstream release
- Fix remaining XInclude failure in documentation (Closes: #672369)
  * d/copyright: Update
  * d/patches: Drop patches that came from upstream

 -- Simon McVittie   Fri, 10 Apr 2020 15:47:07 +0100

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

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

Title:
  Merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main)

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Please merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main)

  Sorry, I can't work on this merge myself. It fixes bugs in Wayland.

  https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS

  Overview of Changes in GTK+ 3.24.18
  ===

  * Wayland:
   - Fix more sizing regressions in Epiphany and LibreOffice
 menus, and popups in general

  * Build:
   - Make resource build reproducible

  * Translation updates
   Basque
   Latvian

  Explanation of the Ubuntu delta:
* Update to the current stable version (based on Debian)

  Changelog entries since current focal version 3.24.17-3ubuntu1:

  gtk+3.0 (3.24.18-1) unstable; urgency=medium

* Team upload
* New upstream release
  - Fix remaining XInclude failure in documentation (Closes: #672369)
* d/copyright: Update
* d/patches: Drop patches that came from upstream

   -- Simon McVittie   Fri, 10 Apr 2020 15:47:07 +0100

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

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

[Touch-packages] [Bug 1503773] Re: Drop ondemand init script

[Launchpad Bug Tracker]

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

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

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

Title:
  Drop ondemand init script

Status in systemd package in Ubuntu:
  Confirmed
Status in sysvinit package in Ubuntu:
  Fix Released

Bug description:
  Ondemand init script is not inherited from Debian, it's an Ubuntu
  specific change.

  Some reasons to get rid of it:
  On my wily cloud test, systemd blame's 669ms on ondemand on a cloud instance 
with no ability to change frequency..
  In the init script we don't run this for android
  Why don't we just always use whatever is that kernel's default?

  There are a number of other reported problems with it:
  https://launchpad.net/ubuntu/+source/sysvinit/+bugs?field.searchtext=ondemand

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

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

[Touch-packages] [Bug 1851695] Re: DEP8 failure/regression in nspr on arm64 and armhf

[Bug Watch Updater]

** Changed in: notary (Debian)
   Status: Confirmed => Fix Released

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

Title:
  DEP8 failure/regression in nspr on arm64 and armhf

Status in notary package in Ubuntu:
  New
Status in nspr package in Ubuntu:
  Invalid
Status in notary package in Debian:
  Fix Released

Bug description:
  nspr 0.6.1~ds1-4 is failing DEP8 test in arm64 and armhf:

  
  autopkgtest [09:46:25]: test command1: /usr/bin/dh_golang_autopkgtest
  autopkgtest [09:46:25]: test command1: [---
  [info] Testing github.com/theupdateframework/notary...
  [info] Source code installed by binary package, overriding 
dh_auto_configure...
  [info] Disabling existing override_dh_auto_configure...
  dh build --builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build \
--buildsystem=golang \
--with=golang
 dh_update_autotools_config 
-O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build 
-O--buildsystem=golang
 dh_autoreconf 
-O--builddirectory=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build 
-O--buildsystem=golang
 debian/rules override_dh_auto_configure
  make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp'
  mkdir -p "_build"
  cp -a /usr/share/gocode/src "_build"
  make[1]: Leaving directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp'
 debian/rules override_dh_auto_build
  make[1]: Entering directory '/tmp/autopkgtest.G91v24/autopkgtest_tmp'
  dh_auto_build -- -tags "pkcs11"
cd _build && go install 
-gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 
-asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 
-v -p 1 -tags pkcs11 github.com/theupdateframework/notary 
github.com/theupdateframework/notary/client 
github.com/theupdateframework/notary/client/changelist 
github.com/theupdateframework/notary/cmd/escrow 
github.com/theupdateframework/notary/cmd/notary 
github.com/theupdateframework/notary/cmd/notary-server 
github.com/theupdateframework/notary/cmd/notary-signer 
github.com/theupdateframework/notary/cryptoservice 
github.com/theupdateframework/notary/passphrase 
github.com/theupdateframework/notary/proto 
github.com/theupdateframework/notary/server 
github.com/theupdateframework/notary/server/errors 
github.com/theupdateframework/notary/server/handlers 
github.com/theupdateframework/notary/server/snapshot 
github.com/theupdateframework/notary/server/storage 
github.com/theupdateframework/notary/server/timestamp 
github.com/theupdateframework/notary/signer 
github.com/theupdateframework/notary/signer/api 
github.com/theupdateframework/notary/signer/client 
github.com/theupdateframework/notary/signer/keydbstore 
github.com/theupdateframework/notary/storage 
github.com/theupdateframework/notary/storage/rethinkdb 
github.com/theupdateframework/notary/trustmanager 
github.com/theupdateframework/notary/trustmanager/remoteks 
github.com/theupdateframework/notary/trustmanager/yubikey 
github.com/theupdateframework/notary/trustpinning 
github.com/theupdateframework/notary/tuf 
github.com/theupdateframework/notary/tuf/data 
github.com/theupdateframework/notary/tuf/signed 
github.com/theupdateframework/notary/tuf/testutils 
github.com/theupdateframework/notary/tuf/testutils/interfaces 
github.com/theupdateframework/notary/tuf/testutils/keys 
github.com/theupdateframework/notary/tuf/utils 
github.com/theupdateframework/notary/tuf/validation 
github.com/theupdateframework/notary/utils 
github.com/theupdateframework/notary/version
  src/github.com/docker/distribution/digestset/set.go:9:2: cannot find package 
"github.com/opencontainers/go-digest" in any of:

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/go-digest
 (vendor tree)
/usr/lib/go-1.12/src/github.com/opencontainers/go-digest (from $GOROOT)

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/go-digest
 (from $GOPATH)
  src/github.com/docker/distribution/blobs.go:13:2: cannot find package 
"github.com/opencontainers/image-spec/specs-go/v1" in any of:

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/docker/distribution/vendor/github.com/opencontainers/image-spec/specs-go/v1
 (vendor tree)
/usr/lib/go-1.12/src/github.com/opencontainers/image-spec/specs-go/v1 
(from $GOROOT)

/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src/github.com/opencontainers/image-spec/specs-go/v1
 (from $GOPATH)
  dh_auto_build: cd _build && go install 
-gcflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 
-asmflags=all=\"-trimpath=/tmp/autopkgtest.G91v24/autopkgtest_tmp/_build/src\" 
-v -p 1 -tags pkcs11 github.com/theupdateframework/notary 
github.com/theupdateframework/notary/client 

[Touch-packages] [Bug 1503773] Re: Drop ondemand init script

[Bryan Quigley]

This continues to cause breakage - https://bugs.launchpad.net/charm-
sysconfig/+bug/1873028

I'm still looking for a modern justification for it to exist -
considering AFAIK no other distro does this.

** Description changed:

  Ondemand init script is not inherited from Debian, it's an Ubuntu
  specific change.
  
  Some reasons to get rid of it:
  On my wily cloud test, systemd blame's 669ms on ondemand on a cloud instance 
with no ability to change frequency..
- In the init script we don't run this for android 
- Ondemand is already on by default!  Why don't we just always use whatever is 
that kernel's default?
+ In the init script we don't run this for android
+ Why don't we just always use whatever is that kernel's default?
  
  There are a number of other reported problems with it:
  https://launchpad.net/ubuntu/+source/sysvinit/+bugs?field.searchtext=ondemand

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

Title:
  Drop ondemand init script

Status in systemd package in Ubuntu:
  New
Status in sysvinit package in Ubuntu:
  Fix Released

Bug description:
  Ondemand init script is not inherited from Debian, it's an Ubuntu
  specific change.

  Some reasons to get rid of it:
  On my wily cloud test, systemd blame's 669ms on ondemand on a cloud instance 
with no ability to change frequency..
  In the init script we don't run this for android
  Why don't we just always use whatever is that kernel's default?

  There are a number of other reported problems with it:
  https://launchpad.net/ubuntu/+source/sysvinit/+bugs?field.searchtext=ondemand

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

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

[Touch-packages] [Bug 1873005] Re: [Bluetooth Bose Headphones, playback] Sound plays exclusively from laptop speakers even when headset is selected as output device

[Potet]

** Description changed:

  The computer will not send any sound output to the headset, and instead
  does all playback through the built in speakers. If headphones are
  connected by AUX sound will be sent there.
  
  Bluetooth media buttons work - I can pause music by tapping the
  bluetooth headset.
  
  If I change bluetooth audio quality the headset makes a notification
  sound, but playback continues as before through computer speakers.
  
  Audio tests (front left, front right) are also channelled through
  computer speakers.
  
  The same headset with the same setup worked flawlessly in 19.10.
  
+ Thank you so much for your work! 20.04 is a joy to use.
  
- Thank you so much for your work! 20.04 is a joy to use.
+ Edit: I tried deleting .config/pulse. This didn't make any difference.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  steinarne   1509 F pulseaudio
-  /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  steinarne   1509 F pulseaudio
+  /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 16:30:16 2020
  InstallationDate: Installed on 2019-08-08 (251 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: LE-Bose NC 700 Headphones
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  steinarne   1509 F pulseaudio
-  /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  steinarne   1509 F pulseaudio
+  /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [LE-Bose NC 700 Headphones, playback] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-04-13 (2 days ago)
  dmi.bios.date: 05/05/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET56W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LS0017MX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET56W(1.33):bd05/05/2019:svnLENOVO:pn20LS0017MX:pvrThinkPadL480:rvnLENOVO:rn20LS0017MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LS0017MX
  dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO

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

Title:
  [Bluetooth Bose Headphones, playback] Sound plays exclusively from
  laptop speakers even when headset is selected as output device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The computer will not send any sound output to the headset, and
  instead does all playback through the built in speakers. If headphones
  are connected by AUX sound will be sent there.

  Bluetooth media buttons work - I can pause music by tapping the
  bluetooth headset.

  If I change bluetooth audio quality the headset makes a notification
  sound, but playback continues as before through computer speakers.

  Audio tests (front left, front right) are also channelled through
  computer speakers.

  The same headset with the same setup worked flawlessly in 19.10.

  Thank you so much for your work! 20.04 is a joy to use.

  Edit: I tried deleting .config/pulse. This didn't make any difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steinarne   1509 F pulseaudio
   /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 16:30:16 2020
  InstallationDate: Installed on 2019-08-08 (251 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: LE-Bose NC 700 Headphones
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steinarne   1509 F pulseaudio
   /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [LE-Bose NC 700 Headphones, playback] No sound at all
  UpgradeStatus: Upgraded to focal 

[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

[Dan Streetman]

@sunil-mukundan I hope you don't mind, I'm adjusting the bug subject
slightly to indicate that things need to be worked on both for SRU
releases as well as for Focal.

** Summary changed:

- systemd-networkd: Setting UseRoutes to False results in DHCP default gateway 
not being installed
+ systemd-networkd: UseRoutes behavior change with introduction of UseGateway 
param

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed

Bug description:
  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in 
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

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

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

[Touch-packages] [Bug 1873031] Re: 245.4-2ubuntu1 has broken dhcp based NTP updates

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/382271

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

Title:
  245.4-2ubuntu1 has broken dhcp based NTP updates

Status in chrony package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd has broken this by the split of timesyncd.

  On a system that installed chrony (or other NTP servers) you'll have:

  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  VersionArchitecture Description
  
+++-=-==--===
  ii  chrony3.5-6ubuntu3   amd64Versatile implementation of 
the Network Time Protocol
  rc  systemd-timesyncd 245.4-4ubuntu1 amd64minimalistic service to 
synchronize local time with NTP servers

  That left this behind:
/etc/dhcp/dhclient-exit-hooks.d/timesyncd

  And if you now run a dhcp based time server push it will fail very
  badly.

  P.S. This is triggered by the chrony autopkgtests but not an issue in chrony 
yet it is in systemd.
  But due to that one can use [1] as easy reproducer, I wonder how systemd 
slipped by this issue in autopkgtest?

  It contains:
  systemctl try-restart systemd-timesyncd.service || true

  Which in the setup the system now has will trigger:
   sudo dhclient dummy0
  Failed to try-restart systemd-timesyncd.service: Unit 
systemd-timesyncd.service is masked.

  P.S. I'll harden the chrony test to not stumble over this but it
  should be revisited for systemd to provide a better fix than causing
  this message every time (maybe pre-check if it is enabled and
  unmasked)?

  [1]: https://git.launchpad.net/ubuntu/+source/chrony/tree/debian/tests
  /time-sources-from-dhcp-servers?h=ubuntu/focal-devel

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

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

[Touch-packages] [Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

[Christian Ehrhardt ]

I filed bug 1873031 for the latter

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

Status in ntp package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in ntp source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in ntp source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
  timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
  systemd-timesyncd.service from starting if the ntp package has been
  installed.  However, ntp.service has a Conflicts directive for
  systemd-timesyncd.service.  If both services are enabled, neither will
  start on boot.  This breaks upgrades from < 19.10 to 19.10 for systems
  that have both ntp and systemd installed.

  Possible workarounds:

  - Uninstall ntp
  - Disable systemd-timesyncd.service

  % lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  % apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status

  % apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu2
Candidate: 1:4.2.8p12+dfsg-3ubuntu2
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe 
amd64 Packages
  100 /var/lib/dpkg/status

  % dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

  % sudo systemctl status ntp
  ● ntp.service - Network Time Service
 Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
 Active: inactive (dead)
   Docs: man:ntpd(8)

  % sudo systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead)
  Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
   Docs: man:systemd-timesyncd.service(8)

  Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
  Time Synchronization being skipped.

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

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

[Touch-packages] [Bug 1873031] [NEW] 245.4-2ubuntu1 has broken dhcp based NTP updates

[Christian Ehrhardt ]

Public bug reported:

systemd has broken this by the split of timesyncd.

On a system that installed chrony (or other NTP servers) you'll have:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  VersionArchitecture Description
+++-=-==--===
ii  chrony3.5-6ubuntu3   amd64Versatile implementation of 
the Network Time Protocol
rc  systemd-timesyncd 245.4-4ubuntu1 amd64minimalistic service to 
synchronize local time with NTP servers

That left this behind:
  /etc/dhcp/dhclient-exit-hooks.d/timesyncd

And if you now run a dhcp based time server push it will fail very
badly.

P.S. This is triggered by the chrony autopkgtests but not an issue in chrony 
yet it is in systemd.
But due to that one can use [1] as easy reproducer, I wonder how systemd 
slipped by this issue in autopkgtest?

It contains:
systemctl try-restart systemd-timesyncd.service || true

Which in the setup the system now has will trigger:
 sudo dhclient dummy0
Failed to try-restart systemd-timesyncd.service: Unit systemd-timesyncd.service 
is masked.

P.S. I'll harden the chrony test to not stumble over this but it should
be revisited for systemd to provide a better fix than causing this
message every time (maybe pre-check if it is enabled and unmasked)?

[1]: https://git.launchpad.net/ubuntu/+source/chrony/tree/debian/tests
/time-sources-from-dhcp-servers?h=ubuntu/focal-devel

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

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

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1873031

Title:
  245.4-2ubuntu1 has broken dhcp based NTP updates

Status in chrony package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd has broken this by the split of timesyncd.

  On a system that installed chrony (or other NTP servers) you'll have:

  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  VersionArchitecture Description
  
+++-=-==--===
  ii  chrony3.5-6ubuntu3   amd64Versatile implementation of 
the Network Time Protocol
  rc  systemd-timesyncd 245.4-4ubuntu1 amd64minimalistic service to 
synchronize local time with NTP servers

  That left this behind:
/etc/dhcp/dhclient-exit-hooks.d/timesyncd

  And if you now run a dhcp based time server push it will fail very
  badly.

  P.S. This is triggered by the chrony autopkgtests but not an issue in chrony 
yet it is in systemd.
  But due to that one can use [1] as easy reproducer, I wonder how systemd 
slipped by this issue in autopkgtest?

  It contains:
  systemctl try-restart systemd-timesyncd.service || true

  Which in the setup the system now has will trigger:
   sudo dhclient dummy0
  Failed to try-restart systemd-timesyncd.service: Unit 
systemd-timesyncd.service is masked.

  P.S. I'll harden the chrony test to not stumble over this but it
  should be revisited for systemd to provide a better fix than causing
  this message every time (maybe pre-check if it is enabled and
  unmasked)?

  [1]: https://git.launchpad.net/ubuntu/+source/chrony/tree/debian/tests
  /time-sources-from-dhcp-servers?h=ubuntu/focal-devel

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

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

[Touch-packages] [Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

[Christian Ehrhardt ]

FYI : This also has broken dhcp based ntp info updates
This is hit by the chrony autopkgtests, how did you get this systemd upload to 
migrate without fixing that?

$ sudo dhclient dummy0
Failed to try-restart systemd-timesyncd.service: Unit systemd-timesyncd.service 
is masked.

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

Status in ntp package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in ntp source package in Eoan:
  Confirmed
Status in systemd source package in Eoan:
  Confirmed
Status in ntp source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
  timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
  systemd-timesyncd.service from starting if the ntp package has been
  installed.  However, ntp.service has a Conflicts directive for
  systemd-timesyncd.service.  If both services are enabled, neither will
  start on boot.  This breaks upgrades from < 19.10 to 19.10 for systems
  that have both ntp and systemd installed.

  Possible workarounds:

  - Uninstall ntp
  - Disable systemd-timesyncd.service

  % lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  % apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status

  % apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu2
Candidate: 1:4.2.8p12+dfsg-3ubuntu2
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe 
amd64 Packages
  100 /var/lib/dpkg/status

  % dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

  % sudo systemctl status ntp
  ● ntp.service - Network Time Service
 Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
 Active: inactive (dead)
   Docs: man:ntpd(8)

  % sudo systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead)
  Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
   Docs: man:systemd-timesyncd.service(8)

  Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
  Time Synchronization being skipped.

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

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

[Touch-packages] [Bug 1843982] Re: Various programs crashed with SIGSEGV in g_str_hash() from g_hash_table_lookup() from update_user()

[Iain Lane]

** Also affects: accountsservice (Ubuntu Focal)
   Importance: High
 Assignee: Iain Lane (laney)
   Status: Triaged

** Changed in: accountsservice (Ubuntu Focal)
Milestone: None => ubuntu-20.04.1

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

Title:
  Various programs crashed with SIGSEGV in g_str_hash() from
  g_hash_table_lookup() from update_user()

Status in accountsservice:
  New
Status in accountsservice package in Ubuntu:
  Triaged
Status in accountsservice source package in Focal:
  Triaged
Status in accountsservice package in Debian:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/597be858df957473f357a9249b002b0e39f42781
  https://errors.ubuntu.com/problem/3a817938d76d231fdfc8f698392fbf5e3724084f
  https://errors.ubuntu.com/problem/3945cd9cdcec914cab9a3220d05e969696c7

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 14 10:29:16 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-05-24 (112 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190523)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=nb_NO.UTF-8
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   g_str_hash () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: gnome-shell crashed with SIGSEGV in g_str_hash()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1873018] Re: Ibus preferences ended unexpectedly on login

[Apport retracing service]

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

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

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

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  Ibus preferences ended unexpectedly on login

Status in ibus package in Ubuntu:
  New

Bug description:
  Booted machine but did not log in for awhile. When I finally did,
  encountered message "ibus preferences ended undexpectedly". Chose to
  relaunch and submit details.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 19:34:49 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2020-04-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f65319f8a01 <__vfprintf_internal+33>:   mov
%ecx,-0x4c0(%rbp)
   PC (0x7f65319f8a01) ok
   source "%ecx" ok
   destination "-0x4c0(%rbp)" (0x7ffde8082bb0) not located in a known VMA 
region (needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ibus_bus_get_engines_by_names () from /lib/x86_64-linux-gnu/libibus-1.0.so.5
   ?? ()
   ?? ()
   g_cclosure_marshal_VOID__STRINGv () from 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGSEGV in ibus_bus_get_engines_by_names()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1873017] Re: Error when install lvm2 on ubuntu 20.04

[Yiu Man Ho]

** Description changed:

  I am using chinese so some log will use chinese.
  These is the logs that i found on terminal:
- 
  
  解開 lvm2 (2.03.07-1ubuntu1) 中...
  設定 lvm2 (2.03.07-1ubuntu1) ...
  update-initramfs: deferring update (trigger activated)
  Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked.
  invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed.
  ● lvm2-lvmpolld.service - LVM2 poll daemon
-  Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; 
vendor p
+  Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; 
vendor p
  reset: enabled)
-  Active: inactive (dead)
-Docs: man:lvmpolld(8)
+  Active: inactive (dead)
+    Docs: man:lvmpolld(8)
  dpkg: error processing package lvm2 (--configure):
-  installed lvm2 package post-installation script 子進程傳回了 1 錯誤退出狀態碼
+  installed lvm2 package post-installation script 子進程傳回了 1 錯誤退出狀態碼
  執行 systemd (245.4-2ubuntu1) 的觸發程式……
  執行 man-db (2.9.1-1) 的觸發程式……
  執行 ureadahead (0.100.0-21) 的觸發程式……
  ureadahead will be reprofiled on next reboot
  執行 initramfs-tools (0.136ubuntu6) 的觸發程式……
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  I: The initramfs will attempt to resume from /dev/sda6
  I: (UUID=52eb06e0-e84e-4146-be3b-e07513046207)
  I: Set the RESUME variable to override this.
  Warning: Not updating LILO; /etc/lilo.conf not found!
  處理時發生錯誤：
-  lvm2
+  lvm2
  E: Sub-process /usr/bin/dpkg returned an error code (1)
- 
+ --
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:17:22 2020
  InstallationDate: Installed on 2020-02-08 (67 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to focal on 2020-04-12 (3 days ago)

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

Title:
  Error when install lvm2 on ubuntu 20.04

Status in lvm2 package in Ubuntu:
  New

Bug description:
  I am using chinese so some log will use chinese.
  These is the logs that i found on terminal:

  解開 lvm2 (2.03.07-1ubuntu1) 中...
  設定 lvm2 (2.03.07-1ubuntu1) ...
  update-initramfs: deferring update (trigger activated)
  Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked.
  invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed.
  ● lvm2-lvmpolld.service - LVM2 poll daemon
   Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; 
vendor p
  reset: enabled)
   Active: inactive (dead)
     Docs: man:lvmpolld(8)
  dpkg: error processing package lvm2 (--configure):
   installed lvm2 package post-installation script 子進程傳回了 1 錯誤退出狀態碼
  執行 systemd (245.4-2ubuntu1) 的觸發程式……
  執行 man-db (2.9.1-1) 的觸發程式……
  執行 ureadahead (0.100.0-21) 的觸發程式……
  ureadahead will be reprofiled on next reboot
  執行 initramfs-tools (0.136ubuntu6) 的觸發程式……
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  I: The initramfs will attempt to resume from /dev/sda6
  I: (UUID=52eb06e0-e84e-4146-be3b-e07513046207)
  I: Set the RESUME variable to override this.
  Warning: Not updating LILO; /etc/lilo.conf not found!
  處理時發生錯誤：
   lvm2
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  --
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:17:22 2020
  InstallationDate: Installed on 2020-02-08 (67 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to focal on 2020-04-12 (3 days ago)

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

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

[Touch-packages] [Bug 1873017] [NEW] Error when install lvm2 on ubuntu 20.04

[Yiu Man Ho]

Public bug reported:

I am using chinese so some log will use chinese.
These is the logs that i found on terminal:


解開 lvm2 (2.03.07-1ubuntu1) 中...
設定 lvm2 (2.03.07-1ubuntu1) ...
update-initramfs: deferring update (trigger activated)
Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked.
invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed.
● lvm2-lvmpolld.service - LVM2 poll daemon
 Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; vendor p
reset: enabled)
 Active: inactive (dead)
   Docs: man:lvmpolld(8)
dpkg: error processing package lvm2 (--configure):
 installed lvm2 package post-installation script 子進程傳回了 1 錯誤退出狀態碼
執行 systemd (245.4-2ubuntu1) 的觸發程式……
執行 man-db (2.9.1-1) 的觸發程式……
執行 ureadahead (0.100.0-21) 的觸發程式……
ureadahead will be reprofiled on next reboot
執行 initramfs-tools (0.136ubuntu6) 的觸發程式……
update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
I: The initramfs will attempt to resume from /dev/sda6
I: (UUID=52eb06e0-e84e-4146-be3b-e07513046207)
I: Set the RESUME variable to override this.
Warning: Not updating LILO; /etc/lilo.conf not found!
處理時發生錯誤：
 lvm2
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lvm2 2.03.07-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 15 23:17:22 2020
InstallationDate: Installed on 2020-02-08 (67 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: lvm2
UpgradeStatus: Upgraded to focal on 2020-04-12 (3 days ago)

** Affects: lvm2 (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 lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1873017

Title:
  Error when install lvm2 on ubuntu 20.04

Status in lvm2 package in Ubuntu:
  New

Bug description:
  I am using chinese so some log will use chinese.
  These is the logs that i found on terminal:

  
  解開 lvm2 (2.03.07-1ubuntu1) 中...
  設定 lvm2 (2.03.07-1ubuntu1) ...
  update-initramfs: deferring update (trigger activated)
  Failed to restart lvm2-lvmpolld.service: Unit lvm2-lvmpolld.socket is masked.
  invoke-rc.d: initscript lvm2-lvmpolld, action "restart" failed.
  ● lvm2-lvmpolld.service - LVM2 poll daemon
   Loaded: loaded (/lib/systemd/system/lvm2-lvmpolld.service; static; 
vendor p
  reset: enabled)
   Active: inactive (dead)
 Docs: man:lvmpolld(8)
  dpkg: error processing package lvm2 (--configure):
   installed lvm2 package post-installation script 子進程傳回了 1 錯誤退出狀態碼
  執行 systemd (245.4-2ubuntu1) 的觸發程式……
  執行 man-db (2.9.1-1) 的觸發程式……
  執行 ureadahead (0.100.0-21) 的觸發程式……
  ureadahead will be reprofiled on next reboot
  執行 initramfs-tools (0.136ubuntu6) 的觸發程式……
  update-initramfs: Generating /boot/initrd.img-5.4.0-21-generic
  I: The initramfs will attempt to resume from /dev/sda6
  I: (UUID=52eb06e0-e84e-4146-be3b-e07513046207)
  I: Set the RESUME variable to override this.
  Warning: Not updating LILO; /etc/lilo.conf not found!
  處理時發生錯誤：
   lvm2
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 23:17:22 2020
  InstallationDate: Installed on 2020-02-08 (67 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to focal on 2020-04-12 (3 days ago)

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

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

[Touch-packages] [Bug 1869796] Re: vague error during upgrade

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/382309

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

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  Incomplete

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-ro.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local read-
  only socket.

  
  Thanks

  ProblemType: Bug
  DistroRelease: 

[Touch-packages] [Bug 1873005] [NEW] [Bluetooth Bose Headphones, playback] Sound plays exclusively from laptop speakers even when headset is selected as output device

[Potet]

Public bug reported:

The computer will not send any sound output to the headset, and instead
does all playback through the built in speakers. If headphones are
connected by AUX sound will be sent there.

Bluetooth media buttons work - I can pause music by tapping the
bluetooth headset.

If I change bluetooth audio quality the headset makes a notification
sound, but playback continues as before through computer speakers.

Audio tests (front left, front right) are also channelled through
computer speakers.

The same headset with the same setup worked flawlessly in 19.10.


Thank you so much for your work! 20.04 is a joy to use.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  steinarne   1509 F pulseaudio
 /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 15 16:30:16 2020
InstallationDate: Installed on 2019-08-08 (251 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: LE-Bose NC 700 Headphones
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  steinarne   1509 F pulseaudio
 /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
Symptom_Type: No sound at all
Title: [LE-Bose NC 700 Headphones, playback] No sound at all
UpgradeStatus: Upgraded to focal on 2020-04-13 (2 days ago)
dmi.bios.date: 05/05/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: R0QET56W (1.33 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20LS0017MX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET56W(1.33):bd05/05/2019:svnLENOVO:pn20LS0017MX:pvrThinkPadL480:rvnLENOVO:rn20LS0017MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L480
dmi.product.name: 20LS0017MX
dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
dmi.product.version: ThinkPad L480
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  [Bluetooth Bose Headphones, playback] Sound plays exclusively from
  laptop speakers even when headset is selected as output device

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The computer will not send any sound output to the headset, and
  instead does all playback through the built in speakers. If headphones
  are connected by AUX sound will be sent there.

  Bluetooth media buttons work - I can pause music by tapping the
  bluetooth headset.

  If I change bluetooth audio quality the headset makes a notification
  sound, but playback continues as before through computer speakers.

  Audio tests (front left, front right) are also channelled through
  computer speakers.

  The same headset with the same setup worked flawlessly in 19.10.

  
  Thank you so much for your work! 20.04 is a joy to use.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steinarne   1509 F pulseaudio
   /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 15 16:30:16 2020
  InstallationDate: Installed on 2019-08-08 (251 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: LE-Bose NC 700 Headphones
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steinarne   1509 F pulseaudio
   /dev/snd/pcmC0D0c:   steinarne   1509 F...m pulseaudio
  Symptom_Type: No sound at all
  Title: [LE-Bose NC 700 Headphones, playback] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-04-13 (2 days ago)
  dmi.bios.date: 05/05/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET56W (1.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LS0017MX
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Touch-packages] [Bug 1518035] Re: package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package libjpeg-turbo-progs 1.3

[Bug Watch Updater]

** Changed in: libjpeg9 (Debian)
   Status: New => Fix Released

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

Title:
  package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying
  to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in
  package libjpeg-turbo-progs 1.3.0-0ubuntu2

Status in libjpeg-turbo package in Ubuntu:
  Fix Released
Status in libjpeg9 package in Ubuntu:
  Invalid
Status in libjpeg9 package in Debian:
  Fix Released

Bug description:
  just upgrading

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-progs 1:9a-2ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  Date: Mon Nov 16 15:38:22 2015
  Dependencies:
   gcc-5-base 5.2.1-23ubuntu1
   libc6 2.21-0ubuntu4
   libgcc1 1:5.2.1-23ubuntu1
   libjpeg9 1:9a-2ubuntu1
   multiarch-support 2.21-0ubuntu4
  DuplicateSignature:
   Unpacking libjpeg-progs (1:9a-2ubuntu1) over (8c-2ubuntu8) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-progs_1%3a9a-2ubuntu1_amd64.deb (--unpack):
trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in 
package libjpeg-turbo-progs 1.3.0-0ubuntu2
  ErrorMessage: trying to overwrite '/usr/share/man/man1/djpeg.1.gz', which is 
also in package libjpeg-turbo-progs 1.3.0-0ubuntu2
  InstallationDate: Installed on 2014-02-24 (633 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.3ubuntu1
   apt  1.0.10.2ubuntu1
  SourcePackage: libjpeg9
  Title: package libjpeg-progs 1:9a-2ubuntu1 failed to install/upgrade: trying 
to overwrite '/usr/share/man/man1/djpeg.1.gz', which is also in package 
libjpeg-turbo-progs 1.3.0-0ubuntu2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1518035/+subscriptions

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

[Touch-packages] [Bug 1872864] Re: appstream metadata not created

[Ken VanDine]

** Changed in: snap-store
   Status: Triaged => Invalid

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

Title:
  appstream metadata not created

Status in snap-store:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  The gnome-software packaged depends on appstream, which was bringing
  in that binary package in previous releases.  With the switch to
  seeding the snap this is causing a problem with the appstream cache
  never getting populated.  The appstream package includes an apt config
  that triggered the appstream cache refresh after update.  We need to
  explicitly seed the appstream package in ubuntu-desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-store/+bug/1872864/+subscriptions

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

[Touch-packages] [Bug 1872983] [NEW] in netcat-openbsd manpage, port argument description is not good

[dinar qurbanov]

Public bug reported:

in netcat-openbsd manpage, port argument description is not good. it is
this:

"port can be a specified as a numeric port number, or as a service name.
Ports may be specified in a range of the form nn-mm.  In general, a
destination port must be specified, unless the -U option is given."

why this is not good:

really, the port argument also is used as source port: while using "nc
-l 1234". this "nc -l 1234" is an example from the manpage in
"CLIENT/SERVER MODEL" section, which is immediately after the port
argument description. and this command works correctly. (while
connecting from other computer with nc IPaddressHere 1234, it works, and
in that case i think it is destination port, and thus source port for
the command on first laptop. it must be source port on first comp,
because a process must listen on a specific source port, they do not
usually listen on all ports, as i know from my experience... unless it
is something like tcpdump, and such programs run with root permission,
while netcat runs with non-root permission... and it is because
processes should not access to listening ports of other processes... )

the text "In general, a destination port must be specified, unless the
-U option is given." is not good, because it says "must" and says "in
general", and it is hard to disambiguate this. it can be understood as
"in general" refers to the all cases except the "unless the -U option is
given". in that way of understanding, it means that if the -U option is
not given, it must be source port only. but really it is not so. so, "in
general" does not refer to the all cases except the "unless the -U
option is given". it just means, that destination port is more usually
used in this place. but this way of understanding is also hard to
accept, because the usage, the intention of the extra word "must"
becomes not understood. it is extra, because it can be said shorter: "a
destination port is specified", or it can be said with less of the
fierce: "a destination port should be specified".

** Affects: netcat-openbsd (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  in netcat-openbsd manpage, port argument description is not good

Status in netcat-openbsd package in Ubuntu:
  New

Bug description:
  in netcat-openbsd manpage, port argument description is not good. it
  is this:

  "port can be a specified as a numeric port number, or as a service
  name.  Ports may be specified in a range of the form nn-mm.  In
  general, a destination port must be specified, unless the -U option is
  given."

  why this is not good:

  really, the port argument also is used as source port: while using "nc
  -l 1234". this "nc -l 1234" is an example from the manpage in
  "CLIENT/SERVER MODEL" section, which is immediately after the port
  argument description. and this command works correctly. (while
  connecting from other computer with nc IPaddressHere 1234, it works,
  and in that case i think it is destination port, and thus source port
  for the command on first laptop. it must be source port on first comp,
  because a process must listen on a specific source port, they do not
  usually listen on all ports, as i know from my experience... unless it
  is something like tcpdump, and such programs run with root permission,
  while netcat runs with non-root permission... and it is because
  processes should not access to listening ports of other processes... )

  the text "In general, a destination port must be specified, unless the
  -U option is given." is not good, because it says "must" and says "in
  general", and it is hard to disambiguate this. it can be understood as
  "in general" refers to the all cases except the "unless the -U option
  is given". in that way of understanding, it means that if the -U
  option is not given, it must be source port only. but really it is not
  so. so, "in general" does not refer to the all cases except the
  "unless the -U option is given". it just means, that destination port
  is more usually used in this place. but this way of understanding is
  also hard to accept, because the usage, the intention of the extra
  word "must" becomes not understood. it is extra, because it can be
  said shorter: "a destination port is specified", or it can be said
  with less of the fierce: "a destination port should be specified".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1872983/+subscriptions

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

[Touch-packages] [Bug 1872980] [NEW] Add field for PresentationIdentity in Online Accounts GUI

[Steven Jay Cohen]

Public bug reported:

Version: focal,now 3.36.0-1ubuntu1 amd64

~/.config/goa-1.0/accounts.conf has a field called PresentationIdentity.
When setting up a Google Account for example, that field gets set to the
email address. This field is used in places like Nautilus to show which
accounts something is connected to. If the addresses are similar (and
long) this can be a bit confusing.

Example:

johnjacobjingleheilmerschm...@gmail.com
johnjacob...@school.edu

If there were an option in the GUI to set the name (to Gmail and School
in this example), there would be less confusion in places like Nautilus.

Visual Example:

__|
johnjacobj|
johnjacobj|
__|

Becomes:

__|
Gmail |
   School |
__|

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

** Attachment added: "Showing my Nautilus after editing accounts.conf"
   
https://bugs.launchpad.net/bugs/1872980/+attachment/5354560/+files/Screenshot%20from%202020-04-15%2008-56-57.png

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

Title:
  Add field for PresentationIdentity in Online Accounts GUI

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

Bug description:
  Version: focal,now 3.36.0-1ubuntu1 amd64

  ~/.config/goa-1.0/accounts.conf has a field called
  PresentationIdentity. When setting up a Google Account for example,
  that field gets set to the email address. This field is used in places
  like Nautilus to show which accounts something is connected to. If the
  addresses are similar (and long) this can be a bit confusing.

  Example:

  johnjacobjingleheilmerschm...@gmail.com
  johnjacob...@school.edu

  If there were an option in the GUI to set the name (to Gmail and
  School in this example), there would be less confusion in places like
  Nautilus.

  Visual Example:

  __|
  johnjacobj|
  johnjacobj|
  __|

  Becomes:

  __|
  Gmail |
 School |
  __|

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1872980/+subscriptions

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

[Touch-packages] [Bug 1872557] Re: apt-get error: cnf-update-db - KeyError: 'suite' (focal)

[Julian Andres Klode]

** No longer affects: apt (Ubuntu)

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

Title:
  apt-get error: cnf-update-db - KeyError: 'suite' (focal)

Status in command-not-found:
  New

Bug description:
  "apt-get update" fails to run when command-not-found is installed on
  Ubuntu 20.04.

  To reproduce with Docker:
  docker pull ubuntu:20.04# Pull latest Ubuntu 20.04 docker image
  docker run -it ubuntu:20.04 # Start an Ubuntu 20.04 docker container

  # Within the container run:
  apt-get update
  apt-get -yy dist-upgrade
  apt-get -yy install command-not-found
  exec bash  # Reload bash to load command-not-found
  apt-get update # Update command-not-found database

  Traceback (most recent call last):
    File "/usr/lib/cnf-update-db", line 26, in 
  col.create(db)
    File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
93, in create
  self._fill_commands(con)
    File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
127, in _fill_commands
  self._parse_single_commands_file(con, fp)
    File "/usr/lib/python3/dist-packages/CommandNotFound/db/creator.py", line 
165, in _parse_single_commands_file
  suite=tagf.section["suite"]
  KeyError: 'suite'
  Reading package lists... Done
  E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
/usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then 
/usr/lib/cnf-update-db > /dev/null; fi'
  E: Sub-process returned an error code

To manage notifications about this bug go to:
https://bugs.launchpad.net/command-not-found/+bug/1872557/+subscriptions

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