[Touch-packages] [Bug 1868396] Re: crashes or freezes with nividia/xorg

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

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

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

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

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


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

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

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

Title:
  crashes or freezes with nividia/xorg

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I have plugged in my Dell precision 5530 laptop a 4k HDMI screen.
  Using it with 200% zoom makes xorg crash.
  I have used proprietary 430, and changed to recommended proprietary 435 
nvidia driver.
  As the system was still very unstable (no to say unusable) I had a go with 
440 from ppa.
  I also ensured that my system was up to date doing a sudo apt-get update and 
upgrade. I was suprised to discover a few packages that needed an upgrade 
although I had previously used the Software Updater tool. Maybe I was doing 
something wrong.
  Anyway, with these updates and the newer 440 driver, I have successfully 
worked a day (sparsely) without problem, and using only 100% zoom.
  As a test, I decided to try to set the zoom to 200% (through devices > 
display, and I have only the external display enabled).
  After several minutes, I clicked on the « full screen » icon to maximize a 
shell, and the PC froze.
  It was so close to my change in the zoom ratio, that I suspect this is 
related.

  dmesg shew me that NVRM had a problem :
  [97501.301998] NVRM: GPU at PCI::01:00: 
GPU-dee28f75-4083-96a8-1a0b-491b6109101a
  [97501.302000] NVRM: Xid (PCI::01:00): 32, pid=493, Channel ID 0018 
intr 0004
  [97501.302134] NVRM: Xid (PCI::01:00): 32, pid=2052, Channel ID 0018 
intr 0020
  [97501.317307] NVRM: Xid (PCI::01:00): 69, pid=902, Class Error: ChId 
001b, Class 902d, Offset 0250, Data 55d3, ErrorCode 000c

  pid 493 is gone

  pid 2052 is xorg
  stan  2052  2050  1 mars20 tty200:25:38 /usr/lib/xorg/Xorg vt2 
-displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset 
-keeptty -verbose 3

  pid 902 is nvidia driver
  root   902 2  0 mars20 ?   00:02:59 [irq/163-nvidia]

  ppid 2052 is 2050 :
  stan  2050  2004  0 mars20 tty200:00:00 /usr/lib/gdm3/gdm-x-session 
--run-script env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session 
--systemd --session=ubuntu

  After such an event, the previous days, the system became unstable,
  and I have got problems with other devices such as audio and network.

  If I run the manufacturer self-check test, everything is fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.6
  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: Sat Mar 21 18:36:53 2020
  DistUpgraded: 2019-11-04 11:06:46,434 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.64, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 

[Touch-packages] [Bug 1868358] Re: intel graphics not detected and showing llvmpipe

2020-03-22 Thread Daniel van Vugt
** 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/1868358

Title:
  intel graphics not detected and showing llvmpipe

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Ubuntu 18.04 install  is unable to detect integrated Intel graphics card UHD 
620. Using a Dell Inspiron 7391 13 2-in-1 the machine is unable to detect 
attached monitors, change resolutions, or adjust brightness.
   No Dual Boot, running linux Ubuntu 18.04.4

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

  % uname -o
  GNU/Linux

  $ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
Version table:
   *** 2:2.99.917+git20171229-1 500
  500 http://ubuntu.ntc.net.np/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ lspci -v
  00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 
(prog-if 00 [VGA controller])
Subsystem: Dell Device 0960
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at 602200 (64-bit, non-prefetchable) [size=16M]
Memory at 40 (64-bit, prefetchable) [size=256M]
I/O ports at 3000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: 

  
  System Settings -> Details:
  Graphics llvmpipe (LLVM 9.0, 256 bits)

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

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


[Touch-packages] [Bug 1868415] Re: Dell l322x Touchpad click drag doesn't work

2020-03-22 Thread Daniel van Vugt
** 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/1868415

Title:
  Dell l322x Touchpad click drag doesn't work

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I've upgraded (fresh installation) my OS from 14.04 to 18.04. And everything 
but the touchpad seems to work properly. 
  When i try to drag and drop something or selecting some text seems dead. I 
tried to do the same things with an external mouse and it works well.
   

  > sudo libinput measure touchpad-pressure
  [sudo] password di matteog: 
  Using CyPS/2 Cypress Trackpad: /dev/input/event6

  Ready for recording data.
  Pressure range used: 30:25
  Palm pressure range used: 130
  Place a single finger on the touchpad to measure pressure values.
  Ctrl+C to exit

  Sequence 116 pressure: min:  46 max:  95 avg:  84 median:  89 tags: down
  Sequence 117 pressure: min:  29 max:  97 avg:  67 median:  86 tags: down
  Sequence 118 pressure: min:  25 max:  50 avg:  41 median:  44 tags: down
  Sequence 119 pressure: min:  13 max:  14 avg:  13 median:  14 tags:
  Sequence 120 pressure: min:  28 max:  31 avg:  29 median:  31 tags: down
  Sequence 121 pressure: min:  15 max:  33 avg:  26 median:  29 tags: down
  Sequence 122 pressure: min:  37 max:  82 avg:  66 median:  73 tags: down
  Sequence 123 pressure: min:  63 max:  94 avg:  83 median:  89 tags: down
  Sequence 124 pressure: min:  66 max: 137 avg: 118 median: 126 tags: down palm
  Sequence 125 pressure: min:  47 max:  73 avg:  63 median:  68 tags: down
  Sequence 126 pressure: min:  33 max:  66 avg:  55 median:  58 tags: down
  Sequence 127 pressure: min:  32 max: 100 avg:  81 median:  91 tags: down
  Sequence 128 pressure: min:  44 max:  86 avg:  72 median:  78 tags: down
  Sequence 129 pressure: min:  62 max: 108 avg:  95 median: 103 tags: down
  Sequence 130 pressure: min:  72 max: 131 avg: 118 median: 124 tags: down palm
  Sequence 131 pressure: min:  52 max: 112 avg:  96 median: 103 tags: down
  Sequence 132 pressure: min:  44 max: 101 avg:  83 median:  88 tags: down
  Sequence 133 pressure: min: 150 max: 150 avg: 150 median: 150 tags: down palm
  Traceback (most recent call last):
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
299, in 
  main(sys.argv)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
289, in main
  loop(device)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
246, in loop
  handle_event(device, event)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
233, in handle_event
  handle_abs(device, event)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
224, in handle_abs
  print("\r{}".format(s))
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
105, in __str__
  return self._str_state() if self.is_active else self._str_summary()
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
114, in _str_summary
  self.avg(),
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
96, in avg
  return int(sum([p.pressure for p in self.points])/len(self.points))
  ZeroDivisionError: division by zero

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

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


[Touch-packages] [Bug 1868358] Re: intel graphics not detected and showing llvmpipe

2020-03-22 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1868358

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

** Tags added: bionic

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

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

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

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

Title:
  intel graphics not detected and showing llvmpipe

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  Ubuntu 18.04 install  is unable to detect integrated Intel graphics card UHD 
620. Using a Dell Inspiron 7391 13 2-in-1 the machine is unable to detect 
attached monitors, change resolutions, or adjust brightness.
   No Dual Boot, running linux Ubuntu 18.04.4

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

  % uname -o
  GNU/Linux

  $ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
Installed: 2:2.99.917+git20171229-1
Candidate: 2:2.99.917+git20171229-1
Version table:
   *** 2:2.99.917+git20171229-1 500
  500 http://ubuntu.ntc.net.np/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ lspci -v
  00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 
(prog-if 00 [VGA controller])
Subsystem: Dell Device 0960
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at 602200 (64-bit, non-prefetchable) [size=16M]
Memory at 40 (64-bit, prefetchable) [size=256M]
I/O ports at 3000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: 

  
  System Settings -> Details:
  Graphics llvmpipe (LLVM 9.0, 256 bits)

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

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


[Touch-packages] [Bug 1868392] Re: Asus ZenBook UX481FL touchscreen not working in 5.3.0-42

2020-03-22 Thread Daniel van Vugt
** Summary changed:

- Touchscreen not working in 5.3.0-42
+ Asus ZenBook UX481FL touchscreen not working in 5.3.0-42

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

** Tags added: regression regression-update

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

Title:
  Asus ZenBook UX481FL touchscreen not working in 5.3.0-42

