[Touch-packages] [Bug 1850551] Re: Xorg freeze

[Daniel van Vugt]

Yes your kernel log is showing lots of errors:

[  808.338925] [drm:drm_mode_addfb2 [drm]] [FB:75]
[  808.355372] [drm:drm_mode_addfb2 [drm]] [FB:73]
[  808.557248] [drm:drm_mode_addfb2 [drm]] [FB:75]

However we are unable to help in this case because you are using an
unsupported PPA ("oibaf") for your graphics libraries, which is not from
Ubuntu. We often find that's the cause of serious graphics bugs. So this
bug will be marked as invalid. Please uninstall that PPA and then if you
continue to have problems feel free to open a new bug.


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

** Changed in: ubuntu
   Status: Incomplete => 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/1850551

Title:
  Xorg freeze

Status in Ubuntu:
  Invalid

Bug description:
  I recently upgraded to ubuntu-18.04 and the screen starts to freeze
  randomly. The CPU used to gets overheated on minimal use.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 02:03:51 2019
  DistUpgraded: 2019-07-26 05:15:58,339 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-64-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-66-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:078b]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:078b]
  InstallationDate: Installed on 2018-02-01 (635 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 15-3567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=bf1c9a5c-ebb8-4edf-8bde-0767ec9746b0 ro nouveau.modeset=0 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2019-07-25 (95 days ago)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.06.00
  dmi.board.name: 0D53F5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0D53F5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.100+git1910210630.c69c9c~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1909090730.ae5ac2~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1909090730.ae5ac2~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:19.1.0+git1910151930.b9bd80~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1910071930.bff5ec~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1906080730.ec2b45~oibaf~b

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

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

[Touch-packages] [Bug 1850823] Re: plz help mw

[Daniel van Vugt]

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

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

Title:
  plz help mw

Status in Ubuntu:
  Incomplete

Bug description:
  like big and big issue

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 22:38:46 2019
  DistUpgraded: 2019-10-31 07:37:10,130 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8329]
 Subsystem: Hewlett-Packard Company Radeon R7 M520 [103c:8329]
  InstallationDate: Installed on 2019-10-29 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05c8:03ac Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP TrueVision HD Camera
   Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 005: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-bs0xx
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-31 (0 days ago)
  dmi.bios.date: 05/10/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8329
  dmi.board.vendor: HP
  dmi.board.version: 23.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8329:rvr23.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bs0xx
  dmi.product.sku: 2EY79PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  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/+bug/1850823/+subscriptions

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

[Touch-packages] [Bug 1851865] Re: bug reporrt

[Daniel van Vugt]

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

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

Title:
  bug reporrt

Status in Ubuntu:
  Incomplete

Bug description:
  Not sure

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-68.77~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-68-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov  7 22:17:53 2019
  DistUpgraded: 2019-11-07 17:58:35,255 DEBUG /openCache(), new cache size 90136
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-66-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-68-generic, x86_64: installed
   virtualbox, 5.1.38, 4.15.0-66-generic, x86_64: installed
   virtualbox, 5.1.38, 4.15.0-68-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02a0]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02a0]
  InstallationDate: Installed on 2019-11-04 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  MachineType: Dell Inc. Studio 1737
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-68-generic 
root=UUID=28143eaf-551d-47e2-90aa-bfd9fb618e90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2019-11-07 (0 days ago)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P792H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1852907] Re: booting problem

[Daniel van Vugt]

This looks relevant:

[   27.460858] [ cut here ]
[   27.460859] Could not determine valid watermarks for inherited state
[   27.460920] WARNING: CPU: 0 PID: 414 at 
/build/linux-dWhjJj/linux-4.15.0/drivers/gpu/drm/i915/intel_display.c:14537 
intel_modeset_init+0xfcf/0x1010 [i915]
[   27.460921] Modules linked in: i915(+) drm_kms_helper drm i2c_algo_bit 
fb_sys_fops syscopyarea sysfillrect snd_seq snd_seq_device sysimgblt snd_timer 
toshiba_acpi iwldvm(+) mac80211 snd sparse_keymap joydev input_leds soundcore 
serio_raw iwlwifi cfg80211 industrialio lpc_ich shpchp mei_me mei mac_hid wmi 
video toshiba_haps sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic usbhid hid ahci psmouse libahci sdhci_pci sdhci atl1c
[   27.460945] CPU: 0 PID: 414 Comm: systemd-udevd Not tainted 
4.15.0-70-generic #79-Ubuntu
[   27.460945] Hardware name: TOSHIBA Satellite P845t/TOSHIBA, BIOS 
6.50 09/26/2012
[   27.460978] RIP: 0010:intel_modeset_init+0xfcf/0x1010 [i915]
[   27.460979] RSP: 0018:ad7d80cb39b0 EFLAGS: 00010286
[   27.460980] RAX:  RBX: 93deb3b8 RCX: 0006
[   27.460981] RDX: 0007 RSI: 0082 RDI: 93debf216490
[   27.460982] RBP: ad7d80cb3a40 R08: 0393 R09: 0004
[   27.460982] R10: 0040 R11: 0001 R12: 93deb3da3400
[   27.460983] R13: 93deb41af000 R14: ffea R15: 93deb3b80358
[   27.460984] FS:  7fdc5ae4b680() GS:93debf20() 
knlGS:
[   27.460985] CS:  0010 DS:  ES:  CR0: 80050033
[   27.460986] CR2: 5625d15bcd30 CR3: 000175632003 CR4: 001606f0
[   27.460987] Call Trace:
[   27.461016]  i915_driver_load+0xa73/0xe60 [i915]
[   27.461043]  i915_pci_probe+0x42/0x70 [i915]
[   27.461045]  local_pci_probe+0x47/0xa0
[   27.461047]  pci_device_probe+0x10e/0x1c0
[   27.461050]  driver_probe_device+0x30c/0x490
[   27.461052]  __driver_attach+0xcc/0xf0
[   27.461053]  ? driver_probe_device+0x490/0x490
[   27.461054]  bus_for_each_dev+0x70/0xc0
[   27.461056]  driver_attach+0x1e/0x20
[   27.461057]  bus_add_driver+0x1c7/0x270
[   27.461058]  ? 0xc08dd000
[   27.461059]  driver_register+0x60/0xe0
[   27.461060]  ? 0xc08dd000
[   27.461061]  __pci_register_driver+0x5a/0x60
[   27.461094]  i915_init+0x5c/0x5f [i915]
[   27.461096]  do_one_initcall+0x52/0x19f
[   27.461099]  ? __vunmap+0x8e/0xc0
[   27.461101]  ? _cond_resched+0x19/0x40
[   27.461103]  ? kmem_cache_alloc_trace+0xa6/0x1b0
[   27.461106]  ? do_init_module+0x27/0x213
[   27.461108]  do_init_module+0x5f/0x213
[   27.461110]  load_module+0x16bc/0x1f10
[   27.461113]  ? ima_post_read_file+0x96/0xa0
[   27.461115]  SYSC_finit_module+0xfc/0x120
[   27.461117]  ? SYSC_finit_module+0xfc/0x120
[   27.461119]  SyS_finit_module+0xe/0x10
[   27.461121]  do_syscall_64+0x73/0x130
[   27.461123]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[   27.461124] RIP: 0033:0x7fdc5a970839
[   27.461125] RSP: 002b:7fff4d3dabd8 EFLAGS: 0246 ORIG_RAX: 
0139
[   27.461126] RAX: ffda RBX: 556fba287290 RCX: 7fdc5a970839
[   27.461127] RDX:  RSI: 7fdc5a64f145 RDI: 0015
[   27.461127] RBP: 7fdc5a64f145 R08:  R09: 7fff4d3dacf0
[   27.461128] R10: 0015 R11: 0246 R12: 
[   27.461129] R13: 556fba29bdc0 R14: 0002 R15: 556fba287290
[   27.461130] Code: e9 46 fc ff ff 48 c7 c6 d7 bd 86 c0 48 c7 c7 2f b1 86 c0 
e8 e4 08 ab e2 0f 0b e9 73 fe ff ff 48 c7 c7 b0 15 88 c0 e8 d1 08 ab e2 <0f> 0b 
e9 4b fe ff ff 48 c7 c6 e4 bd 86 c0 48 c7 c7 2f b1 86 c0 
[   27.461153] ---[ end trace 71f8aa9290c71f88 ]---

** Summary changed:

- booting problem
+ [Ivy Bridge] Booting problem

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

Title:
  [Ivy Bridge] Booting problem

Status in linux package in Ubuntu:
  New

Bug description:
  the booting problem was sometimes solved by turn the laptop off and wait for 
few minutes to turn it on again. but it was not always worked.
  my laptop was preinstalled with windows 8 and upgraded into windows 10. then 
i chosed to erased all data and install ubuntu 18

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 17 19:08:41 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running

[Touch-packages] [Bug 1854998] Re: Kernel logs: hdaudio hdaudioC0D3: Unable to bind the codec

[Daniel van Vugt]

** Summary changed:

- snd_hda_codec_hdmi hdaudioC0D3: No i915 binding for Intel HDMI/DP codec
+ Kernel logs: hdaudio hdaudioC0D3: Unable to bind the codec

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

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

Title:
  Kernel logs: hdaudio hdaudioC0D3: Unable to bind the codec

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  hdaudio hdaudioC0D3: Unable to bind the codec

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec  3 21:28:01 2019
  InstallationDate: Installed on 2019-04-28 (219 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to eoan on 2019-11-03 (29 days ago)
  dmi.bios.date: 07/04/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P09ABE
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP350E7C-S0BFR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: BOARD REVISION 00
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP09ABE:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/351V5C/3540VC/3440VC:pvrP09ABE.012.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350E7C-S0BFR:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: Eureka
  dmi.product.name: 350V5C/351V5C/3540VC/3440VC
  dmi.product.sku: P09ABE.012.CP
  dmi.product.version: P09ABE.012.CP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Touch-packages] [Bug 1854877] Re: External HDMI display not working with Intel GPU

[Daniel van Vugt]

This might be related to the fact that some HDMI ports are only
connected to the Nvidia GPU and others only connected to Intel. That's
normal, but might not be the only factor here.

To help us diagnose it further please run this command to collect more
system info:

  apport-collect 1854877

** Tags added: eoan multimonitor

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

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

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

Title:
  External HDMI display not working with Intel GPU

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have Asus UX580 laptop with intel and nvidia 1050 video cards under Ubuntu 
19.10. 
  For some reason dual monitor setup with external monitor via HDMI only works 
if I switch to Nvidia only. If I select Intel GPU or "on-demand" in Nvidia 
server settings HDMI out is not working at all - xrandr shows HDMI out 
disconnected.

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

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

[Touch-packages] [Bug 1854838] Re: During soft power cycle test, the option to shut down not available in Ubuntu

[Daniel van Vugt]

** Tags added: bionic

** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu)

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

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

** Summary changed:

- During soft power cycle test, the option to shut down not available in Ubuntu
+ Power off dialog does not appear in ~0.4% of cases when the power button is 
pressed

** Changed in: gdm3 (Ubuntu)
   Importance: Undecided => Low

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

** Changed in: upower (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Power off dialog does not appear in ~0.4% of cases when the power
  button is pressed

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  18.04 LTS

  During soft power cycle test, the option to shut down not available in
  Ubuntu. This occurred 4/1000 times during test. Power needed to be
  removed from the unit in order to power down.

  
  Test steps -
  1) Press power button on unit with power connected
  2) Wait for system to boot - verify by observing Ubuntu OS "user select" 
screen
  3) Select the power button/icon
  4) Select "power off" from the available options
  Repeat steps 1-4 1000 times.

  Expected result -
  Each time the user selects the power button/icon they will be presented with 
options to power off or restart the unit.

  Actual result -
  Of 1000 cycles, 4 cycles resulted in the system not presenting the options to 
power off or restart the unit.

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

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

[Touch-packages] [Bug 1854737] Re: [arrandale] games dont start

[Daniel van Vugt]

Please run:

  sudo apt install mesa-utils
  glxinfo > glxinfo.txt

and then attach the file 'glxinfo.txt' to this bug.

Please also detail any error messages you get when "games don't start".

** Summary changed:

- games dont start
+ [arrandale] games dont start

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

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

Title:
  [arrandale] games dont start

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  games dont start on my intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  2 14:45:32 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Limited. Core Processor Integrated Graphics Controller 
[10cf:150a]
  InstallationDate: Installed on 2019-12-02 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: FUJITSU LIFEBOOK AH530
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=81837462-24c5-4880-b5bc-ed8f2196cdfe ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2019
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.22
  dmi.board.name: FJNBB06
  dmi.board.vendor: FUJITSU
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.22:bd04/03/2019:svnFUJITSU:pnLIFEBOOKAH530:pvr:rvnFUJITSU:rnFJNBB06:rvr:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK AH530
  dmi.sys.vendor: FUJITSU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1855514] [NEW] ibus preferences do not show up in search or indicator bar

[MrMister]

Public bug reported:

This might be two separate bugs. But I feel like they have the same
root, so I reported them as one.

Remarks:
[1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No 
Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] 
https://launchpad.net/bugs/1854610

[2] This report might be related to
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm
not sure. Someone with more technical knowledge should look into this.

 1 ---
steps to reproduce:
1) Have a fresh ubuntu 19.10 installation
2) install ibus and ibus-anthy
3) press windows key to open all applications
4) type in ibus

Actual:
5) ibus settings will not show up

Expected:
5) ibus settings show up

Workaround:
6) open Software center
7) search for ibus
8) click "launch there"

 2 --
steps to reproduce:
1) Have a fresh Ubuntu 19.10 installation
2) install ibus and ibus-anthy
3) Set input method to "ibus"
4) restart

Actual:
5) ibus preferences do not show up in the top bar at the indicators

Expected
6) "ibus preferences" is visible at the top bar inside the indicators area.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ibus 1.5.21-1~exp2ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec  7 13:10:27 2019
SourcePackage: ibus
UpgradeStatus: no upgrade log present

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


** Tags: amd64 apport-bug eoan

** Description changed:

  This might be two separate bugs. But I feel like they have the same
  root, so I reported them as one.
  
- Remarks: 
+ Remarks:
  [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No 
Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] 
https://launchpad.net/bugs/1854610
  
  [2] This report might be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm
  not sure. Someone with more technical knowledge should look into this.
  
   1 ---
  steps to reproduce:
  1) Have a fresh ubuntu 19.10 installation
  2) install ibus and ibus-anthy
- 3) press windows key to open all applications 
+ 3) press windows key to open all applications
  4) type in ibus
  
  Actual:
  5) ibus settings will not show up
  
  Expected:
  5) ibus settings show up
  
- Workaround: 
+ Workaround:
  6) open Software center
  7) search for ibus
  8) click "launch there"
  
   2 --
  steps to reproduce:
  1) Have a fresh Ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) Set input method to "ibus"
  4) restart
  
  Actual:
  5) ibus preferences do not show up in the top bar at the indicators
  
  Expected
  6) "ibus preferences" is visible at the top bar inside the indicators area.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.21-1~exp2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
- CurrentDesktop: XFCE
+ CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec  7 13:10:27 2019
  SourcePackage: ibus
- UpgradeStatus: Upgraded to eoan on 2019-12-01 (6 days ago)
+ UpgradeStatus: no upgrade log present

** Description changed:

  This might be two separate bugs. But I feel like they have the same
  root, so I reported them as one.
  
  Remarks:
  [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No 
Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] 
https://launchpad.net/bugs/1854610
  
  [2] This report might be related to
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm
  not sure. Someone with more technical knowledge should look into this.
  
   1 ---
  steps to reproduce:
  1) Have a fresh ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) press windows key to open all applications
  4) type in ibus
  
  Actual:
  5) ibus settings will not show up
  
  Expected:
  5) ibus settings show up
  
  Workaround:
  6) open Software center
  7) search for ibus
  8) click "launch there"
  
   2 --
  steps to reproduce:
  1) Have a fresh Ubuntu 19.10 installation
  2) install ibus and ibus-anthy
  3) Set input method to "ibus"
  4) restart
  
  Actual:
  5) ibus preferences do not show up in the top bar at the indicators
  
  Expected
  6) "ibus preferences" is visible at the top bar inside the indicators area.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.21-1~exp2ubuntu2
- ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
- Uname: Linux 5.3.0-23-generic x86_64
+ ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
+ Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  

[Touch-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

[Launchpad Bug Tracker]

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

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bluetooth headset selected as default sound output, yet sound outputs
  to laptop speakers

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1850766] Re: Bluetooth headset selected as default sound output, yet sound outputs to laptop speakers

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth headset selected as default sound output, yet sound outputs
  to laptop speakers

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 19.10 (using -proposed pocket)
  Kernel 5.3.0-21-generic #22
  pulseaudio 1:13.0-1ubuntu1
  bluez 5.50-0ubuntu4

  Device: Dell Inspiron 7370

  Step to reproduce
  =

  1. Pair a bluetooth headset with the laptop
  2. Go to sound settings
-> in "Output device", the bluetooth headset is selected
  3. Click Test, then "Front Left" and/or "Front Right"
-> the sound outputs to the laptop speakers instead of the bluetooth headset

  If I select "Speakers - Built-in audio" in the "Output device", then
  select back the bluetooth headset from the "Output device" list and
  test it, it works as expected.

  I tried this with 2 different bluetooth headsets (UE Boom and
  TaoTronics TT-BH07) which work fine on an Android device.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: pulseaudio 1:13.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-21.22-generic 5.3.7
  Uname: Linux 5.3.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1532 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 17:36:10 2019
  InstallationDate: Installed on 2019-07-02 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to eoan on 2019-10-19 (12 days ago)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1855513] [NEW] log file

[narendra]

Public bug reported:

required log and cli bash

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

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

Title:
  log file

Status in lxc package in Ubuntu:
  New

Bug description:
  required log and cli bash

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

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

[Touch-packages] [Bug 1855500] Re: obs-studio: "Failed to initialize video."

[Daniel van Vugt]

** Summary changed:

- OpenGL failure
+ obs-studio: "Failed to initialize video."

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

Title:
  obs-studio: "Failed to initialize video."

Status in obs-studio package in Ubuntu:
  New

Bug description:
  Trying to install and run obs-studio and "Failed to initialize video."
  Is the response.  Installed OpenGL and still having issues.  Pursuing
  other suggestions from online forums.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Dec  6 14:36:52 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0277]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0277]
  InstallationDate: Installed on 2018-05-16 (569 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Latitude E4200
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=b530de86-febb-4cdc-b67e-e870e3f68bb5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 0X271R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd12/06/2011:svnDellInc.:pnLatitudeE4200:pvr:rvnDellInc.:rn0X271R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E4200
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1855500/+subscriptions

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

[Touch-packages] [Bug 1854864] Re: "Dock" is used instead of "Dash"

[Daniel van Vugt]

** Tags added: eoan

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

** No longer affects: ubuntu-settings (Ubuntu)

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

Title:
  "Dock" is used instead of "Dash"

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  1) Open Settings app. The word "Dock" is displayed as an option.
  2) The word "Dash" should have been displayed instead of "Dock". The "Visual 