Status in linux package in Ubuntu:
  New

Bug description:
  My Asus Zenbook touch screen works in 5.3.0-40, but stops working when
  I boot into the 5.3.0-42 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)
  ApportVersion: 2.20.11-0ubuntu8.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Mar 21 17:52:19 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.3.0-40-generic, x86_64: installed
   nvidia, 435.21, 5.3.0-42-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed
   virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:13ff]
 Subsystem: ASUSTeK Computer Inc. GP108BM [GeForce MX250] [1043:13ff]
  InstallationDate: Installed on 2020-02-11 (38 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook UX481FL_UX481FL
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=af_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=c157ba74-8933-4447-9f11-e965279079be ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX481FL.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX481FL
  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.:bvrUX481FL.206:bd08/06/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX481FL_UX481FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX481FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX481FL_UX481FL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/linux/+bug/1868392/+subscriptions

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


[Touch-packages] [Bug 1868332] Re: Scrolling jumps after switching windows

2020-03-22 Thread Daniel van Vugt
We can't track bugs in Chrome here because Chrome is not part of Ubuntu.
However Chromium is so I will assume the same bug exists there.

** Summary changed:

- Scrolling jumps after switching tabs
+ Scrolling jumps after switching windows

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

Title:
  Scrolling jumps after switching windows

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  The bug has to do with mouse scrolling and switching windows; I do not
  know which package it is part of.

  The problem arises when I have two windows of two different
  applications open, such as Google Chrome and a text editor. To
  reproduce the error, I have Google Chrome open initially, then I
  switch tabs (using the shortcut Alt-Tab) to the text editor, then
  scroll around on the text editor. When I Alt-Tab back to Google
  Chrome, my first scroll leads to the page jumping by a large amount
  either up or down before resuming regular mouse scrolling. It is only
  this initial scroll after switching tabs that jumps like this. It also
  happens regardless of whether I use a mouse or the touch pad.

  I also notice, given the same scenario, if I scroll up on the text
  editor, the Google Chrome initial scroll jump will be upward. If I
  scroll down on the text editor, the Chrome jump will be downward. If I
  scroll a lot in the text editor, the Chrome jump will be large. If I
  scroll a small amount in the text editor, the Chrome jump will be
  small.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 17:17:39 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9]
  InstallationDate: Installed on 2020-01-26 (54 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 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd 
   Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83B9
  dmi.board.vendor: HP
  dmi.board.version: 56.43
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
  dmi.product.sku: 1WU65AV
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Touch-packages] [Bug 1868358] [NEW] intel graphics not detected and showing llvmpipe

2020-03-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

[Impact]
Ubuntu 18.04 install  is unable to detect integrated Intel graphics card UHD 
620. Using a Dell Inspiron 7391 13 2-in-1 the machine is unable to detect 
attached monitors, change resolutions, or adjust brightness.
 No Dual Boot, running linux Ubuntu 18.04.4

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

% uname -o
GNU/Linux

$ apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.99.917+git20171229-1
  Candidate: 2:2.99.917+git20171229-1
  Version table:
 *** 2:2.99.917+git20171229-1 500
500 http://ubuntu.ntc.net.np/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

$ lspci -v
00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 
(prog-if 00 [VGA controller])
Subsystem: Dell Device 0960
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at 602200 (64-bit, non-prefetchable) [size=16M]
Memory at 40 (64-bit, prefetchable) [size=256M]
I/O ports at 3000 [size=64]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: 


System Settings -> Details:
Graphics llvmpipe (LLVM 9.0, 256 bits)

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


** Tags: bionic
-- 
intel graphics not detected and showing llvmpipe
https://bugs.launchpad.net/bugs/1868358
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1757375] Re: Desktop unable to Suspend when Inactive

2020-03-22 Thread Ryan C. Underwood
Still a major laptop usability problem in eoan.

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

Title:
  Desktop unable to Suspend when Inactive

Status in policykit-desktop-privileges package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu 16.04 and later versions (Xfce/Xubuntu) the power-manager is
  unable to suspend the system when the user is inactive. A PK user-
  agent dialog is presented for the user to authenticate first - and as
  this action occurs specifically when the user is idle and away the PC
  can end up having an unplanned loss of power when the battery is
  exhausted.

  /var/log/auth.log shows:

  polkitd(authority=local): Operator of unix-session:c2 FAILED to
  authenticate to gain authorization for action
  org.freedesktop.login1.suspend for system-bus-name::1.47 [xfce4-power-
  manager --restart --sm-client-id 2992705d4-6fa2-4fba-966c-
  f7631ecd0b46] (owned by unix-user:tj)

  The problem seems to be "com.ubuntu.desktop.pkla" is missing an entry
  to allow Suspend. Currently it only has an entry for hibernate.

  Adding the following stanza solves the issue:

  [Enable suspend by default in logind]
  Identity=unix-user:*
  
Action=org.freedesktop.login1.suspend;org.freedesktop.login1.inhibit-handle-suspend-key;org.freedesktop.login1;org.freedesktop.login1.suspend-multiple-sessions;org.freedesktop.login1.suspend-ignore-inhibit
  ResultActive=yes
  ResultInactive=yes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1757375/+subscriptions

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


[Touch-packages] [Bug 1868405] Re: Untranslatable "Monitor of ..."

2020-03-22 Thread Daniel van Vugt
PulseAudio development is not tracked here so please report the issue
upstream at:

  https://gitlab.freedesktop.org/groups/pulseaudio/-/issues

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

Title:
  Untranslatable "Monitor of ..."

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  It is impossible to translate string "Monitor of %s". Please add
  gettext call here and export the string into the .pot template.

  
https://git.launchpad.net/ubuntu/+source/pulseaudio/tree/src/pulsecore/sink.c?id=25a10a09f88d51bfd7d80574fa6c329086630531#n373

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

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


[Touch-packages] [Bug 1868405] Re: Untranslatable "Monitor of ..."

2020-03-22 Thread Daniel van Vugt
and then tell us the new bug ID.

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

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

Title:
  Untranslatable "Monitor of ..."

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  It is impossible to translate string "Monitor of %s". Please add
  gettext call here and export the string into the .pot template.

  
https://git.launchpad.net/ubuntu/+source/pulseaudio/tree/src/pulsecore/sink.c?id=25a10a09f88d51bfd7d80574fa6c329086630531#n373

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

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


[Touch-packages] [Bug 1868415] Re: Dell l322x Touchpad click drag doesn't work

2020-03-22 Thread Daniel van Vugt
If you upgraded from 14.04 then you might not even be using the libinput
driver. Please run this command to send us more information about the
machine:

  apport-collect 1868415


** No longer affects: ubuntu

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

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

** Tags added: bionic

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

Title:
  Dell l322x Touchpad click drag doesn't work

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I've upgraded (fresh installation) my OS from 14.04 to 18.04. And everything 
but the touchpad seems to work properly. 
  When i try to drag and drop something or selecting some text seems dead. I 
tried to do the same things with an external mouse and it works well.
   

  > sudo libinput measure touchpad-pressure
  [sudo] password di matteog: 
  Using CyPS/2 Cypress Trackpad: /dev/input/event6

  Ready for recording data.
  Pressure range used: 30:25
  Palm pressure range used: 130
  Place a single finger on the touchpad to measure pressure values.
  Ctrl+C to exit

  Sequence 116 pressure: min:  46 max:  95 avg:  84 median:  89 tags: down
  Sequence 117 pressure: min:  29 max:  97 avg:  67 median:  86 tags: down
  Sequence 118 pressure: min:  25 max:  50 avg:  41 median:  44 tags: down
  Sequence 119 pressure: min:  13 max:  14 avg:  13 median:  14 tags:
  Sequence 120 pressure: min:  28 max:  31 avg:  29 median:  31 tags: down
  Sequence 121 pressure: min:  15 max:  33 avg:  26 median:  29 tags: down
  Sequence 122 pressure: min:  37 max:  82 avg:  66 median:  73 tags: down
  Sequence 123 pressure: min:  63 max:  94 avg:  83 median:  89 tags: down
  Sequence 124 pressure: min:  66 max: 137 avg: 118 median: 126 tags: down palm
  Sequence 125 pressure: min:  47 max:  73 avg:  63 median:  68 tags: down
  Sequence 126 pressure: min:  33 max:  66 avg:  55 median:  58 tags: down
  Sequence 127 pressure: min:  32 max: 100 avg:  81 median:  91 tags: down
  Sequence 128 pressure: min:  44 max:  86 avg:  72 median:  78 tags: down
  Sequence 129 pressure: min:  62 max: 108 avg:  95 median: 103 tags: down
  Sequence 130 pressure: min:  72 max: 131 avg: 118 median: 124 tags: down palm
  Sequence 131 pressure: min:  52 max: 112 avg:  96 median: 103 tags: down
  Sequence 132 pressure: min:  44 max: 101 avg:  83 median:  88 tags: down
  Sequence 133 pressure: min: 150 max: 150 avg: 150 median: 150 tags: down palm
  Traceback (most recent call last):
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
299, in 
  main(sys.argv)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
289, in main
  loop(device)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
246, in loop
  handle_event(device, event)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
233, in handle_event
  handle_abs(device, event)
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
224, in handle_abs
  print("\r{}".format(s))
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
105, in __str__
  return self._str_state() if self.is_active else self._str_summary()
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
114, in _str_summary
  self.avg(),
File 
"/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", line 
96, in avg
  return int(sum([p.pressure for p in self.points])/len(self.points))
  ZeroDivisionError: division by zero

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

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


[Touch-packages] [Bug 1868415] [NEW] Dell l322x Touchpad click drag doesn't work

2020-03-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I've upgraded (fresh installation) my OS from 14.04 to 18.04. And everything 
but the touchpad seems to work properly. 
When i try to drag and drop something or selecting some text seems dead. I 
tried to do the same things with an external mouse and it works well.
 

> sudo libinput measure touchpad-pressure
[sudo] password di matteog: 
Using CyPS/2 Cypress Trackpad: /dev/input/event6

Ready for recording data.
Pressure range used: 30:25
Palm pressure range used: 130
Place a single finger on the touchpad to measure pressure values.
Ctrl+C to exit

Sequence 116 pressure: min:  46 max:  95 avg:  84 median:  89 tags: down
Sequence 117 pressure: min:  29 max:  97 avg:  67 median:  86 tags: down
Sequence 118 pressure: min:  25 max:  50 avg:  41 median:  44 tags: down
Sequence 119 pressure: min:  13 max:  14 avg:  13 median:  14 tags:
Sequence 120 pressure: min:  28 max:  31 avg:  29 median:  31 tags: down
Sequence 121 pressure: min:  15 max:  33 avg:  26 median:  29 tags: down
Sequence 122 pressure: min:  37 max:  82 avg:  66 median:  73 tags: down
Sequence 123 pressure: min:  63 max:  94 avg:  83 median:  89 tags: down
Sequence 124 pressure: min:  66 max: 137 avg: 118 median: 126 tags: down palm
Sequence 125 pressure: min:  47 max:  73 avg:  63 median:  68 tags: down
Sequence 126 pressure: min:  33 max:  66 avg:  55 median:  58 tags: down
Sequence 127 pressure: min:  32 max: 100 avg:  81 median:  91 tags: down
Sequence 128 pressure: min:  44 max:  86 avg:  72 median:  78 tags: down
Sequence 129 pressure: min:  62 max: 108 avg:  95 median: 103 tags: down
Sequence 130 pressure: min:  72 max: 131 avg: 118 median: 124 tags: down palm
Sequence 131 pressure: min:  52 max: 112 avg:  96 median: 103 tags: down
Sequence 132 pressure: min:  44 max: 101 avg:  83 median:  88 tags: down
Sequence 133 pressure: min: 150 max: 150 avg: 150 median: 150 tags: down palm
Traceback (most recent call last):
  File "/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", 
line 299, in 
main(sys.argv)
  File "/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", 
line 289, in main
loop(device)
  File "/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", 
line 246, in loop
handle_event(device, event)
  File "/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", 
line 233, in handle_event
handle_abs(device, event)
  File "/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", 
line 224, in handle_abs
print("\r{}".format(s))
  File "/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", 
line 105, in __str__
return self._str_state() if self.is_active else self._str_summary()
  File "/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", 
line 114, in _str_summary
self.avg(),
  File "/usr/lib/x86_64-linux-gnu/libinput/libinput-measure-touchpad-pressure", 
line 96, in avg
return int(sum([p.pressure for p in self.points])/len(self.points))
ZeroDivisionError: division by zero

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


** Tags: bot-comment
-- 
Dell l322x Touchpad click drag doesn't work
https://bugs.launchpad.net/bugs/1868415
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1868286] Re: Disable A2DP when switch input device

2020-03-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1838151 ***
https://bugs.launchpad.net/bugs/1838151

Please also try downloading the deb files for the previous version:

https://launchpad.net/ubuntu/+source/bluez/5.50-0ubuntu4/+build/17750409

and then install them:

  sudo dpkg -i *.deb

Does that fix the problem?

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

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

Title:
  Disable A2DP when switch input device

Status in bluez package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  How to reproduce:

  1) Connect the headset via Bluetooth
  2) Automatically will use A2DP (until here everything ok)
  3) Go to sound settings, will be the "internal microphone" selected. Switch 
to use the microphone of the headset and will switch to low-quality audio HSP

  Happens with the upgrade: bluez:amd64 (5.50-0ubuntu4 ->
  5.50-0ubuntu5). Before that upgrade, everything was working fine. Only
  the automatic selection of A2DP fails sometimes but the microphone and
  A2DP were possible to use. After the mentioned upgrade to
  5.50-0ubuntu5, it's just impossible to use the microphone and the A2DP
  audio at the same time.

  When I do the switch in the input device in the syslog it's the
  following message:

  kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0

  I tried to downgrade to 5.50-0ubuntu4 but didn't work, the A2DP is not
  usable at all.

  pulseaudio[8370]: Refused to switch profile to a2dp_sink: Not
  connected

  
  Description:  Ubuntu 19.10
  Release:  19.10
  Device: LE_WH-H900N (h.ear)

  Regards,

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

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


[Touch-packages] [Bug 1868286] Re: Disable A2DP when switch input device

2020-03-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1838151 ***
https://bugs.launchpad.net/bugs/1838151

Please clarify: You say the latest bluez update caused the problem:

  Happens with the upgrade: bluez:amd64 (5.50-0ubuntu4 ->
5.50-0ubuntu5). Before that upgrade, everything was working fine.

and you also say it didn't cause the problem:

  I tried to downgrade to 5.50-0ubuntu4 but didn't work, the A2DP is not
usable at all.

So this is probably a kernel bug or a pulseaudio bug.

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

Title:
  Disable A2DP when switch input device

Status in bluez package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  How to reproduce:

  1) Connect the headset via Bluetooth
  2) Automatically will use A2DP (until here everything ok)
  3) Go to sound settings, will be the "internal microphone" selected. Switch 
to use the microphone of the headset and will switch to low-quality audio HSP

  Happens with the upgrade: bluez:amd64 (5.50-0ubuntu4 ->
  5.50-0ubuntu5). Before that upgrade, everything was working fine. Only
  the automatic selection of A2DP fails sometimes but the microphone and
  A2DP were possible to use. After the mentioned upgrade to
  5.50-0ubuntu5, it's just impossible to use the microphone and the A2DP
  audio at the same time.

  When I do the switch in the input device in the syslog it's the
  following message:

  kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0

  I tried to downgrade to 5.50-0ubuntu4 but didn't work, the A2DP is not
  usable at all.

  pulseaudio[8370]: Refused to switch profile to a2dp_sink: Not
  connected

  
  Description:  Ubuntu 19.10
  Release:  19.10
  Device: LE_WH-H900N (h.ear)

  Regards,

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

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


[Touch-packages] [Bug 1868286] Re: Disable A2DP when switch input device

2020-03-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1838151 ***
https://bugs.launchpad.net/bugs/1838151

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

apport-collect 1868286

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

** Tags added: eoan

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

** Also affects: bluez (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/1868286

Title:
  Disable A2DP when switch input device

Status in bluez package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  How to reproduce:

  1) Connect the headset via Bluetooth
  2) Automatically will use A2DP (until here everything ok)
  3) Go to sound settings, will be the "internal microphone" selected. Switch 