overview of Gnome" in the "Ubuntu Desktop Guide" refers to the icon bar as the 
"Dash".
  3) The word "Dock" was displayed instead of "Dash".

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

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

[Touch-packages] [Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash

[Daniel van Vugt]

OK. It sounds like the desktop-icons extension blocking is the main
problem here. A secondary problem, which might be an unfixable design
choice, is that it sounds like PulseAudio clients can block the sound of
the entire server.

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

** Also affects: gnome-shell-extension-desktop-icons (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Audio Stops Playing Briefly When Emptying Trash

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 19.10 and encountered this issue. I had a podcast
  playing in the background on Firefox v. 70.0.1 and I was deleting some
  files. I then proceeded to empty the trash and saw that the audio
  stops briefly till the "Empty all items from Trash?" prompt shows up.

  I was able to duplicate this many times and it even occurred with
  audio on Chrome.

  The expected way for things to work would be the audio keeps on
  playing, if I just empty the trash.

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

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

[Touch-packages] [Bug 1855442] Re: internal microphone not detected on L530 thinkpad 18.04.03

[Daniel van Vugt]

** Tags added: bionic

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

Title:
  internal microphone not detected on  L530 thinkpad 18.04.03

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It used to work but now on Ubuntu 18.04.03, my internal microphone on
  Thinkpad L530 is automatically muted and not recognised by pulse audio
  nor alsamixer. Actioning the physical mute/unmute button has no
  effect.

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

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

[Touch-packages] [Bug 1855511] [NEW] WLAN hardware no longer detected after disconnecting VPN

[James]

Public bug reported:

Issue began after installing (clean) Ubuntu 19.10.
network-manager:
  Installed: 1.20.4-2ubuntu2


Anytime I disconnect from my VPN service, I lose network connectivity.
When looking at Settings, I no longer see any WLAN/WiFi hardware.  To
work around this, I must either restart the computer or restart the
NetworkManager service.

Here is the syslog output beginning from when I disconnect from the VPN
service:

Dec  7 05:48:01 hostname NetworkManager[10146]:   [1575686881.6055] 
device (tun0): state change: activated -> unmanaged (reason 'unmanaged', 
sys-iface-state: 'removed')
Dec  7 05:48:01 hostname gnome-shell[27723]: Removing a network device that was 
not added
Dec  7 05:48:01 hostname dbus-daemon[751]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8785' (uid=0 
pid=10146 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Dec  7 05:48:01 hostname systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Dec  7 05:48:01 hostname dnsmasq[2171]: reading /etc/resolv.conf
Dec  7 05:48:01 hostname dnsmasq[2171]: using nameserver 127.0.0.53#53
Dec  7 05:48:01 hostname dbus-daemon[751]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
Dec  7 05:48:01 hostname systemd[1]: Started Network Manager Script Dispatcher 
Service.
Dec  7 05:48:01 hostname gnome-shell[27723]: JS ERROR: TypeError: 
connectionSettings is 
null#012_updateConnection@resource:///org/gnome/shell/ui/status/network.js:1922:9
Dec  7 05:48:01 hostname systemd-resolved[714]: Flushed all caches.
Dec  7 05:48:01 hostname avahi-daemon[790]: Joining mDNS multicast group on 
interface lo.IPv6 with address ::1.
Dec  7 05:48:01 hostname avahi-daemon[790]: New relevant interface lo.IPv6 for 
mDNS.
Dec  7 05:48:01 hostname avahi-daemon[790]: Registering new address record for 
::1 on lo.*.
Dec  7 05:48:01 hostname NetworkManager[10146]:   [1575686881.9239] 
manager: disable requested (sleeping: no  enabled: yes)
Dec  7 05:48:01 hostname NetworkManager[10146]:   [1575686881.9240] 
device (p2p-dev-wlp58s0): state change: disconnected -> unmanaged (reason 
'sleeping', sys-iface-state: 'managed')
Dec  7 05:48:01 hostname NetworkManager[10146]:   [1575686881.9247] 
manager: NetworkManager state is now ASLEEP
Dec  7 05:48:01 hostname NetworkManager[10146]:   [1575686881.9253] 
audit: op="networking-control" arg="off" pid=12063 uid=0 result="success"
Dec  7 05:48:01 hostname NetworkManager[10146]:   [1575686881.9254] 
device (wlp58s0): state change: activated -> deactivating (reason 'sleeping', 
sys-iface-state: 'managed')
Dec  7 05:48:01 hostname systemd-resolved[714]: Got packet on unexpected IP 
range, refusing.
Dec  7 05:48:01 hostname kernel: [436979.950637] wlp58s0: deauthenticating from 
40:f4:ec:13:53:af by local choice (Reason: 3=DEAUTH_LEAVING)
Dec  7 05:48:01 hostname systemd-resolved[714]: Got packet on unexpected IP 
range, refusing.
Dec  7 05:48:02 hostname NetworkManager[10146]:   [1575686882.0071] 
manager: enable requested (sleeping: no  enabled: no)
Dec  7 05:48:02 hostname NetworkManager[10146]:   [1575686882.0072] 
device (p2p-dev-wlp58s0): state change: unmanaged -> unavailable (reason 
'managed', sys-iface-state: 'managed')
Dec  7 05:48:02 hostname NetworkManager[10146]:   [1575686882.0096] 
manager: NetworkManager state is now DISCONNECTING
Dec  7 05:48:02 hostname NetworkManager[10146]:   [1575686882.0111] 
audit: op="networking-control" arg="on" pid=12068 uid=0 result="success"
Dec  7 05:48:02 hostname wpa_supplicant[758]: wlp58s0: CTRL-EVENT-DISCONNECTED 
bssid=40:f4:ec:13:53:af reason=3 locally_generated=1
Dec  7 05:48:02 hostname wpa_supplicant[758]: dbus: wpa_dbus_property_changed: 
no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/4
Dec  7 05:48:02 hostname wpa_supplicant[758]: wlp58s0: CTRL-EVENT-REGDOM-CHANGE 
init=CORE type=WORLD
Dec  7 05:48:02 hostname NetworkManager[10146]:   [1575686882.0481] 
sup-iface[0x55a4c662b910,wlp58s0]: connection disconnected (reason -3)
Dec  7 05:48:02 hostname NetworkManager[10146]:   [1575686882.0482] 
device (wlp58s0): supplicant interface state: completed -> disconnected
Dec  7 05:48:02 hostname gnome-shell[27723]: An active wireless connection, in 
infrastructure mode, involves no access point?
Dec  7 05:48:02 hostname NetworkManager[10146]:   [1575686882.0731] 
device (wlp58s0): state change: deactivating -> disconnected (reason 
'sleeping', sys-iface-state: 'managed')
Dec  7 05:48:02 hostname avahi-daemon[790]: Withdrawing address record for 
fe80::9eb6:d0ff:fed1:f2cb on wlp58s0.
Dec  7 05:48:02 hostname avahi-daemon[790]: Leaving mDNS multicast group on 
interface wlp58s0.IPv6 with address fe80::9eb6:d0ff:fed1:f2cb.
Dec  7 05:48:02 hostname avahi-daemon[790]: Interface wlp58s0.IPv6 no longer 
relevant for mDNS.
Dec  7 05:48:02 hostname NetworkManager[10146]:   [1575686882.0771] dhcp4 
(wlp58s0): cancele

[Touch-packages] [Bug 1854864] Re: "Dock" is used instead of "Dash"

[Clinton H]

** Summary changed:

- In the Settings app, the word "Dock" is used instead of "Dash"
+ "Dock" is used instead of "Dash"

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

Title:
  "Dock" is used instead of "Dash"

Status in gnome-shell package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Ubuntu 19.10

  1) Open Settings app. The word "Dock" is displayed as an option.
  2) The word "Dash" should have been displayed instead of "Dock". The "Visual 
overview of Gnome" in the "Ubuntu Desktop Guide" refers to the icon bar as the 
"Dash".
  3) The word "Dock" was displayed instead of "Dash".

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

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

[Touch-packages] [Bug 1855510] [NEW] Sort menu items alphabetically.

[Clinton H]

Public bug reported:

1) Ubuntu 19.10
2) 1:3.34.1-1ubuntu2
3) Menu items sorted alphabetically.
4) Menu items were not sorted alphabetically.

** Affects: ubuntu-settings (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-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1855510

Title:
  Sort menu items alphabetically.

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Menu items sorted alphabetically.
  4) Menu items were not sorted alphabetically.

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

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

[Touch-packages] [Bug 1855508] [NEW] Add an "Appearance" item to the menu.

[Clinton H]

Public bug reported:

1) Ubuntu 19.10
2) 1:3.34.1-1ubuntu2
3) The ability to change window appearance, icons, etc. Switch between light or 
dark theme.
4) Unable to change window appearance, icons, etc. Switch between light or dark 
theme.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "windows_icon_style.png"
   
https://bugs.launchpad.net/bugs/1855508/+attachment/5310389/+files/windows_icon_style.png

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

Title:
  Add an "Appearance" item to the menu.

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) The ability to change window appearance, icons, etc. Switch between light 
or dark theme.
  4) Unable to change window appearance, icons, etc. Switch between light or 
dark theme.

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

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

[Touch-packages] [Bug 1855507] [NEW] Previous screen or next screen is not displayed when the left or right arrow is pressed.

[Clinton H]

Public bug reported:

1) Ubuntu 19.10
2) 1:3.34.1-1ubuntu2
3) Select an item, press right arrow to show next screen. Press left arrow to 
show previous screen.
4) Selected an item, pressed right arrow, next screen was not displayed.

** Affects: ubuntu-settings (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-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1855507

Title:
  Previous screen or next screen is not displayed when the left or right
  arrow is pressed.

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Select an item, press right arrow to show next screen. Press left arrow to 
show previous screen.
  4) Selected an item, pressed right arrow, next screen was not displayed.

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

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

[Touch-packages] [Bug 1855505] [NEW] Could you add a "Secure Delete" option to the "Purge Trash and Temporary Files" option.

[Clinton H]

Public bug reported:

1) Ubuntu 19.10
2) 1:3.34.1-1ubuntu2
3) Option to enable secure deletion.
4) There is no option for secure deletion.

** Affects: ubuntu-settings (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-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1855505

Title:
  Could you add a "Secure Delete" option to the "Purge Trash and
  Temporary Files" option.

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  1) Ubuntu 19.10
  2) 1:3.34.1-1ubuntu2
  3) Option to enable secure deletion.
  4) There is no option for secure deletion.

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

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

[Touch-packages] [Bug 1846787] Re: systemd-logind leaves leftover sessions and scope files

[Mauricio Faria de Oliveira]

For documentation purposes, the (unrelated) autopkgtest failure on
docker.io is reported/worked on bug 1855481.

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

Title:
  systemd-logind leaves leftover sessions and scope files

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

Bug description:
  [Impact]
  Scope file leakage can cause SSH delays and reduce performance in systemd

  [Description]
  The current systemd-logind version present in Xenial can leave abandoned SSH
  sessions and scope files in cases where the host sees a lot of concurrent SSH
  connections. These leftover sessions can slow down systemd performance
  greatly, and can have an impact on sshd handling a great number of concurrent
  connections.

  To fix this issue, patches are needed in both dbus and systemd. These improve 
the
  performance of the communication between dbus and systemd, so that they can
  handle a better volume of events (e.g. SSH logins). All of those patches are
  already present from Bionic onwards, so we only need those fixes for Xenial.

  == Systemd ==
  Upstream patches:
  - core: use an AF_UNIX/SOCK_DGRAM socket for cgroup agent notification 
(d8fdc62037b5)

  $ git describe --contains d8fdc62037b5
  v230~71^2~2

  $ rmadison systemd
   systemd | 229-4ubuntu4 | xenial  | source, ...
   systemd | 229-4ubuntu21.21 | xenial-security | source, ...
   systemd | 229-4ubuntu21.22 | xenial-updates  | source, ... <
   systemd | 237-3ubuntu10| bionic  | source, ...
   systemd | 237-3ubuntu10.29 | bionic-security | source, ...
   systemd | 237-3ubuntu10.29 | bionic-updates  | source, ...
   systemd | 237-3ubuntu10.31 | bionic-proposed | source, ...

  == DBus ==
  Upstream patches:
  - Only read one message at a time if there are fds pending (892f084eeda0)
  - bus: Fix timeout restarts  (529600397bca)
  - DBusMainLoop: ensure all required timeouts are restarted (446b0d9ac75a)

  $ git describe --contains 892f084eeda0 529600397bca 446b0d9ac75a
  dbus-1.11.10~44
  dbus-1.11.10~45
  dbus-1.11.16~2

  $ rmadison dbus
   dbus | 1.10.6-1ubuntu3| xenial   | source, ...
   dbus | 1.10.6-1ubuntu3.4  | xenial-security  | source, ...
   dbus | 1.10.6-1ubuntu3.4  | xenial-updates   | source, ... <
   dbus | 1.12.2-1ubuntu1| bionic   | source, ...
   dbus | 1.12.2-1ubuntu1.1  | bionic-security  | source, ...
   dbus | 1.12.2-1ubuntu1.1  | bionic-updates   | source, ...

  [Test Case]
  1) Simulate a lot of concurrent SSH connections with e.g. a for loop:
  multipass@xenial-logind:~$ for i in {1..1000}; do sleep 0.1; ssh localhost 
sleep 1 & done

  2) Check for leaked sessions in /run/systemd/system/:
  multipass@xenial-logind:~$ ls -ld /run/systemd/system/session-*.scope*
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-103.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-104.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-105.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-106.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-110.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-111.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-112.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-113.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-114.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-115.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-116.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-117.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-118.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-119.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-120.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-121.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-122.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-123.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-126.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-131.scope.d
  drwxr-xr-x 2 root root 160 Oct 4 15:34 /run/systemd/system/session-134.scope.d
  ...

  [Regression Potential]
  As the patches change the communication socket between dbus and systemd, 
possible regressions could cause systemd to not be notified of dbus events and 
vice-versa. We could see units not getting started 