to use the microphone of the headset and will switch to low-quality audio HSP

  Happens with the upgrade: bluez:amd64 (5.50-0ubuntu4 ->
  5.50-0ubuntu5). Before that upgrade, everything was working fine. Only
  the automatic selection of A2DP fails sometimes but the microphone and
  A2DP were possible to use. After the mentioned upgrade to
  5.50-0ubuntu5, it's just impossible to use the microphone and the A2DP
  audio at the same time.

  When I do the switch in the input device in the syslog it's the
  following message:

  kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0

  I tried to downgrade to 5.50-0ubuntu4 but didn't work, the A2DP is not
  usable at all.

  pulseaudio[8370]: Refused to switch profile to a2dp_sink: Not
  connected

  
  Description:  Ubuntu 19.10
  Release:  19.10
  Device: LE_WH-H900N (h.ear)

  Regards,

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

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


[Touch-packages] [Bug 1868286] Re: Disable A2DP when switch input device

2020-03-22 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1838151 ***
https://bugs.launchpad.net/bugs/1838151

Sorry, I should have noticed this earlier. A2DP does not support
microphones. If you want to use a microphone then yes it will switch to
low quality HSP mode. This is not a bug, but is a limitation in the
Bluetooth spec. Everything is behaving correctly...

But something better is on the way, so I will mark this as a duplicate
of bug 1838151.

** This bug has been marked a duplicate of bug 1838151
   Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing wide 
band speech support.

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

Title:
  Disable A2DP when switch input device

Status in bluez package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  How to reproduce:

  1) Connect the headset via Bluetooth
  2) Automatically will use A2DP (until here everything ok)
  3) Go to sound settings, will be the "internal microphone" selected. Switch 
to use the microphone of the headset and will switch to low-quality audio HSP

  Happens with the upgrade: bluez:amd64 (5.50-0ubuntu4 ->
  5.50-0ubuntu5). Before that upgrade, everything was working fine. Only
  the automatic selection of A2DP fails sometimes but the microphone and
  A2DP were possible to use. After the mentioned upgrade to
  5.50-0ubuntu5, it's just impossible to use the microphone and the A2DP
  audio at the same time.

  When I do the switch in the input device in the syslog it's the
  following message:

  kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0

  I tried to downgrade to 5.50-0ubuntu4 but didn't work, the A2DP is not
  usable at all.

  pulseaudio[8370]: Refused to switch profile to a2dp_sink: Not
  connected

  
  Description:  Ubuntu 19.10
  Release:  19.10
  Device: LE_WH-H900N (h.ear)

  Regards,

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

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


[Touch-packages] [Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected

2020-03-22 Thread Daniel van Vugt
** Package changed: alsa-driver (Ubuntu) => linux-firmware (Ubuntu)

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

Title:
  [Dell Vostro 5590] PCI/internal sound card not detected

Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  Problem with detecting audio input/output device.
  Device: Dell Vostro 5590

  Tested earlier also on Ubuntu 18.04 and 19.10.
  On older systems with some configurations output device was working, but I 
never succeeded making build-in microphone to work (be properly detected).

  On current Ubuntu 20.04 (14.03.2020) both input and output audio
  devices are not visible at all.

  Devices are work without any issues on Windows 10 originally installed
  on the device.

  Let me know if I can provide any additional information that will help
  solving the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 14 23:45:55 2020
  InstallationDate: Installed on 2020-03-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 051P23
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1866217] Re: Mouse pointer vanished on Wayland (okay on X)

2020-03-22 Thread Daniel van Vugt
Is this with an AMD/Radeon GPU? If so then it would be bug 1867080.

** Package changed: wayland (Ubuntu) => mutter (Ubuntu)

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

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

Title:
  Mouse pointer vanished on Wayland (okay on X)

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Running 20.04 with all the repos enabled (including focal-proposed)

  A recent update (apt-get dist-upgrade) made the mouse point disappear.

  
  The mouse worked on a text console... and lsusb etc showed the presence of 
the mouse.
  In Wayland, pressing control key showed the pointer location.

  
  Resolution
  Edited /etc/gdm3/custom.conf and uncommented "WaylandEnable=false"
  Rebooted a mouse pointer is now back.

  Wayland device driver problem?

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

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


[Touch-packages] [Bug 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

2020-03-22 Thread Hui Wang
BTW, this SRU is not backported from upstream of alsa-lib and this SRU
is not going to be submitted to upstream. That is because the latest
alsa-lib already supported the ucm2 and with ucm2 all machines could
share one ucm, so there is no this problem for latest alsa-lib. This
problem is only specific to the alsa-lib of Eoan and Bionic.


** Description changed:

+ This SRU is not backported from upstream of alsa-lib and this SRU is not
+ going to be submitted to upstream. That is because the latest alsa-lib
+ already supported the ucm2 and with ucm2 all machines could share one
+ ucm, so there is no this problem for latest alsa-lib. This problem is
+ only specific to the alsa-lib of Eoan and Bionic.
+ 
  [Impact]
  On some lenovo notebooks, ucm files are not loaded and mic can't be used
  
  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.
  
  [Test Case]
  after applying this patch, I installed the testing alsa-lib on lenovo X1C7 
and Dell vostro5390 which are all machines with the dmic connected to pch, 
after booing up, I checked the /usr/share/alsa/ucm/, the LENOVO-BIOSID-xxx 
folders are there, and the LENOVO machine loaded the N2H/*.conf, it worked 
well, the Dell machine still loaded the ucm by cardname, it worked as good as 
before.
  
  [Regression Potential]
  low, just add some new ucms and let LENOVO machine find the ucm by 
bios_version if it fails by cardlongname. And already tested the change on 
lenovo and dell machines.

** Tags added: originate-from-1862577 sutton

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Confirmed
Status in alsa-lib source package in Eoan:
  Confirmed
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supported the ucm2 and with ucm2 all machines could
  share one ucm, so there is no this problem for latest alsa-lib. This
  problem is only specific to the alsa-lib of Eoan and Bionic.

  [Impact]
  On some lenovo notebooks, ucm files are not loaded and mic can't be used

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  after applying this patch, I installed the testing alsa-lib on lenovo X1C7 
and Dell vostro5390 which are all machines with the dmic connected to pch, 
after booing up, I checked the /usr/share/alsa/ucm/, the LENOVO-BIOSID-xxx 
folders are there, and the LENOVO machine loaded the N2H/*.conf, it worked 
well, the Dell machine still loaded the ucm by cardname, it worked as good as 
before.

  [Regression Potential]
  low, just add some new ucms and let LENOVO machine find the ucm by 
bios_version if it fails by cardlongname. And already tested the change on 
lenovo and dell machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1868210/+subscriptions

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


[Touch-packages] [Bug 962082] Re: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips

2020-03-22 Thread Daniel van Vugt
This bug is closed.

Please report any new issues by running:

  ubuntu-bug bluez

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

Title:
  Profiles that require duplex audio like Head Set (HSP) and Hands Free
  (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips

Status in HWE Next:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  This problem seems to occur on every device that uses  the BCM20702A0
  Bluetooth hardware.

  How to reproduce:

  (1) Pair a bluetooth headset with a machine equipped with a BCM20702A0.
  (2) Activate the device.  Usually there is a button on the headset you should 
press to notify the bluetooth stack that you're ready to use the device.  This 
creates SCO link and the plumbs the audio components.
  (3) Open the sound settings tool and select the bluetooth device under the 
"Input" and "Output" tabs.  Under each tab you should see a table with an entry 
that has a headset icon on the left with the bluetooth device name to the 
right.  This is the item to select.

  Now, everything should be configured so that you can use your
  bluetooth device to hear and record audio.  Test this by:

  Testing Input:

  (1) In the sound settings tool, select the "Input" tab.
  (2) Make sure the "Input Volume" is not muted and the scale widget is not set 
to zero.
  (3) Make sounds into the headset mic -- you should see the "Input Level" bar 
raise.

  Testing Output:
  In the same program:
  (1) Select the "Hardware" tab.
  (2) In the box labeled "Choose a device to configure", select your bluetooth 
device.
  (3) A combobox should appear at the bottom of the window labeled "Settings 
for the selected device".  Choose "Telephony Duplex (HSP/HFP)".
  (4) Now click on the "Test Speakers" button to the right.
  (5) Run speaker test.  You should hear a sound.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/962082/+subscriptions

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


[Touch-packages] [Bug 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work

2020-03-22 Thread Hui Wang
Mar 21 18:57:22 user-ThinkPad-X1-Carbon-7th
chromium_chromium.desktop[4806]:
[4806:4806:0321/185722.248501:ERROR:pulse_util.cc(300)] pa_operation is
nullptr.

Maybe the chromium is not compatible with the new pulseaudio (13.99)?
The api is changed in the PA-13.99 while the chromium still uses the old
API?

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

Title:
  Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Focal Fossa the microphone is recognised but doesn't work.

  Chromium shows the microphone as present but off, and if it is
  renabled it goes off again after a couple of seconds.

  Chromium logs this error:

  [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
  [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete
  [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
  [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete
  [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
  [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete

  Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th
  chromium_chromium.desktop[9531]:
  [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation
  is nullptr.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1687 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1687 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 23:03:01 2020
  InstallationDate: Installed on 2020-03-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Black Mic, Right
  Symptom_Type: None of the above
  Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20R1000RUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20R1000RUS
  dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712

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

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


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

2020-03-22 Thread Chad Smith
A separate bug has been filed against ifupdown package as well. Though
I'm not sure it will be a bug that will be fixed because Ubuntu Bionic
and later do not really support ifupdown, they support using netplan for
network configuration.

https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1868329

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

Title:
  Package ifupdown breaks network configuration by cloud-init

Status in cloud-init:
  In Progress
Status in ifupdown package in Ubuntu:
  New

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

  To reproduce with Packer (I confirmed this method):

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

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

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

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

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

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

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

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

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

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


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

2020-03-22 Thread Chad Smith
An upstream commit is up for review with a fix for this issue:
https://github.com/canonical/cloud-init/pull/267

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

Title:
  Package ifupdown breaks network configuration by cloud-init

Status in cloud-init:
  In Progress
Status in ifupdown package in Ubuntu:
  New

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

  To reproduce with Packer (I confirmed this method):

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

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1868335] Re: Sync colord 1.4.4-2 (main) from Debian unstable (main)

2020-03-22 Thread Amr Ibrahim
** Changed in: colord (Ubuntu)
   Status: New => Fix Released

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

Title:
  Sync colord 1.4.4-2 (main) from Debian unstable (main)

Status in colord package in Ubuntu:
  Fix Released

Bug description:
  Please sync colord 1.4.4-2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* No-change rebuild with fixed binutils on arm64.
* Omit colord-sensor-argyll on i386.
  The change to omit colord-sensor-argyll on i386 was adopted in Debian.

  Changelog entries since current focal version 1.4.4-1ubuntu2:

  colord (1.4.4-2) unstable; urgency=medium

* Team upload.
* Bump debhelper to 12 and install the daemons in /usr/libexec
* debian/rules: Explicitly disable systemd and udev on non-linux 
architectures
* debian/control: Bump Standards-Version to 4.5.0 (no further changes)
* debian/control: Drop docbook-utils from build-dep, this doesn't seems
  necessary and add xsltproc instead
* debian/control: Mark the -dev and gir packages as Multi-arch: same
* Omit colord-sensor-argyll on Ubuntu/i386.
  Thanks to Steve Langasek  (Closes: #948540)
* debian/control: Set Rules-Requires-Root: no
* debian/watch: Use https:// instead of http://
* d/p/tests-Make-the-build-reproductible.patch: Make the build reproductible
* debian/gbp.conf: Set upstream-vcs-tag and make sure patches are not 
numbered

   -- Laurent Bigonville   Fri, 20 Mar 2020 15:50:36
  +0100

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

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


[Touch-packages] [Bug 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work

2020-03-22 Thread Thomas Parrott
I tried installing that kernel and rebooting but I get a grub error
"cant find command hwmatch" and cannot boot into that kernel.

linux-headers-5.6.0-050600rc6_5.6.0-050600rc6.202003200818_all.deb
linux-headers-5.6.0-050600rc6-generic_5.6.0-050600rc6.202003200818_amd64.deb
linux-image-unsigned-5.6.0-050600rc6-generic_5.6.0-050600rc6.202003200818_amd64.deb
linux-modules-5.6.0-050600rc6-generic_5.6.0-050600rc6.202003200818_amd64.deb


dpkg -i *.deb

Thanks
Tom

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

Title:
  Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On Focal Fossa the microphone is recognised but doesn't work.

  Chromium shows the microphone as present but off, and if it is
  renabled it goes off again after a couple of seconds.

  Chromium logs this error:

  [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
  [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete
  [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
  [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete
  [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
  [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete

  Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th
  chromium_chromium.desktop[9531]:
  [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation
  is nullptr.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1687 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1687 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 23:03:01 2020
  InstallationDate: Installed on 2020-03-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Black Mic, Right
  Symptom_Type: None of the above
  Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20R1000RUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20R1000RUS
  dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712

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

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


[Touch-packages] [Bug 1868501] [NEW] software-properties-gtk is blank when run as normal user.

2020-03-22 Thread Solitaire
Public bug reported:

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

Upgraded install from 19.10

"Software & Updates" windows is blank when initiated from either the
terminal or via the "Settings..." button in the "Software Updater".

If I run "software-properties-gtk" in the terminal the window is also blank.
If I run it with sudo the "Software and Updates" window opens as normal.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: software-properties-gtk 0.98.7
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 22 21:30:12 2020
InstallationDate: Installed on 2019-12-15 (98 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to focal on 2020-03-22 (0 days ago)

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


** Tags: amd64 apport-bug focal

** Attachment added: "blank window after clicking "settings" in "Software 
Updater""
   
https://bugs.launchpad.net/bugs/1868501/+attachment/5340284/+files/Screenshot%20from%202020-03-22%2021-21-08.png

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

Title:
  software-properties-gtk is blank when run as normal user.

Status in software-properties package in Ubuntu:
  New

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

  Upgraded install from 19.10

  "Software & Updates" windows is blank when initiated from either the
  terminal or via the "Settings..." button in the "Software Updater".

  If I run "software-properties-gtk" in the terminal the window is also blank.
  If I run it with sudo the "Software and Updates" window opens as normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.7
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 22 21:30:12 2020
  InstallationDate: Installed on 2019-12-15 (98 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to focal on 2020-03-22 (0 days ago)

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

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


[Touch-packages] [Bug 1866217] Re: Mouse pointer vanished on Wayland (okay on X)

2020-03-22 Thread Andi Chandler
Updating ticket as requested by bot to assign to a package.

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

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

Title:
  Mouse pointer vanished on Wayland (okay on X)

Status in wayland package in Ubuntu:
  New

Bug description:
  Running 20.04 with all the repos enabled (including focal-proposed)

  A recent update (apt-get dist-upgrade) made the mouse point disappear.

  
  The mouse worked on a text console... and lsusb etc showed the presence of 
the mouse.
  In Wayland, pressing control key showed the pointer location.

  
  Resolution
  Edited /etc/gdm3/custom.conf and uncommented "WaylandEnable=false"
  Rebooted a mouse pointer is now back.

  Wayland device driver problem?

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

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


[Touch-packages] [Bug 1866217] [NEW] Mouse pointer vanished on Wayland (okay on X)

2020-03-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Running 20.04 with all the repos enabled (including focal-proposed)

A recent update (apt-get dist-upgrade) made the mouse point disappear.


The mouse worked on a text console... and lsusb etc showed the presence of the 
mouse.
In Wayland, pressing control key showed the pointer location.


Resolution
Edited /etc/gdm3/custom.conf and uncommented "WaylandEnable=false"
Rebooted a mouse pointer is now back.

Wayland device driver problem?

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


** Tags: bot-comment focal gdm ubuntu wayland
-- 
Mouse pointer vanished on Wayland (okay on X)
https://bugs.launchpad.net/bugs/1866217
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to wayland in Ubuntu.

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


[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-03-22 Thread rolfinator
I am on the HP 830 G6 and with 'options snd-hda-intel index=0 model
=laptop-dmic' I finally see the microphone appearing in pavucontrol.
However, I cannot get the microphone/input working.

Currently, I have the following lines added to make at least output
sound working and *see* the microphone in pavucontrol:

options snd-hda-intel dmic_detect=0
options snd-hda-intel index=0 model=laptop-dmic

My system is as follow:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename:   eoan

$ inxi -Fxz
Audio: Device-1: Intel Cannon Point-LP High Definition Audio vendor: 
Hewlett-Packard driver: snd_hda_intel v: kernel 
   bus ID: 00:1f.3 
   Sound Server: ALSA v: k5.3.0-42-generic 

$ uname -a
Linux hostname 5.3.0-42-generic #34-Ubuntu SMP Fri Feb 28 05:49:40 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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


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

2020-03-22 Thread Norbert
** Tags added: rpi

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

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

Status in Ubuntu MATE:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Error occured during UBUNTU Mate upgrade to 15.10 on Raspberry PI2 and
  once trying perform manual update getting:

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up initramfs-tools (0.120ubuntu6) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools (0.120ubuntu6) ...
  update-initramfs: Generating /boot/initrd.img-3.18.0-25-rpi2
  Unsupported platform.
  run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 
1
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: initramfs-tools 0.120ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-25.26-rpi2 3.18.17
  Uname: Linux 3.18.0-25-rpi2 armv7l
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: armhf
  Date: Sun Oct 25 08:19:08 2015
  DuplicateSignature: package:initramfs-tools:0.120ubuntu6:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.2ubuntu5
   apt  1.0.10.2ubuntu1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to wily on 2015-10-25 (0 days ago)

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

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


[Touch-packages] [Bug 1854588] Re: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox

2020-03-22 Thread Norbert
** Tags added: eoan focal

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

Title:
  Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened
  from Chrome/Firefox

Status in Ubuntu MATE:
  New
Status in gdebi package in Ubuntu:
  New

Bug description:
  Before anyone says this bug already exists... it doesn't (at least as
  far as I can see).  It's just that a lot of similar bugs do/did exist
  where people have also experienced the same symptoms (of gdebi-gtk
  vanishing upon clicking 'Install').

  So yes this is the same symptoms, but it must be a different cause as
  the circumstances are different and doesn't have the same resolution.

  The meat of it...

  Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or 
with Chrome if you installed that) go to any site that offers a .deb package 
and either...
  a) choose to open it directly from the browser (rather than saving it to 
'Downloads' folder)
  b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that 
file from within the browser itself.

  You should find that gdebi-gtk appears but vanishes the moment you
  click 'Install' without a prompt for a password, an explanation or the
  package actually getting installed.

  This bug has existed since the beginning of Ubuntu 18.04 however it's
  been largely confused with other similar bugs.  I've had it on half a
  dozen machines and confirmed it exists with IRC users on #ubuntu-mate
  of freenode.

  However with *this* bug (compared to others) gdebi-gtk works perfectly
  fine if you run it from the terminal or just double click the .deb
  package from your file manager.

  It's the kind of bug which if you're a hardened desktop Linux user,
  you'd just work around it...

  But if you're a novice and you can't get a simple thing like
  Teamviewer installed (which is a .deb, and a thing I might ask someone
  to do over the phone to try to help them) you likely get fed up and
  re-install Windows :S

  Any input on this would be brilliant as I can't seem to get any
  logs/output.

  ~lantizia

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

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


[Touch-packages] [Bug 1868474] [NEW] 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

2020-03-22 Thread D
Public bug reported:

The installation scripts loads the correct drivers so the touch pad and
pointer works during the install. However after the install neither
work.

I've worked around it by using a wireless USB from Vilros for mouse input while 
logging in. Then issuing (found on https://askubuntu.com/questions/1143663):
 sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

So it's a bug for me but one I can work around and should be fixed
before 20.04 goes live.

** Affects: init-system-helpers (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73

Status in init-system-helpers package in Ubuntu:
  New

Bug description:
  The installation scripts loads the correct drivers so the touch pad
  and pointer works during the install. However after the install
  neither work.

  I've worked around it by using a wireless USB from Vilros for mouse input 
while logging in. Then issuing (found on 
https://askubuntu.com/questions/1143663):
   sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol'

  So it's a bug for me but one I can work around and should be fixed
  before 20.04 goes live.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1868474/+subscriptions

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


[Touch-packages] [Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"

2020-03-22 Thread Norbert
** Tags added: eoan focal

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

Title:
  Battery indicator crashes when unchecking "Show Percentage in Menu
  Bar"

Status in Ubuntu MATE:
  New
Status in indicator-power package in Ubuntu:
  Confirmed
Status in mate-indicator-applet package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1. Click on the battery indicator.
  2. Click "Show Percentage on Menu Bar" to enable it.
  3. Do it again to disable it.
  4. Battery indicator disappears

  
  Output from dmesg:

  [  613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 
7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000]
  [  749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 
7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000]
  [  775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 
7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000]
  [  816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 
7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000]
  [  841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 
7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000]

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

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


[Touch-packages] [Bug 1868473] [NEW] 20.04 Install screen corrupt on Lenovo P73+NVIDEA RTX-5000

2020-03-22 Thread D
Public bug reported:

Hardware: Lenovo P73 with NVIDEA RTX-5000 QMax

20.04 Daily Build install.

On using the USB drive for a new install the screen is corrupt. This can be 
worked around by:
1. Waiting for Focal Fossa to give the sound showing the splash screen.
2. Closing the screen so it goes into sleep mode.
3. Open the screen and hit the power button to wake the system.
4. Wait a second or two and screen loads correctly and the rest of the install 
works beautifully.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: init 1.57
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 22 08:27:04 2020
InstallationDate: Installed on 2020-03-21 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: init-system-helpers
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: init-system-helpers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  20.04 Install screen corrupt on Lenovo P73+NVIDEA RTX-5000

Status in init-system-helpers package in Ubuntu:
  New

Bug description:
  Hardware: Lenovo P73 with NVIDEA RTX-5000 QMax

  20.04 Daily Build install.

  On using the USB drive for a new install the screen is corrupt. This can be 
worked around by:
  1. Waiting for Focal Fossa to give the sound showing the splash screen.
  2. Closing the screen so it goes into sleep mode.
  3. Open the screen and hit the power button to wake the system.
  4. Wait a second or two and screen loads correctly and the rest of the 
install works beautifully.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: init 1.57
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 22 08:27:04 2020
  InstallationDate: Installed on 2020-03-21 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: init-system-helpers
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1868473/+subscriptions

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


[Touch-packages] [Bug 1660121] Re: LightDM can't use the user background on Mate

2020-03-22 Thread Norbert
** 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/1660121

Title:
  LightDM can't use the user background on Mate

Status in Ubuntu MATE:
  New
Status in lightdm package in Ubuntu:
  New

Bug description:
  Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04
  alpha 2).

  On Mate, the LightDM Gtk Greeter can't use the user background. It
  works fine on other DEs like Xfce.

  From what I understand, LightDM and/or the Gkt greeter (not sure which
  one handles the background) gets the background path from Gsettings,
  so I assume it can't find the one from Mate, which stores it in
  "org.mate.background picture-filename".

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

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


[Touch-packages] [Bug 1868456] [NEW] "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container

2020-03-22 Thread Jeff Lane
Public bug reported:

I fired up a LXD container using ubuntu-daily:f on my machine and every
time I issue a comment inside the container using sudo, I get this
error:

sudo: setrlimit(RLIMIT_CORE): Operation not permitted

I did some digging online and found this was reported against Fedora last fall 
which lead me to this bugzilla report:
https://bugzilla.redhat.com/show_bug.cgi?id=1773148

which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.

Focal has 1.8.31:
bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo
sudo:
  Installed: 1.8.31-1ubuntu1
  Candidate: 1.8.31-1ubuntu1
  Version table:
 *** 1.8.31-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

This is not an issue on Bionic:
bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy 
sudo
sudo:
  Installed: 1.8.21p2-3ubuntu1.2
  Candidate: 1.8.21p2-3ubuntu1.2
  Version table:
 *** 1.8.21p2-3ubuntu1.2 500
500 http://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
 1.8.21p2-3ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

>From the redhat bug, the described workaround does clear these messages
up:

# set disable_coredump false

Once I've done that, the error messages go away.

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

** Description changed:

  I fired up a LXD container using ubuntu-daily:f on my machine and every
  time I issue a comment inside the container using sudo, I get this
  error:
  
  sudo: setrlimit(RLIMIT_CORE): Operation not permitted
  
- I did some digging online and found this was reported against Fedora last 
fall:
+ I did some digging online and found this was reported against Fedora last 
fall which lead me to this bugzilla report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1773148
  
  which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.
  
  Focal has 1.8.31:
  bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy 
sudo
  sudo:
-   Installed: 1.8.31-1ubuntu1
-   Candidate: 1.8.31-1ubuntu1
-   Version table:
-  *** 1.8.31-1ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1.8.31-1ubuntu1
+   Candidate: 1.8.31-1ubuntu1
+   Version table:
+  *** 1.8.31-1ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  This is not an issue on Bionic:
  bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy 
sudo
  sudo:
-   Installed: 1.8.21p2-3ubuntu1.2
-   Candidate: 1.8.21p2-3ubuntu1.2
-   Version table:
-  *** 1.8.21p2-3ubuntu1.2 500
- 500 http://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
-  1.8.21p2-3ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+   Installed: 1.8.21p2-3ubuntu1.2
+   Candidate: 1.8.21p2-3ubuntu1.2
+   Version table:
+  *** 1.8.21p2-3ubuntu1.2 500
+ 500 http://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
+  1.8.21p2-3ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
  From the redhat bug, the described workaround does clear these messages
  up:
  
  # set disable_coredump false
  
  Once I've done that, the error messages go away.

** Package changed: lxd (Ubuntu) => sudo (Ubuntu)

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

Title:
  "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when
  using sudo in 20.04 LXD container

Status in sudo package in Ubuntu:
  New

Bug description:
  I fired up a LXD container using ubuntu-daily:f on my machine and
  every time I issue a comment inside the container using sudo, I get
  this error:

  sudo: setrlimit(RLIMIT_CORE): Operation not permitted

  I did some digging online and found this was reported against Fedora last 
fall which lead me to this bugzilla report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1773148

  which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.

  Focal has 1.8.31:
  bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy 
sudo
  sudo:
    Installed: 1.8.31-1ubuntu1
    Candidate: 1.8.31-1ubuntu1
    Version table:
   *** 1.8.31-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 

[Touch-packages] [Bug 1868456] [NEW] "sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo in 20.04 LXD container

2020-03-22 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I fired up a LXD container using ubuntu-daily:f on my machine and every
time I issue a comment inside the container using sudo, I get this
error:

sudo: setrlimit(RLIMIT_CORE): Operation not permitted

I did some digging online and found this was reported against Fedora last fall 
which lead me to this bugzilla report:
https://bugzilla.redhat.com/show_bug.cgi?id=1773148

which seems to tie this to a change in sudo between 1.8.28 and 1.8.29.

Focal has 1.8.31:
bladernr@focal-builder:~/development/kernels-ubuntu/focal$ apt-cache policy sudo
sudo:
  Installed: 1.8.31-1ubuntu1
  Candidate: 1.8.31-1ubuntu1
  Version table:
 *** 1.8.31-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

This is not an issue on Bionic:
bladernr@galactica:~/development/kernels-upstream/mainline$ apt-cache policy 
sudo
sudo:
  Installed: 1.8.21p2-3ubuntu1.2
  Candidate: 1.8.21p2-3ubuntu1.2
  Version table:
 *** 1.8.21p2-3ubuntu1.2 500
500 http://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
 1.8.21p2-3ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

>From the redhat bug, the described workaround does clear these messages
up:

# set disable_coredump false

Once I've done that, the error messages go away.

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

-- 
"sudo: setrlimit(RLIMIT_CORE): Operation not permitted" error when using sudo 
in 20.04 LXD container
https://bugs.launchpad.net/bugs/1868456
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to sudo in Ubuntu.

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


[Touch-packages] [Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background

2020-03-22 Thread Norbert
** Also affects: base-files (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-mate

** Tags added: eoan focal

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

Title:
  motd-news transmitting private hardware data without consent or
  knowledge in background

Status in base-files package in Ubuntu:
  New

Bug description:
  In package base-files there is a script /etc/update-motd.d/50-motd-
  news that harvests private hardware data from the machine and
  transmits it in the background every day.  There is no notice, no
  consent, no nothing.  This should be by default disabled until there
  is informed consent.

  This solution is simple:

  1. Change ENABLED=1 to ENABLED=0 in the file /etc/default/motd-news and 
  2. Place a comment in the file disclosing the fact that the 50-motd-news 
script will harvest private hardware data and upload it to motd.ubuntu.com 
daily if the end-user enables it.

  Creating databases that maps ip address to specify hardware is a
  threat to both privacy and security.  If an adversary knows the
  specific hardware and the ip address for that hardware their ability
  to successfully attack it is greatly increased.

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

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


[Touch-packages] [Bug 269441] Re: Trash always full

2020-03-22 Thread Norbert
** Tags added: bionic eoan focal xenial

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

Title:
  Trash always full

Status in Ubuntu MATE:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  I've seen other users having problems with that the trash appears
  empty even though it isn't. I have the opposite problem: my trash icon
  on the desktop always appears full, even if empty.

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

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


[Touch-packages] [Bug 1766108] Re: Battery indicator crashes when unchecking "Show Percentage in Menu Bar"

2020-03-22 Thread Norbert
** Tags added: bionic

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

Title:
  Battery indicator crashes when unchecking "Show Percentage in Menu
  Bar"

Status in Ubuntu MATE:
  New
Status in indicator-power package in Ubuntu:
  Confirmed
Status in mate-indicator-applet package in Ubuntu:
  Confirmed
Status in mate-panel package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:

  1. Click on the battery indicator.
  2. Click "Show Percentage on Menu Bar" to enable it.
  3. Do it again to disable it.
  4. Battery indicator disappears

  
  Output from dmesg:

  [  613.877855] mate-panel[1604]: segfault at 1c ip 7f51b23daa20 sp 
7ffe8df7f5d8 error 4 in libcairo.so.2.11510.0[7f51b236c000+118000]
  [  749.662960] mate-panel[2930]: segfault at 38 ip 7fc98aa82300 sp 
7fffa5290f68 error 4 in libgdk-3.so.0.2200.30[7fc98aa3b000+eb000]
  [  775.815530] mate-panel[3127]: segfault at 1c ip 7fc317b61a20 sp 
7ffea6e1f028 error 4 in libcairo.so.2.11510.0[7fc317af3000+118000]
  [  816.504199] mate-panel[3225]: segfault at 38 ip 7fa314f0e300 sp 
7fffa993f928 error 4 in libgdk-3.so.0.2200.30[7fa314ec7000+eb000]
  [  841.353444] mate-panel[3363]: segfault at 38 ip 7fbc86c4a300 sp 
7ffd6b3a5d58 error 4 in libgdk-3.so.0.2200.30[7fbc86c03000+eb000]

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

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


[Touch-packages] [Bug 1854588] Re: Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened from Chrome/Firefox

2020-03-22 Thread Norbert
** Tags added: bionic

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

Title:
  Clicking 'Install' on gdebi-gtk makes it vanish ONLY when .deb opened
  from Chrome/Firefox

Status in Ubuntu MATE:
  New
Status in gdebi package in Ubuntu:
  New

Bug description:
  Before anyone says this bug already exists... it doesn't (at least as
  far as I can see).  It's just that a lot of similar bugs do/did exist
  where people have also experienced the same symptoms (of gdebi-gtk
  vanishing upon clicking 'Install').

  So yes this is the same symptoms, but it must be a different cause as
  the circumstances are different and doesn't have the same resolution.

  The meat of it...

  Basically on a fresh install of Ubuntu MATE 18.04.3 amd64... with Firefox (or 
with Chrome if you installed that) go to any site that offers a .deb package 
and either...
  a) choose to open it directly from the browser (rather than saving it to 
'Downloads' folder)
  b) or... save the file (e.g. to the 'Downloads' folder), BUT!.. open that 
file from within the browser itself.

  You should find that gdebi-gtk appears but vanishes the moment you
  click 'Install' without a prompt for a password, an explanation or the
  package actually getting installed.

  This bug has existed since the beginning of Ubuntu 18.04 however it's
  been largely confused with other similar bugs.  I've had it on half a
  dozen machines and confirmed it exists with IRC users on #ubuntu-mate
  of freenode.

  However with *this* bug (compared to others) gdebi-gtk works perfectly
  fine if you run it from the terminal or just double click the .deb
  package from your file manager.

  It's the kind of bug which if you're a hardened desktop Linux user,
  you'd just work around it...

  But if you're a novice and you can't get a simple thing like
  Teamviewer installed (which is a .deb, and a thing I might ask someone
  to do over the phone to try to help them) you likely get fed up and
  re-install Windows :S

  Any input on this would be brilliant as I can't seem to get any
  logs/output.

  ~lantizia

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

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


[Touch-packages] [Bug 1706770] Re: Lock screen can be bypassed when auto-login is enabled.

2020-03-22 Thread Norbert
** 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/1706770

Title:
  Lock screen can be bypassed when auto-login is enabled.

Status in Ubuntu MATE:
  Confirmed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in mate-session-manager package in Ubuntu:
  Confirmed

Bug description:
  16.04 LTS
  =

  Hi,

  My machine is set up with full-disk encryption, so it requires a
  password when I boot it up. Because of this I thought I would enable
  auto-login to avoid having to enter two passwords at boot.

  When I leave my computer for short periods of time, I lock it. I
  thought this was working fine for a long time, but I've discovered the
  lock screen is actually easily bypassable when auto-login is enabled.
  All one has to do is click "Switch User" on the lock screen, then
  press "Unlock" and the computer unlocks without prompting for a
  password.

  Perhaps this is just me being an idiot, but I thought this was secure
  until now. It seems like either unlocking should always require a
  password (otherwise what's the point of locking in the first place) or
  it should be made totally obvious that unlocking doesn't actually
  require a password (i.e. removing the password box from the lock
  screen when auto-login is enabled).

  Thanks,
  Chris

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

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


[Touch-packages] [Bug 1827958] Re: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system

2020-03-22 Thread dharman
@solotareff, I've an Acer Swift SF514-52TP and you solution worked for
me too!

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

Title:
  [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone -
  since installation of system

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The inbuilt microphone has never worked on the version of ubuntu on
  this computer. The hardware works completely fine on other operating
  systems (Windows).

  
  Distribution:   Ubuntu 18.04.2 LTS

  alsa-base:  Installed: 1.0.25+dfsg-0ubuntu5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.19.21-041921-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lune   1908 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  6 23:54:58 2019
  InstallationDate: Installed on 2019-01-06 (120 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 1 0 3 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1273 F pulseaudio
lune   1908 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.name: Carlsberg_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF514-53T
  dmi.product.sku: 
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 1827958] Re: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system

2020-03-22 Thread 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/1827958

Title:
  [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone -
  since installation of system

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The inbuilt microphone has never worked on the version of ubuntu on
  this computer. The hardware works completely fine on other operating
  systems (Windows).

  
  Distribution:   Ubuntu 18.04.2 LTS

  alsa-base:  Installed: 1.0.25+dfsg-0ubuntu5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.19.21-041921-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lune   1908 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  6 23:54:58 2019
  InstallationDate: Installed on 2019-01-06 (120 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 1 0 3 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1273 F pulseaudio
lune   1908 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.name: Carlsberg_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF514-53T
  dmi.product.sku: 
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 1827958] Re: [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone - since installation of system

2020-03-22 Thread solotareff
I have seek very long to find the solution on Switf5 Acer. the solution is :
sudo gedit /etc/default/grub

then change :
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" par GRUB_CMDLINE_LINUX_DEFAULT="quiet 
splash snd_hda_intel.dmic_detect=0"  and save

then

sudo update-grub

then restart your computer

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

Title:
  [Acer Swift 5 SF514-53T] No sound at all from the inbuilt microphone -
  since installation of system

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  The inbuilt microphone has never worked on the version of ubuntu on
  this computer. The hardware works completely fine on other operating
  systems (Windows).

  
  Distribution:   Ubuntu 18.04.2 LTS

  alsa-base:  Installed: 1.0.25+dfsg-0ubuntu5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.19.21-041921-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lune   1908 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  6 23:54:58 2019
  InstallationDate: Installed on 2019-01-06 (120 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 1 0 3 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1273 F pulseaudio
lune   1908 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.03
  dmi.board.name: Carlsberg_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.03
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd12/17/2018:svnAcer:pnSwiftSF514-53T:pvrV1.03:rvnWL:rnCarlsberg_WL:rvrV1.03:cvnAcer:ct10:cvrV1.03:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF514-53T
  dmi.product.sku: 
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

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

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


[Touch-packages] [Bug 1868409] Re: gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by snap-

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  gnome-{calculator,logs,characters} snaps not removed after the
  equivalent APT packages are installed on 20.04, and gnome-software APT
  package not replaced by snap-store

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  I'm trialing the development release of Ubuntu 20.04, installed in
  December and kept up-to-date by regularly running apt full-upgrade.

  I understand from [1] that 20.04 will ship
  gnome-{calculator,logs,characters} as APT packages rather than snap
  apps, and gnome-software as a snap app (called snap-store) rather than
  an APT package.

  Following an apt full-upgrade in late February, I now have:

  * both the snap and the APT versions of gnome-{calculator,logs,characters}
  * still only the APT version of gnome-software, no snap-store

  Is this normal? A user in the #ubuntu+1 IRC channel reports that a
  fresh install of the development release:

  * only features the APT versions of gnome-{calculator,logs,characters}
  * features the snap-store (but also the APT version of gnome-software)

  Are users of older installs of the development release supposed to
  manually uninstall the snap versions of
  gnome-{calculator,logs,characters} and manually install the snap-
  store?

  [1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
  remove-for-snap-snap-store/14542

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

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


[Touch-packages] [Bug 1766503] Re: ibus-* randomly use high CPU

2020-03-22 Thread Charles Lohr
New note.  As commented here:
https://github.com/linuxmint/xed/issues/237 you can make it happen by
pressing control key is pressed in rapid succession.

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

Title:
  ibus-* randomly use high CPU

Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+subscriptions

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


[Touch-packages] [Bug 1766503] Re: ibus-* randomly use high CPU

2020-03-22 Thread Charles Lohr
I have observed this is happening Mint Mate 19.3 but also only when
using Xed.  I have been unable to track down this problem any further.

** Bug watch added: github.com/linuxmint/xed/issues #237
   https://github.com/linuxmint/xed/issues/237

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

Title:
  ibus-* randomly use high CPU

Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+subscriptions

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


[Touch-packages] [Bug 1823721] Re: systemctl fstrim.timer freeze computer with a SSD on a dual boot system Windows 10/Ubuntu 18.04

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

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

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

Title:
  systemctl fstrim.timer freeze computer with a SSD  on a dual boot
  system Windows 10/Ubuntu 18.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The default systemctl fstrim.timer on Ubuntu 18.04 entirely freeze the
  computer once a week (usually on Monday midnight) in the case of a
  dual boot system installed on a SSD (Windows/Ubuntu) due to high IO
  overhead. I also had several freeze at boot due to the same problem.

  When the freeze occur I can open a tty terminal and type the command
  iotop to see the process which use that amount of IO. It was mount
  .ntfs-3g which point to my mount point to my Windows 10 install on my
  SSD.

  When the freeze occur the system is not responsive for about 10-15
  minutes.

  I solved my issue by disabling the fstrim.timer entirely with this
  command:

  sudo systemctl disable fstrim.timer

  I can reproduce the problem on my installation by launching the
  fstrim-timer:

  sudo systemctl start fstrim.timer

  Imediately after launching fstrim.timer, iotop display this line at
  top, with my Windows 10 mount point:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
    893 be/4 root0.00 B/s0.00 B/s  0.00 % 99.10 % mount.ntfs-3g 
/dev/sda1 /media/systeme_windows -o 
rw,noatime,noexec,nosuid,nodev,gid=100,uid=1000,nls=utf8,windows_names,umask=002,user

  And a few minutes later:

    TID  PRIO  USER DISK READ  DISK WRITE  SWAPIN IO>COMMAND
  20077 be/4 root0.00 B/s0.00 B/s  0.00 % 99.45 % fstrim -av

  
  Systemd 237-3ubuntu10.19
  Ubuntu 18.04.2
  Linux 4.18.0-17-generic

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

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