[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~rbalint/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/376485

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

Title:
  Please make /etc/update-motd.d snippets runnable by regular users

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New
Status in base-files source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * /etc/update-motd.d snippets throw errors when a normal user runs them.
   * This prevents showing MOTD when the user is dropped to a regular user's 
shell in WSL.

  [Test Case]

   * Run update-motd's autopkgtest and observe scripts not throwing
  errors.

  [Regression Potential]

   * The fixes are fairly simple, but to ensure no breakage the scripts
  are also run as root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions

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

[Touch-packages] [Bug 1852489] Re: [SRU] Enable support for Ussuri Cloud Archive

[Brian Murray]

Hello Corey, or anyone else affected,

Accepted software-properties into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/software-properties/0.96.24.32.12 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: software-properties (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

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

Title:
  [SRU] Enable support for Ussuri Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Bionic:
  Fix Committed
Status in software-properties source package in Focal:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:ussuri
 cloud-archive:ussuri-proposed

  This will also need to be SRU'd back to bionic.

  [Impact]
  End users have to manually enable the ussuri cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:ussuri
  sudo add-apt-repository cloud-archive:ussuri-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852489/+subscriptions

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

[Touch-packages] [Bug 1855402] Re: [TGL] mesa support

[Timo Aaltonen]

target should be 20.04, we'll need it on top of Mesa 20.0.x

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

Title:
  [TGL] mesa support

Status in intel:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Description:

  this feature tracks the updates of mesa 3d for TGL support.

  We will update the commitid list as necessary

  Target Release: 20.10
  Target version: TBD

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

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

[Touch-packages] [Bug 1855500] [NEW] OpenGL failure

[Saxon Holbrook]

Public bug reported:

Trying to install and run obs-studio and "Failed to initialize video."
Is the response.  Installed OpenGL and still having issues.  Pursuing
other suggestions from online forums.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: MATE
Date: Fri Dec  6 14:36:52 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0277]
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0277]
InstallationDate: Installed on 2018-05-16 (569 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
MachineType: Dell Inc. Latitude E4200
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=b530de86-febb-4cdc-b67e-e870e3f68bb5 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/06/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A22
dmi.board.name: 0X271R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd12/06/2011:svnDellInc.:pnLatitudeE4200:pvr:rvnDellInc.:rn0X271R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E4200
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


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

Title:
  OpenGL failure

Status in xorg package in Ubuntu:
  New

Bug description:
  Trying to install and run obs-studio and "Failed to initialize video."
  Is the response.  Installed OpenGL and still having issues.  Pursuing
  other suggestions from online forums.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Dec  6 14:36:52 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0277]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0277]
  InstallationDate: Installed on 2018-05-16 (569 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Latitude E4200
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=b530de86-febb-4cdc-b67e-e870e3f68bb5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A22
  dmi.board.name: 0X271R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA22:bd12/06/2011:svnDellInc.:pnLatitudeE4200:pvr:rvnDellInc.:rn0X271R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E4200
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-i

[Touch-packages] [Bug 1825946] Re: 'nm' autopkgtest fails due to GI stderr output

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted network-manager into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.2.6-0ubuntu0.16.04.4 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: network-manager (Ubuntu Xenial)
   Status: New => Fix Committed

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

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

Title:
  'nm' autopkgtest fails due to GI stderr output

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [impact]

  'nm' testcase contains:
  from gi.repository import NetworkManager, NMClient, GLib  


 

  which generates output to stderr:
  /tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning: 
NetworkManager was imported without specifying a version first. Use 
gi.require_version('NetworkManager', '1.0') before import to ensure that the 
right version gets loaded.

  the gi.require_version call has already been added to cosmic and
  disco.

  [test case]

  see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
  results.

  [other info]

  this only fails intermittently, but the failure is clearly not an
  actual problem.

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

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

[Touch-packages] [Bug 1855009] Please test proposed package

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted network-manager into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.2.6-0ubuntu0.16.04.4 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Fix Committed
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [impact]

  all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  autopkgtest [00:19:32]:  summary
  wpa-dhclient FAIL non-zero exit status 1
  nm.pyFAIL non-zero exit status 1
  killswitches-no-urfkill FAIL non-zero exit status 1
  urfkill-integration  FAIL non-zero exit status 1

  [regression potential]

  this essentially skips all the autopkgtests for network-manager on
  s390x, so regressions could occur now or in the future due to lack of
  testing on s390x.  However, all the tests already fail on s390x and
  have since xenial (or earlier), so there hasn't been any useful test
  coverage on s390x before; this doesn't change that.

  [other info]

  as mentioned in comment 2, wireless networking is specifically
  excluded on s390 systems:

  menuconfig WIRELESS
  bool "Wireless"
  depends on !S390
  default y

  The 'wpa-dhclient' test is specific to wireless, and both
  'killswitches-no-urfkill' and 'urfkill-integration' require rfkill
  which requires wireless, so none of those tests are valid on s390x,
  since it doesn't have any wireless support.

  However the 'nm.py' test does have some test cases that don't rely on
  wireless capability, but it would be much more intrusive to update the
  test to split out wired vs. wireless testing, and that might introduce
  test regressions on other archs.  The use case for network-manager on
  s390x in general is questionable, since s390x has no wireless support
  and obviously is never 'mobile', which are 2 main reasons to use
  network-manager instead of systemd-networkd.  Additionally, all tests
  are currently skipped on armhf due to the requirement for machine
  isolation (and armhf tests run in containers), so s390x is not the
  first arch to simply skip all network-manager autopkgtests.

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

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

[Touch-packages] [Bug 1855009] Re: autopkgtests all fail on s390x

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.3 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: network-manager (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

** Changed in: network-manager (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Fix Committed
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [impact]

  all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  autopkgtest [00:19:32]:  summary
  wpa-dhclient FAIL non-zero exit status 1
  nm.pyFAIL non-zero exit status 1
  killswitches-no-urfkill FAIL non-zero exit status 1
  urfkill-integration  FAIL non-zero exit status 1

  [regression potential]

  this essentially skips all the autopkgtests for network-manager on
  s390x, so regressions could occur now or in the future due to lack of
  testing on s390x.  However, all the tests already fail on s390x and
  have since xenial (or earlier), so there hasn't been any useful test
  coverage on s390x before; this doesn't change that.

  [other info]

  as mentioned in comment 2, wireless networking is specifically
  excluded on s390 systems:

  menuconfig WIRELESS
  bool "Wireless"
  depends on !S390
  default y

  The 'wpa-dhclient' test is specific to wireless, and both
  'killswitches-no-urfkill' and 'urfkill-integration' require rfkill
  which requires wireless, so none of those tests are valid on s390x,
  since it doesn't have any wireless support.

  However the 'nm.py' test does have some test cases that don't rely on
  wireless capability, but it would be much more intrusive to update the
  test to split out wired vs. wireless testing, and that might introduce
  test regressions on other archs.  The use case for network-manager on
  s390x in general is questionable, since s390x has no wireless support
  and obviously is never 'mobile', which are 2 main reasons to use
  network-manager instead of systemd-networkd.  Additionally, all tests
  are currently skipped on armhf due to the requirement for machine
  isolation (and armhf tests run in containers), so s390x is not the
  first arch to simply skip all network-manager autopkgtests.

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

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

[Touch-packages] [Bug 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.3 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: network-manager (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  autopkgtest 'nm' fails because it can't find dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  [impact]

  test 'nm' fails because dnsmasq-base isn't installed

  [test case]

  see test results
  http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

  [regression potential]

  low, test fix only

  [other info]

  The d/t/control file 'nm' test section, for bionic, needs to include
  dnsmasq-base in its dep list.

  disco and later already include dnsmasq-base in test dep packages, and
  in xenial network-manager directly depends on dnsmasq-base.  So this
  is needed only for bionic.

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

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

[Touch-packages] [Bug 1855009] Re: autopkgtests all fail on s390x

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted network-manager into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.16.0-0ubuntu2.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: network-manager (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-disco

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

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Committed
Status in network-manager source package in Bionic:
  Fix Committed
Status in network-manager source package in Disco:
  Fix Committed
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [impact]

  all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  autopkgtest [00:19:32]:  summary
  wpa-dhclient FAIL non-zero exit status 1
  nm.pyFAIL non-zero exit status 1
  killswitches-no-urfkill FAIL non-zero exit status 1
  urfkill-integration  FAIL non-zero exit status 1

  [regression potential]

  this essentially skips all the autopkgtests for network-manager on
  s390x, so regressions could occur now or in the future due to lack of
  testing on s390x.  However, all the tests already fail on s390x and
  have since xenial (or earlier), so there hasn't been any useful test
  coverage on s390x before; this doesn't change that.

  [other info]

  as mentioned in comment 2, wireless networking is specifically
  excluded on s390 systems:

  menuconfig WIRELESS
  bool "Wireless"
  depends on !S390
  default y

  The 'wpa-dhclient' test is specific to wireless, and both
  'killswitches-no-urfkill' and 'urfkill-integration' require rfkill
  which requires wireless, so none of those tests are valid on s390x,
  since it doesn't have any wireless support.

  However the 'nm.py' test does have some test cases that don't rely on
  wireless capability, but it would be much more intrusive to update the
  test to split out wired vs. wireless testing, and that might introduce
  test regressions on other archs.  The use case for network-manager on
  s390x in general is questionable, since s390x has no wireless support
  and obviously is never 'mobile', which are 2 main reasons to use
  network-manager instead of systemd-networkd.  Additionally, all tests
  are currently skipped on armhf due to the requirement for machine
  isolation (and armhf tests run in containers), so s390x is not the
  first arch to simply skip all network-manager autopkgtests.

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

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

[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~rbalint/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/376480

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

Title:
  Please make /etc/update-motd.d snippets runnable by regular users

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New
Status in base-files source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * /etc/update-motd.d snippets throw errors when a normal user runs them.
   * This prevents showing MOTD when the user is dropped to a regular user's 
shell in WSL.

  [Test Case]

   * Run update-motd's autopkgtest and observe scripts not throwing
  errors.

  [Regression Potential]

   * The fixes are fairly simple, but to ensure no breakage the scripts
  are also run as root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions

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

[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users

[Brian Murray]

Hello Balint, or anyone else affected,

Accepted base-files into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/base-
files/10.2ubuntu7.19.10.0 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

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

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

Title:
  Please make /etc/update-motd.d snippets runnable by regular users

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New
Status in base-files source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * /etc/update-motd.d snippets throw errors when a normal user runs them.
   * This prevents showing MOTD when the user is dropped to a regular user's 
shell in WSL.

  [Test Case]

   * Run update-motd's autopkgtest and observe scripts not throwing
  errors.

  [Regression Potential]

   * The fixes are fairly simple, but to ensure no breakage the scripts
  are also run as root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions

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

[Touch-packages] [Bug 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.20.4-2ubuntu3

---
network-manager (1.20.4-2ubuntu3) focal; urgency=medium

  * d/t/killswitches-no-urfkill, d/t/urfkill-integration,
d/t/wpa-dhclient, d/t/nm.py, d/t/control:
- skip tests on s390 due to missing wireless kernel support
  (LP: #1855009)
- skip tests on i386 since there is no i386 kernel anymore,
  so we can't build our custom rfkill test module
  (LP: #1855183)

 -- Dan Streetman   Wed, 04 Dec 2019 12:17:37
-0500

** Changed in: network-manager (Ubuntu Focal)
   Status: In Progress => Fix Released

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

Title:
  autopkgtest fails on i386 because linux-headers-generic no longer
  built for i386

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [impact]

  the kernel is no longer built for i386, starting with Eoan.  However
  some of the autopkgtests depend on linux-headers-generic, which isn't
  available for i386, so the test fails with bad dependency.

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386

  Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none 
@un H >
Removing autopkgtest-satdep:i386 because I can't find 
linux-headers-generic:i386

  [regression potential]

  test case fix only, regressions would involve more/continued test
  failure

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

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

[Touch-packages] [Bug 1851806] Re: 'module' object has no attribute 'O_PATH'

[Albert Pool]

The above looks like some Python 3 code ended up in a Python 2.7
document, given opener= was added in Python 3.3 it seems.

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

Title:
  'module' object has no attribute 'O_PATH'

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I encountered the following exception in python-apport while
  encountering an exception `bup` which uses `python-apport`. I'm sure
  that the exception lies in the responsibility of `python-apport` (the
  `AttributeError` stacktrace is relevant):

  ```
  Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in 
  update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
  mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
  os.rename(self.tmpname, self.filename)
  OSError: [Errno 13] Permission denied
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/bup/bup/helpers.py", line 916, in newhook
  return oldhook(exctype, value, traceback)
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in 
apport_excepthook
  pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 544, in 
add_proc_info
  proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH | 
os.O_DIRECTORY)
  AttributeError: 'module' object has no attribute 'O_PATH'

  Original exception was:
  Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in 
  update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
  mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
  os.rename(self.tmpname, self.filename)
  OSError: [Errno 13] Permission denied
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: python-apport 2.20.11-0ubuntu8.2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log'
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 10:43:02 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago)

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

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

[Touch-packages] [Bug 1855009] Re: autopkgtests all fail on s390x

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager - 1.20.4-2ubuntu3

---
network-manager (1.20.4-2ubuntu3) focal; urgency=medium

  * d/t/killswitches-no-urfkill, d/t/urfkill-integration,
d/t/wpa-dhclient, d/t/nm.py, d/t/control:
- skip tests on s390 due to missing wireless kernel support
  (LP: #1855009)
- skip tests on i386 since there is no i386 kernel anymore,
  so we can't build our custom rfkill test module
  (LP: #1855183)

 -- Dan Streetman   Wed, 04 Dec 2019 12:17:37
-0500

** Changed in: network-manager (Ubuntu Focal)
   Status: In Progress => Fix Released

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

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Bionic:
  In Progress
Status in network-manager source package in Disco:
  In Progress
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  Fix Released

Bug description:
  [impact]

  all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  autopkgtest [00:19:32]:  summary
  wpa-dhclient FAIL non-zero exit status 1
  nm.pyFAIL non-zero exit status 1
  killswitches-no-urfkill FAIL non-zero exit status 1
  urfkill-integration  FAIL non-zero exit status 1

  [regression potential]

  this essentially skips all the autopkgtests for network-manager on
  s390x, so regressions could occur now or in the future due to lack of
  testing on s390x.  However, all the tests already fail on s390x and
  have since xenial (or earlier), so there hasn't been any useful test
  coverage on s390x before; this doesn't change that.

  [other info]

  as mentioned in comment 2, wireless networking is specifically
  excluded on s390 systems:

  menuconfig WIRELESS
  bool "Wireless"
  depends on !S390
  default y

  The 'wpa-dhclient' test is specific to wireless, and both
  'killswitches-no-urfkill' and 'urfkill-integration' require rfkill
  which requires wireless, so none of those tests are valid on s390x,
  since it doesn't have any wireless support.

  However the 'nm.py' test does have some test cases that don't rely on
  wireless capability, but it would be much more intrusive to update the
  test to split out wired vs. wireless testing, and that might introduce
  test regressions on other archs.  The use case for network-manager on
  s390x in general is questionable, since s390x has no wireless support
  and obviously is never 'mobile', which are 2 main reasons to use
  network-manager instead of systemd-networkd.  Additionally, all tests
  are currently skipped on armhf due to the requirement for machine
  isolation (and armhf tests run in containers), so s390x is not the
  first arch to simply skip all network-manager autopkgtests.

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

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

[Touch-packages] [Bug 1851806] Re: 'module' object has no attribute 'O_PATH'

[Albert Pool]

Simply removing O_PATH from the line in question leads to:

Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 597, in 
app.run_argv()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 661, in run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 559, in 
run_update_report
self.report.add_proc_environ()
  File "/usr/lib/python2.7/dist-packages/apport/report.py", line 592, in 
add_proc_environ
env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
  File "/usr/lib/python2.7/dist-packages/apport/report.py", line 73, in 
_read_file
with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
TypeError: 'opener' is an invalid keyword argument for this function

(Linux Mint 18.2, python-apport 2.20.1-0ubuntu2.21)

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

Title:
  'module' object has no attribute 'O_PATH'

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I encountered the following exception in python-apport while
  encountering an exception `bup` which uses `python-apport`. I'm sure
  that the exception lies in the responsibility of `python-apport` (the
  `AttributeError` stacktrace is relevant):

  ```
  Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in 
  update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
  mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
  os.rename(self.tmpname, self.filename)
  OSError: [Errno 13] Permission denied
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/bup/bup/helpers.py", line 916, in newhook
  return oldhook(exctype, value, traceback)
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in 
apport_excepthook
  pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 544, in 
add_proc_info
  proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH | 
os.O_DIRECTORY)
  AttributeError: 'module' object has no attribute 'O_PATH'

  Original exception was:
  Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in 
  update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
  mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
  os.rename(self.tmpname, self.filename)
  OSError: [Errno 13] Permission denied
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: python-apport 2.20.11-0ubuntu8.2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log'
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 10:43:02 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago)

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

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

[Touch-packages] [Bug 1855492] [NEW] Please drop LTSP specific Ubuntu diff

[Alkis Georgopoulos]

Public bug reported:

Hi, I'm upstream and Debian/Ubuntu maintainer for LTSP.
In the past, LTSP required some patches in isc-dhcp-server and tftpd-hpa.
Since Bullseye and Focal these are no longer needed and they should be dropped.

Specifically, LTSP now defaults to dnsmasq, and in the case where users
need isc-dhcp-server instead, the LTSP wiki (https://ltsp.org/advanced
/isc-dhcp-server/) proposes manually editing the appropriate file. We do
not ship an /etc/ltsp/dhcpd.conf file anymore at all.

Thank you.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Please drop LTSP specific Ubuntu diff

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Hi, I'm upstream and Debian/Ubuntu maintainer for LTSP.
  In the past, LTSP required some patches in isc-dhcp-server and tftpd-hpa.
  Since Bullseye and Focal these are no longer needed and they should be 
dropped.

  Specifically, LTSP now defaults to dnsmasq, and in the case where
  users need isc-dhcp-server instead, the LTSP wiki
  (https://ltsp.org/advanced/isc-dhcp-server/) proposes manually editing
  the appropriate file. We do not ship an /etc/ltsp/dhcpd.conf file
  anymore at all.

  Thank you.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1855492/+subscriptions

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

[Touch-packages] [Bug 1851806] Re: 'module' object has no attribute 'O_PATH'

[Launchpad Bug Tracker]

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

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

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

Title:
  'module' object has no attribute 'O_PATH'

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I encountered the following exception in python-apport while
  encountering an exception `bup` which uses `python-apport`. I'm sure
  that the exception lies in the responsibility of `python-apport` (the
  `AttributeError` stacktrace is relevant):

  ```
  Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in 
  update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
  mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
  os.rename(self.tmpname, self.filename)
  OSError: [Errno 13] Permission denied
  Error in sys.excepthook:
  Traceback (most recent call last):
File "/usr/lib/bup/bup/helpers.py", line 916, in newhook
  return oldhook(exctype, value, traceback)
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in 
apport_excepthook
  pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 544, in 
add_proc_info
  proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH | 
os.O_DIRECTORY)
  AttributeError: 'module' object has no attribute 'O_PATH'

  Original exception was:
  Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in 
  update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
  mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
  os.rename(self.tmpname, self.filename)
  OSError: [Errno 13] Permission denied
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: python-apport 2.20.11-0ubuntu8.2
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log'
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  8 10:43:02 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago)

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

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

[Touch-packages] [Bug 1855092] Re: [SRU] Please set MOTD_SHOWN=pam when MOTD was shown

[Brian Murray]

Hello Balint, or anyone else affected,

Accepted pam into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/pam/1.3.1-5ubuntu1.19.10.0 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: pam (Ubuntu Eoan)
   Status: New => Fix Committed

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

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

Title:
  [SRU] Please set MOTD_SHOWN=pam when MOTD was shown

Status in pam package in Ubuntu:
  In Progress
Status in pam source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

    * Users of containers may never see the MOTD of the container if they are 
always to the container's shell without PAM being involved.
    * MOTD contains important information about the system's health including 
the security updates to be installed thus it is desired to show MOTD in 
container shells, too.
    * The fix in update-motd is creating a snippet in /etc/profile.d which 
shows MOTD, but only if UPDATE_MOTD is not set, to avoid printing MOTD twice.

  [Test Case]

   * Log in to the system, where PAM prints the MOTD.
   * After seeing the MOTD observe MOTD_SHOWN set:
     $ echo $MOTD_SHOWN
     pam
     $

  [Regression Potential]

   * The fix is simple thus it is unlikely to see any regression due to bad 
implementation.
   * The newly set environment variable may interact with existing software, 
but this variable seems to be not used:
   https://codesearch.debian.net/search?q=MOTD_SHOWN&literal=1

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

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

[Touch-packages] [Bug 1855009] Re: autopkgtests all fail on s390x

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted network-manager into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.20.4-2ubuntu2.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: network-manager (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Bionic:
  In Progress
Status in network-manager source package in Disco:
  In Progress
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [impact]

  all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  autopkgtest [00:19:32]:  summary
  wpa-dhclient FAIL non-zero exit status 1
  nm.pyFAIL non-zero exit status 1
  killswitches-no-urfkill FAIL non-zero exit status 1
  urfkill-integration  FAIL non-zero exit status 1

  [regression potential]

  this essentially skips all the autopkgtests for network-manager on
  s390x, so regressions could occur now or in the future due to lack of
  testing on s390x.  However, all the tests already fail on s390x and
  have since xenial (or earlier), so there hasn't been any useful test
  coverage on s390x before; this doesn't change that.

  [other info]

  as mentioned in comment 2, wireless networking is specifically
  excluded on s390 systems:

  menuconfig WIRELESS
  bool "Wireless"
  depends on !S390
  default y

  The 'wpa-dhclient' test is specific to wireless, and both
  'killswitches-no-urfkill' and 'urfkill-integration' require rfkill
  which requires wireless, so none of those tests are valid on s390x,
  since it doesn't have any wireless support.

  However the 'nm.py' test does have some test cases that don't rely on
  wireless capability, but it would be much more intrusive to update the
  test to split out wired vs. wireless testing, and that might introduce
  test regressions on other archs.  The use case for network-manager on
  s390x in general is questionable, since s390x has no wireless support
  and obviously is never 'mobile', which are 2 main reasons to use
  network-manager instead of systemd-networkd.  Additionally, all tests
  are currently skipped on armhf due to the requirement for machine
  isolation (and armhf tests run in containers), so s390x is not the
  first arch to simply skip all network-manager autopkgtests.

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

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

[Touch-packages] [Bug 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386

[Brian Murray]

Hello Dan, or anyone else affected,

Accepted network-manager into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.20.4-2ubuntu2.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: network-manager (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  autopkgtest fails on i386 because linux-headers-generic no longer
  built for i386

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Eoan:
  Fix Committed
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [impact]

  the kernel is no longer built for i386, starting with Eoan.  However
  some of the autopkgtests depend on linux-headers-generic, which isn't
  available for i386, so the test fails with bad dependency.

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386

  Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none 
@un H >
Removing autopkgtest-satdep:i386 because I can't find 
linux-headers-generic:i386

  [regression potential]

  test case fix only, regressions would involve more/continued test
  failure

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

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

[Touch-packages] [Bug 1855271] Proposed package upload rejected

[Brian Murray]

An upload of base-files to eoan-proposed has been rejected from the
upload queue for the following reason: "This version number seems like a
strange mash-up of focal and eoan's version.".

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

Title:
  Please make /etc/update-motd.d snippets runnable by regular users

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New

Bug description:
  [Impact]

   * /etc/update-motd.d snippets throw errors when a normal user runs them.
   * This prevents showing MOTD when the user is dropped to a regular user's 
shell in WSL.

  [Test Case]

   * Run update-motd's autopkgtest and observe scripts not throwing
  errors.

  [Regression Potential]

   * The fixes are fairly simple, but to ensure no breakage the scripts
  are also run as root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions

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

[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users

[Steve Langasek]

** Description changed:

  [Impact]
  
-  * /etc/update-motd.d snippets throw errors when a nomal user runs them.
+  * /etc/update-motd.d snippets throw errors when a normal user runs them.
   * This prevents showing MOTD when the user is dropped to a regular user's 
shell in WSL.
  
  [Test Case]
  
   * Run update-motd's autopkgtest and observe scripts not throwing
  errors.
  
  [Regression Potential]
  
   * The fixes are fairly simple, but to ensure no breakage the scripts
  are also run as root.

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

Title:
  Please make /etc/update-motd.d snippets runnable by regular users

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New

Bug description:
  [Impact]

   * /etc/update-motd.d snippets throw errors when a normal user runs them.
   * This prevents showing MOTD when the user is dropped to a regular user's 
shell in WSL.

  [Test Case]

   * Run update-motd's autopkgtest and observe scripts not throwing
  errors.

  [Regression Potential]

   * The fixes are fairly simple, but to ensure no breakage the scripts
  are also run as root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions

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

[Touch-packages] [Bug 1855482] Re: Apport caused the entire system to freeze when I forced-quit it

[Seija Kijin]

** Attachment removed: "xserver-xorg-video-radeon_18.0.1-1_amd64.deb"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1855482/+attachment/5310298/+files/xserver-xorg-video-radeon_18.0.1-1_amd64.deb

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

Title:
  Apport caused the entire system to freeze when I forced-quit it

Status in apport package in Ubuntu:
  New

Bug description:
  When I wanted to stop Apport from uploading something that did not
  need to be uploaded, I clicked the X button on the Window meant to
  close it.

  Apport froze, and I was asked whether to force-quit the program or
  wait. I forced-quit the app. The entire machine froze, not even the
  machine responded, even though only apport was quit.

  apport:
Installed: 2.20.9-0ubuntu7.9
Candidate: 2.20.9-0ubuntu7.9
Version table:
   *** 2.20.9-0ubuntu7.9 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main i386 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.20.9-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.9
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Fri Dec  6 13:53:58 2019
  InstallationDate: Installed on 2019-12-01 (5 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1855482] Re: Apport caused the entire system to freeze when I forced-quit it

[Seija Kijin]

The issue occurred on December 6, 2019, at 1:57 PM, EDT.

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

Title:
  Apport caused the entire system to freeze when I forced-quit it

Status in apport package in Ubuntu:
  New

Bug description:
  When I wanted to stop Apport from uploading something that did not
  need to be uploaded, I clicked the X button on the Window meant to
  close it.

  Apport froze, and I was asked whether to force-quit the program or
  wait. I forced-quit the app. The entire machine froze, not even the
  machine responded, even though only apport was quit.

  apport:
Installed: 2.20.9-0ubuntu7.9
Candidate: 2.20.9-0ubuntu7.9
Version table:
   *** 2.20.9-0ubuntu7.9 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main i386 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.20.9-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.9
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Fri Dec  6 13:53:58 2019
  InstallationDate: Installed on 2019-12-01 (5 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1855482] Re: Apport caused the entire system to freeze when I forced-quit it

[Seija Kijin]

** Attachment added: "backupLogs.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1855482/+attachment/5310301/+files/backupLogs.tar.gz

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

Title:
  Apport caused the entire system to freeze when I forced-quit it

Status in apport package in Ubuntu:
  New

Bug description:
  When I wanted to stop Apport from uploading something that did not
  need to be uploaded, I clicked the X button on the Window meant to
  close it.

  Apport froze, and I was asked whether to force-quit the program or
  wait. I forced-quit the app. The entire machine froze, not even the
  machine responded, even though only apport was quit.

  apport:
Installed: 2.20.9-0ubuntu7.9
Candidate: 2.20.9-0ubuntu7.9
Version table:
   *** 2.20.9-0ubuntu7.9 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main i386 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.20.9-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.9
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Fri Dec  6 13:53:58 2019
  InstallationDate: Installed on 2019-12-01 (5 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1855482] [NEW] Apport caused the entire system to freeze when I forced-quit it

[Seija Kijin]

Public bug reported:

When I wanted to stop Apport from uploading something that did not need
to be uploaded, I clicked the X button on the Window meant to close it.

Apport froze, and I was asked whether to force-quit the program or wait.
I forced-quit the app. The entire machine froze, not even the machine
responded, even though only apport was quit.

apport:
  Installed: 2.20.9-0ubuntu7.9
  Candidate: 2.20.9-0ubuntu7.9
  Version table:
 *** 2.20.9-0ubuntu7.9 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
100 /var/lib/dpkg/status
 2.20.9-0ubuntu7 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7.9
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
ApportLog:
 
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Fri Dec  6 13:53:58 2019
InstallationDate: Installed on 2019-12-01 (5 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "xserver-xorg-video-radeon_18.0.1-1_amd64.deb"
   
https://bugs.launchpad.net/bugs/1855482/+attachment/5310298/+files/xserver-xorg-video-radeon_18.0.1-1_amd64.deb

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

Title:
  Apport caused the entire system to freeze when I forced-quit it

Status in apport package in Ubuntu:
  New

Bug description:
  When I wanted to stop Apport from uploading something that did not
  need to be uploaded, I clicked the X button on the Window meant to
  close it.

  Apport froze, and I was asked whether to force-quit the program or
  wait. I forced-quit the app. The entire machine froze, not even the
  machine responded, even though only apport was quit.

  apport:
Installed: 2.20.9-0ubuntu7.9
Candidate: 2.20.9-0ubuntu7.9
Version table:
   *** 2.20.9-0ubuntu7.9 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main i386 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   2.20.9-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.9
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Fri Dec  6 13:53:58 2019
  InstallationDate: Installed on 2019-12-01 (5 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:20.04.6

---
ubuntu-release-upgrader (1:20.04.6) focal; urgency=medium

  * debian/control: Update Vcs-*: URLs
  * Rename .bzrignore to .gitignore
  * debian/gbp.conf: Add default configuration
  * debian/gbp.conf: Move prebuild command here from .bzr-builddeb/default.conf
  * Build source on Focal (LP: #1855437)

ubuntu-release-upgrader (1:20.04.5) focal; urgency=medium

  * debian/release-upgrade-motd: Don't try to update cached info
as a regular user. That would fail.
(LP: #1855271)

 -- Balint Reczey   Fri, 06 Dec 2019 12:55:52 +0100

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please make /etc/update-motd.d snippets runnable by regular users

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  New

Bug description:
  [Impact]

   * /etc/update-motd.d snippets throw errors when a nomal user runs them.
   * This prevents showing MOTD when the user is dropped to a regular user's 
shell in WSL.

  [Test Case]

   * Run update-motd's autopkgtest and observe scripts not throwing
  errors.

  [Regression Potential]

   * The fixes are fairly simple, but to ensure no breakage the scripts
  are also run as root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions

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

[Touch-packages] [Bug 1855478] [NEW] [Satellite Pro R50-C, Intel Broadwell HDMI, Digital Out, HDMI] No sound at all

[Azeline]

Public bug reported:

[Satellite Pro R50-C, Intel Broadwell HDMI, Digital Out, HDMI] No sound at all
Alsa mixer is set on 00 00 00 00 with no possibility to change
I've tried pressing F6 to change the default sound card, it doesn't work either.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  azeline1653 F pulseaudio
 /dev/snd/controlC1:  azeline1653 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Dec  6 19:54:13 2019
InstallationDate: Installed on 2017-12-05 (730 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
Symptom_Card: Audio interne - HDA Intel HDMI
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1148 F pulseaudio
  azeline1653 F pulseaudio
 /dev/snd/controlC1:  gdm1148 F pulseaudio
  azeline1653 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [Satellite Pro R50-C, Intel Broadwell HDMI, Digital Out, HDMI] No sound 
at all
UpgradeStatus: Upgraded to bionic on 2018-09-12 (450 days ago)
dmi.bios.date: 03/17/2016
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 6.20
dmi.board.asset.tag: 00
dmi.board.name: Satellite Pro R50-C
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion6.20:bd03/17/2016:svnTOSHIBA:pnSatelliteProR50-C:pvrPS562E-02W01TFR:rvnTOSHIBA:rnSatelliteProR50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.family: 00
dmi.product.name: Satellite Pro R50-C
dmi.product.version: PS562E-02W01TFR
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug bionic

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

Title:
  [Satellite Pro R50-C, Intel Broadwell HDMI, Digital Out, HDMI] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [Satellite Pro R50-C, Intel Broadwell HDMI, Digital Out, HDMI] No sound at all
  Alsa mixer is set on 00 00 00 00 with no possibility to change
  I've tried pressing F6 to change the default sound card, it doesn't work 
either.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  azeline1653 F pulseaudio
   /dev/snd/controlC1:  azeline1653 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  6 19:54:13 2019
  InstallationDate: Installed on 2017-12-05 (730 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Audio interne - HDA Intel HDMI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1148 F pulseaudio
azeline1653 F pulseaudio
   /dev/snd/controlC1:  gdm1148 F pulseaudio
azeline1653 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Satellite Pro R50-C, Intel Broadwell HDMI, Digital Out, HDMI] No 
sound at all
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (450 days ago)
  dmi.bios.date: 03/17/2016
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 6.20
  dmi.board.asset.tag: 00
  dmi.board.name: Satellite Pro R50-C
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion6.20:bd03/17/2016:svnTOSHIBA:pnSatelliteProR50-C:pvrPS562E-02W01TFR:rvnTOSHIBA:rnSatelliteProR50-C:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: Satellite Pro R50-C
  dmi.pr

[Touch-packages] [Bug 1849261] Re: Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart=

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: Triaged => In Progress

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

Title:
  Update systemd for ubuntu 18.04 with fix for interaction between
  OnFailure= and Restart=

Status in Ubuntu on IBM z Systems:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386
  ppc64el s390x is available,

  The pull request for 240 is now requested to backport to 237 for
  Ubuntu 18.04, which is integrated within the IBM product.

  Pull request: https://github.com/systemd/systemd/pull/9158

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1849261/+subscriptions

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

[Touch-packages] [Bug 1849261] Re: Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart=

[Dan Streetman]

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

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

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

** Tags added: bionic ddstreet systemd

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

Title:
  Update systemd for ubuntu 18.04 with fix for interaction between
  OnFailure= and Restart=

Status in Ubuntu on IBM z Systems:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386
  ppc64el s390x is available,

  The pull request for 240 is now requested to backport to 237 for
  Ubuntu 18.04, which is integrated within the IBM product.

  Pull request: https://github.com/systemd/systemd/pull/9158

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1849261/+subscriptions

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

[Touch-packages] [Bug 1852018] Re: Audio Stops Playing Briefly When Emptying Trash

[Kashif Khan]

Im doing it via the desktop icon. Ive also noticed stops in music or
freezes when Im running CLI commands such as update etc.

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

Title:
  Audio Stops Playing Briefly When Emptying Trash

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 19.10 and encountered this issue. I had a podcast
  playing in the background on Firefox v. 70.0.1 and I was deleting some
  files. I then proceeded to empty the trash and saw that the audio
  stops briefly till the "Empty all items from Trash?" prompt shows up.

  I was able to duplicate this many times and it even occurred with
  audio on Chrome.

  The expected way for things to work would be the audio keeps on
  playing, if I just empty the trash.

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

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

[Touch-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

[clayg]

After a reboot applied an automatic system update I applied today to my
18.04.3 LTS IBM ThinkPad X1 Carbon my mouse wasn't working!

Some comments in scripts I'd left around helped me found my way back to
this bug and ...

modprobe -r i2c-i801

... fixed the immediate issue.

But I saw the "scroll doesn't work after suspend" issue again.

Right now I've un-commented the i2c_i801 in
/etc/modprobe.d/blacklist.conf and I also feel like I had to REadd
psmouse.synaptics_intertouch=0 in /etc/default/grub - could that have
gotten overwritten on an upgrade?

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

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Dan Streetman]

> /etc/resolv.conf:
> nameserver 127.0.0.53
> nameserver 10.2.2.3

You shouldn't hand-edit your resolv.conf file; don't put the upstream
nameserver in there.

Anyway, assuming you haven't edited out the search domain because you
thought it wasn't relevant, you're using single-label hostnames, which
shouldn't be used.  resolved refuses to perform upstream lookups for
single-label domains, and you don't have your hostname defined in your
/etc/hosts file, so resolved has nobody to ask to lookup your hostname.

You should set up your network using a dns domain.

For reference:
https://www.iab.org/documents/correspondence-reports-documents/2013-2/iab-statement-dotless-domains-considered-harmful/

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

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

Title:
  systemd resolves own hostname to link local ipv6 address

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  I've got an ethernet-device that only has a configured ipv4 address,
  and some auto-generated link-local (aka "scope link") ipv6 address.

  Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
  DNS-server listening on 127.0.0.53) for this host's hostname gets back
  two addresses: the correct ipv4 address, and a broken ipv6 address.

  Unlike on ipv4,  it is possible for the same ipv6-address to be
  assigned to multiple devices, and therefore the address is only valid
  in the context of the eth-device.

  Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7  prefixlen 64  
scopeid 0x20"
  then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall 
connect() typically fails with EINVAL.

  To make it a valid address, it needs to be suffixed with a "%" and the device 
name, like:
  fe80::4687:fcff:fe9e:4ac7%enp4s0

  Either the resolver can return the link name attached to the address
  separated with a "%" char, or it needs to ignore link-local inet6
  addresses.

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

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Andreas L]

Apologies...

I'll leave out the comment-headers and just paste the relevant contents:

/etc/resolv.conf:
nameserver 127.0.0.53
nameserver 10.2.2.3


/etc/systemd/resolved.conf:
[Resolve]
#DNS=
#FallbackDNS=
#Domains=
#LLMNR=no
#MulticastDNS=no
#DNSSEC=no
#Cache=yes
#DNSStubListener=yes

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

Title:
  systemd resolves own hostname to link local ipv6 address

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I've got an ethernet-device that only has a configured ipv4 address,
  and some auto-generated link-local (aka "scope link") ipv6 address.

  Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
  DNS-server listening on 127.0.0.53) for this host's hostname gets back
  two addresses: the correct ipv4 address, and a broken ipv6 address.

  Unlike on ipv4,  it is possible for the same ipv6-address to be
  assigned to multiple devices, and therefore the address is only valid
  in the context of the eth-device.

  Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7  prefixlen 64  
scopeid 0x20"
  then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall 
connect() typically fails with EINVAL.

  To make it a valid address, it needs to be suffixed with a "%" and the device 
name, like:
  fe80::4687:fcff:fe9e:4ac7%enp4s0

  Either the resolver can return the link name attached to the address
  separated with a "%" char, or it needs to ignore link-local inet6
  addresses.

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

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Dan Streetman]

You missed contents of /etc/resolv.conf

Also paste contents of /etc/systemd/resolved.conf

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

Title:
  systemd resolves own hostname to link local ipv6 address

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I've got an ethernet-device that only has a configured ipv4 address,
  and some auto-generated link-local (aka "scope link") ipv6 address.

  Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
  DNS-server listening on 127.0.0.53) for this host's hostname gets back
  two addresses: the correct ipv4 address, and a broken ipv6 address.

  Unlike on ipv4,  it is possible for the same ipv6-address to be
  assigned to multiple devices, and therefore the address is only valid
  in the context of the eth-device.

  Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7  prefixlen 64  
scopeid 0x20"
  then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall 
connect() typically fails with EINVAL.

  To make it a valid address, it needs to be suffixed with a "%" and the device 
name, like:
  fe80::4687:fcff:fe9e:4ac7%enp4s0

  Either the resolver can return the link name attached to the address
  separated with a "%" char, or it needs to ignore link-local inet6
  addresses.

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

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Andreas L]

/etc/hosts:

127.0.0.1   localhost
127.0.1.1   kato i7

# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

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

Link 2 (enp4s0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Remark: I have no idea where these ##.172.in-addr.arpa come from.

$ systemd-resolve fpc
fpc: 10.2.2.1%enp4s0
 10.2.2.250%enp4s0
 fe80::4687:fcff:fe9e:4ac7%2%enp4s0

-- Information acquired via protocol DNS in 1.6ms.
-- Data is authenticated: yes

Remark: ah, here it still has the network-name along with the ipv6

$ systemd-resolve -t A fpc
fpc IN A 10.2.2.1 # interface enp4s0
fpc IN A 10.2.2.250 # interface enp4s0

-- Information acquired via protocol DNS in 2.2ms.
-- Data is authenticated: yes

$ systemd-resolve -t  fpc
fpc IN  fe80::4687:fcff:fe9e:4ac7 # interface enp4s0

-- Information acquired via protocol DNS in 2.1ms.
-- Data is authenticated: yes

Remark: ah, here it also has the network-name along with the ipv6

$ dig @10.2.2.3 -t A fpc

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> @10.2.2.3 -t A fpc
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57577
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;fpc.   IN  A

;; ANSWER SECTION:
fpc.0   IN  A   10.2.2.1

;; Query time: 0 msec
;; SERVER: 10.2.2.3#53(10.2.2.3)
;; WHEN: Fri Dec 06 17:11:19 CET 2019
;; MSG SIZE  rcvd: 48

Remark: As I said, upstream DNS 10.2.2.3 doesn't know about the second
10.2.2.250 address.

$ dig @10.2.2.3 -t  fpc

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> @10.2.2.3 -t  fpc
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 924
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;fpc.   IN  

;; Query time: 0 msec
;; SERVER: 10.2.2.3#53(10.2.2.3)
;; WHEN: Fri Dec 06 17:12:03 CET 2019
;; MSG SIZE  rcvd: 21

Remark: As I said, upstream DNS 10.2.2.3 doesn't know about inet6 link
local addresses.

$ dig @127.0.0.53 -t A fpc

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> @127.0.0.53 -t A fpc
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7210
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
fpc.0   IN  A   10.2.2.1
fpc.0   IN  A   10.2.2.250

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Fri Dec 06 17:15:14 CET 2019
;; MSG SIZE  rcvd: 64

Remark:  systemd-resolved DOES obtain this info elsewhere than from
upstream DNS.

$ dig @127.0.0.53 -t  fpc

; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> @127.0.0.53 -t  fpc
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45149
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

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

;; ANSWER SECTION:
fpc.0   IN  fe80::4687:fcff:fe9e:4ac7

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Fri Dec 06 17:16:16 CET 2019
;; MSG SIZE  rcvd: 60

Remark:  systemd-resolved DOES obtain this info elsewhere than from
upstream DNS.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

[VERIFICATION DISCO]

I have installed Disco, layout /usr on it's on LV, and at reboot same
problem as describe in the impact section. Server stuck in trying to
mount /usr due to lack of LVM activation.

At the initramfs prompt, I ran 'lvm vgchange -ay' to boot properly. I
installed the disco-proposed package of lvm2[0], reboot the system and
everything boot fine. The udev rule fix does the work correctly.

[0] dpkg -l
ii  liblvm2app2.2:amd64  2.02.176-4.1ubuntu4.2  
  amd64LVM2 application library
ii  liblvm2cmd2.02:amd64 2.02.176-4.1ubuntu4.2  
  amd64LVM2 command library
ii  lvm2 2.02.176-4.1ubuntu4.2  
  amd64Linux Logical Volume Manager
ubuntu

Additionally, as stated in comment #13, the autopkgtest failure can be
ignored as they are unrelated to this SRU.

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

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in lvm2 package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in lvm2 source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Won't Fix
Status in lvm2 source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Disco:
  Won't Fix
Status in lvm2 source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM 
activation doesn't occurs during the boot process (except for LVM root 
partition) and since /usr is an important component before the 'pivot'[0], the 
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume 
then it will try to mount it while its backend device is not activated yet (due 
to the actual auto-activation issue), thus the mounting will fails and bring 
the user to the initramfs prompt for debugging.

  Workaround:
  At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the 
boot process.

  [Test Case]

  - Install Bionic or Disco
  - Create a VG with /usr on its on LV
  - Complete the installation
  - At reboot the system will be stuck at mounting /usr file system

  Extra notes:
  Since this problem is ONLY related to LVM activation. If one create a non-LVM 
/usr separate partition, everything will work as expected.

  Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
  LVM volume will not be activate either, but since they don't need to
  be mounted in the initramfs space, it's not a problem, they can be
  activated later on (after the pivot) by systemd.

  So the only combination possible is when /usr is on its separate LV
  only.

  [Regression potential]

  I don't foresee any regression, the fix will instruct udev rule to
  pvscan activate volume based on their major/minor number if LVM is
  scanned.

  +RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
  --minor $minor", ENV{LVM_SCANNED}="1"

  The current situation doesn't auto-activate at all.

  One downside, for users who will see this fixed, will still experience
  the situation in standard ISO, since I'm afraid Disco won't produces
  new ISO. (it is not recommended to do new disco installs anyway since
  it's going EOL shortly) One would need to rely on the mini.iso for
  fetching the latest lvm2 package in the archive.

  IIRC Bionic will have a new point release somewhere in Feb 2020 but
  until then one would need to rely on the mini.iso for fetching the
  latest lvm2 package in the archive as well.

  or use the workaround in the [Impact] section and then apt-get dist-
  upgrade in order to get the latest lvm2.

  [Other information]

  This problem only exhibit in Bionic and Disco.
  Xenial and Eoan and late didn't exhibit the situation.

  https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
  https://wiki.debian.org/UsrMerge

  [Original Description]

  Only the lv for root volume get activated, because of the grub
  parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
  --lv"

  http://man7.org/linux/man-pages/man7/bootparam.7.html
  'root=...'
    This argument tells the kernel what device is to be used as
    the root filesystem while booting.

  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.

  At initramfs prompt, we notice that 'lv-usr' status is 'NOT
  available'.

  Performing 'lvm vgchange -ay' at initramfs prompt workaround the
  problem and allow one to successfully boot.

  Adding 'debug' parameter, we clearly we see /root being detected

[Touch-packages] [Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial

[Eric Desrochers]

Please see (LP: #1854981).

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

Title:
  LVM boot problem - volumes not activated after upgrade to Xenial

Status in curtin:
  Invalid
Status in MAAS:
  Invalid
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Soon after upgrade to Xenial (from 15.10) the boot process got broken.
  I'm using LVM for /root swap and other partitions.

  ===
  The current behaviour is:

  When I boot short after the Grub login screen I'm getting log messages
  like:

  ---
  Scanning for Btrfs filesystems
  resume: Could not state the resume device file: '/dev/mapper/VolGroup'
  Please type in the full path...
  ---

  Then I press ENTER, for a few minutes some errors about floppy device
  access are raised (for some reason it tries to scan fd0 when floppy
  drive is empty). And then:

  ---
  Gave up waiting for root device. Common problems: ...
  ...
  ALERT! UUID=xxx-xxx does not exist.
  Dropping to a shell.
  ---

  From the BusyBox shell I managed to recover the boot by issuing "lvm
  vgchange -ay", then exit and then boot continues fine (all LVM file
  systems are successfully mounted).

  ===
  One workaround so far is creating 
/etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange 
-ay". But I'm looking for cleaner solution.

  Boot used to work fine with 15.10. Actually the first boot after
  upgrading to Xenial actually worked OK too, I'm not sure what might
  changed meanwhile (I've been fixing some packages installation since
  mysql server upgrade has failed).

  ===
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

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

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

[Touch-packages] [Bug 1311056] Re: apt-add-repository adds duplicate commented/disabled source lines

[Dave Jones]

I have an updated patch available from the following branch for focal:

https://code.launchpad.net/~waveform/ubuntu/+source/python-apt/+git
/python-apt/+ref/fix-dupe-ppa


Currently building a test package in the following PPA:

https://launchpad.net/~waveform/+archive/ubuntu/python-apt/+packages

I realize most of the people affected by this are on older
distributions, so I'm just in the process of back-porting the patch to
bionic, xenial, and trusty, and will provide test builds in the same PPA
once that's done.

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

Title:
  apt-add-repository adds duplicate commented/disabled source lines

Status in python-apt package in Ubuntu:
  Triaged
Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  Trusty Tahr 14.04

  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list 
  deb http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#apt-add-repository -y 
ppa:aims/aims-desktop
  gpg: keyring `/tmp/tmp0ufdhnmv/secring.gpg' created
  gpg: keyring `/tmp/tmp0ufdhnmv/pubring.gpg' created
  gpg: requesting key BE796FF2 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp0ufdhnmv/trustdb.gpg: trustdb created
  gpg: key BE796FF2: public key "Launchpad PPA for AIMS" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  0 root@osprey:/etc/apt/sources.list.d#cat aims-aims-desktop-trusty.list deb 
http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  # deb-src http://ppa.launchpad.net/aims/aims-desktop/ubuntu trusty main
  0 root@osprey:/etc/apt/sources.list.d#

  That deb-src line should have stayed commented out, and not been
  duplicated. (Commented deb lines should of course be uncommented, as
  already fixed per https://bugs.launchpad.net/ubuntu/+source/python-
  apt/+bug/1042916 .)

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

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

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

I have restart the autopkgtest and they all passes BUT the disco cinder
ones.

Looking at the failure, it's not related to this current SRU, and it
seems to be a recurrent failing pattern:

autopkgtest [04:07:34]: test cinder-daemons: [---
2019-12-06 04:07:37.800 12844 WARNING oslo_db.sqlalchemy.engines [-] URL 
mysql://cinder:***@localhost/cinder does not contain a '+drivername' portion, 
and will make use of a default driver. A full dbname+drivername:// protocol is 
recommended. For MySQL, it is strongly recommended that mysql+pymysql:// be 
specified for maximum service compatibility
2019-12-06 04:07:37.803 12844 CRITICAL cinder [-] Unhandled error: 
ModuleNotFoundError: No module named 'MySQLdb'
2019-12-06 04:07:37.803 12844 ERROR cinder Traceback (most recent call last):
..
2019-12-06 04:07:37.803 12844 ERROR cinder File 
"/usr/lib/python3/dist-packages/sqlalchemy/dialects/mysql/mysqldb.py", line 
102, in dbapi
2019-12-06 04:07:37.803 12844 ERROR cinder return __import__('MySQLdb')
2019-12-06 04:07:37.803 12844 ERROR cinder ModuleNotFoundError: No module named 
'MySQLdb'
2019-12-06 04:07:37.803 12844 ERROR cinder 
autopkgtest [04:07:38]: test cinder-daemons: ---]
autopkgtest [04:07:39]: test cinder-daemons: - - - - - - - - - - results - - - 
- - - - - - -
cinder-daemons FAIL non-zero exit status 1

Please ignore the following disco failures:

Regression in autopkgtest for cinder (ppc64el): test log
Regression in autopkgtest for cinder (s390x): test log
Regression in autopkgtest for cinder (amd64): test log
Regression in autopkgtest for cinder (arm64): test log
Regression in autopkgtest for cinder (i386): test log
Regression in autopkgtest for cinder (armhf): test log

Its failing because it can't find the MySQLdb module which is unrelated
to the current LVM2 SRU.

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in lvm2 package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in lvm2 source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Won't Fix
Status in lvm2 source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Disco:
  Won't Fix
Status in lvm2 source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM 
activation doesn't occurs during the boot process (except for LVM root 
partition) and since /usr is an important component before the 'pivot'[0], the 
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume 
then it will try to mount it while its backend device is not activated yet (due 
to the actual auto-activation issue), thus the mounting will fails and bring 
the user to the initramfs prompt for debugging.

  Workaround:
  At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the 
boot process.

  [Test Case]

  - Install Bionic or Disco
  - Create a VG with /usr on its on LV
  - Complete the installation
  - At reboot the system will be stuck at mounting /usr file system

  Extra notes:
  Since this problem is ONLY related to LVM activation. If one create a non-LVM 
/usr separate partition, everything will work as expected.

  Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
  LVM volume will not be activate either, but since they don't need to
  be mounted in the initramfs space, it's not a problem, they can be
  activated later on (after the pivot) by systemd.

  So the only combination possible is when /usr is on its separate LV
  only.

  [Regression potential]

  I don't foresee any regression, the fix will instruct udev rule to
  pvscan activate volume based on their major/minor number if LVM is
  scanned.

  +RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
  --minor $minor", ENV{LVM_SCANNED}="1"

  The current situation doesn't auto-activate at all.

  One downside, for users who will see this fixed, will still experience
  the situation in standard ISO, since I'm afraid Disco won't produces
  new ISO. (it is not recommended to do new disco installs anyway since
  it's going EOL shortly) One would need to rely on the mini.iso for
  fetching the latest lvm2 package in the archive.

  IIRC Bionic will have a new point release somewhere in Feb 2020 but
  until then one would need to rely on the mini.iso for fetching the
  latest lvm2 package in the archive as well.

  or use the workaround in the [Impact] section and then apt-get dist-
  upgrade in order to get the latest lvm2.

  [Other information]

  This problem only exhibit in Bionic and Disco.
  Xenial and Eoan and late didn't exhibit the 

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

I have restart the autopkgtest and they all passes BUT the disco cinder
ones.

Looking at the failure, it's not related to this current SRU, and it
seems to be a recurrent failing pattern:


autopkgtest [04:07:34]: test cinder-daemons: [---
2019-12-06 04:07:37.800 12844 WARNING oslo_db.sqlalchemy.engines [-] URL 
mysql://cinder:***@localhost/cinder does not contain a '+drivername' portion, 
and will make use of a default driver.  A full dbname+drivername:// protocol is 
recommended. For MySQL, it is strongly recommended that mysql+pymysql:// be 
specified for maximum service compatibility
2019-12-06 04:07:37.803 12844 CRITICAL cinder [-] Unhandled error: 
ModuleNotFoundError: No module named 'MySQLdb'
2019-12-06 04:07:37.803 12844 ERROR cinder Traceback (most recent call last):
..
2019-12-06 04:07:37.803 12844 ERROR cinder   File 
"/usr/lib/python3/dist-packages/sqlalchemy/dialects/mysql/mysqldb.py", line 
102, in dbapi
2019-12-06 04:07:37.803 12844 ERROR cinder return __import__('MySQLdb')
2019-12-06 04:07:37.803 12844 ERROR cinder ModuleNotFoundError: No module named 
'MySQLdb'
2019-12-06 04:07:37.803 12844 ERROR cinder 
autopkgtest [04:07:38]: test cinder-daemons: ---]
autopkgtest [04:07:39]: test cinder-daemons:  - - - - - - - - - - results - - - 
- - - - - - -
cinder-daemons   FAIL non-zero exit status 1

Please ignore the following disco failures:

Regression in autopkgtest for cinder (ppc64el): test log
Regression in autopkgtest for cinder (s390x): test log
Regression in autopkgtest for cinder (amd64): test log
Regression in autopkgtest for cinder (arm64): test log
Regression in autopkgtest for cinder (i386): test log
Regression in autopkgtest for cinder (armhf): test log

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in lvm2 package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in lvm2 source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Won't Fix
Status in lvm2 source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Disco:
  Won't Fix
Status in lvm2 source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM 
activation doesn't occurs during the boot process (except for LVM root 
partition) and since /usr is an important component before the 'pivot'[0], the 
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume 
then it will try to mount it while its backend device is not activated yet (due 
to the actual auto-activation issue), thus the mounting will fails and bring 
the user to the initramfs prompt for debugging.

  Workaround:
  At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the 
boot process.

  [Test Case]

  - Install Bionic or Disco
  - Create a VG with /usr on its on LV
  - Complete the installation
  - At reboot the system will be stuck at mounting /usr file system

  Extra notes:
  Since this problem is ONLY related to LVM activation. If one create a non-LVM 
/usr separate partition, everything will work as expected.

  Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
  LVM volume will not be activate either, but since they don't need to
  be mounted in the initramfs space, it's not a problem, they can be
  activated later on (after the pivot) by systemd.

  So the only combination possible is when /usr is on its separate LV
  only.

  [Regression potential]

  I don't foresee any regression, the fix will instruct udev rule to
  pvscan activate volume based on their major/minor number if LVM is
  scanned.

  +RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
  --minor $minor", ENV{LVM_SCANNED}="1"

  The current situation doesn't auto-activate at all.

  One downside, for users who will see this fixed, will still experience
  the situation in standard ISO, since I'm afraid Disco won't produces
  new ISO. (it is not recommended to do new disco installs anyway since
  it's going EOL shortly) One would need to rely on the mini.iso for
  fetching the latest lvm2 package in the archive.

  IIRC Bionic will have a new point release somewhere in Feb 2020 but
  until then one would need to rely on the mini.iso for fetching the
  latest lvm2 package in the archive as well.

  or use the workaround in the [Impact] section and then apt-get dist-
  upgrade in order to get the latest lvm2.

  [Other information]

  This problem only exhibit in Bionic and Disco.
  Xenial and Eoan and late didn't exhibit the situation.

  https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMer

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Dan Streetman]

> I don't understand what lsof tries to tell me here, but naively I'd
assume that systemd-resolved also queries the routing table, and for
that I also attach the output of "route -n -6" at the end of this
message.

that's not correct.

What's the contents of your /etc/hosts file?  Contents of
/etc/resolv.conf?

What do these show:

$ systemd-resolve --status

$ systemd-resolve fpc

$ systemd-resolve -t A fpc

$ systemd-resolve -t  fpc

$ dig @10.2.2.3 -t A fpc

$ dig @10.2.2.3 -t  fpc

$ dig @127.0.0.53 -t A fpc

$ dig @127.0.0.53 -t  fpc

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

Title:
  systemd resolves own hostname to link local ipv6 address

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I've got an ethernet-device that only has a configured ipv4 address,
  and some auto-generated link-local (aka "scope link") ipv6 address.

  Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
  DNS-server listening on 127.0.0.53) for this host's hostname gets back
  two addresses: the correct ipv4 address, and a broken ipv6 address.

  Unlike on ipv4,  it is possible for the same ipv6-address to be
  assigned to multiple devices, and therefore the address is only valid
  in the context of the eth-device.

  Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7  prefixlen 64  
scopeid 0x20"
  then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall 
connect() typically fails with EINVAL.

  To make it a valid address, it needs to be suffixed with a "%" and the device 
name, like:
  fe80::4687:fcff:fe9e:4ac7%enp4s0

  Either the resolver can return the link name attached to the address
  separated with a "%" char, or it needs to ignore link-local inet6
  addresses.

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

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

[Touch-packages] [Bug 1854981] Re: system doesn't properly boot as expected if /usr is on its own LV

[Eric Desrochers]

[VERIFICATION BIONIC]

I have installed Bionic, layout /usr on it's on LV, and at reboot same
problem as describe in the impact section. Server stuck in trying to
mount /usr due to lack of LVM activation.

At the initramfs prompt, I ran 'lvm vgchange -ay' to boot properly. I
installed the bionic-proposed package of lvm2[0], reboot the system and
everything boot fine. The udev rule fix does the work correctly.


[0] dpkg -l 
ii  liblvm2app2.2:amd64   2.02.176-4.1ubuntu3.18.04.2   
  amd64LVM2 application library
ii  liblvm2cmd2.02:amd64  2.02.176-4.1ubuntu3.18.04.2   
  amd64LVM2 command library
ii  lvm2  2.02.176-4.1ubuntu3.18.04.2   
  amd64Linux Logical Volume Manage

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

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

Title:
  system doesn't properly boot as expected if /usr is on its own LV

Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in lvm2 package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Won't Fix
Status in lvm2 source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Won't Fix
Status in lvm2 source package in Bionic:
  Fix Committed
Status in initramfs-tools source package in Disco:
  Won't Fix
Status in lvm2 source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  In summary, the problem is a LVM 'auto-activation' issue. Basically the LVM 
activation doesn't occurs during the boot process (except for LVM root 
partition) and since /usr is an important component before the 'pivot'[0], the 
init inside the initramfs space tries to mount /usr. If /usr is a LVM volume 
then it will try to mount it while its backend device is not activated yet (due 
to the actual auto-activation issue), thus the mounting will fails and bring 
the user to the initramfs prompt for debugging.

  Workaround:
  At the initramfs prompt: lvm vgchange -ay and then 'ctrl-d' to resume the 
boot process.

  [Test Case]

  - Install Bionic or Disco
  - Create a VG with /usr on its on LV
  - Complete the installation
  - At reboot the system will be stuck at mounting /usr file system

  Extra notes:
  Since this problem is ONLY related to LVM activation. If one create a non-LVM 
/usr separate partition, everything will work as expected.

  Other separate LVM (e.g. /home, /var/, /srv) if on its own separate
  LVM volume will not be activate either, but since they don't need to
  be mounted in the initramfs space, it's not a problem, they can be
  activated later on (after the pivot) by systemd.

  So the only combination possible is when /usr is on its separate LV
  only.

  [Regression potential]

  I don't foresee any regression, the fix will instruct udev rule to
  pvscan activate volume based on their major/minor number if LVM is
  scanned.

  +RUN+="(LVM_EXEC)/lvm pvscan --cache --activate ay --major $major
  --minor $minor", ENV{LVM_SCANNED}="1"

  The current situation doesn't auto-activate at all.

  One downside, for users who will see this fixed, will still experience
  the situation in standard ISO, since I'm afraid Disco won't produces
  new ISO. (it is not recommended to do new disco installs anyway since
  it's going EOL shortly) One would need to rely on the mini.iso for
  fetching the latest lvm2 package in the archive.

  IIRC Bionic will have a new point release somewhere in Feb 2020 but
  until then one would need to rely on the mini.iso for fetching the
  latest lvm2 package in the archive as well.

  or use the workaround in the [Impact] section and then apt-get dist-
  upgrade in order to get the latest lvm2.

  [Other information]

  This problem only exhibit in Bionic and Disco.
  Xenial and Eoan and late didn't exhibit the situation.

  https://www.freedesktop.org/wiki/Software/systemd/TheCaseForTheUsrMerge/
  https://wiki.debian.org/UsrMerge

  [Original Description]

  Only the lv for root volume get activated, because of the grub
  parameter that specifies/enforce it "root=/dev/mapper/ubuntu-vg-ubuntu
  --lv"

  http://man7.org/linux/man-pages/man7/bootparam.7.html
  'root=...'
    This argument tells the kernel what device is to be used as
    the root filesystem while booting.

  If one add a separate LV for /usr, the system will go straight to
  initramfs prompt failling to mount /usr.

  At initramfs prompt, we notice that 'lv-usr' status is 'NOT
  available'.

  Performing 'lvm vgchange -ay' at initramfs prompt workaround the
  problem and allow one to successfully boot.

  Adding 'debug' parameter, we clearly we see /root being detected and mounted:
  initramfs.debug:
  => + mount -r -t ext4 /dev/mapper/ubuntu--vg-ubuntu--lv /

[Touch-packages] [Bug 1855445] [NEW] Touchpad is not working

[Rohit Prasad]

Public bug reported:

Day before yesterday, I updated Ubuntu in my laptop, then the next
morning when I try to use touch-pad it wasn't working, I switched to
windows to see whether touch-pad was working or not, it was working
fine. Here's the details

$ xinput

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech USB Receiver id=11   [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPadid=17   [slave  pointer  (2)]
⎜   ↳ Synaptics TM3252-001  id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Video Bus id=7[slave  keyboard (3)]
↳ Power Button  id=8[slave  keyboard (3)]
↳ Sleep Button  id=9[slave  keyboard (3)]
↳ Logitech USB Receiver id=10   [slave  keyboard (3)]
↳ Integrated_Webcam_HD: Integrate   id=12   [slave  keyboard (3)]
↳ Intel HID events  id=14   [slave  keyboard (3)]
↳ Dell WMI hotkeys  id=15   [slave  keyboard (3)]
↳ AT Translated Set 2 keyboard  id=16   [slave  keyboard (3)]
↳ Logitech USB Receiver id=18   [slave  keyboard (3)]

$ dmesg | grep i2c

[0.766631] i2c /dev entries driver
[2.419114] psmouse serio1: synaptics: Your touchpad (PNP: SYN0609 PNP0f13) 
says it can support a different bus. If i2c-hid and hid-rmi are not used, you 
might want to try setting psmouse.synaptics_intertouch to 1 and report this to 
linux-in...@vger.kernel.org.
[   34.129216] i2c_hid i2c-DELL0792:00: i2c-DELL0792:00 supply vdd not found, 
using dummy regulator
[   34.837858] input: Synaptics TM3252-001 as 
/devices/pci:00/:00:15.0/i2c_designware.0/i2c-0/i2c-DELL0792:00/0018:06CB:7F09.0003/input/input13
[   34.837945] hid-rmi 0018:06CB:7F09.0003: input,hidraw2: I2C HID v1.00 Mouse 
[DELL0792:00 06CB:7F09] on i2c-DELL0792:00

$ locate i2c-designware

/lib/modules/4.15.0-70-generic/kernel/drivers/i2c/busses/i2c-designware-pci.ko
/lib/modules/4.15.0-72-generic/kernel/drivers/i2c/busses/i2c-designware-pci.ko
/usr/src/linux-headers-4.15.0-70/include/linux/platform_data/i2c-designware.h
/usr/src/linux-headers-4.15.0-72/include/linux/platform_data/i2c-designware.h

$ uname -a

Linux ubuntu-vostro-14-3468 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26
12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -crid

Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename:   bionic

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Touchpad is not working

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Day before yesterday, I updated Ubuntu in my laptop, then the next
  morning when I try to use touch-pad it wasn't working, I switched to
  windows to see whether touch-pad was working or not, it was working
  fine. Here's the details

  $ xinput

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Receiver   id=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=17   [slave  pointer 
 (2)]
  ⎜   ↳ Synaptics TM3252-001id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Logitech USB Receiver   id=10   [slave  
keyboard (3)]
  ↳ Integrated_Webcam_HD: Integrate id=12   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=14   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Logitech USB Receiver   id=18   [slave  
keyboard (3)]

  $ d

[Touch-packages] [Bug 1855442] [NEW] internal microphone not detected on L530 thinkpad 18.04.03

[mauricebis]

Public bug reported:

It used to work but now on Ubuntu 18.04.03, my internal microphone on
Thinkpad L530 is automatically muted and not recognised by pulse audio
nor alsamixer. Actioning the physical mute/unmute button has no effect.

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

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

Title:
  internal microphone not detected on  L530 thinkpad 18.04.03

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  It used to work but now on Ubuntu 18.04.03, my internal microphone on
  Thinkpad L530 is automatically muted and not recognised by pulse audio
  nor alsamixer. Actioning the physical mute/unmute button has no
  effect.

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

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

[Touch-packages] [Bug 1825946] Re: 'nm' autopkgtest fails due to GI stderr output

[Dan Streetman]

** Tags added: block-proposed-xenial

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

Title:
  'nm' autopkgtest fails due to GI stderr output

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New
Status in network-manager source package in Bionic:
  Fix Released

Bug description:
  [impact]

  'nm' testcase contains:
  from gi.repository import NetworkManager, NMClient, GLib  


 

  which generates output to stderr:
  /tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning: 
NetworkManager was imported without specifying a version first. Use 
gi.require_version('NetworkManager', '1.0') before import to ensure that the 
right version gets loaded.

  the gi.require_version call has already been added to cosmic and
  disco.

  [test case]

  see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
  results.

  [other info]

  this only fails intermittently, but the failure is clearly not an
  actual problem.

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

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

[Touch-packages] [Bug 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq

[Dan Streetman]

** Tags added: block-proposed-bionic

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

Title:
  autopkgtest 'nm' fails because it can't find dnsmasq

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  In Progress

Bug description:
  [impact]

  test 'nm' fails because dnsmasq-base isn't installed

  [test case]

  see test results
  http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64

  [regression potential]

  low, test fix only

  [other info]

  The d/t/control file 'nm' test section, for bionic, needs to include
  dnsmasq-base in its dep list.

  disco and later already include dnsmasq-base in test dep packages, and
  in xenial network-manager directly depends on dnsmasq-base.  So this
  is needed only for bionic.

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

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

[Touch-packages] [Bug 1855009] Re: autopkgtests all fail on s390x

[Dan Streetman]

** Tags added: block-proposed-bionic block-proposed-disco block-
proposed-eoan block-proposed-xenial

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

Title:
  autopkgtests all fail on s390x

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Bionic:
  In Progress
Status in network-manager source package in Disco:
  In Progress
Status in network-manager source package in Eoan:
  In Progress
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [impact]

  all autopkgtests fail on s390x

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-focal/focal/s390x/n/network-
  manager/20191130_001946_a5512@/log.gz

  autopkgtest [00:19:32]:  summary
  wpa-dhclient FAIL non-zero exit status 1
  nm.pyFAIL non-zero exit status 1
  killswitches-no-urfkill FAIL non-zero exit status 1
  urfkill-integration  FAIL non-zero exit status 1

  [regression potential]

  this essentially skips all the autopkgtests for network-manager on
  s390x, so regressions could occur now or in the future due to lack of
  testing on s390x.  However, all the tests already fail on s390x and
  have since xenial (or earlier), so there hasn't been any useful test
  coverage on s390x before; this doesn't change that.

  [other info]

  as mentioned in comment 2, wireless networking is specifically
  excluded on s390 systems:

  menuconfig WIRELESS
  bool "Wireless"
  depends on !S390
  default y

  The 'wpa-dhclient' test is specific to wireless, and both
  'killswitches-no-urfkill' and 'urfkill-integration' require rfkill
  which requires wireless, so none of those tests are valid on s390x,
  since it doesn't have any wireless support.

  However the 'nm.py' test does have some test cases that don't rely on
  wireless capability, but it would be much more intrusive to update the
  test to split out wired vs. wireless testing, and that might introduce
  test regressions on other archs.  The use case for network-manager on
  s390x in general is questionable, since s390x has no wireless support
  and obviously is never 'mobile', which are 2 main reasons to use
  network-manager instead of systemd-networkd.  Additionally, all tests
  are currently skipped on armhf due to the requirement for machine
  isolation (and armhf tests run in containers), so s390x is not the
  first arch to simply skip all network-manager autopkgtests.

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

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

[Touch-packages] [Bug 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386

[Dan Streetman]

** Tags added: block-proposed-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/1855183

Title:
  autopkgtest fails on i386 because linux-headers-generic no longer
  built for i386

Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager source package in Eoan:
  In Progress
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [impact]

  the kernel is no longer built for i386, starting with Eoan.  However
  some of the autopkgtests depend on linux-headers-generic, which isn't
  available for i386, so the test fails with bad dependency.

  [test case]

  check autopkgtest logs, e.g.
  http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386

  Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none 
@un H >
Removing autopkgtest-satdep:i386 because I can't find 
linux-headers-generic:i386

  [regression potential]

  test case fix only, regressions would involve more/continued test
  failure

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

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

[Touch-packages] [Bug 1852016] Re: Applications delayed on launch

[Chris Rorden]

This issue is easy to replicate in any clean install of Ubuntu 19.10. For 
example, 
  $ sudo apt install hexchat
  $ hexchat
That would allow you to trouble shoot on an development system. 

Happy to provide a full 'journalctl -b 0' log if requested, but probably
more useful to generate on a development machine. Here are the last few
lines of mine, the "Failed: Could not get window list" sounds
promising...

Dec 06 07:42:03 zb systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Dec 06 07:42:03 zb dbus-daemon[1012]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Dec 06 07:42:03 zb systemd[1]: Started Network Manager Script Dispatcher 
Service.
Dec 06 07:42:14 zb systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Dec 06 07:42:25 zb thunderbird.desktop[1942]: console.debug: 
"main/language-dictionaries 80 records loaded from JSON dump"
Dec 06 07:42:25 zb thunderbird.desktop[1942]: console.debug: 
"main/sites-classification 7 records loaded from JSON dump"
Dec 06 07:42:53 zb xdg-desktop-por[1874]: Failed to get application states: 
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not 
allowed
Dec 06 07:42:53 zb kernel: [UFW BLOCK] IN=wlp41s0 OUT= 
MAC=01:00:5e:00:00:01:00:23:04:18:e6:00:08:00 SRC=10.73.1.1 DST=224.0.0.1 
LEN=28 TOS=0x00 PREC=0xC0 TTL=1 ID=21410 PROTO=2 
Dec 06 07:42:56 zb kernel: [UFW BLOCK] IN=wlp41s0 OUT= 
MAC=01:00:5e:00:00:fb:f0:79:59:70:d6:ac:08:00 SRC=10.73.1.231 DST=224.0.0.251 
LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 
Dec 06 07:43:51 zb gnome-shell[1942]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200034
Dec 06 07:43:51 zb gnome-shell[1942]: Window manager warning: Buggy client sent 
a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4200034
Dec 06 07:43:53 zb xdg-desktop-por[1874]: Failed to get application states: 
GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: 
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not 
allowed

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

Title:
  Applications delayed on launch

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  i am unsure if this is really a problem with dbus but my first
  research showed it could be related to dbus.

  1.) 
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  Ubuntu Budgie on T460 with 256GB SSD and 16GB RAM

  2.)
  dbus:
Installed: 1.12.14-1ubuntu2
Candidate: 1.12.14-1ubuntu2
Version table:
   *** 1.12.14-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  3.) I've expected just "normal" loading applications

  4.) Some applications are delayed at startup. The application will
  take around 30s to launch, but afterwards it just runs fine. Affected
  application I found so far are KeepassXC, Filezilla and OnlyOffice
  Desktop-Editor. From strace I saw this applications are stopping (for
  about 20-30s) at this point:

  connect(12, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 110) = 0
  getpid()= 8165
  geteuid()   = 1000
  getegid()   = 1000
  getpid()= 8165
  geteuid()   = 1000
  getegid()   = 1000
  sendmsg(12, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0", 
iov_len=1}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET, 
cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=8165, uid=1000, gid=1000}}], 
msg_controllen=32, msg_flags=0}, MSG_NOSIGNAL) = 1
  sendto(12, "AUTH\r\n", 6, MSG_NOSIGNAL, NULL, 0) = 6
  recvfrom(12, "REJECTED EXTERNAL\r\n", 4096, 0, NULL, NULL) = 19
  sendto(12, "AUTH EXTERNAL 31303030\r\n", 24, MSG_NOSIGNAL, NULL, 0) = 24
  recvfrom(12, "OK 7f079149c4e5e774135107445dc85"..., 4096, 0, NULL, NULL) = 37
  sendto(12, "NEGOTIATE_UNIX_FD\r\n", 19, MSG_NOSIGNAL, NULL, 0) = 19
  recvfrom(12, "AGREE_UNIX_FD\r\n", 4096, 0, NULL, NULL) = 15
  sendto(12, "BEGIN\r\n", 7, MSG_NOSIGNAL, NULL, 0) = 7
  write(15, "\1\0\0\0\0\0\0\0", 8)= 8
  eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK)   = 14
  write(14, "\1\0\0\0\0\0\0\0", 8)= 8
  write(15, "\1\0\0\0\0\0\0\0", 8)= 8
  poll([{fd=14, events=POLLIN}], 1, 25000) = 1 ([{fd=14, revents=POLLIN}])
  read(14, "\1\0\0\0\0\0\0\0", 16)= 8
  poll([{fd=14, events=POLLIN}], 1, 25000

  
  During my first research I found this following to topics related to the 
issue:
  
https://askubuntu.com/questions/1184774/some-applications-on-ubuntu-19-10-very-slow-to-start

  Th

[Touch-packages] [Bug 1852016] Re: Applications delayed on launch

[Chris Rorden]

This bug seems to impact many GTK2 applications including KeepassXC,
Filezilla and OnlyOffice Desktop-Editor, HexChat, Lazarus and any
application built using Lazarus that targets the GTK2 platform.
Descriptions include

https://askubuntu.com/questions/1182155/filezilla-start-after-25-seconds-delay
https://forum.lazarus.freepascal.org/index.php?topic=47240.0
https://askubuntu.com/questions/1187246/ubuntu-19-10-crash-when-lazarus-runs
https://askubuntu.com/questions/1184774/some-applications-on-ubuntu-19-10-very-slow-to-start

Solutions include:
 1. (temporary). Run as super user, e.g.: sudo ./project1
 2. (temporary). Run using: dbus-launch --exit-with-session ./project1
 3. (Permanent). Install "sudo apt-get install appmenu-gtk2-module" and restart.
I am not sure what the root cause is, but one solution would be to have 
appmenu-gtk2-module installed whenever someone installs "libgtk2.0-0". It is 
obvious to the user that that these applications require libgtk-x11-2.0.so.0 as 
the programs will not launch without it. The problem with the current situation 
is that the programs do not list appmenu-dtk2-module as a dependency but do not 
launch appropriately without it.

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

Title:
  Applications delayed on launch

Status in dbus package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  i am unsure if this is really a problem with dbus but my first
  research showed it could be related to dbus.

  1.) 
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 19.10
  Release:  19.10
  Codename: eoan

  Ubuntu Budgie on T460 with 256GB SSD and 16GB RAM

  2.)
  dbus:
Installed: 1.12.14-1ubuntu2
Candidate: 1.12.14-1ubuntu2
Version table:
   *** 1.12.14-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  3.) I've expected just "normal" loading applications

  4.) Some applications are delayed at startup. The application will
  take around 30s to launch, but afterwards it just runs fine. Affected
  application I found so far are KeepassXC, Filezilla and OnlyOffice
  Desktop-Editor. From strace I saw this applications are stopping (for
  about 20-30s) at this point:

  connect(12, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 110) = 0
  getpid()= 8165
  geteuid()   = 1000
  getegid()   = 1000
  getpid()= 8165
  geteuid()   = 1000
  getegid()   = 1000
  sendmsg(12, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0", 
iov_len=1}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET, 
cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=8165, uid=1000, gid=1000}}], 
msg_controllen=32, msg_flags=0}, MSG_NOSIGNAL) = 1
  sendto(12, "AUTH\r\n", 6, MSG_NOSIGNAL, NULL, 0) = 6
  recvfrom(12, "REJECTED EXTERNAL\r\n", 4096, 0, NULL, NULL) = 19
  sendto(12, "AUTH EXTERNAL 31303030\r\n", 24, MSG_NOSIGNAL, NULL, 0) = 24
  recvfrom(12, "OK 7f079149c4e5e774135107445dc85"..., 4096, 0, NULL, NULL) = 37
  sendto(12, "NEGOTIATE_UNIX_FD\r\n", 19, MSG_NOSIGNAL, NULL, 0) = 19
  recvfrom(12, "AGREE_UNIX_FD\r\n", 4096, 0, NULL, NULL) = 15
  sendto(12, "BEGIN\r\n", 7, MSG_NOSIGNAL, NULL, 0) = 7
  write(15, "\1\0\0\0\0\0\0\0", 8)= 8
  eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK)   = 14
  write(14, "\1\0\0\0\0\0\0\0", 8)= 8
  write(15, "\1\0\0\0\0\0\0\0", 8)= 8
  poll([{fd=14, events=POLLIN}], 1, 25000) = 1 ([{fd=14, revents=POLLIN}])
  read(14, "\1\0\0\0\0\0\0\0", 16)= 8
  poll([{fd=14, events=POLLIN}], 1, 25000

  
  During my first research I found this following to topics related to the 
issue:
  
https://askubuntu.com/questions/1184774/some-applications-on-ubuntu-19-10-very-slow-to-start

  This Stackoverflow topic links to the archlinux forum:
  https://bbs.archlinux.org/viewtopic.php?id=230036

  I can confirm that running the delayed applications with "dbus-launch
  --exit-with-session application" or by running it as root they are all
  starting without any delay.

  Thanks for your help! Let me know if you need any further information.

  Best Regards,
  Sebastian

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

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

[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu-release-upgrader

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

Title:
  Please make /etc/update-motd.d snippets runnable by regular users

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in update-notifier package in Ubuntu:
  New

Bug description:
  [Impact]

   * /etc/update-motd.d snippets throw errors when a nomal user runs them.
   * This prevents showing MOTD when the user is dropped to a regular user's 
shell in WSL.

  [Test Case]

   * Run update-motd's autopkgtest and observe scripts not throwing
  errors.

  [Regression Potential]

   * The fixes are fairly simple, but to ensure no breakage the scripts
  are also run as root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Andreas L]

Here is some more info, namely an "strace" of the systemd-resolved
program.

(An "lsof"-excerpt with the open channels follows the trace-log, to make
sense of filedescriptors)

In a nutshell:  at some point, it receives the inet6 address 
"fe80::4687:fcff:fe9e:4ac7" in an "recvmsg" call on FD 9, which lsof prints as:
"systemd-r 4966 systemd-resolve9u  netlink 0t0 
15693998 ROUTE"
I don't understand what lsof tries to tell me here, but naively I'd assume that 
systemd-resolved also queries the routing table, and for that I also attach the 
output of "route -n -6" at the end of this message.

strace: Process 4966 attached
epoll_wait(4, [{EPOLLIN, {u32=3769468528, u64=94647668803184}}], 14, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {tv_sec=1269407, tv_nsec=930758302}) = 0
recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 21
recvmsg(12, {msg_name={sa_family=AF_INET, sin_port=htons(55365), 
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=128->16, 
msg_iov=[{iov_base="j\204\1\0\0\1\0\0\0\0\0\0\3fpc\0\0\1\0\1", iov_len=3928}], 
msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, cmsg_data={ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, cmsg_data=[64]}], 
msg_controllen=56, msg_flags=0}, 0) = 21
stat("/etc/hosts", {st_mode=S_IFREG|0644, st_size=356, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=324, ...}) = 0
clock_gettime(CLOCK_BOOTTIME, {tv_sec=1269407, tv_nsec=931200245}) = 0
sendto(9, {{len=24, type=RTM_GETADDR, flags=NLM_F_REQUEST|NLM_F_ACK|NLM_F_DUMP, 
seq=9, pid=0}, {ifa_family=AF_INET, ifa_prefixlen=32, ifa_flags=0, 
ifa_scope=RT_SCOPE_UNIVERSE, ifa_index=0}}, 24, 0, {sa_family=AF_NETLINK, 
nl_pid=0, nl_groups=}, 16) = 24
recvmsg(9, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 
msg_namelen=128->12, msg_iov=[{iov_base=NULL, iov_len=0}], msg_iovlen=1, 
msg_control=[{cmsg_len=20, cmsg_level=SOL_NETLINK, cmsg_type=0x3}], 
msg_controllen=24, msg_flags=MSG_TRUNC}, MSG_PEEK|MSG_TRUNC) = 256
recvmsg(9, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 
msg_namelen=128->12, msg_iov=[{iov_base=[{{len=76, type=RTM_NEWADDR, 
flags=NLM_F_MULTI, seq=9, pid=4966}, {ifa_family=AF_INET, ifa_prefixlen=8, 
ifa_flags=IFA_F_PERMANENT, ifa_scope=RT_SCOPE_HOST, 
ifa_index=if_nametoindex("lo")}, [{{nla_len=8, nla_type=IFA_ADDRESS}, 
127.0.0.1}, {{nla_len=8, nla_type=IFA_LOCAL}, 127.0.0.1}, {{nla_len=7, 
nla_type=IFA_LABEL}, "lo"}, {{nla_len=8, nla_type=IFA_FLAGS}, IFA_F_PERMANENT}, 
{{nla_len=20, nla_type=IFA_CACHEINFO}, {ifa_prefered=4294967295, 
ifa_valid=4294967295, cstamp=3449, tstamp=3449}}]}, {{len=88, type=RTM_NEWADDR, 
flags=NLM_F_MULTI, seq=9, pid=4966}, {ifa_family=AF_INET, ifa_prefixlen=24, 
ifa_flags=IFA_F_PERMANENT, ifa_scope=RT_SCOPE_UNIVERSE, 
ifa_index=if_nametoindex("enp4s0")}, [{{nla_len=8, nla_type=IFA_ADDRESS}, 
10.2.2.1}, {{nla_len=8, nla_type=IFA_LOCAL}, 10.2.2.1}, {{nla_len=8, 
nla_type=IFA_BROADCAST}, 10.2.2.255}, {{nla_len=11, nla_type=IFA_LABEL}, 
"enp4s0"}, {{nla_len=8, nla_type=IFA_FLAGS}, IFA_F_PERMANENT}, {{nla_len=20, 
nla_type=IFA_CACHEINFO}, {ifa_prefered=4294967295, ifa_valid=4294967295, 
cstamp=3810, tstamp=3810}}]}, {{len=92, type=RTM_NEWADDR, flags=NLM_F_MULTI, 
seq=9, pid=4966}, {ifa_family=AF_INET, ifa_prefixlen=8, 
ifa_flags=IFA_F_PERMANENT, ifa_scope=RT_SCOPE_UNIVERSE, 
ifa_index=if_nametoindex("enp4s0")}, [{{nla_len=8, nla_type=IFA_ADDRESS}, 
10.2.2.250}, {{nla_len=8, nla_type=IFA_LOCAL}, 10.2.2.250}, {{nla_len=8, 
nla_type=IFA_BROADCAST}, 10.255.255.255}, {{nla_len=13, nla_type=IFA_LABEL}, 
"enp4s0:1"}, {{nla_len=8, nla_type=IFA_FLAGS}, IFA_F_PERMANENT}, {{nla_len=20, 
nla_type=IFA_CACHEINFO}, {ifa_prefered=4294967295, ifa_valid=4294967295, 
cstamp=10833228, tstamp=10833228}}]}], iov_len=5200}], msg_iovlen=1, 
msg_control=[{cmsg_len=20, cmsg_level=SOL_NETLINK, cmsg_type=0x3}], 
msg_controllen=24, msg_flags=0}, MSG_TRUNC) = 256
ppoll([{fd=9, events=POLLIN}], 1, {tv_sec=24, tv_nsec=999785000}, NULL, 8) = 1 
([{fd=9, revents=POLLIN}], left {tv_sec=24, tv_nsec=999783625})
recvmsg(9, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 
msg_namelen=128->12, msg_iov=[{iov_base=NULL, iov_len=0}], msg_iovlen=1, 
msg_control=[{cmsg_len=20, cmsg_level=SOL_NETLINK, cmsg_type=0x3}], 
msg_controllen=24, msg_flags=MSG_TRUNC}, MSG_PEEK|MSG_TRUNC) = 20
recvmsg(9, {msg_name={sa_family=AF_NETLINK, nl_pid=0, nl_groups=}, 
msg_namelen=128->12, msg_iov=[{iov_base={{len=20, type=NLMSG_DONE, 
flags=NLM_F_MULTI, seq=9, pid=4966}, 0}, iov_len=5200}], msg_iovlen=1, 
msg_control=[{cmsg_len=20, cmsg_level=SOL_NETLINK, cmsg_type=0x3}], 
msg_controllen=24, msg_flags=0}, MSG_TRUNC) = 20
sendmsg(12, {msg_name={sa_family=AF_INET, sin_port=htons(55365), 
sin_addr=inet_addr("127.0.0.1")}, msg_namelen=16, 
msg_iov=[{iov_base="j\204\201\200\0\1\0\2\0\0\0\0\3fpc\0\0\1\0\1\300\

[Touch-packages] [Bug 1854608] Re: Screen Flickering during Boot up

[Daniel van Vugt]

These kernel messages look related to possible flickering:

[   20.272352] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
[   20.272749] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
[   20.272809] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

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

Title:
  Screen Flickering during Boot up

Status in linux package in Ubuntu:
  New

Bug description:
  The Screen flickers during boot up and System runs very slow.

  This is my GPU info.

  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
  Core Processor Family Integrated Graphics Controller (rev 09)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  1 11:07:19 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.0.0-32-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.0.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3977]
  InstallationDate: Installed on 2019-05-22 (192 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20157
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic 
root=UUID=fb1d2555-5fe7-4a82-804c-8b91c22c2a1f ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 62CN34WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake 2
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr62CN34WW:bd04/26/2012:svnLENOVO:pn20157:pvrLenovoG580:rvnLENOVO:rnEmeraldLake2:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 20157
  dmi.product.sku: System SKUNumber
  dmi.product.version: Lenovo G580
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1854578] Re: Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

[Daniel van Vugt]

Please try removing the kernel parameter:

acpi_backlight=vendor

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  Package: xo

[Touch-packages] [Bug 1854578] Re: Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

[Daniel van Vugt]

Also please open a separate bug for your touchpad.

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

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

Title:
  Nvidia driver on ASUS G752VM screen brigtness and touchpad not working

Status in xorg-server package in Ubuntu:
  New

Bug description:
  The brightness buttons (FN+ F5/F6) show an on-screen pop-up window and
  move the brightness bar in that window, but actual screen brightness
  does not change. Also, the touchpad does not work at all, however a
  few times it did work after a reboot without any recognisable change
  in the driver or system settings.

  Ubuntu driver does not load after Ubuntu upgrade (now upgraded to
  19.10) and only starts to work (giving required screen resolution)
  only after installing lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Nov 30 18:09:10 2019
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. G752VM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=9e718d14-26a1-4d47-a1a3-98803ad7bf61 ro nomodset 
acpi_backlight=vendor acpi_osi=Linux
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to eoan on 2019-11-30 (0 days ago)
  dmi.bios.date: 04/24/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VM.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VM
  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.:bvrG752VM.308:bd04/24/2019:svnASUSTeKCOMPUTERINC.:pnG752VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Sat Nov 30 17:38:28 2019
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for pci::01:00.0: -19
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.5+git20191008-0ubuntu1
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompositorRunning: None
  DistUpgraded: 2019-11-30 16:54:55,819 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroRelease: Ubuntu 19.10
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 440.26, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB] [10de:1c60] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP106BM [GeForce GTX 1060 Mobile 6GB] 
[1043:13f0]
  InstallationDate: Installed on 2017-03-08 (996 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineTyp

[Touch-packages] [Bug 1854336] Re: GNOME apps in Kubuntu 19.10 doesn't respect GNOME window settings

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  GNOME apps in Kubuntu 19.10 doesn't respect GNOME window settings

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  All GNOME/Gtk apps in Kubuntu 19.10 ignore gnome settings, both from gui and 
cli tool. 
  i.e. setting schema button-layout in org.gnome.desktop.wm.preferences from 
default 'appmenu:close' to custom 'close,minimize,maximize:' doesn't have any 
effect - gtk window widgets are always on the right, while KDE ones are on 
left, as set in KDE settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Nov 28 11:13:01 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:5059]
  InstallationDate: Installed on 2019-10-29 (29 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20GKS0HQ00
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET27W (1.15 )
  dmi.board.asset.tag: 
  dmi.board.name: 20GKS0HQ00
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET27W(1.15):bd09/05/2016:svnLENOVO:pn20GKS0HQ00:pvrThinkPad13:rvnLENOVO:rn20GKS0HQ00:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad 13
  dmi.product.name: 20GKS0HQ00
  dmi.product.sku: LENOVO_MT_20GK_BU_Think_FM_ThinkPad 13
  dmi.product.version: ThinkPad 13
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1854531] Re: Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false in gdm3's custom.conf

[Daniel van Vugt]

It sounds like graphics corruption might be the main issue here. Please
include a photo of that.

** Tags added: radeon

** Summary changed:

- Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled to false 
in gdm3's custom.conf
+ [radeon] Ubuntu fails to run Xorg the first reboot after I set WaylandEnabled 
to false in gdm3's custom.conf

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

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

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

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

Title:
  [radeon] Ubuntu fails to run Xorg the first reboot after I set
  WaylandEnabled to false in gdm3's custom.conf

Status in gdm3 package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Whenever I set Wayland to false in Gnome Display Manager's custom.conf
  file and then reboot, I still see the same scrambled graphics on the
  machine as if it were using Wayland. Rebooting the machine a SECOND
  time resolves the issue. However, I should not have to reboot twice
  for the new setting to take effect.

  Steps to Reproduce:
  1. When the machine boots up with scrambled graphics, press Control+Alt+F3
  2. Log into the machine using the tty session and run "sudo editor 
/etc/gdm3/custom.conf
  3. Set Wayland to false and reboot
  4. Notice after reboot the same scrambled graphics appear until the user 
reboots again

  Expected Results:
  Gnome Display Manager runs xorg and xorg shows the correct graphics for the 
machine.

  Actual Results:
  Graphics are scrambled and settings do not appear to take effect until next 
reboot.

  This issue occurred right before 12:45 PM, EDT, on November 29, 2019.

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  gdm3:
Installed: 3.28.3-0ubuntu18.04.4
Candidate: 3.28.3-0ubuntu18.04.4
Version table:
   *** 3.28.3-0ubuntu18.04.4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 29 12:39:33 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=751019b9-8693-494c-ad69-17ddf9e51235 ro splash quiet vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications 

[Touch-packages] [Bug 1852566] Re: [OptiPlex 3050, Intel ID 280b, Digital Out, HDMI] No sound at all

[Daniel van Vugt]

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

Ubuntu 14.04 is no longer supported (for free) but we can continue
tracking the issue in bug 1853828.

** This bug has been marked a duplicate of bug 1853828
   [OptiPlex 3050, Realtek ALC3234, Black Headphone Out, Front] No sound at all

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

Title:
  [OptiPlex 3050, Intel ID 280b, Digital Out, HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound is coming

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-170-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Nov 14 16:43:36 2019
  InstallationDate: Installed on 2018-05-12 (550 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  subhrashree   1845 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [OptiPlex 3050, Intel ID 280b, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1853786] Re: Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.

[Daniel van Vugt]

** Tags added: bionic

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

Title:
  Fullscreen stuck in various applications. Ubuntu 18.04 with Unity.

Status in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Release: Ubuntu 18.04.3 LTS
  Lightdm Version: 1.26.0-0ubuntu1

  In some programs I can't get out of fullscreen.

  I'm using Ubuntu 18.04 Bionic Beaver with Unity. I installed Unity because I 
simply don't like GNOME. The problem is that some programs get stucked in 
fullscreen, freezing the screen, not getting any response of any kind. The 
mouse moves, but that's it. Killing the process does not resolve the issue.
  This problem came with Ubuntu 18.04 or Unity since the release of Bionic 
Beaver. At this point I'm used to it. I get rid of it by going to terminal with 
ctrl+alt+f4 and typing "sudo service lightdm restart" or by rebooting with 
"sudo reboot now". But It's kind of a nuisance having to do this everytime. The 
programs that get stucked are Stellarium, Whatsdesk, SMPlayer and some flash 
players in firefox. Everyday I upgrade Ubuntu and Lightdm hoping this to be 
solved, but nothing happens.
  Weird thing: When I restart lightdm the problem dissapears until I sleep or 
reboot my notebook.

  Attached here is the "cat /var/log/syslog" output when the problem is
  ocurring using Whatdesk (at 19:53:01 I restart lightdm).

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

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

[Touch-packages] [Bug 1853828] Re: [OptiPlex 3050, Realtek ALC3234, Black Headphone Out, Front] No sound at all

[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/1853828

Title:
  [OptiPlex 3050, Realtek ALC3234, Black Headphone Out, Front] No sound
  at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  As soon as I've booted my ubuntu 19.10, I've plugged my headphones and
  got some clicking sound, but then there was no sound at all
  afterwards.

  The device shows on Settings > Output and it's detected by alsamixer
  also.

  The headphone works normally on my phone.

  This is the first time I've booted ubuntu since I've updated it (not
  considering when you have to do so for the installing process). Sound
  worked normally back then.

  Only sound I hear is the clicking sound whenever I plug it in and off.

  Headphone is at maximum gain on alsamixer.

  HW info shows at title.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tadeu  1556 F pulseaudio
tadeu  5159 F alsamixer
   /dev/snd/pcmC0D0p:   tadeu  1556 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 25 07:51:05 2019
  InstallationDate: Installed on 2019-03-27 (242 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tadeu  1556 F pulseaudio
tadeu  5159 F alsamixer
   /dev/snd/pcmC0D0p:   tadeu  1556 F...m pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [OptiPlex 3050, Realtek ALC3234, Black Headphone Out, Front] No sound 
at all
  UpgradeStatus: Upgraded to eoan on 2019-11-22 (3 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.2
  dmi.board.name: 0JP3NX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.2:bd08/09/2018:svnDellInc.:pnOptiPlex3050:pvr:rvnDellInc.:rn0JP3NX:rvrA01:cvnDellInc.:ct3:cvr:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 3050
  dmi.product.sku: 07A3
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1854120] Re: Screen contents visible briefly on lock screen on resolution change

[Daniel van Vugt]

I actually don't remember the relevant processes from pre-GNOME, sorry.

** Tags added: xenial

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

Title:
  Screen contents visible briefly on lock screen on resolution change

Status in lightdm package in Ubuntu:
  New

Bug description:
  I am using a remote application to AnyDesk to remote access my Ubuntu
  16.04 LTS 64 bit. On the application we can resize the screen and have
  the resolution of the target computer scale up and down when this is
  done.

  When the computer is locked on the login screen if the screen is
  resized ( resolution changes ) - For a brief fraction of a second the
  unlocked screen flashes and the login screen shows up again. I think
  this is a security breach to be able to peek into the inside contents
  even though the computer is locked.

  Please feel free to close this issue if this is an already known issue
  or if its already fixed in later releases.

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

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

[Touch-packages] [Bug 1853762] Re: Headphones stop working until pairing again

[Daniel van Vugt]

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Headphones stop working until pairing again

Status in bluez package in Ubuntu:
  New
Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I'm using Marshall MID ANC headphones with Ubuntu 19.10.
  Every now and then, I won't be able to use them without re-pairing first 
(like today - see logs).
  After re-pairing, everything works again for a while : I can switch off and 
on the headphones, reboot... Until it breaks again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Nov 24 19:13:40 2019
  InstallationDate: Installed on 2018-07-28 (483 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC 
WebCam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago)
  dmi.bios.date: 11/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 14:AB:C5:7E:41:26  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:319948 acl:71 sco:0 events:45583 errors:0
TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0

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

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

[Touch-packages] [Bug 1853741] Re: [arrandale] system freezes randomly on boot, after loading initial ramdisk

[Daniel van Vugt]

** Summary changed:

- system freezes randomly on boot, after loading initial ramdisk
+ [arrandale] system freezes randomly on boot, after loading initial ramdisk

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

Title:
  [arrandale] system freezes randomly on boot, after loading initial
  ramdisk

Status in linux package in Ubuntu:
  New

Bug description:
  adding nomodeset to grub parameter negates the problem, not 100% but
  almost sure this has to do with graphics initialization.

  first appeared after a recent upgrade

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 24 13:42:39 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-66-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-70-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0457]
  InstallationDate: Installed on 2018-08-22 (458 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron N7010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=5dd50c10-bb05-48da-af7d-ad4ca2d73eef ro quiet splash 
acpi_backlight=video vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 08VFX1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd03/31/2011:svnDellInc.:pnInspironN7010:pvrA11:rvnDellInc.:rn08VFX1:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Inspiron N7010
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1853739] Re: BUG: triggered 'if (axnum >= dev->valuator->numAxes)'

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1424888
   BUG: triggered 'if (axnum >= dev->valuator->numAxes)'

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

Title:
  BUG: triggered 'if (axnum >= dev->valuator->numAxes)'

Status in xorg package in Ubuntu:
  New

Bug description:
  UI stopped responding
  ctrl +alt +f3 to htop
  1 of the cpus at 100%

  I see whoopsie is at 100%
  then another app

  ctrl +alt +f2 
  back to desktop

  no apps are running
  terminal
  apport-bug xorg

  I know running apport-bug xorg from terminal will FAIL

  ubuntu 19.1 is crashing 5X per week at minimum!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 24 12:13:45 2019
  DistUpgraded: 2019-10-23 09:33:56,809 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:84ca]
  InstallationDate: Installed on 2015-08-23 (1553 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (32 days ago)
  dmi.bios.date: 07/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V LX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Mon Aug 20 17:24:57 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1853583] Re: Brightness changes randomly for my msi ge62 6qf apache pro

[Daniel van Vugt]

Are you sure automatic brightness is off? Check in Settings > Power >
...

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

** Changed in: 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/1853583

Title:
  Brightness changes randomly for my msi ge62 6qf apache pro

Status in Ubuntu:
  Incomplete

Bug description:
  Brightness of my laptop keeps changing randomly while I am working I
  have tried certain fixes online but none worked, brightness may change
  automatically to bright or dark irrespective of surrounding brightness
  even if the auto brightness is kept off. Its is really disturbing
  while working!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 22 16:46:55 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-18-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:116d]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GM204M [GeForce GTX 
970M] [1462:116d]
  InstallationDate: Installed on 2019-11-19 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Micro-Star International Co., Ltd. GE62 6QF
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=eee8aca7-3661-4ee4-99ee-4c42968c0738 ro quiet splash 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16J4IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16J4
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16J4IMS.10E:bd04/11/2016:svnMicro-StarInternationalCo.,Ltd.:pnGE626QF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J4:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GE62 6QF
  dmi.product.sku: Default string
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1853707] Re: Whose system stopped responding because of single program's fault - no way out, had to force power off

[Daniel van Vugt]

It's possible something related to the screen crashed. Next time the
problem occurs please look in /var/crash and tell us if you find
anything.

Please also (after any future hang) reboot and then run:

  journalctl -b-1 > prevboot.txt

and attach the file 'prevboot.txt' to this bug.

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

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

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

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

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

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

Title:
  Whose system stopped responding because of single program's fault - no
  way out, had to force power off

Status in compiz package in Ubuntu:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  What I did was:

  - install LibreCAD (by adding their ppa and then using apt-get)
  - open it
  - try to open the attached .dwf file

  LibreCAD hanged and the whole system stopped responding. The mouse
  button stopped moving, the system wouldn't respond to keyboard
  strokes, AND not even Ctrl+Alt+F1 worked to open a virtual terminal
  where I could have tried killing some process.

  Obviously there's a bug in LibreCAD, but no matter how badly a buggy
  (or even evil) process behaves, if a single misbehaving program can
  cause the whole OS to stall in a way that you cannot recover from,
  then by definition there's a bug in the OS.

  You must ALWAYS be able to kill the offending program and resume
  normal operation without having to stop one single application other
  than the offending one.

  I have no idea whether the bug is actually in Xorg or somewhere else;
  the reason I'm reporting it against xorg is that ctrl+alt+F1 wouldn't
  work. I might very well be wrong but I believe xorg is responsible for
  providing the virtual terminal via ctrl+alt+f1?

  Either way, that MUST ALWAYS be available no matter how badly things
  go.

  That a single program hanging causes me to have to force-power down
  the computer is outrageous.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-169.198-generic 4.4.197
  Uname: Linux 4.4.0-169-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.12)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Nov 23 17:27:22 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0647]
   NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 
620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691]
  InstallationDate: Installed on 2013-10-11 (2233 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Acer Aspire V3-571G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-169-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2

[Touch-packages] [Bug 1853466] Re: I have installed the xserver-xorg-video-intel package but cannot detect monitor

[Daniel van Vugt]

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

It appears your i7-1065G7 processor is too new for Ubuntu 18.04 to
support.

To fix this please try installing Ubuntu 18.04.3 instead:

https://ubuntu.com/download/desktop/thank-
you?version=18.04.3&architecture=amd64

or Ubuntu 19.10:

https://ubuntu.com/download/desktop/thank-
you?version=19.10&architecture=amd64

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

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

** This bug has been marked a duplicate of bug 1853585
   Intel graphics card not detected and reverts to llvmpipe

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

Title:
  I have installed the xserver-xorg-video-intel package but cannot
  detect monitor

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The monitor U2414H is not detected by Ubuntu, the graphics card
  displayed in settings is llvmpipe (LLVM 8.0, 256 bits). I believe it
  should be "Intel Iris Plus Graphics", which is what shows up in
  Windows Device Manager (my device is set up to dual boot).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 21 15:03:21 2019
  DistUpgraded: SystemError: E:Setting in Stop via TCSAFLUSH for stdin failed! 
- tcsetattr (5: Input/output error), W:Operation was interrupted before it 
could finish
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   backport-iwlwifi, 8042, 4.15.0-70-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-70-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:8a52] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:08b0]
  InstallationDate: Installed on 2019-11-15 (6 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 
(20190227)
  MachineType: Dell Inc. XPS 13 7390 2-in-1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=4540fdd6-b986-43c5-99ec-e2baa34ca219 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-11-19 (2 days ago)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  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.13:bd09/17/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.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Nov 21 15:01:07 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.3

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

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

[Touch-packages] [Bug 1853439] Re: xubuntu 18.04.3 rt5651 sound problem

[Daniel van Vugt]

Most likely the cause is:

PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.

Please look in /var/crash and tell us if there are any crash files.
Please also run:

  ps auxw | grep pulse

and tell us what it says.

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

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

Title:
  xubuntu 18.04.3 rt5651 sound problem

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  no sound !

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Thu Nov 21 13:27:58 2019
  InstallationDate: Installed on 2019-11-20 (0 days ago)
  InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   LANGUAGE=tr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

[Touch-packages] [Bug 1853439] Re: xubuntu 18.04.3 rt5651 sound problem

[Daniel van Vugt]

Please also:

1. Reboot

2. Verify sound is NOT working.

3. Run:  journalctl -b0 > journal.txt

4. Attach the file 'journal.txt' here.

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

Title:
  xubuntu 18.04.3 rt5651 sound problem

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  no sound !

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC1', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Thu Nov 21 13:27:58 2019
  InstallationDate: Installed on 2019-11-20 (0 days ago)
  InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   LANGUAGE=tr
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Andreas L]

It occurred to me, that the actual query might be cached at that time,
so I did a fresh restart of systemd-resolved and query,  and then
follows the log for these times: I don't see much relevant details in
it, except that it also tries to find MX-records but fails till
.

avl@fpc:~$ date; sudo systemctl restart systemd-resolved
Fr Dez  6 09:27:34 CET 2019
avl@fpc:~$ date; host fpc
Fr Dez  6 09:27:39 CET 2019
fpc has address 10.2.2.1
fpc has address 10.2.2.250  
fpc has IPv6 address fe80::4687:fcff:fe9e:4ac7
avl@fpc:~$ 

Note: the 10.2.2.250 is a remainder from a recent experiment, adding a
second IP address to the same network device.  It is not in 10.2.2.3's
/etc/hosts .  The problem of bad inet6 returned predates my addition of
the second ip-address.

Here the log:

Dez 06 09:27:34 fpc systemd[1]: Stopping Network Name Resolution...
Dez 06 09:27:34 fpc systemd-resolved[4579]: Removing scope on link *, protocol 
dns, family *
Dez 06 09:27:34 fpc systemd[1]: Stopped Network Name Resolution.
Dez 06 09:27:34 fpc systemd[1]: Starting Network Name Resolution...
Dez 06 09:27:35 fpc systemd-resolved[4616]: Positive Trust Anchors:
Dez 06 09:27:35 fpc systemd-resolved[4616]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Dez 06 09:27:35 fpc systemd-resolved[4616]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Dez 06 09:27:35 fpc systemd-resolved[4616]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 
19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 
23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 
27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 
31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal 
intranet lan local private test
Dez 06 09:27:35 fpc systemd-resolved[4616]: Using system hostname 'fpc'.
Dez 06 09:27:35 fpc systemd-resolved[4616]: New scope on link *, protocol dns, 
family *
Dez 06 09:27:35 fpc systemd-resolved[4616]: Found new link 2/enp4s0
Dez 06 09:27:35 fpc systemd-resolved[4616]: Found new link 1/lo
Dez 06 09:27:35 fpc systemd-resolved[4616]: Bus n/a: changing state UNSET → 
OPENING
Dez 06 09:27:35 fpc systemd-resolved[4616]: Bus n/a: changing state OPENING → 
AUTHENTICATING
Dez 06 09:27:35 fpc systemd-resolved[4616]: Creating stub listener using 
UDP/TCP.
Dez 06 09:27:35 fpc systemd-resolved[4616]: Switching to system DNS server 
10.2.2.3.
Dez 06 09:27:35 fpc systemd-resolved[4616]: Bus n/a: changing state 
AUTHENTICATING → HELLO
Dez 06 09:27:35 fpc systemd-resolved[4616]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=Hello cookie=1 reply_cookie=0 
signature=n/a error-name=n/a error-message=n/a
Dez 06 09:27:35 fpc systemd-resolved[4616]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=RequestName cookie=2 reply_cookie=0 
signature=su error-name=n/a error-message=n/a
Dez 06 09:27:35 fpc systemd-resolved[4616]: Sent message type=method_call 
sender=n/a destination=org.freedesktop.DBus path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=AddMatch cookie=3 reply_cookie=0 
signature=s error-name=n/a error-message=n/a
Dez 06 09:27:35 fpc systemd-resolved[4616]: Got message type=method_return 
sender=org.freedesktop.DBus destination=:1.2788 path=n/a interface=n/a 
member=n/a cookie=1 reply_cookie=1 signature=s error-name=n/a error-message=n/a
Dez 06 09:27:35 fpc systemd-resolved[4616]: Bus n/a: changing state HELLO → 
RUNNING
Dez 06 09:27:35 fpc systemd-resolved[4616]: Got message type=signal 
sender=org.freedesktop.DBus.Local destination=n/a 
path=/org/freedesktop/DBus/Local interface=org.freedesktop.DBus.Local 
member=Connected cookie=4294967295 reply_cookie=0 signature=n/a error-name=n/a 
error-message=n/a
Dez 06 09:27:35 fpc systemd-resolved[4616]: Got message type=signal 
sender=org.freedesktop.DBus destination=:1.2788 path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=NameAcquired cookie=2 reply_cookie=0 
signature=s error-name=n/a error-message=n/a
Dez 06 09:27:35 fpc systemd[1]: Started Network Name Resolution.
Dez 06 09:27:35 fpc systemd-resolved[4616]: Got message type=signal 
sender=org.freedesktop.DBus destination=:1.2788 path=/org/freedesktop/DBus 
interface=org.freedesktop.DBus member=NameAcquired cookie=3 reply_cookie=0 
signature=s error-name=n/a error-message=n/a
Dez 06 09:27:35 fpc systemd-resolved[4616]: Got message type=method_return 
sender=org.freedesktop.DBus destination=:1.2788 path=n/a interface=n/a 
member=n/a cookie=4 reply_cookie=2 signature=u error-name=n/a error-message=n/a
Dez 06 09:27:35 fpc systemd-resolved[4616]: Successfully acquired requested 
service name.
Dez 06 09:27:35 fpc systemd-resolved[4616]: Got messag

[Touch-packages] [Bug 1853393] Re: Xorg freeze

[Daniel van Vugt]

Please explain in more detail what freezes and for how long. If the
whole system freezes forever then on the next reboot after a freeze
please run:

  journalctl -b-1 > prevboot.txt

and attach the file 'prevboot.txt' to this bug.

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

** Changed in: 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/1853393

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  when using ubuntu it randomly freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 21 09:41:08 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: I don't know
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GV102 [10de:1e07] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3711]
  InstallationDate: Installed on 2019-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Micro-Star International Co., Ltd. MS-7C37
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic 
root=UUID=4ada2956-717e-4d5d-ae06-bd4aad086b48 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MPG X570 GAMING PLUS (MS-7C37)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd09/10/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C37:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGX570GAMINGPLUS(MS-7C37):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C37
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1853378] Re: ryzen 2500u random Xorg freeze

[Daniel van Vugt]

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

** Summary changed:

- ryzen 2500u random Xorg freeze
+ [amdgpu] ryzen 2500u random Xorg freeze

** Tags added: amdgpu

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

Title:
  [amdgpu] ryzen 2500u random Xorg freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Currently using a Dell Inspiron 3835 with a ryzen 2500u with 8gb of
  ram on a pcie nvme ssd. PC randomly freezes at times. This actually
  occurs on asus x505za also running 2500u.

  I checked the log files and there was this error.
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process 
gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654

  I think it may be a problem with gnome since I was running lubuntu
  before and there's no hang whatsoever when using that.

  Ubuntu 18.04.3 LTS
  Release 18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.3.12-050312-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 21 07:04:57 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller])
 Subsystem: Dell Vega [Radeon Vega 8 Mobile] [1028:08d7]
  InstallationDate: Installed on 2019-11-19 (1 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Inspiron 3585
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_PH.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.12-050312-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash idle=nomwait iommu=soft 
pci=nomsi vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.asset.tag: not specified
  dmi.board.name: 0TY9XW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.4.0
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/29/2019:svnDellInc.:pnInspiron3585:pvr1.4.0:rvnDellInc.:rn0TY9XW:rvrX01:cvnDellInc.:ct10:cvr1.4.0:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 3585
  dmi.product.sku: 08D7
  dmi.product.version: 1.4.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100+git1911150630.a39c34~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0~git1911201930.bcfc9c~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0~git1911201930.bcfc9c~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address

[Andreas L]

Well, ok, here is the real data: my hostname is "fpc" and really has
IPv4 10.2.2.1, the next upstream nameserver is another machine in my
home network, 10.2.2.3 which is configured to also use its /etc/hosts
(so I only need to maintain it on one machine).  Doing the nslookup
directly on 10.2.2.3 ONLY gives the ipv4 address (as I had already
checked before opening this ticket, and which also made me very positive
that the local resolver was to blame).

Unfortunately, the log doesn't really show much about where it gets what
data from...

Dez 06 09:02:14 fpc systemd-resolved[25637]: Got DNS stub UDP query packet for 
id 24958
Dez 06 09:02:14 fpc systemd-resolved[25637]: Looking up RR for fpc IN A.
Dez 06 09:02:14 fpc systemd-resolved[25637]: Sending response packet with id 
24958 on interface 1/AF_INET.
Dez 06 09:02:14 fpc systemd-resolved[25637]: Processing query...
Dez 06 09:02:14 fpc systemd-resolved[25637]: Got DNS stub UDP query packet for 
id 63588
Dez 06 09:02:14 fpc systemd-resolved[25637]: Looking up RR for fpc IN .
Dez 06 09:02:14 fpc systemd-resolved[25637]: Sending response packet with id 
63588 on interface 1/AF_INET.
Dez 06 09:02:14 fpc systemd-resolved[25637]: Processing query...
Dez 06 09:02:14 fpc systemd-resolved[25637]: Got DNS stub UDP query packet for 
id 13823
Dez 06 09:02:14 fpc systemd-resolved[25637]: Looking up RR for fpc IN MX.
Dez 06 09:02:14 fpc systemd-resolved[25637]: Cache miss for fpc IN MX
Dez 06 09:02:14 fpc systemd-resolved[25637]: Transaction 22387 for  
scope dns on */*.
Dez 06 09:02:14 fpc systemd-resolved[25637]: Using feature level UDP for 
transaction 22387.
Dez 06 09:02:14 fpc systemd-resolved[25637]: Using DNS server 10.2.2.3 for 
transaction 22387.
Dez 06 09:02:14 fpc systemd-resolved[25637]: Sending query packet with id 22387.
Dez 06 09:02:14 fpc systemd-resolved[25637]: Processing query...
Dez 06 09:02:14 fpc systemd-resolved[25637]: Processing incoming packet on 
transaction 22387. (rcode=SUCCESS)
Dez 06 09:02:14 fpc systemd-resolved[25637]: Not caching negative entry without 
a SOA record: fpc IN MX
Dez 06 09:02:14 fpc systemd-resolved[25637]: Transaction 22387 for  
on scope dns on */* now complete with  from network (unsigned).
Dez 06 09:02:14 fpc systemd-resolved[25637]: Sending response packet with id 
13823 on interface 1/AF_INET.
Dez 06 09:02:14 fpc systemd-resolved[25637]: Freeing transaction 22387.

At that minute&second I did a "host fpc". The log entries before and
after had sufficiently separate timings. (I repeated it a few times,
until other requests from other applications didn't mix in.)

This is what I get from asking "upstream" DNS directly:
$ nslookup fpc 10.2.2.3
Server: 10.2.2.3
Address:10.2.2.3#53

Name:   fpc
Address: 10.2.2.1

$
That machine 10.2.2.3 is still running Ubuntu 16.04 and dnsmasq.

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

Title:
  systemd resolves own hostname to link local ipv6 address

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I've got an ethernet-device that only has a configured ipv4 address,
  and some auto-generated link-local (aka "scope link") ipv6 address.

  Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the
  DNS-server listening on 127.0.0.53) for this host's hostname gets back
  two addresses: the correct ipv4 address, and a broken ipv6 address.

  Unlike on ipv4,  it is possible for the same ipv6-address to be
  assigned to multiple devices, and therefore the address is only valid
  in the context of the eth-device.

  Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7  prefixlen 64  
scopeid 0x20"
  then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall 
connect() typically fails with EINVAL.

  To make it a valid address, it needs to be suffixed with a "%" and the device 
name, like:
  fe80::4687:fcff:fe9e:4ac7%enp4s0

  Either the resolver can return the link name attached to the address
  separated with a "%" char, or it needs to ignore link-local inet6
  addresses.

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

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