from:"Pierre"

@lotuspsychje: I have the same problems as the ones you mention in
lp:1949183.

** Description changed:

  There is a problem with Cheese on 22.04 beta (image shows up scrambled
- even though it works as expected when I visit www.webcamtests.com).
+ even though it works as expected when I visit www.webcamtests.com)[1].
  
  I tried to report the problem using `ubuntu-bug cheese`.
  
  I am asked if the problem is with Cheese, or with the image shown in
  Cheese. I select the latter option, then after around 20 seconds, the
  error
  
  -
  Setting pipeline to PAUSED ...
  Failed to set pipeline to PAUSED.
  Setting pipeline to NULL ...
  ERROR: from element 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
 Internal data stream error.
  Additional debug info:
  ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
  streaming stopped, reason not-negotiated (-4)
  ERROR: pipeline doesn't want to preroll.
  Freeing pipeline ...
  
  (cheese:25538): cheese-WARNING **: 16:22:49.180: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)
  -
  
  shows up in the terminal where I had launched `ubuntu-bug apport`.
  
  Finally, Cheese is launched with a black screen instead of the webcam
  picture and the text "There was an error playing the video from the
  webcam".
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportLog:
-  
+ 
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:124:24532:2022-04-13 10:33:31.216692388 +0800:2022-04-13 
10:33:31.216692388 
+0800:/var/crash/_usr_bin_checkbox-support-eddystone_scanner.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 16:24:43 2022
  InstallationDate: Installed on 2022-04-01 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
+ 
+ 
+ [1] https://gitlab.gnome.org/GNOME/cheese/-/issues/139

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

Title:
  apport fails when trying to report a problem about Cheese

Status in apport package in Ubuntu:
  New

Bug description:
  There is a problem with Cheese on 22.04 beta (image shows up scrambled
  even though it works as expected when I visit www.webcamtests.com)[1].

  I tried to report the problem using `ubuntu-bug cheese`.

  I am asked if the problem is with Cheese, or with the image shown in
  Cheese. I select the latter option, then after around 20 seconds, the
  error

  -
  Setting pipeline to PAUSED ...
  Failed to set pipeline to PAUSED.
  Setting pipeline to NULL ...
  ERROR: from element 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
 Internal data stream error.
  Additional debug info:
  ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
  streaming stopped, reason not-negotiated (-4)
  ERROR: pipeline doesn't want to preroll.
  Freeing pipeline ...

  (cheese:25538): cheese-WARNING **: 16:22:49.180: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)
  -

  shows up in the terminal where I had launched `ubuntu-bug apport`.

  Finally, Cheese is launched with a black screen instead of the webcam
  picture and the text "There was an error playing the video from the
  webcam".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:124:24532:2022-04-13 10:33:31.216692388 +0800:2022-04-13 
10:33:31.216692388 
+0800:/var/crash/_usr_bin_checkbox-support-eddystone_scanner.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 16:24:43 2022
  InstallationDate: Installed on 2022-04-01 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present

[Touch-packages] [Bug 1968855] Re: apport fails when trying to report a problem about Cheese

Cheese issue filed in upstream project:

https://gitlab.gnome.org/GNOME/cheese/-/issues/139

** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #139
   https://gitlab.gnome.org/GNOME/cheese/-/issues/139

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

Title:
  apport fails when trying to report a problem about Cheese

Status in apport package in Ubuntu:
  New

Bug description:
  There is a problem with Cheese on 22.04 beta (image shows up scrambled
  even though it works as expected when I visit www.webcamtests.com)[1].

  I tried to report the problem using `ubuntu-bug cheese`.

  I am asked if the problem is with Cheese, or with the image shown in
  Cheese. I select the latter option, then after around 20 seconds, the
  error

  -
  Setting pipeline to PAUSED ...
  Failed to set pipeline to PAUSED.
  Setting pipeline to NULL ...
  ERROR: from element 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
 Internal data stream error.
  Additional debug info:
  ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
  streaming stopped, reason not-negotiated (-4)
  ERROR: pipeline doesn't want to preroll.
  Freeing pipeline ...

  (cheese:25538): cheese-WARNING **: 16:22:49.180: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)
  -

  shows up in the terminal where I had launched `ubuntu-bug apport`.

  Finally, Cheese is launched with a black screen instead of the webcam
  picture and the text "There was an error playing the video from the
  webcam".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:124:24532:2022-04-13 10:33:31.216692388 +0800:2022-04-13 
10:33:31.216692388 
+0800:/var/crash/_usr_bin_checkbox-support-eddystone_scanner.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 16:24:43 2022
  InstallationDate: Installed on 2022-04-01 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

  
  [1] https://gitlab.gnome.org/GNOME/cheese/-/issues/139

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


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

[Touch-packages] [Bug 1968855] Re: apport fails when trying to report a problem about Cheese

** Attachment added: "Screenshot from 2022-04-13 16-31-40.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1968855/+attachment/5580362/+files/Screenshot%20from%202022-04-13%2016-31-40.png

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

Title:
  apport fails when trying to report a problem about Cheese

Status in apport package in Ubuntu:
  New

Bug description:
  There is a problem with Cheese on 22.04 beta (image shows up scrambled
  even though it works as expected when I visit www.webcamtests.com).

  I tried to report the problem using `ubuntu-bug cheese`.

  I am asked if the problem is with Cheese, or with the image shown in
  Cheese. I select the latter option, then after around 20 seconds, the
  error

  -
  Setting pipeline to PAUSED ...
  Failed to set pipeline to PAUSED.
  Setting pipeline to NULL ...
  ERROR: from element 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
 Internal data stream error.
  Additional debug info:
  ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
  streaming stopped, reason not-negotiated (-4)
  ERROR: pipeline doesn't want to preroll.
  Freeing pipeline ...

  (cheese:25538): cheese-WARNING **: 16:22:49.180: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)
  -

  shows up in the terminal where I had launched `ubuntu-bug apport`.

  Finally, Cheese is launched with a black screen instead of the webcam
  picture and the text "There was an error playing the video from the
  webcam".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:124:24532:2022-04-13 10:33:31.216692388 +0800:2022-04-13 
10:33:31.216692388 
+0800:/var/crash/_usr_bin_checkbox-support-eddystone_scanner.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 16:24:43 2022
  InstallationDate: Installed on 2022-04-01 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1968855] [NEW] apport fails when trying to report a problem about Cheese

Public bug reported:

There is a problem with Cheese on 22.04 beta (image shows up scrambled
even though it works as expected when I visit www.webcamtests.com).

I tried to report the problem using `ubuntu-bug cheese`.

I am asked if the problem is with Cheese, or with the image shown in
Cheese. I select the latter option, then after around 20 seconds, the
error

-
Setting pipeline to PAUSED ...
Failed to set pipeline to PAUSED.
Setting pipeline to NULL ...
ERROR: from element 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
 Internal data stream error.
Additional debug info:
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
streaming stopped, reason not-negotiated (-4)
ERROR: pipeline doesn't want to preroll.
Freeing pipeline ...

(cheese:25538): cheese-WARNING **: 16:22:49.180: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
streaming stopped, reason not-negotiated (-4)
-

shows up in the terminal where I had launched `ubuntu-bug apport`.

Finally, Cheese is launched with a black screen instead of the webcam
picture and the text "There was an error playing the video from the
webcam".

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu80
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: pass
CrashReports: 640:0:124:24532:2022-04-13 10:33:31.216692388 +0800:2022-04-13 
10:33:31.216692388 
+0800:/var/crash/_usr_bin_checkbox-support-eddystone_scanner.0.crash
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 13 16:24:43 2022
InstallationDate: Installed on 2022-04-01 (12 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  apport fails when trying to report a problem about Cheese

Status in apport package in Ubuntu:
  New

Bug description:
  There is a problem with Cheese on 22.04 beta (image shows up scrambled
  even though it works as expected when I visit www.webcamtests.com).

  I tried to report the problem using `ubuntu-bug cheese`.

  I am asked if the problem is with Cheese, or with the image shown in
  Cheese. I select the latter option, then after around 20 seconds, the
  error

  -
  Setting pipeline to PAUSED ...
  Failed to set pipeline to PAUSED.
  Setting pipeline to NULL ...
  ERROR: from element 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
 Internal data stream error.
  Additional debug info:
  ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstPipeline:pipeline0/GstAutoVideoSrc:autovideosrc0/GstPipeWireSrc:autovideosrc0-actual-src-pipewir:
  streaming stopped, reason not-negotiated (-4)
  ERROR: pipeline doesn't want to preroll.
  Freeing pipeline ...

  (cheese:25538): cheese-WARNING **: 16:22:49.180: Internal data stream error.: 
../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): 
/GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1:
  streaming stopped, reason not-negotiated (-4)
  -

  shows up in the terminal where I had launched `ubuntu-bug apport`.

  Finally, Cheese is launched with a black screen instead of the webcam
  picture and the text "There was an error playing the video from the
  webcam".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:0:124:24532:2022-04-13 10:33:31.216692388 +0800:2022-04-13 
10:33:31.216692388 
+0800:/var/crash/_usr_bin_checkbox-support-eddystone_scanner.0.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 13 16:24:43 2022
  InstallationDate: Installed on 2022-04-01 (12 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list:

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-11-24 Thread paquin pierre

I can confirm crash on latest 20.04 is still there.

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-11-24 Thread paquin pierre

Hello,

Thanks for your answers. I did a full update/upgrade and install latest
displaylink driver. I'll let you know if crash still here.

"X server crash in iris driver" subject is still open, no news since 8
months. Any way to know if it's still in progress or if it's on pause? I
just try to know if this problem will be still there in next Ubuntu LTS
release.

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-11-22 Thread paquin pierre

Hello,

You spoke about a fixed in your comment on 2021-06-22
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1871959/comments/30
. Is that to say that no fix will be part of Ubuntu next LTS version
22.04?

I see your link on mesa. No reponse since 8 months. In your comment on
2021-03-05 you sid "The fix isn't in the 21.0 branch yet. Only on master
(22)." => is that to say that Ubuntu 22.04 will have the fix ?

Thanks

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-11-22 Thread paquin pierre

Hello Daniel,

So far I still have the issue on Ubuntu 20.04 LTS. Can you tell me if
the patch will be in next 22.04 LTS ? Or maybe there's a way to patch
20.04?

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1609750]

2021-09-27 Thread pierre-louis.bossart

if patching the PulseAudio default.pa works, then the initial issue was
probably a problem with alsa-ucm-conf not being updated in your distros.
There's no reason to use asound.state these days, it's a much better
idea to use UCM. my 2 cents.

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:12:03 2016
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux-image-4.4.0-33-generic 4.4.0-33.52
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: Linux 4.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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


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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-06-23 Thread paquin pierre

Well, maybe or not but I don't understand how to install the patch

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-06-15 Thread paquin pierre

Hello,

Any news on when it will be solved ? No update solved it on my ubuntu
with officials updates.

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1816674] Re: Update-mime-database is getting very slow during apps installation

2021-04-12 Thread Pierre-Antoine Champin

@Sebastien Sorry for the late reply.

I recall that the workaround consisted in adding a random delay to the
apt-daily task, so that it would not happen *right* at startup.

How exactly this was done, unfortunately, I did write it down :-/ but I
think it was adding or creating the file ./system/apt-daily.timer,
ensuring that it contained the RandomizedDelaySec directive.

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

Title:
  Update-mime-database is getting very slow during apps installation

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  The installation of some apps has become very slow due to the update-
  mime-database command that takes up a lot of time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: shared-mime-info 1.10-1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 19 22:37:53 2019
  InstallationDate: Installed on 2019-01-16 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: shared-mime-info
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+subscriptions

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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-03-03 Thread paquin pierre

Hi,

Last message seems to indicate that a fix is found, good news! Anything
to do to get the fix?

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Committed
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-02-21 Thread paquin pierre

Hello,

I sent a mail to DisplayLink, here is their answer...
"
Thank you for bringing it to our attention but based on the log files and 
errors over there the best way would be to discuss it with Xorg engineers as 
the majority of problems comes from the OS itself and not from our driver here.
"

Do you have any news about the bug?

Thanks

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-02-11 Thread paquin pierre

Hi, thanks,

can't I just do a sudo apt purge linux-generic-hwe-20.04 ?

For now, i'll keep the choice to boot on kernel 5.8 or 5.4. About the
subject you opened on
https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 it seems to have
some news. That's very technical, can you put here informations when you
have a piece of solution ?

Many thanks

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-02-11 Thread paquin pierre

Hello,

This is why you have no report from kernel 5.8+ : 
"The supported kernel version range is from 4.15 to 5.5, minimum supported Xorg 
version is 1.16 and minimum supported Mutter (Wayland) is 3.32."

https://support.displaylink.com/knowledgebase/articles/684649

Some people seems to have kernel 5.9 working, but I tried without success, 
still have the above message. Here's an entry on DisplayLink forum with the 
same problem : 
https://displaylink.org/forum/showthread.php?t=67561

I can't create an account on this forum, don't know why... The mail with
code never arrive. If anyone has my problem, he can reply on displaylink
forum to get help with kernel 5.8+

Here's a tuto for kernel 5.9, don't work for me, but seemed to help sometimes : 
https://displaylink.org/forum/showpost.php?p=90853=2

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-02-11 Thread paquin pierre

Hello,

Well I tried... and have some troubles :). After reboot, displaylink didn't 
work anymore. I tried to uninstall but when  I try to reinstall, here what I 
get : 
ERROR (dkms apport): binary package for evdi: 1.7.0 not found
Error! Bad return status for module build on kernel: 5.8.0-43-generic (x86_64)
Consult /var/lib/dkms/evdi/1.7.0/build/make.log for more information.
ERROR: Failed to install evdi/5.3.1.34 to the kernel tree.

I know this is ubuntu, not displaylink, but if you have any idea that
would be great.

Notice : If i run install twice, I got only 1 error : "Error! DKMS tree
already contains: evdi-1.7.0" and installation continue. But don't
work... Uninstall / reinstall will do same thing (1st fatal error that
stop installer, then this one)

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

--

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush.cold() from iris_fence_flush() from st_glFlush()

Hi,

I created an account on mesa forum. I don't really know what to tell,
and which file send them. Can you help me and tell me what to say and
send?

Thanks,

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush.cold() from
  iris_fence_flush() from st_glFlush()

Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

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

Hi,

Ok thanks. In bug 1871959 you ask to report to mesa, what's "mesa"? I
don't think I have installed myself this. If it cause the bug, is it
possible to remove it?

Thanks,

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

Title:
  [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so
  when using DisplayLink

Status in evdi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

Well if I couldn't use ubuntu bug, I could use that, hope it'll help : 
apport-cli -c /var/crash/_usr_lib_xorg_Xorg.1000.crash

It then create this bug entry : 
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1915375

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

Title:
  [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so
  when using DisplayLink

Status in evdi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

Oh I forgot, Yes, i have installed dbgsym :

$ dpkg -l| grep dbgsym
ii libgl1-mesa-dri-dbgsym:amd64 20.2.6-0ubuntu0.20.04.1 amd64 debug symbols for 
libgl1-mesa-dri
ii xserver-xorg-core-dbgsym 2:1.20.9-2ubuntu1.2~20.04.1 amd64 debug symbols for 
xserver-xorg-core

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

Title:
  [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so
  when using DisplayLink

Status in evdi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

Hi,

Ok, if there's nothing here about xorg crash, how may I provide you more 
information about that : 
ppaquin@PORTABLE-PPAQUIN:/var/crash$ ls -alrt
.
-rw-r-  1 username  whoopsie  17322105 févr. 10 14:15 
_usr_lib_xorg_Xorg.1000.crash


It seems I have some informations on my system about crash. but the following 
command doesn't work. I have a message with some "internal error" : 
sudo ubuntu-bug _usr_lib_xorg_Xorg.1000.crash

Thanks,

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

Title:
  [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so
  when using DisplayLink

Status in evdi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1907142] Re: [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so when using DisplayLink

Hi, one more crash for me, you'll find iris_dri error at 14:15:47 time

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1907142/+attachment/5462347/+files/prevboot.txt

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

Title:
  [DisplayLink] [evdi] [i915] Xorg crashes with abort in iris_dri.so
  when using DisplayLink

Status in evdi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade from 18.04 to 20.04 I experience rather frequent
  crashes of the X server. Nothing specific of applications running,
  presumably at videos (VLC, Youtube in a browser tab ...).

  If not yet attached, I'll attach the *.old log with the most recent
  trace.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Mon Dec  7 22:15:34 2020
  DistUpgraded: 2020-11-30 17:56:17,036 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5300 [17aa:222b]
  InstallationDate: Installed on 2019-02-16 (660 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-11-30 (7 days ago)
  dmi.bios.date: 03/24/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETB2W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETB2W(2.12):bd03/24/2020:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.sku: LENOVO_MT_20CH_BU_Think_FM_ThinkPad Helix 2nd
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1816674] Re: Update-mime-database is getting very slow during apps installation

2021-02-10 Thread Pierre-Antoine Champin

Same problem with 20.04.

I believe this is related to this issue:
https://bbs.archlinux.org/viewtopic.php?id=255817 .

FTR, as `apt-daily.service` is running on startup, this was also
increasing my boot-time significantly (although I found a workaround for
this particular problem). Just to emphasize that this is a serious bug.

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

Title:
  Update-mime-database is getting very slow during apps installation

Status in shared-mime-info package in Ubuntu:
  Confirmed

Bug description:
  The installation of some apps has become very slow due to the update-
  mime-database command that takes up a lot of time.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: shared-mime-info 1.10-1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 19 22:37:53 2019
  InstallationDate: Installed on 2019-01-16 (34 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: shared-mime-info
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+subscriptions

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

[Touch-packages] [Bug 1915125] [NEW] xorg crash

2021-02-09 Thread paquin pierre

Public bug reported:

follow up for https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/1914573

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Feb  9 08:49:45 2021
DistUpgraded: 2020-07-01 20:04:15,616 DEBUG icon theme changed, re-reading
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509]
InstallationDate: Installed on 2017-11-08 (1188 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Notebook W65_W67RZ1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=1dd47b4a-9e41-4e2b-b247-2a3123742422 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-07-01 (222 days ago)
dmi.bios.date: 09/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.03
dmi.board.asset.tag: Tag 12345
dmi.board.name: W65_W67RZ1
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd09/19/2016:svnNotebook:pnW65_W67RZ1:pvrNotApplicable:rvnNotebook:rnW65_W67RZ1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: W65_W67RZ1
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Thu Feb  4 18:39:51 2021
xserver.configfile: default
xserver.errors:
 modeset(G0): glamor initialization failed
 modeset(G1): glamor initialization failed
 modeset(G2): glamor initialization failed
 modeset(G3): glamor initialization failed
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.9-2ubuntu1.2~20.04.1
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  follow up for https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1914573

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Feb  9 08:49:45 2021
  DistUpgraded: 2020-07-01 20:04:15,616 DEBUG icon theme changed, re-reading
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6509]
  InstallationDate: Installed on 2017-11-08 (1188 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Notebook W65_W67RZ1
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=1dd47b4a-9e41-4e2b-b247-2a3123742422 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to focal on 2020-07-01 (222 days ago)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_W67RZ1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A

[Touch-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive

2021-01-12 Thread Pierre Wilch

I had the same problem.
- Since this bug only appeared by me by consulting the proprieties of the file 
with Nautilus, and did not occur with linux mint 20 and Nemo, I reported it as 
bug 1890958 in Nautilus.
- Since updates beginning of the year 2021 I can no longer reproduce it. It 
seems to be solved.
- Ubuntu team, can you confirm it here (or not?), so people who spent time to 
report this to help you could sleep on their two ears and use ubuntu 20.04 
again, with no fear of such dangerous bugs?

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

Title:
  date modified is wrong for files on an exfat formatted drive

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  When using exfat formatted drives (e.g. my camera card) with focal
  fossa any access causes the date modified to be set, even when it
  would not normally be set, and it is set a month into the future.

  Installing exfat-fuse and exfat-utils results in the correct
  behaviour.

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

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

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

[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2020-06-02 Thread Pierre Equoy

Hi Salima,

this bug has been identified as happening only for people who were
upgrading from a previous version of Ubuntu (that came with a previous
version of Pulseaudio). Daniel Van Vugt found a workaround (check
comments 18 and 19 above), and a fix has been made by the Pulseaudio
developers and is being reviewed (see comment 41 above).

In your case, it seems the issue happens on a fresh install, so I
believe this issue is different. Please file a new bug for this.

Thanks!

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

Title:
External audio device shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker, or none at
all.

Status in gnome-control-center:
Unknown
Status in PulseAudio:
New
Status in gnome-control-center package in Ubuntu:
Invalid
Status in pulseaudio package in Ubuntu:
In Progress
Status in gnome-control-center source package in Focal:
Invalid
Status in pulseaudio source package in Focal:
In Progress

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

1. Connect an audio interface. I tried with BT headphones and speakers as
well as a USB microphone/output.
2. Make sure it's the one selected as "Output device"
3. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
4. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
5. Try to switch back to the BT device and click Test
-> same result as in step 3

Tested with 2 different BT devices (one headset and one speaker) as
well as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

Up to this morning, it was harder to connect the BT device, but once
connected, the sound would output on it as expected. Now, the BT
connection seems to work better, but I can't output the sound to the
BT device...

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output
from the internal laptop speakers, even when the BT device is selected
in the Sound settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pieq 1566 F pulseaudio
/dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio
/dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 5 22:15:50 2020
InstallationDate: Installed on 2020-01-17 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

Another correction. For the one workaround, switching to discrete
graphics in the BIOS only seemed to get past the initial gnome login.
But resuming from DPMS off/suspend, the same error loop happens even
when hybrid graphics is disabled in the BIOS.

Even worse, seems hardware acceleration ends up being disabled:

$ journalctl --no-hostname -b -p warning _COMM=gnome-shell
-- Logs begin at Wed 2019-02-06 14:13:52 SAST, end at Sun 2020-05-03 16:09:45 
SAST. --
May 03 14:51:40 org.gnome.Shell.desktop[2284]: glamor: 'wl_drm' not supported
May 03 14:51:40 org.gnome.Shell.desktop[2284]: Missing Wayland requirements for 
glamor GBM backend
May 03 14:51:40 org.gnome.Shell.desktop[2284]: Failed to initialize glamor, 
falling back to sw
...
May 03 14:53:25 gnome-shell[6549]: setup_framebuffers: assertion 'width > 0' 
failed

The "EGL failed to allocate resources" error stops happening probably
because gnome-shell isn't even using hardware acceleration now.

I've also disabled all gnome shell extensions to avoid noise/errors in
the logs and will try weed out the problem better.

I checked `grep -C2 -E '(EE)|(WW)' /var/log/Xorg.0.log` and things seem
fine:

[45.181] (II) NVIDIA dlloader X Driver  440.59  Thu Jan 30 01:08:17 UTC 2020
[45.181] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
--
[45.182] (II) LoadModule: "ramdac"
[45.182] (II) Module "ramdac" already built-in
[45.183] (WW) Falling back to old probe method for modesetting
[45.183] (II) NVIDIA(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 24/32
--
[46.392] (==) NVIDIA(0): Silken mouse enabled
[46.392] (==) NVIDIA(0): DPMS enabled
[46.393] (WW) NVIDIA(0): Option "PrimaryGPU" is not used
[46.393] (II) Loading sub module "dri2"
[46.393] (II) LoadModule: "dri2"

Note, I've done no customisation to X config - trying to stick to
defaults.

xrandr confirms only one provider / hybrid is indeed off and Intel not
in use:

$ xrandr --listproviders 
Providers: number : 1
Provider 0: id: 0x218 cap: 0x1, Source Output crtcs: 4 outputs: 6 associated 
providers: 0 name:NVIDIA-0

I'm guessing the Lenovo P53 impliments a mux/switch to connect the
laptop panel to the NVidia card so that Intel is disabled in this mode.

And double checking, also no i915 modules are loaded:

$ lsmod | grep '^drm'
drm_kms_helper180224  1 nvidia_drm
drm   491520  10 drm_kms_helper,nvidia_drm

So there seems to be, on current Ubuntu 18.04.4 LTS (fully up to date as
of today), a 4K / UHD 60Hz issue with Nvidia, as seen in X log

[45.228] (II) NVIDIA GLX Module  440.59  Thu Jan 30 01:05:38 UTC
2020

Lastly, I think due to `needs_root_rights=yes` in
/etc/X11/Xwrapper.config, X logs to /var/log/Xorg.0.log again instead of
the X without root which used to log at  ~/.local/share/xorg/Xorg.0.log

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

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Touch-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

Apologies, continuing the comment above (mistakenly posted when adding
the log attachment). Let me retry.

Failure loop observed:

- Failed to blit shared framebuffer: EGL failed to allocate resources for the 
requested operation.
- Failed to set CRTC mode 3840x2160: No such file or directory

To summarise and share my experience of it on a Lenovo P53 and some
quirks/workarounds:

- `sudo ubuntu-drivers autoinstall` got Nvidia 440.59 drivers installed.
- However, Nvidia modeset was not enabled as yet.

$ sudo cat /sys/module/nvidia_drm/parameters/modeset
N

- Blank external screen occurs with modeset=0 (disabled)
- Then, using `prime-select nvidia`, I tried to ensure nvidia was primary
- `prime-select nvidia` sets `options nvidia-drm modeset=1` but it's not 
effective, even after I rebooted

~$ cat /lib/modprobe.d/nvidia-kms.conf
# This file was generated by nvidia-prime
# Set value to 0 to disable modesetting
options nvidia-drm modeset=1

- To make it effective, because modeset is done during initramfs part of boot, 
I ran `sudo update-initramfs -u -k all`. 
- It seems the prime-select option fails to trigger a intiramfs update 
(probably should be filed as a separate bug)
- Regardless, the blank screen issue occured on my Lenovo P53 with or without 
Nvidia KMS modeset enabled
- But one benefit of KMS modeset for Nvida is now the external display gets 
properly recognised.  /sys/class/drm/card1-HDMI-A-1/ now exists (was missing 
with Ubuntu 18.04.4 LTS default proprietary install) including the EDID data 
being read properly and X getting the actual DPI of the screen correctly.

Without nvidia modeset, as seen in `journalctl -b _COMM=gdm-x-session |
grep -C2 -E '(EE)|(WW)'`:

(WW) NVIDIA(0): Unable to get display device for DPI computation.

With nvidia modeset:

(II) NVIDIA(0): Validated MetaModes:
(II) NVIDIA(0): "DFP-3:nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 3840 x 2160
(--) NVIDIA(0): DPI set to (139, 140); computed from "UseEdidDpi" X config

I've also found two workarounds to my issue.

1. Run a script that sets the frequency to 30HZ and then back to 60HZ
2. Switch to discrete only graphics in the BIOS

In most cases, when one is using a 2nd display, there's usually a
powersource available so the complexity of hybrid graphics isn't worth
it and I went with simply disabling hybrid graphics in the BIOS.

It's quite interesting that toggling the display refresh rate down to
30HZ and then back up to 60HZ seems to work around the problem of gnome-
shell mutter's "EGL failed to allocate resources for the requested
operation" bug.

To conclude, even with the root access workaround in place:

$ tail -n 2 /etc/X11/Xwrapper.config
# Added by xserver-xorg-video-nvidia-440
needs_root_rights=yes

I still had external display connection issues with 4K 60Hz.

This might need to be logged as different bug? I'm unsure it's GDM3s
fault given the root workaround was in place, but it's highly
related/similar.

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

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Touch-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

Here's the script I run to workaround the intital failure of gnome to
use the external display after unlocking or resuming from DPMS
suspend/off.

** Attachment added: "fix-hdmi-uhd.sh"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365719/+files/fix-hdmi-uhd.sh

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

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Touch-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

Hi, thanks to everyone, especially Daniel for unpacking this issue.

I have had a very similar issue, where gnome shell fails to run my
external 4K/UHD display at 60HZ and I see the following failure loop
triggered in  `journalctl -b -p warning _COMM=gnome-shell`:

May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared 
framebuffer: EGL failed to allocate resources for the requested operation.
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 
3840x2160: No such file or directory
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to flip: Device or 
resource busy
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 
3840x2160: No such file or directory
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared 
framebuffer: EGL failed to allocate resources for the requested operation.
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 
3840x2160: No such file or directory
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared 
framebuffer: EGL failed to allocate resources for the requested operation.
May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 
3840x2160: No such file or directory
...


 While not sure it's exactly the same, it should still inform the
overall discussion about dealing with GDM3 + Mutter + proprietary Nvidia
drivers modeset problems.

To summarise and share my experience of it on a Lenovo P53 and some
quirks/workarounds:

- `sudo ubuntu-drivers autoinstall` got Nvidia 440.59 drivers installed.
- However, Nvidia modeset was not enabled as yet. 

$ sudo cat /sys/module/nvidia_drm/parameters/modeset
N

-

- Using prime-select

- For laptops like mine, seems the external port is connected to the Nvidia GPU.
- Using the proprietary Nvidia drivers seems to then bump into a 


** Attachment added: "gnome-shell_journal_warnings_egl_resource_failed.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365716/+files/gnome-shell_journal_warnings_egl_resource_failed.txt

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

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

Status in gdm3 package in Ubuntu:
  Opinion
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Context:
  17.10 development packages, nvidia binary driver 375, modeset=1 for the 
nvidia driver.
  ubuntu desktop (gnome shell), fresh install
  ThinkPad W520 in Nvidia Optimus bios mode.
  Nvidia profile.

  Result:
  no external monitors are detected.
  xrandr does not even list them as disconnected (normally it would list five 
external disconnected monitors)

  
  lsmod 
  shows that nvidia driver is loaded
  and the modesetting is working at some level because there is no tearing on 
the laptop panel

  
  Note: modeset=1 is the only way to get flicker-free graphics on the laptop 
panel. modeset=1 is not the default setting but it is highly desirable. 

  It works if lightdm is used which is why I have reported this against gdm3
  My sessions in this configuration have mostly crashed after a few minutes 
with a gdm3 fail whale message in syslog but nothing else looks interesting.

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

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

[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

2020-04-13 Thread Pierre Equoy

@Daniel:

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

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

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

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

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

Bug description:

  
  Summary
  ===

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

  Steps to reproduce
  ==

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

  Expected Results
  

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

  
  Actual results
  ==

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

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

  
  Additional Info
  ===

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1871329/+subscriptions

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

[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

** Tags added: ce-qa-concern champagne

** Tags added: ubuntu-certified

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

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  Summary
  ===

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

  Steps to reproduce
  ==

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

  Expected Results
  

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

  
  Actual results
  ==

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

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

  
  Additional Info
  ===

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

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

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

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

[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

** Attachment added: "pactl_list_headphones.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348500/+files/pactl_list_headphones.log

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

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  Summary
  ===

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

  Steps to reproduce
  ==

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

  Expected Results
  

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

  
  Actual results
  ==

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

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

  
  Additional Info
  ===

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

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

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

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

[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

** Attachment added: "pactl_info_internal_speakers.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348499/+files/pactl_info_internal_speakers.log

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

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  Summary
  ===

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

  Steps to reproduce
  ==

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

  Expected Results
  

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

  
  Actual results
  ==

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

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

  
  Additional Info
  ===

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

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

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

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

[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

** Attachment added: "pactl_list_internal_speakers.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348501/+files/pactl_list_internal_speakers.log

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

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  Summary
  ===

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

  Steps to reproduce
  ==

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

  Expected Results
  

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

  
  Actual results
  ==

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

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

  
  Additional Info
  ===

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

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

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

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

[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

** Attachment added: "pactl_info_headphones.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871329/+attachment/5348498/+files/pactl_info_headphones.log

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

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  Summary
  ===

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

  Steps to reproduce
  ==

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

  Expected Results
  

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

  
  Actual results
  ==

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

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

  
  Additional Info
  ===

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

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

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

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

[Touch-packages] [Bug 1871329] [NEW] No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

Public bug reported:


Summary
===

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

Steps to reproduce
==

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

Expected Results


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


Actual results
==

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

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


Additional Info
===

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

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

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

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

Status in pulseaudio package in Ubuntu:
  New

Bug description:

  
  Summary
  ===

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

  Steps to reproduce
  ==

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

  Expected Results
  

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

  
  Actual results
  ==

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

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

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device:

[Touch-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

2020-04-05 Thread Pierre Equoy

Installed bluez 5.50 -> same result.

Installed linux 5.3 -> same result.

Tried a combination of all the linux/bluez possibilites -> same result.

Until now, I was only looking at the output of btmon (so basically, low
level BT commands).

Then, while I was doing one of the tests above, I tailed
/var/log/syslog, and I saw this weird thing whenever I tried pairing a
BT device (just when it turned from "connected" to immediately
"disconnected" in g-c-c):

bluetoothd[965]: a2dp-sink profile connect failed for 88:C6:26:1A:9E:AF: 
Protocol not available
bluetoothd[965]: a2dp-source profile connect failed for 88:C6:26:1A:9E:AF: 
Protocol not available

Turns out [1] this is because I was lacking the pulseaudio-module-
bluetooth package! After installing it and restarting the device, I can
pair and connect my usual BT devices...

I don't know why it used to work earlier (while I was already on 20.04)
and why it broke one day. I kept upgrading regularly using `sudo apt
update` and `sudo apt dist-upgrade`...

Anyway, it seems the issue was a non-issue... and I wasted a lot of time
investigating it!


[1] 
https://donjajo.com/bluetooth-fix-a2dp-source-profile-connect-failed-xx-protocol-not-available-linux/

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

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device

[Touch-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

2020-03-31 Thread Pierre Equoy

Please find attached my dmesg. I don't see anything related to
bluetoothd.

The same issue happens with two other BT devices (2 earphones from the
same brand, TaoTronics), so I'm pretty confident it's not a BT device
issue. Plus, as I mention, it works well with the same hardware (laptop
and BT devices) on 19.10 (kernel 5.3 + bluez 5.50).

How can I install kernel 5.3 on focal?

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1869857/+attachment/5343943/+files/dmesg.log

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect:

[Touch-packages] [Bug 1869857] Re: [Intel 7265][Regression] Cannot connect BT earphones or speakers

2020-03-31 Thread Pierre Equoy

** Attachment added: "5.3.0-18-btmon-speaker.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1869857/+attachment/5343689/+files/5.3.0-18-btmon-speaker.log

** Description changed:

  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2
  
  Summary
  ===
  
  BT earphones/speaker cannot be connected either using GNOME control
- center, either using bluetoothctl.
+ center, either using bluetoothctl. I've tried with previous versions of
+ the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue,
+ so I believe this is a problem with bluez.
  
  However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18,
- bluez 5.50)
+ bluez 5.50), so I think it's a regression in bluez.
  
  Steps to reproduce
  ==
  
  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
-   -> in g-c-c, the device appears as "Not Set Up" (OK)
+   -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
-   -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)
+   -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)
  
  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.
  
  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)
  
  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:
  
- $ sudo bluetoothctl 
+ $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
-   0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
+   0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  
- 
- 
  Additional information
  ==
  
  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
-   Subsystem: Intel Corporation Dual

[Touch-packages] [Bug 1869857] [NEW] [Intel 7265][Regression] Cannot connect BT earphones or speakers

2020-03-31 Thread Pierre Equoy

Public bug reported:

Laptop: Dell Inspiron 7370
CID: 201704-25503
Ubuntu version: 20.04 daily
Linux kernel: 5.4.0-18-generic
Bluez: 5.53-0ubuntu2

Summary
===

BT earphones/speaker cannot be connected either using GNOME control
center, either using bluetoothctl. I've tried with previous versions of
the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue,
so I believe this is a problem with bluez.

However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18,
bluez 5.50), so I think it's a regression in bluez.

Steps to reproduce
==

1. Open GNOME control center, go to Bluetooth, make sure it's turned on
2. Put the BT device in pairing mode (usually, long press on the Power button)
  -> in g-c-c, the device appears as "Not Set Up" (OK)
3. Click on the device to pair it
  -> the device is briefly marked as "Connected", then immediately switches to 
"Disconnected" (Not OK)

The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
when I follow steps 1-3 above.

I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

Back to Ubuntu 20.04, if I try to pair and connect the device using
bluetoothctl, it fails:

$ sudo bluetoothctl
Agent registered
[CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
[NEW] Device 88:C6:26:1A:9E:AF UE BOOM
[CHG] Device 61:E5:46:38:58:8B RSSI: -86
[CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
[CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
  0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
[CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
[CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
[CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
[CHG] Device 56:AE:9C:58:00:BA RSSI: -87
[CHG] Device 56:AE:9C:58:00:BA TxPower: 12
[CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
[CHG] Device 75:79:4D:66:E9:FF RSSI: -81
[CHG] Device 75:79:4D:66:E9:FF TxPower: 12
[CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
[bluetooth]# scan off
Discovery stopped
[CHG] Controller C8:21:58:B7:2E:82 Discovering: no
[CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
[CHG] Device 75:79:4D:66:E9:FF TxPower is nil
[CHG] Device 75:79:4D:66:E9:FF RSSI is nil
[CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
[CHG] Device 56:AE:9C:58:00:BA TxPower is nil
[CHG] Device 56:AE:9C:58:00:BA RSSI is nil
[CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
[CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
[CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
[CHG] Device 61:E5:46:38:58:8B RSSI is nil
[CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
[CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
[bluetooth]# pair 88:C6:26:1A:9E:AF
Attempting to pair with 88:C6:26:1A:9E:AF
[CHG] Device 88:C6:26:1A:9E:AF Connected: yes
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
[CHG] Device 88:C6:26:1A:9E:AF Paired: yes
Pairing successful
[CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
[CHG] Device 88:C6:26:1A:9E:AF Connected: no
[bluetooth]# trust 88:C6:26:1A:9E:AF
[CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
Changing 88:C6:26:1A:9E:AF trust succeeded
[bluetooth]# connect 88:C6:26:1A:9E:AF
Attempting to connect to 88:C6:26:1A:9E:AF
Failed to connect: org.bluez.Error.Failed
[bluetooth]# connect 88:C6:26:1A:9E:AF
Attempting to connect to 88:C6:26:1A:9E:AF
Failed to connect: org.bluez.Error.Failed

Additional information
==

$ lspci -vv -s 01:00.0
01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
 Subsystem: Intel Corporation Dual Band Wireless-AC 7265
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi

$ dmesg | grep -i bluetooth
[   15.748300] Bluetooth: Core ver 2.22
[   15.748312] Bluetooth: HCI device and connection manager initialized
[   15.748315] Bluetooth: HCI socket layer initialized
[   15.748317] Bluetooth: L2CAP socket layer initialized
[   15.748320] Bluetooth: SCO socket layer initialized
[   15.925524] Bluetooth: hci0: read Intel version: 370810011003110e00
[   15.926254] Bluetooth: hci0: Intel Bluetooth firmware file:

[Touch-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

I filed an issue upstream:

https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/832

** Bug watch added: PulseAudio #832
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/832

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

Title:
[Dell Inspiron 7370] shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker

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

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

Tested with 2 different BT devices (one headset and one speaker) as
well as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

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

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

[Touch-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

** Description changed:

Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503

Steps to reproduce:

- 1. Go to Bluetooth settings panel
- 2. Pair a BT device
- 3. Make sure it's marked as Connected, and go to the Sound settings
- 4. Make sure it's the one selected as "Output device"
- 5. Click "Test"
+ 1. Connect an audio interface. I tried with BT headphones and speakers as
well as a USB microphone/output.
+ 2. Make sure it's the one selected as "Output device"
+ 3. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
- 6. Select "Speakers - Built-in Audio" as Output device and click "Test"
+ 4. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
- 7. Try to switch back to the BT device and click Test
- -> same result as in step 5
+ 5. Try to switch back to the BT device and click Test
+ -> same result as in step 3

- Tested with 2 different BT devices (one headset and one speaker)
+ Tested with 2 different BT devices (one headset and one speaker) as well
+ as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output from
the internal laptop speakers, even when the BT device is selected in the
Sound settings.

** Description changed:

Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
+ Pulseaudio: 1:13.99.1-1ubuntu1
Device CID: 201704-25503

Steps to reproduce:

Tested with 2 different BT devices (one headset and one speaker) as well
as a USB audio interface (Zoom H2N microphone).

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output from
the internal laptop speakers, even when the BT device is selected in the
Sound settings.

[Touch-packages] [Bug 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

** Summary changed:

- [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options 
but the sound keeps being emitted from the internal laptop speaker
+ [Dell Inspiron 7370] shows up in the sound output options but the sound keeps 
being emitted from the internal laptop speaker

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

Title:
  [Dell Inspiron 7370] shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1866194] Re: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

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

Daniel,

this bug is not a duplicate of lp:1850766. In lp:1850766, selecting the
output device back and forth is an enough workaround to make it work.
Here, doing so doesn't do anything, and the only workaround I found is
by manually switching the sink-inputs as I described in comment #7.

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

Title:
[Zoom USB audio on Dell Inspiron 7370] shows up in the sound output
options but the sound keeps being emitted from the internal laptop
speaker

Status in pulseaudio package in Ubuntu:
New

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503

Steps to reproduce:

1. Go to Bluetooth settings panel
2. Pair a BT device
3. Make sure it's marked as Connected, and go to the Sound settings
4. Make sure it's the one selected as "Output device"
5. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
6. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
7. Try to switch back to the BT device and click Test
-> same result as in step 5

Tested with 2 different BT devices (one headset and one speaker)

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

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

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

[Touch-packages] [Bug 1866194] Re: [Zoom USB audio on Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

2020-03-19 Thread Pierre Equoy

** Description changed:

Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503

Steps to reproduce:

Tested with 2 different BT devices (one headset and one speaker)

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.
+
+ I was previously using 19.04 and 19.10 on this device and never
+ experienced this kind of issue.

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output from
the internal laptop speakers, even when the BT device is selected in the
Sound settings.

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

Title:
[Zoom USB audio on Dell Inspiron 7370] shows up in the sound output
options but the sound keeps being emitted from the internal laptop
speaker

Status in pulseaudio package in Ubuntu:
New

Bug description:
Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503

Steps to reproduce:

Tested with 2 different BT devices (one headset and one speaker)

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

I was previously using 19.04 and 19.10 on this device and never
experienced this kind of issue.

[Touch-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

2020-03-15 Thread Pierre Equoy

Thanks a lot for the input, Ken!

You were right, it is not related to BT, but to the sound devices being
added and removed.

I happend to have a Zoom microphone that can be connected as USB and
creates a new audio interface (both input and output). Here are my new
tests and findings:

1. Plug the Zoom USB device
-> it appears in the Sound Settings Output Device and is automatically selected
2. Press Test and check the sound output
-> the sound outputs on the internal speakers (NOK)

After some investigation using pactl, I found how to fix the issue, for
both the USB audio interface and the Bluetooth speaker:

1. Make sure the audio interface you want is connected (in my case, I
connected both the USB and the Bluetooth speaker):

$ pactl list short sinks
1   alsa_output.pci-_00_1f.3.analog-stereo  module-alsa-card.c  
s16le 2ch 48000Hz   SUSPENDED
6   alsa_output.usb-ZOOM_Corporation_H2n_-00.iec958-stereo  
module-alsa-card.c  s16le 2ch 44100Hz   SUSPENDED
7   bluez_sink.88_C6_26_1A_9E_AF.a2dp_sink  module-bluez5-device.c  s16le 
2ch 44100Hz   SUSPENDED

2. Play an audio stream, for instance a Youtube video. The output should
come from the internal speakers, and can be seen in pactl as well:

$ pactl list short sink-inputs
10  1   16  protocol-native.c   float32le 2ch 44100Hz

3. Ask pactl to move the stream to the desired sink (output); for
instance, the Bluetooth speaker:

$ pactl move-sink-input 10 7

-> The sound outputs to the Bluetooth device! \o/

However, going back to Sound Settings (where the "Output Device" shows
my Bluetooth Speaker) and clicking Test still outputs to the internal
speakers


Do you think it could be a GNOME issue? What should I do next?


** Summary changed:

- After connecting a Bluetooth headset or speaker, it shows up in the sound 
output options but the sound keeps being emitted from the internal laptop 
speaker
+ After connecting an external output device (USB audio interface, Bluetooth 
speaker...), it shows up in the sound output options but the sound keeps being 
emitted from the internal laptop speaker

** Tags removed: a2dp

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

Title:
  After connecting an external output device (USB audio interface,
  Bluetooth speaker...), it shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias:

[Touch-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

** Tags added: ce-qa-concern rls-ff-incoming

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

Title:
  After connecting a Bluetooth headset or speaker, it shows up in the
  sound output options but the sound keeps being emitted from the
  internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

** Attachment added: "btmon_bt_speaker.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333852/+files/btmon_bt_speaker.log

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

Title:
  After connecting a Bluetooth headset or speaker, it shows up in the
  sound output options but the sound keeps being emitted from the
  internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

** Attachment added: "pactl_list_after_bt_speaker_connected.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333856/+files/pactl_list_after_bt_speaker_connected.log

** Description changed:

  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
+ Device CID: 201704-25503
  
  Steps to reproduce:
  
  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
- -> the test sound outputs from the internal laptop speakers (NOK)
+ -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
- -> the test sound outputs from the internal laptop speakers (OK)
+ -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
- -> same result as in step 5
+ -> same result as in step 5
  
  Tested with 2 different BT devices (one headset and one speaker)
  
  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.
  
  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the BT
  device...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  pieq   1566 F pulseaudio
-  /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
-  /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  pieq   1566 F pulseaudio
+  /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
+  /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

** Description changed:

  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503
  
  Steps to reproduce:
  
  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5
  
  Tested with 2 different BT devices (one headset and one speaker)
  
  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.
  
  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the BT
  device...
+ 
+ I tried to reboot the device, and also to suspend/resume, but in each
+ case, the BT device can connect back, but the sound is still output from
+ the internal laptop speakers, even when the BT device is selected in the
+ Sound settings.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)

[Touch-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

** Attachment added: "btmon_pair_headset.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333853/+files/btmon_pair_headset.log

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

Title:
  After connecting a Bluetooth headset or speaker, it shows up in the
  sound output options but the sound keeps being emitted from the
  internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1866194] Re: After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

** Attachment added: "pactl_list_after_bt_headset_paired_and_connected.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1866194/+attachment/5333854/+files/pactl_list_after_bt_headset_paired_and_connected.log

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

Title:
  After connecting a Bluetooth headset or speaker, it shows up in the
  sound output options but the sound keeps being emitted from the
  internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1866194] [NEW] After connecting a Bluetooth headset or speaker, it shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

Public bug reported:

Ubuntu version: focal dev
Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
Device CID: 201704-25503

Steps to reproduce:

1. Go to Bluetooth settings panel
2. Pair a BT device
3. Make sure it's marked as Connected, and go to the Sound settings
4. Make sure it's the one selected as "Output device"
5. Click "Test"
-> the test sound outputs from the internal laptop speakers (NOK)
6. Select "Speakers - Built-in Audio" as Output device and click "Test"
-> the test sound outputs from the internal laptop speakers (OK)
7. Try to switch back to the BT device and click Test
-> same result as in step 5

Tested with 2 different BT devices (one headset and one speaker)

Attached are btmon logs captured during the procedure described above,
and pactl logs capture after step 7.

Up to this morning, it was harder to connect the BT device, but once
connected, the sound would output on it as expected. Now, the BT
connection seems to work better, but I can't output the sound to the BT
device...

I tried to reboot the device, and also to suspend/resume, but in each
case, the BT device can connect back, but the sound is still output from
the internal laptop speakers, even when the BT device is selected in the
Sound settings.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pieq   1566 F pulseaudio
 /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
 /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  5 22:15:50 2020
InstallationDate: Installed on 2020-01-17 (48 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/23/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.14.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7370
dmi.product.sku: 07E9
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug focal wayland-session

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

Title:
  After connecting a Bluetooth headset or speaker, it shows up in the
  sound output options but the sound keeps being emitted from the
  internal laptop speaker

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Device CID: 201704-25503

  Steps to reproduce:

  1. Go to Bluetooth settings panel
  2. Pair a BT device
  3. Make sure it's marked as Connected, and go to the Sound settings
  4. Make sure it's the one selected as "Output device"
  5. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  6. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  7. Try to switch back to the BT device and click Test
  -> same result as in step 5

  Tested with 2 different BT devices (one headset and one speaker)

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log

[Touch-packages] [Bug 1860606] Re: TypeError: _fetch_archives() missing 1 required positional argument: 'allow_unauthenticated'

2020-01-22 Thread Pierre-Emmanuel Novac

Sorry forgot that I commented out the updates and security repositories
in /etc/apt/sources.list . You can probably hold the python3-apt package
to get the same effect.

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

Title:
  TypeError: _fetch_archives() missing 1 required positional argument:
  'allow_unauthenticated'

Status in python-apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in python-apt source package in Xenial:
  Fix Released
Status in ubuntu-release-upgrader source package in Xenial:
  Invalid
Status in python-apt source package in Bionic:
  Confirmed
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid
Status in python-apt source package in Disco:
  Fix Released
Status in ubuntu-release-upgrader source package in Disco:
  Invalid
Status in python-apt source package in Eoan:
  Confirmed
Status in ubuntu-release-upgrader source package in Eoan:
  Invalid
Status in python-apt source package in Focal:
  Confirmed
Status in ubuntu-release-upgrader source package in Focal:
  Invalid

Bug description:
  I was upgrading my workstation from 19.04 to 19.10 and following that
  to 20.04. In each case I used do-release-upgrade (without and with -d
  respectively). The 20.04 upgrade failed as the tool crashed on invalid
  function signature:

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-f_816ncr/focal", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeMain.py", line 
238, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 2082, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 1998, in fullUpgrade
  if not self.doDistUpgradeFetching():
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 1233, in doDistUpgradeFetching
  self.cache._fetch_archives(self.fetcher, pm)
  TypeError: _fetch_archives() missing 1 required positional argument: 
'allow_unauthenticated'

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

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

[Touch-packages] [Bug 1860606] Re: TypeError: _fetch_archives() missing 1 required positional argument: 'allow_unauthenticated'

2020-01-22 Thread Pierre-Emmanuel Novac

sudo mv /etc/apt/sources.list.distUpgrade /etc/apt/sources.list
sudo apt update
sudo apt install python3-apt=1.8.4
sudo do-release-upgrade

That gets it going for Lubuntu 19.04 to 19.10 upgrade.

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

Title:
  TypeError: _fetch_archives() missing 1 required positional argument:
  'allow_unauthenticated'

Status in python-apt package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed
Status in python-apt source package in Xenial:
  Confirmed
Status in ubuntu-release-upgrader source package in Xenial:
  Confirmed
Status in python-apt source package in Bionic:
  Confirmed
Status in ubuntu-release-upgrader source package in Bionic:
  Confirmed
Status in python-apt source package in Disco:
  Confirmed
Status in ubuntu-release-upgrader source package in Disco:
  Confirmed
Status in python-apt source package in Eoan:
  Confirmed
Status in ubuntu-release-upgrader source package in Eoan:
  Confirmed
Status in python-apt source package in Focal:
  Confirmed
Status in ubuntu-release-upgrader source package in Focal:
  Confirmed

Bug description:
  I was upgrading my workstation from 19.04 to 19.10 and following that
  to 20.04. In each case I used do-release-upgrade (without and with -d
  respectively). The 20.04 upgrade failed as the tool crashed on invalid
  function signature:

  Original exception was:
  Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-f_816ncr/focal", line 8, in 
  sys.exit(main())
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeMain.py", line 
238, in main
  if app.run():
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 2082, in run
  return self.fullUpgrade()
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 1998, in fullUpgrade
  if not self.doDistUpgradeFetching():
File 
"/tmp/ubuntu-release-upgrader-f_816ncr/DistUpgrade/DistUpgradeController.py", 
line 1233, in doDistUpgradeFetching
  self.cache._fetch_archives(self.fetcher, pm)
  TypeError: _fetch_archives() missing 1 required positional argument: 
'allow_unauthenticated'

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

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

[Touch-packages] [Bug 1609750]

2019-11-19 Thread pierre-louis.bossart

if you can recompile a kernel, using Mark Brown's for-next should have
have all the latest changes from Google for Cyan.

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:12:03 2016
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux-image-4.4.0-33-generic 4.4.0-33.52
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: Linux 4.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

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

2019-11-17 Thread Pierre Equoy

** Attachment added: 
"pactl_list_before_switching_output_device_back_and_forth.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306132/+files/pactl_list_before_switching_output_device_back_and_forth.log

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

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

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

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

  Device: Dell Inspiron 7370

  Step to reproduce
  =

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

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

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

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

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

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

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

2019-11-17 Thread Pierre Equoy

I ran the following steps:

1. Power laptop on with bluetooth turned off
2. Turn BT on in gnome settings and set my BT headphones in pairing mode
3. Pair the headphones.
4. In Sound settings, it looks like the selected device is the BT headphones, 
but if I play something it outputs on the laptop speakers.

output of `pactl list` gives something interesting though:

Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: no
Volume: front-left: 30421 /  46% / -20.00 dB,   front-right: 30421 /  
46% / -20.00 dB
balance 0.00
Base Volume: 6554 /  10% / -60.00 dB
Monitor of Sink: n/a
Latency: 123 usec, configured 4 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY 
Properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC3254 Analog"
alsa.id = "ALC3254 Analog"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "0"
alsa.card = "0"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xd1128000 irq 128"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1f.3"
sysfs.path = "/devices/pci:00/:00:1f.3/sound/card0"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "9d71"
device.product.name = "Sunrise Point-LP HD Audio"
device.form_factor = "internal"
device.string = "front:0"
device.buffering.buffer_size = "65536"
device.buffering.fragment_size = "32768"
device.access_mode = "mmap+timer"
device.profile.name = "analog-stereo"
device.profile.description = "Analog Stereo"
device.description = "Built-in Audio Analog Stereo"
alsa.mixer_name = "Realtek ALC3254"
alsa.components = "HDA:10ec0295,102807e9,0012 
HDA:8086280b,80860101,0010"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
Ports:
analog-input-internal-mic: Internal Microphone (priority: 8900)
analog-input-headphone-mic: Microphone (priority: 8700, not 
available)
analog-input-headset-mic: Headset Microphone (priority: 8800, 
not available)
Active Port: analog-input-internal-mic
Formats:
pcm

Source #2
State: SUSPENDED
Name: bluez_sink.E3_28_E9_21_94_78.a2dp_sink.monitor
Description: Monitor of TaoTronics TT-BH07
Driver: module-bluez5-device.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 25
Mute: no
Volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor of Sink: bluez_sink.E3_28_E9_21_94_78.a2dp_sink
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY 
Properties:
device.description = "Monitor of TaoTronics TT-BH07"
device.class = "monitor"
device.string = "E3:28:E9:21:94:78"
device.api = "bluez"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_E3_28_E9_21_94_78"
bluez.class = "0x240404"
bluez.alias = "TaoTronics TT-BH07"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
Formats:
pcm


This matches what I have, but not what I see in Sound settings.

5. Now, if I select the speakers as the output device in the sound
settings, then back to BT device, the sound is correctly output to the
BT headphones (and not the laptop speakers), and I see this in `pactl
list`:

Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: no
Volume: front-left: 30421 /  46% / -20.00 dB,   front-right: 30421 /  
46% / -20.00 dB

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

2019-11-17 Thread Pierre Equoy

** Attachment added: 
"pactl_list_after_switching_output_device_back_and_forth.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850766/+attachment/5306133/+files/pactl_list_after_switching_output_device_back_and_forth.log

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

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

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

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

  Device: Dell Inspiron 7370

  Step to reproduce
  =

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

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

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

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

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

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

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

2019-10-31 Thread Pierre Equoy

Public bug reported:

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

Device: Dell Inspiron 7370

Step to reproduce
=

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

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

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

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

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


** Tags: amd64 apport-bug ce-qa-concern eoan ubuntu-certified wayland-session

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

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

Status in pulseaudio package in Ubuntu:
  New

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

  Device: Dell Inspiron 7370

  Step to reproduce
  =

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

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

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

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

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

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

[Touch-packages] [Bug 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell

2019-10-13 Thread Pierre-Antoine Champin

Sorry (again) for the late reply.

I just got an opportunity to install a fresh ubuntu 19.04, so I thought
I would give a try to the patch... But on this fresh install, I do not
have the problem... (without even enabling proposed packaged).

I don't even understand *why* the x11-bell module is *not* loaded... 
(I did install the ubuntu-sounds package, as this is a condition in 
start-pulseaudio-x11).

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Committed

Bug description:
  * Impact
  The package force load a bell sound which can conflicts with the user 
configuration

  * Test case
  - Enable a login sound in session
  - Login into a GNOME/Ubuntu session
  -> the configured sound should be played

  * Regression potential
  Try other desktop environments to make sure their login sound behaviour isn't 
changed, it shouldn't since the customization dropped was specific to the 
Ubuntu sound theme

  ---

  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

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

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

[Touch-packages] [Bug 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell

2019-06-27 Thread Pierre-Antoine Champin

Sorry for the late answer.

In my case, the sound was the correct one, but it was played twice at
the same time, causing some unpleasant saturation.

Furthermore, if I changed the sound in the Gnome control panel, than I
would have two different sounds playing at the same time (the newly
configure Gnome sound, plus the old one, played by module-x11-bell).

That being said, I have not tried it on a fresh disco install. Mine was
installed a year ago, and upgraded to disco... It took me that much time
to investigate the problem and report it ;-)

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

Title:
  pulseaudio should not load module-x11-bell in gnome-shell

Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  The package `pulseaudio` installs a startup script in 
`/etc/xdg/autostart/pulseaudio.desktop`,
  which itself runs `/usr/bin/start-pulseaudio-x11`,
  which loads a number of x11 related modules in `pulseaudio`.

  One of these modules is `module-x11-bell`,
  which makes `pulseaudio` play a sound each time a system bell is emitted
  (usually by terminal applications, such as bash or vim).

  This is redundant with gnome-shell, which is also able to handle the system 
bell
  (through the gsetting key `org.gnome.desktop.sound event-sounds`).

  The gnome system bell is directly configurable by the user (Settings > Sound),
  so it should be preferred over pulseaudio's own system bell.

  I suggest to patch the `/usr/bin/start-pulseaudio-x11`,
  to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome 
Shell
  (e.g. if GNOME_SHELL_SESSION_MODE is set).

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

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

[Touch-packages] [Bug 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter

@Daniel

4/5. I collected the attached drminfo.txt while at login screen.

While in tty4, I noticed that the computer would freeze for more or less
long periods of time because of some nouveau-related kernel messages
that were printed on the screen. I managed to type the command you
mentioned between two freeze periods.

Hope this helps. Let me know if you need additional info!

** Attachment added: "drminfo.txt"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822047/+attachment/5250116/+files/drminfo.txt

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

Title:
After install, cannot boot into system unless I use nomodeset kernel
parameter

Status in xorg package in Ubuntu:
Incomplete

Bug description:
System: Disco (19.04 beta)
Hardware: Dell Precision 7530

After installing the system, it cannot start unless manually adding
`nomodeset` in the kernel command line at boot time.

Steps to reproduce:

1. Install disco 19.04 beta on the device. Leave all the options at default
values (i.e. do not install third party drivers)
2. Once installation is finished, restart the system (the system will freeze
after install is finished, it's a known issue -> lp:1822044)

Expected result:

2. The system boots and user can log in and see Gnome interface.

Actual result:

2. The first time, I could log into the system. However, when I tried
to access the Settings screen, the system froze. After that, everytime
I tried to boot the device, the screen was filled with dark purple, a
mouse cursor may appear, but nothing else would happen. At that stage,
the only thing I could do was to force shutdown the device, start it
again and at Grub screen, press `e` to edit the kernel parameters and
add `nomodeset`.

This bug is created from the actual device, using `nomodeset` kernel
parameter. `nouveau` graphics driver is most likely the culprit, like
in all the previous issues that have been raised (see lp:1822026,
lp:1822044, lp:1821882)

Two workarounds exist:

1. After installation, use `nomodeset` kernel parameter to boot into the
system, then install proprietary nvidia drivers.
2. During installation, install third party drivers. If Secure Boot is
enabled, this requires to set a password that will be asked when the device
reboots.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 28 15:39:40 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA
controller])
Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889]
NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889]
InstallationDate: Installed on 2019-03-28 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
MachineType: Dell Inc. Precision 7530
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic
root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 7530
dmi.product.sku: 0889
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter

1/2/3. I made a fresh install.

On the first boot, device was blocked at the "Ubuntu" logo with the dots
blinking white and orange forever. Pressing Esc wouldn't do anything
(it's supposed to show the boot process) and pressing NumLock on the
numpad wouldn't light the NumLock LED (it's my to-go check to see if the
system froze or not).

I force-shutdown it, started again, this time it showed me the login
screen, I logged in and it remained on a dark purple screen with a black
mouse cursor for about 1-2 minutes before finally displaying the OOBE
screen (where you have to press Next and select if you want to send
anonymous report etc.).

I then typed `journalctl -b-1 > prevboot.txt`, this is the file attached
to this comment. Apologies as the locale is set to Chinese because my
timezone is Taipei.

** Attachment added: "prevboot.txt"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822047/+attachment/5250111/+files/prevboot.txt

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

Title:
After install, cannot boot into system unless I use nomodeset kernel
parameter

Status in xorg package in Ubuntu:
Incomplete

Bug description:
System: Disco (19.04 beta)
Hardware: Dell Precision 7530

After installing the system, it cannot start unless manually adding
`nomodeset` in the kernel command line at boot time.

Steps to reproduce:

Expected result:

2. The system boots and user can log in and see Gnome interface.

Actual result:

Two workarounds exist:

[Touch-packages] [Bug 1822047] Re: After install, cannot boot into system unless I use nomodeset kernel parameter

To see a sample of dmesg when nouveau is activated, please refer to
lp:1822026

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

Title:
  After install, cannot boot into system unless I use nomodeset kernel
  parameter

Status in xorg package in Ubuntu:
  New

Bug description:
  System: Disco (19.04 beta)
  Hardware: Dell Precision 7530

  After installing the system, it cannot start unless manually adding
  `nomodeset` in the kernel command line at boot time.

  Steps to reproduce:

  1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
  2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

  Expected result:

  2. The system boots and user can log in and see Gnome interface.

  Actual result:

  2. The first time, I could log into the system. However, when I tried
  to access the Settings screen, the system froze. After that, everytime
  I tried to boot the device, the screen was filled with dark purple, a
  mouse cursor may appear, but nothing else would happen. At that stage,
  the only thing I could do was to force shutdown the device, start it
  again and at Grub screen, press `e` to edit the kernel parameters and
  add `nomodeset`.

  This bug is created from the actual device, using `nomodeset` kernel
  parameter. `nouveau` graphics driver is most likely the culprit, like
  in all the previous issues that have been raised (see lp:1822026,
  lp:1822044, lp:1821882)

  Two workarounds exist:

  1. After installation, use `nomodeset` kernel parameter to boot into the 
system, then install proprietary nvidia drivers.
  2. During installation, install third party drivers. If Secure Boot is 
enabled, this requires to set a password that will be asked when the device 
reboots.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 28 15:39:40 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889]
   NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889]
  InstallationDate: Installed on 2019-03-28 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: Dell Inc. Precision 7530
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 7530
  dmi.product.sku: 0889
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1822047] [NEW] After install, cannot boot into system unless I use nomodeset kernel parameter

Public bug reported:

System: Disco (19.04 beta)
Hardware: Dell Precision 7530

After installing the system, it cannot start unless manually adding
`nomodeset` in the kernel command line at boot time.

Steps to reproduce:

1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

Expected result:

2. The system boots and user can log in and see Gnome interface.

Actual result:

2. The first time, I could log into the system. However, when I tried to
access the Settings screen, the system froze. After that, everytime I
tried to boot the device, the screen was filled with dark purple, a
mouse cursor may appear, but nothing else would happen. At that stage,
the only thing I could do was to force shutdown the device, start it
again and at Grub screen, press `e` to edit the kernel parameters and
add `nomodeset`.

This bug is created from the actual device, using `nomodeset` kernel
parameter. `nouveau` graphics driver is most likely the culprit, like in
all the previous issues that have been raised (see lp:1822026,
lp:1822044, lp:1821882)

Two workarounds exist:

1. After installation, use `nomodeset` kernel parameter to boot into the 
system, then install proprietary nvidia drivers.
2. During installation, install third party drivers. If Secure Boot is enabled, 
this requires to set a password that will be asked when the device reboots.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 28 15:39:40 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0889]
 NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Dell GP107GLM [Quadro P1000 Mobile] [1028:0889]
InstallationDate: Installed on 2019-03-28 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
MachineType: Dell Inc. Precision 7530
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=e07663b1-0b3d-4cdb-aa6c-f6f2e8c4ee5d ro quiet splash nomodeset 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd02/19/2019:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 7530
dmi.product.sku: 0889
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug ce-qa-concern disco rls-dd-incoming ubuntu

** Tags added: ce-qa-concern rls-dd-incoming

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

Title:
  After install, cannot boot into system unless I use nomodeset kernel
  parameter

Status in xorg package in Ubuntu:
  New

Bug description:
  System: Disco (19.04 beta)
  Hardware: Dell Precision 7530

  After installing the system, it cannot start unless manually adding
  `nomodeset` in the kernel command line at boot time.

  Steps to reproduce:

  1. Install disco 19.04 beta on the device. Leave all the options at default 
values (i.e. do not install third party drivers)
  2. Once installation is finished, restart the system (the system will freeze 
after install is finished, it's a known issue -> lp:1822044)

  Expected result:

  2. The system boots and user can log in and see Gnome interface.

  Actual result:

  2. The first time, I could log into the system. However, when I tried
  to access the Settings screen, the system froze. After that, everytime
  I tried to boot the device, the screen was filled with dark purple, a
  mouse cursor

[Touch-packages] [Bug 1821882] Re: Screen is very dark and brightness cannot be adjusted

** Tags added: ce-qa-concern

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

Title:
  Screen is very dark and brightness cannot be adjusted

Status in xorg package in Ubuntu:
  New

Bug description:
  Device: Dell Precision 7530
  In the BIOS, the Switchable Graphics option is deactived, which means only 
the nVidia GPU is used.

  When booting 19.04 beta live USB, the screen becomes very dark and
  brightness cannot be adjusted. (The same issue happens with 18.04.2)

  There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
  intel_backlight):

  $ ll /sys/class/backlight/
  total 0
  drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
  drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
  lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

  Trying to manually change brightness doesn't do anything:

  $ sudo su
  root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
  root@ubuntu:/sys/class/backlight/nv_backlight# ll
  total 0
  drwxr-xr-x 3 root root0 Mar 27 09:28 ./
  drwxr-xr-x 4 root root0 Mar 27 09:28 ../
  -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
  -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
  lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
  drwxr-xr-x 2 root root0 Mar 27 09:28 power/
  lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 type
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
  root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  50

  Although the value is changed, the screen brightness doesn't change.

  in dmesg, I can see the following:

  [0.241878] ACPI: Added _OSI(Module Device)
  [0.241878] ACPI: Added _OSI(Processor Device)
  [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.241878] ACPI: Added _OSI(Processor Aggregator Device)
  [0.241878] ACPI: Added _OSI(Linux-Dell-Video)
  [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
  [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
  [0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.288614] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.288619] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.288620] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.288623] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog

[Touch-packages] [Bug 1821882] Re: Screen is very dark and brightness cannot be adjusted

2019-03-27 Thread Pierre Equoy

I tried the same while blacklisting nouveau driver in grub:

$ cat /proc/cmdline
BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet 
splash modprobe.blacklist=nouveau ---

This time, I have "acpi_video0" in /sys/class/backlight, but the result
is the same. The screen is very dark.

/sys/class/backlight/acpi_video0/brightness is 100 by default. I can
modify this value with

$ sudo su
# echo 60 > /sys/class/backlight/acpi_video0/brightness

and the brightness actually changes to something even darker. If I try
to set it over 100, I get:

write error: Invalid argument

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

Title:
  Screen is very dark and brightness cannot be adjusted

Status in xorg package in Ubuntu:
  New

Bug description:
  Device: Dell Precision 7530
  In the BIOS, the Switchable Graphics option is deactived, which means only 
the nVidia GPU is used.

  When booting 19.04 beta live USB, the screen becomes very dark and
  brightness cannot be adjusted. (The same issue happens with 18.04.2)

  There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
  intel_backlight):

  $ ll /sys/class/backlight/
  total 0
  drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
  drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
  lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

  Trying to manually change brightness doesn't do anything:

  $ sudo su
  root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
  root@ubuntu:/sys/class/backlight/nv_backlight# ll
  total 0
  drwxr-xr-x 3 root root0 Mar 27 09:28 ./
  drwxr-xr-x 4 root root0 Mar 27 09:28 ../
  -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
  -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
  lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
  drwxr-xr-x 2 root root0 Mar 27 09:28 power/
  lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
  -r--r--r-- 1 root root 4096 Mar 27 09:28 type
  -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
  root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
  100
  root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
  root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
  50

  Although the value is changed, the screen brightness doesn't change.

  in dmesg, I can see the following:

  [0.241878] ACPI: Added _OSI(Module Device)
  [0.241878] ACPI: Added _OSI(Processor Device)
  [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
  [0.241878] ACPI: Added _OSI(Processor Aggregator Device)
  [0.241878] ACPI: Added _OSI(Linux-Dell-Video)
  [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
  [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
  [0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
  [0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
  [0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
  [0.287869] ACPI:

[Touch-packages] [Bug 1821882] [NEW] Screen is very dark and brightness cannot be adjusted

2019-03-27 Thread Pierre Equoy

Public bug reported:

Device: Dell Precision 7530
In the BIOS, the Switchable Graphics option is deactived, which means only the 
nVidia GPU is used.

When booting 19.04 beta live USB, the screen becomes very dark and
brightness cannot be adjusted. (The same issue happens with 18.04.2)

There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no
intel_backlight):

$ ll /sys/class/backlight/
total 0
drwxr-xr-x  2 root root 0 Mar 27 09:36 ./
drwxr-xr-x 74 root root 0 Mar 27 09:28 ../
lrwxrwxrwx  1 root root 0 Mar 27 09:28 nv_backlight -> 
../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/

Trying to manually change brightness doesn't do anything:

$ sudo su
root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight
root@ubuntu:/sys/class/backlight/nv_backlight# ll
total 0
drwxr-xr-x 3 root root0 Mar 27 09:28 ./
drwxr-xr-x 4 root root0 Mar 27 09:28 ../
-r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness
-rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power
-rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness
lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/
-r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness
drwxr-xr-x 2 root root0 Mar 27 09:28 power/
lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> 
../../../../../../../../class/backlight/
-r--r--r-- 1 root root 4096 Mar 27 09:28 type
-rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent
root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness
100
root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness
root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness
50

Although the value is changed, the screen brightness doesn't change.

in dmesg, I can see the following:

[0.241878] ACPI: Added _OSI(Module Device)
[0.241878] ACPI: Added _OSI(Processor Device)
[0.241878] ACPI: Added _OSI(3.0 _SCP Extensions)
[0.241878] ACPI: Added _OSI(Processor Aggregator Device)
[0.241878] ACPI: Added _OSI(Linux-Dell-Video)
[0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[0.286326] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.286336] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287096] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287102] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287858] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.287864] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.288614] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.288619] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.288620] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.288623] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.288625] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.289376] ACPI BIOS Error (bug): Failure creating 
[\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324)
[0.289379] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20181213/psobject-221)
[0.289381] ACPI: Skipping parse of AML opcode: Method (0x0014)
[0.289382] ACPI BIOS Error (bug): Failure creating

[Touch-packages] [Bug 1790816] Re: Terrible sound after update to 18.04

It's a shot in the dark, but in my case, pulse sound server (atop of
alsa) seems to have gotten into a mess with an upgrade between 16.04 and
18.04. Post login, removing old / session start user config fixed my
dodgy channel mappings (but not quite the same as crackling, etc):

pulseaudio --kill \
&& rm -r ~/.config/pulse/* \
&& pulseaudio --start

However, every new boot, the same missing channel mappings cause my
audio to sound bad (not mapped correctly to 5.1 channels).

Also, try alsa-info which is a script that bundles all the alsa
inspection commands and then maybe try fish for the problem in that.
Also try figure out how to play a sound file directly to alsa vs via the
pulse sound server to rule out pulse causing the problem.

I think the speaker-test command also directly tests the alsa layer
where as the gnome-control-centre (settings) sound page "Test Speakers"
tests the setup via pulse.

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

Title:
Terrible sound after update to 18.04

Status in alsa-driver package in Ubuntu:
New

Bug description:
The sound just is extremely distorted after update to 18.04. Like an
old radio that's not picking up the station right. I saw a webpage
about the same device I am using and tried their solution. That didn't
help at all. Hope I didn't make things worse.

I saw a page that mentioned the lspci command. Based on that, I guess
I am using an Intel 82801 JD/DO audio card. One site said that
requires an snd_hda_intel driver, but all I could find in Synaptic
Package Manager was that an alsa driver and pulse audio were
installed. Could the correct driver have been removed with the new
installation?

This computer has been kind of buggy as of late, but the audio had
been working. I had problems installing this OS. Mostly it seems to be
working otherwise though.

1) Description: Ubuntu 18.04.1 LTS
Release: 18.04

2) N: Unable to locate package pkgname

3) What you expected to happen: sound to work properly

4) What happened instead: sound distorted

Hope my attempt to fix it doesn't screw up the bug report.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: szettner 2030 F pulseaudio
CurrentDesktop: GNOME-Flashback:GNOME
Date: Wed Sep 5 03:07:08 2018
InstallationDate: Installed on 2017-06-28 (433 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: High background noise, or volume is too low
Title: [OptiPlex 760, Analog Devices AD1984A, Green Headphone Out, Front]
Background noise or low volume
UpgradeStatus: Upgraded to bionic on 2018-09-02 (2 days ago)
dmi.bios.date: 12/03/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0D517D
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA01:bd12/03/2008:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0D517D:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex 760
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1791417] Re: Sound bug ubuntu 18.04

Wish there was a "needs more info" tag or a way to tag bug reports like
this. There's no context as to exactly what the problem is despite the
alsa-info script output being supplied.

It's unfair to maintainers to expect them to fish out the problem.
"Sound bug ubuntu 18.04" is way too generic.

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

Title:
  Sound bug ubuntu 18.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod
  +x ./alsa-info.sh && ./alsa-info.sh

  --2018-09-07 12:24:00--  http://www.alsa-project.org/alsa-info.sh
  Resolving www.alsa-project.org (www.alsa-project.org)... 77.48.224.243
  Connecting to www.alsa-project.org 
(www.alsa-project.org)|77.48.224.243|:80... connected.
  HTTP request sent, awaiting response... 302 Found
  Location: 
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
 [following]
  --2018-09-07 12:24:00--  
http://git.alsa-project.org/?p=alsa-utils.git;a=blob_plain;f=alsa-info/alsa-info.sh
  Resolving git.alsa-project.org (git.alsa-project.org)... 77.48.224.243
  Connecting to git.alsa-project.org 
(git.alsa-project.org)|77.48.224.243|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: unspecified [application/x-sh]
  Saving to: ‘alsa-info.sh’

  alsa-info.sh[ <=>
  ]  28.03K   170KB/sin 0.2s

  2018-09-07 12:24:01 (170 KB/s) - ‘alsa-info.sh’ saved [28707]

  ALSA Information Script v 0.4.64
  

  This script visits the following commands/files to collect diagnostic
  information about your ALSA installation and sound related hardware.

dmesg
lspci
lsmod
aplay
amixer
alsactl
/proc/asound/
/sys/class/sound/
~/.asoundrc (etc.)

  See './alsa-info.sh --help' for command line options.

  Automatically upload ALSA information to www.alsa-project.org? [y/N] : y
  Uploading information to www.alsa-project.org ...  Done!

  Your ALSA information is located at http://www.alsa-
  project.org/db/?f=84ba91e70cc537608d8ffa04c5ec05a08bcf1ed6

  Please inform the person helping you.

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

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

[Touch-packages] [Bug 736349] Re: "Test speakers" is silent

See
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1774904/comments/4.
gnome-control-center should rather add libcanberra-pulse to depends
rather than just recommends.

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

Title:
  "Test speakers" is silent

Status in OEM Priority Project:
  Fix Released
Status in gnome-media package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Invalid
Status in ubuntu-sounds package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-media

  My speakers are working fine (I can year playback with Banshee and
  VLC), but "Test speakers" is silent. I hear nothing when I press on
  the "Test" button.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-media 2.32.0-0ubuntu5
  Uname: Linux 2.6.38-020638-generic x86_64
  Architecture: amd64
  Date: Wed Mar 16 20:30:19 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
  ProcEnviron:
   LANGUAGE=de_DE:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-media
  UpgradeStatus: Upgraded to natty on 2011-03-11 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/736349/+subscriptions

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

[Touch-packages] [Bug 1774904] Re: No defualt sound. Test speakers not working.

Hi, in my case, I think it was simply a missing package dependency.
Installing the libcanberra-pulse package fixed it for me.

gnome-control should probably add libcanberra-pulse to a proper
dependency rather than just recommends since it's likely common that
people would want to test speakers and the test silently failing (e.g.
control-centre doesn't even warn its missing the libs it needs) makes a
user (me for example) get lost (i.e. inspecting ALSA, etc) when the
silent test failure misleads.

Also noted at the end of: https://bugs.launchpad.net/ubuntu/+source
/gnome-media/+bug/736349

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

Title:
  No defualt sound. Test speakers not working.

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

Bug description:
  Default sound is silent, choosing another sound (ie. Sonar) plays the
  sound until the control panel is closed. Test speakers does not
  produce any sounds. Sounds and music work in FF and Rhythm Box.

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1766 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jun  3 21:10:36 2018
  InstallationDate: Installed on 2018-03-26 (69 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: CO96510J.86A.6100.2009.1004.2331
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DQ965GF
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD41676-402
  dmi.chassis.type: 3
  dmi.chassis.vendor: IN WIN
  dmi.chassis.version: IW-Z583
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrCO96510J.86A.6100.2009.1004.2331:bd10/04/2009:svnPrimeSystems:pnCF2007-965:pvr:rvnIntelCorporation:rnDQ965GF:rvrAAD41676-402:cvnINWIN:ct3:cvrIW-Z583:
  dmi.product.name: CF2007-965
  dmi.sys.vendor: Prime Systems

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

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

[Touch-packages] [Bug 1732411] Re: On upgrade, daemon-reexec should only be issued if safe

2018-11-13 Thread Pierre Schweitzer

A fix [1] in LXC was pushed recently and actually allows systemd daemon-
reexec without the cap sys_admin in a container.

We tested that it totally solved the issue for us.
Would it possible to move this bug report to the LXC project? And to ask for a 
backport of such fix to Xenial LXC?

Thanks!

[1]
https://github.com/lxc/lxc/commit/af949cc1938ff3a4e06148867a64d7715ce89a50

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

Title:
  On upgrade, daemon-reexec should only be issued if safe

Status in lxc package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New

Bug description:
  Dear all,

  Following up the bug #1713674, when executing systemd in a hardened
  LXC context, it might not be suitable to reexec systemd daemon, that
  would not be able to perform.

  For instance, in our LXC, we drop several capabilities, including
  sys_admin and we set /sys to read-only (in which, systemd will find
  its cgroups). This means, systemd cannot be reexecuted, it will fail
  to restart and will freeze (properly) at restart making the LXC
  container in frozen state (still working, but no new services
  startable, no interaction with systemd possible anymore).

  When upgrading systemd the debian package, as postinst, will always
  attempt to reexecute systemd, possibly breaking every other upgrade
  where a daemon restart is made in postinst, and leaving the system in
  a degraded state.

  It would likely be appropriate the check whether the reexecute can
  work will before performing it: checking capabilities, sys mount point
  perms, etc. If not applicable, not performing a reexucte and possibly
  print a message to the user.

  Occurs with Ubuntu Xenial 16.04.3 LTS and systemd 229-4ubuntu21.

  Cheers

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

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

[Touch-packages] [Bug 1165420] Re: Unable to access indicators from HUD

2018-10-28 Thread pierre

** Changed in: hud (Ubuntu)
 Assignee: (unassigned) => pierre (pierrefischer)

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

Title:
  Unable to access indicators from HUD

Status in Ayatana Design:
  Confirmed
Status in Unity HUD:
  Confirmed
Status in hud package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 12.10 I was able to use HUD to access Messaging menu and Gwibber's 
"Update Status" option there, making status updates to Twitter easy and fast.
  I could also use HUD to change my status in Empathy from Available to Busy 
and vice-versa.

  In Ubuntu 13.04 Beta HUD no longer finds the "Update Status" option when 
typing "Update Status" or "Update"
  Also writing "Available" "Away" or "Busy" no longer gives any results.

  Other indicators however are accessible and I can use HUD to Suspend
  my computer or to view Skype status or Ubuntu one indicator options.

  Repeating:
  1. Press alt key to start HUD
  2. Write "Update status" or "Available"

  What was expected:
  HUD should have shown options ether from Gwibber to Update Status or Empathy 
to change status to Available both available from the messaging indicator.

  What happened:
  HUD didn't find any results.

  Notes:
  I have Ubuntu 13.04 Beta 64bit upgraded from Ubuntu 12.10 64bits and I'm 
using proprietary fglrx drivers.

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

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

[Touch-packages] [Bug 1452193] Re: Backends can't look at FINAL_CONTENT_TYPE to determine MIME type of job

2018-10-09 Thread Pierre Ossman (Cendio AB)

I can confirm that this is fixed in (at least) 18.04.

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

Title:
  Backends can't look at FINAL_CONTENT_TYPE to determine MIME type of
  job

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  We have a custom cups backend ("thinlocal") that looks at
  FINAL_CONTENT_TYPE to find out whether the submitted job is
  application/pdf and if so, take special actions. The PPD for this
  backend accepts PDF:s directly through this line:

  *cupsFilter: "application/pdf 0 -"

  However, FINAL_CONTENT_TYPE is always set to printer/thinlocal, so the
  backend can't possibly determine the input format by looking at the
  FINAL_CONTENT_TYPE.

  This is broken with (at least):
   - Ubuntu 14.04 (cups 1.7.2),
   - Ubuntu 14.10 (cups 1.7.5)
   - Ubuntu 15.04 (cups 2.0.2).

  Related bug reports, upstream and elsewhere:
   - https://www.cups.org/str.php?L4494
   - https://bugzilla.redhat.com/show_bug.cgi?id=1010580
   - https://bugzilla.redhat.com/show_bug.cgi?id=1149244

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

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

[Touch-packages] [Bug 1762314] Re: Sound output too low

2018-09-10 Thread Pierre-Alexis Ciavaldini

Same issue here on T570 running Manjaro, this is the only bug report talking 
about the problem which seems not related to Ubuntu but to alsa. All sliders 
are up in alsamixer, sound is around half-volume compared to the Windows 
install. ALSA Driver Version: k4.14.67-1-MANJARO.
these did not help: 
https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture/Troubleshooting#Volume_is_too_low

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

Title:
  Sound output too low

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound output on lenovo p51s is too low. No option to go above 100% in volume 
settings. Download pulse audio volume control to raise application and output 
volume to 153%, which helps to some extent, but then leads to distortion. 
  Was running windows 10 on same system and audio was loud enough!
  Also after this morning
  s update, the volume keys no longer work, even after re-mapping them in 
shortcuts.3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jatin  2098 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Apr  8 22:50:04 2018
  InstallationDate: Installed on 2018-03-23 (17 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180307.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [20HCS06601, Realtek ALC298, Speaker, Internal] Background noise or 
low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1VET36W (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HCS06601
  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:bvrN1VET36W(1.26):bd10/03/2017:svnLENOVO:pn20HCS06601:pvrThinkPadP51s:rvnLENOVO:rn20HCS06601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51s
  dmi.product.name: 20HCS06601
  dmi.product.version: ThinkPad P51s
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1784897] [NEW] [HDA-Intel - HDA Intel PCH, playback] Playback problem

2018-08-01 Thread Pierre OLLIER

Public bug reported:

Plus de son sur la prise jack depuis le noyau 4.4.0.131. Le noyau
4.4.0.127 continue à bien fonctionner. Dell inspiron 5667.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
Uname: Linux 4.4.0-131-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pierre 1521 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Aug  1 18:28:12 2018
InstallationDate: Installed on 2016-10-12 (658 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Audio interne - HDA Intel PCH
Symptom_Type: None of the above
Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.9
dmi.board.name: 03XWWJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5767:pvr:rvnDellInc.:rn03XWWJ:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.name: Inspiron 5767
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T10:48:57.448177

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


** Tags: amd64 apport-bug xenial

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Plus de son sur la prise jack depuis le noyau 4.4.0.131. Le noyau
  4.4.0.127 continue à bien fonctionner. Dell inspiron 5667.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134
  Uname: Linux 4.4.0-131-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1521 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Aug  1 18:28:12 2018
  InstallationDate: Installed on 2016-10-12 (658 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Audio interne - HDA Intel PCH
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.9
  dmi.board.name: 03XWWJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5767:pvr:rvnDellInc.:rn03XWWJ:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5767
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T10:48:57.448177

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-19 Thread Aurélien PIERRE

I have the same problem of power drains even when prime-select is on
intel. I know for sure that the nvidia GPU is running because the
external HDMI port is working and shouldn't since it's wired to the GPU.

 sudo sh -c 'echo auto > /sys/bus/pci/devices/\:01\:00.0/power/control'
 sudo sh -c "echo "1" > remove"

gives no result on my system (Nvidia Quadro M2000M/Thinkpad P51).

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Touch-packages] [Bug 1762603] Re: bluetooth keeps turning off

2018-04-10 Thread Aurélien PIERRE

Ok I troubleshot this problem.

Apparently, it came from the package `connman`, an Intel utility to
manage wlan and bluetooth that I installed wrongly since it's intended
for embedded systems.

Removing it solved all my problems.

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

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

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

Title:
  bluetooth keeps turning off

Status in connman package in Ubuntu:
  Invalid

Bug description:
  the bluetooth worked well right after install. After a few reboots,
  it's impossible to keep it on and to connect devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 23:24:56 2018
  InstallationDate: Installed on 2018-04-08 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20HHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop 
vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET46W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40112 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1762603] Re: bluetooth keeps turning off

2018-04-10 Thread Aurélien PIERRE

Yes it looks like the same bug (at least for the GUI part), and it's a
Thinkpad as well.

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

Title:
  bluetooth keeps turning off

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  the bluetooth worked well right after install. After a few reboots,
  it's impossible to keep it on and to connect devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 23:24:56 2018
  InstallationDate: Installed on 2018-04-08 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20HHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop 
vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET46W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40112 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

2018-04-10 Thread Aurélien PIERRE

Same bug on Ubuntu 18.04 / Thinkpad P51.

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Fix Released
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  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:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1762603] Re: bluetooth keeps turning off

2018-04-09 Thread Aurélien PIERRE

Also I have tried with blueman instead, with and without acpi-calls-
dkms, tp-smapi-dkms, tlp installed, the issue remains.

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

Title:
  bluetooth keeps turning off

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  the bluetooth worked well right after install. After a few reboots,
  it's impossible to keep it on and to connect devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 23:24:56 2018
  InstallationDate: Installed on 2018-04-08 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20HHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop 
vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET46W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40112 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1762603] Re: bluetooth keeps turning off

2018-04-09 Thread Aurélien PIERRE

I mean reboots.

So, on boot, the airplane mode is turned on by default (for an unknwon
reason).

The rfkill output is attached above. I have to trigger several `sudo
rfkill unblock all` to actually have them unlocked (in command line).
But then, the GUI still shows the bluetooth switch as OFF. When I try to
enable the BT in the GUI, the gnome-control-center window freezes but no
device detection happens. Closing and re-opening the gnome-control-
center shows that BT is still OFF.

Using the BT hotkey from the laptop chenges nothing.

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

Title:
  bluetooth keeps turning off

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  the bluetooth worked well right after install. After a few reboots,
  it's impossible to keep it on and to connect devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 23:24:56 2018
  InstallationDate: Installed on 2018-04-08 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20HHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop 
vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET46W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40112 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1762603] [NEW] bluetooth keeps turning off

2018-04-09 Thread Aurélien PIERRE

Public bug reported:

the bluetooth worked well right after install. After a few reboots, it's
impossible to keep it on and to connect devices.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  9 23:24:56 2018
InstallationDate: Installed on 2018-04-08 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
InterestingModules: bnep btusb bluetooth
MachineType: LENOVO 20HHCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop 
vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/26/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1UET46W (1.20 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q40112 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P51
dmi.product.name: 20HHCTO1WW
dmi.product.version: ThinkPad P51
dmi.sys.vendor: LENOVO
hciconfig:

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


** Tags: amd64 apport-bug bionic

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

Title:
  bluetooth keeps turning off

Status in bluez package in Ubuntu:
  New

Bug description:
  the bluetooth worked well right after install. After a few reboots,
  it's impossible to keep it on and to connect devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 23:24:56 2018
  InstallationDate: Installed on 2018-04-08 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20HHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=f6fc1852-25c6-47a6-9776-4ed8b8d6b70e ro quiet splash elevator=noop 
vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1UET46W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q40112 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1UET46W(1.20):bd02/26/2018:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0Q40112WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P51
  dmi.product.name: 20HHCTO1WW
  dmi.product.version: ThinkPad P51
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1752528] Re: initramfs swretu up wrong swap partition for resuming when zram-config is active

2018-03-01 Thread Pierre-Etienne SCHNEIDER

Sorry. Mistyped. Read initramfs SETS UP wrong ..

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

Title:
  initramfs swretu up wrong swap partition for resuming when zram-config
  is active

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have a low end laptop on which using zram to improve memory (2GB
  only) is critical.

  When I have zram-config installed and running, every kernel update
  tells initramfs to try to resume from /dev/zram0 (which it can't it's
  compressed virtual memory!)

  At next reboot, computer locks up for one minute trying resuming from
  /dev/zram0 which it can't, then throws an error message "invalid
  resume partition" or the like, and proceeds on booting normally.
  Needless to say, it also breaks suspend mode.

  Is it possible to make initramfs-tools zram-aware or blacklist zram
  devices as being candidates for resuming?

  Yours truly. With great respect. Mr SCHNEIDER

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  1 10:10:19 2018
  InstallationDate: Installed on 2017-11-29 (91 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to bionic on 2018-02-25 (3 days ago)

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

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

[Touch-packages] [Bug 1752528] [NEW] initramfs swretu up wrong swap partition for resuming when zram-config is active

2018-03-01 Thread Pierre-Etienne SCHNEIDER

Public bug reported:

I have a low end laptop on which using zram to improve memory (2GB only)
is critical.

When I have zram-config installed and running, every kernel update tells
initramfs to try to resume from /dev/zram0 (which it can't it's
compressed virtual memory!)

At next reboot, computer locks up for one minute trying resuming from
/dev/zram0 which it can't, then throws an error message "invalid resume
partition" or the like, and proceeds on booting normally. Needless to
say, it also breaks suspend mode.

Is it possible to make initramfs-tools zram-aware or blacklist zram
devices as being candidates for resuming?

Yours truly. With great respect. Mr SCHNEIDER

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Mar  1 10:10:19 2018
InstallationDate: Installed on 2017-11-29 (91 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: Upgraded to bionic on 2018-02-25 (3 days ago)

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


** Tags: amd64 apport-bug bionic

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

Title:
  initramfs swretu up wrong swap partition for resuming when zram-config
  is active

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have a low end laptop on which using zram to improve memory (2GB
  only) is critical.

  When I have zram-config installed and running, every kernel update
  tells initramfs to try to resume from /dev/zram0 (which it can't it's
  compressed virtual memory!)

  At next reboot, computer locks up for one minute trying resuming from
  /dev/zram0 which it can't, then throws an error message "invalid
  resume partition" or the like, and proceeds on booting normally.
  Needless to say, it also breaks suspend mode.

  Is it possible to make initramfs-tools zram-aware or blacklist zram
  devices as being candidates for resuming?

  Yours truly. With great respect. Mr SCHNEIDER

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
  Uname: Linux 4.15.0-11-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  1 10:10:19 2018
  InstallationDate: Installed on 2017-11-29 (91 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to bionic on 2018-02-25 (3 days ago)

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

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

Re: [Touch-packages] [Bug 1739322] Re: Hazardous displays when coming back from sleep state

2018-02-17 Thread Pierre Wilch

Christopher M. Penalver,


- I tried to reproduce the problem after login with GNOME Flashback 
(Metacity) for 2 days.
I tried many things, but without success, everything worked perfectly.

- By awakening with Unity, the display comes back during one second, 
then every time becomes black again during another second, and then 
stays on with or without the blinking problem of parts of the screen.
With Metacity, as a normal behavior, the screen does not become black 
again during one second, and the display is immediately good, as expected.
The screen becoming black again is not normal and is a sign for a not 
mastered screen processing, pieces of code taking their liberty for 
undesirable results.

- I have noticed that the problem has more chance to occur after opening 
and closing several windows, and switching between them. Again today.

- It is possible that the problem appeared with the kernel release which 
began to manage Intel graphic cards.
I remember, without warranty, having feared the worse at that moment, 
_before_. Since, perhaps with Unity a crazy process is remaining on 
awakening.


Pierre Wilch


Le 16/02/2018 à 01:20, Christopher M. Penalver a écrit :
> Pierre Wilch:
>
> Regarding GNOME Flashback, one would have to install it via a terminal:
> sudo apt-get install gnome-session-flashback
>
> Once installed, and you restart to the login screen, GNOME Flashback
> (Metacity) should be an option.
>

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

Title:
  Hazardous displays when coming back from sleep state

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Conditions:
  - in the upper bar the display of the seconds must be enabled
    (in my case the entire date-and-time is displayed, excepted the week 
number);
  - system is set to automatically go into sleep state after the selected delay
    (in my case the option "lock the keyboard" is not enabled).
  On awakening, for example by using the shift touch, parts of the screen are 
blinking according to 1 second rate and 3 seconds cycle.
  Coming back to normal behavior needs to close and re-open windows.

  To help to reproduce:
  - edit a message with thunderbird;
  - select ubuntu "parameters";
  - select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
  - select "1 minute";
  - wait 1 minute and going into sleep state;
  - when in sleep state press the "shift" key;
  and then I have a blinking "Christmas tree", too complicated to be described.
  I tested it again 3 times why writing this post (firefox had also an opened 
window, under thunderbird; with firefox alone, the screen blinks only one time 
-should also not-).

  WORKAROUND: When the seconds are not displayed in the upper bar there
  is no problem.

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fb31]
  InstallationDate: Installed on 2017-06-29 (223 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: TOSHIBA SATELLITE PRO C850-1GR
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=7169ec32-1674-4c34-b45b-2001ed412887 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEPROC850-1GR:pvrPSCBXE-01T01GFR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  d

Re: [Touch-packages] [Bug 1739322] Re: Hazardous displays when coming back from sleep state

2018-02-15 Thread Pierre Wilch

Christopher M. Penalver,

Thank you for your help.

1)  I was using Ubuntu 16.04 since July 2016, and 14.04 before.
I think the problem appeared in spring or summer 2017 with an update.
I do not remember since when I put the seconds display in the upper bar. 
I think already in 2014, but without warranty.
In May 2017 I changed my hard disk from a 320 GB with Windows 10 in dual 
boot UEFI to a 1 TB without Windows, and made a fresh install of Ubuntu 
16.04 only.
I do not remember if the problem came at that time or later. There were 
many things to think about,... and other serious problems with the 16.04 
(now solved) .

2)  I clicked on your link about GNOME Flashback, tried a couple of 
clicks, but did not find the way to log in.
How should I do?
What is Metacity?


On the video I joined notice that the blinking of the screen happens 
simultaneously with the display of the seconds. You can improve the 
description in this way.


I discovered Ubuntu in April 2014.
At the beginning it worked by me on a SD card (legacy) to see what it 
was about, and since that time I have learned a lot, and it is not finished.
With Ubuntu/linux it is never finished.


Le 15/02/2018 à 19:16, Christopher M. Penalver a écrit :
> Pierre Wilch:
>
> 1)
>> "So long I remember, this bug appeared before september 2017. No problem in 
>> year 2016."
> What version of Ubuntu were you using in 2016 when this was not reproducible?
>   
> 2) To further root cause, could you please test for this problem by logging 
> into a GNOME Flashback (Metacity) session via 
> https://launchpad.net/ubuntu/+source/gnome-flashback and advise to the 
> results?
>
> ** Description changed:
>
> - Ubuntu 16.04.3 LTS, every updates done.
> -
>Conditions:
>- in the upper bar the display of the seconds must be enabled
> -   (in my case the entire date-and-time is displayed, excepted the week 
> number);
> - - system has set himself automatically in sleep state after the selected 
> delay
> -   (in my case the option "lock the keyboard" is not enabled).
> +   (in my case the entire date-and-time is displayed, excepted the week 
> number);
> + - system is set to automatically go into sleep state after the selected 
> delay
> +   (in my case the option "lock the keyboard" is not enabled).
>On awakening, for example by using the shift touch, parts of the screen 
> are blinking according to 1 second rate and 3 seconds cycle.
> - Coming back to normal behavior needs to close and re-open windows (no!, not 
> M$), etc...
> + Coming back to normal behavior needs to close and re-open windows.
>
>To help to reproduce:
>- edit a message with thunderbird;
>- select ubuntu "parameters";
>- select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
>- select "1 minute";
>- wait 1 minute and going into sleep state;
>- when in sleep state press the "shift" key;
>and then I have a blinking "Christmas tree", too complicated to be 
> described.
>I tested it again 3 times why writing this post (firefox had also an 
> opened window, under thunderbird; with firefox alone, the screen blinks only 
> one time -should also not-).
> - When the seconds are not displayed in the upper bar there is no problem.
>
> - Please do not blame me if xorg is not involved. A way to post had to be 
> found.
> - 'apt-cache policy pkgname' with or without sudo: 'Impossible de trouver le 
> paquet pkgname'.
> - ---
> + WORKAROUND: When the seconds are not displayed in the upper bar there is
> + no problem.
> +
> + ---
>.tmp.unity_support_test.0:
> -
> +
>ApportVersion: 2.20.1-0ubuntu2.15
>Architecture: amd64
>CompizPlugins: No value set for 
> `/apps/compiz-1/general/screen0/options/active_plugins'
>CompositorRunning: compiz
>CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>CompositorUnredirectFSW: true
>CurrentDesktop: Unity
>DistUpgraded: Fresh install
>DistroCodename: xenial
>DistroRelease: Ubuntu 16.04
>DistroVariant: ubuntu
>ExtraDebuggingInterest: Yes
>GraphicsCard:
> -  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
> (rev 09) (prog-if 00 [VGA controller])
> -Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
> Controller [1179:fb31]
> +  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
> (rev 09) (prog-if 00 [VGA controller])
> +    Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
> Controller [1179:fb31]
>InstallationDate: Installed on 2017-06-29 (223 days ago)
>InstallationMedia: Ubuntu 16.04.2 L

[Touch-packages] [Bug 1739322] Re: Hazardous displays when coming back from sleep state

2018-02-15 Thread Pierre Wilch

A new xorg version has been installed yesterday 14.02.2018.
I could make a video of the problem on my screen before that installation, and 
have joined it.
The bug as posted is still active with the new version.
It is not easy to reproduce. Sometimes it comes often, sometimes not.
Open and close several windows, switch between tasks..., or verify source code.
So long I remember, this bug appeared before september 2017. No problem in year 
2016.
On the video one can see that abnormal blinking stops on next going into sleep 
state.

** Attachment added: "Bug 1739322.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1739322/+attachment/5055814/+files/Bug%201739322.mp4

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

Title:
  Hazardous displays when coming back from sleep state

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.3 LTS, every updates done.

  Conditions:
  - in the upper bar the display of the seconds must be enabled
(in my case the entire date-and-time is displayed, excepted the week 
number);
  - system has set himself automatically in sleep state after the selected delay
(in my case the option "lock the keyboard" is not enabled).
  On awakening, for example by using the shift touch, parts of the screen are 
blinking according to 1 second rate and 3 seconds cycle.
  Coming back to normal behavior needs to close and re-open windows (no!, not 
M$), etc...

  To help to reproduce:
  - edit a message with thunderbird;
  - select ubuntu "parameters";
  - select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
  - select "1 minute";
  - wait 1 minute and going into sleep state;
  - when in sleep state press the "shift" key;
  and then I have a blinking "Christmas tree", too complicated to be described.
  I tested it again 3 times why writing this post (firefox had also an opened 
window, under thunderbird; with firefox alone, the screen blinks only one time 
-should also not-).
  When the seconds are not displayed in the upper bar there is no problem.

  Please do not blame me if xorg is not involved. A way to post had to be found.
  'apt-cache policy pkgname' with or without sudo: 'Impossible de trouver le 
paquet pkgname'.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fb31]
  InstallationDate: Installed on 2017-06-29 (223 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: TOSHIBA SATELLITE PRO C850-1GR
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=7169ec32-1674-4c34-b45b-2001ed412887 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEPROC850-1GR:pvrPSCBXE-01T01GFR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-1GR
  dmi.product.version: PSCBXE-01T01GFR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  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:

[Touch-packages] [Bug 1739322] xdpyinfo.txt

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1739322/+attachment/5050655/+files/xdpyinfo.txt

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

Title:
  Hazardous displays when coming back from sleep state

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.3 LTS, every updates done.

  Conditions:
  - in the upper bar the display of the seconds must be enabled
(in my case the entire date-and-time is displayed, excepted the week 
number);
  - system has set himself automatically in sleep state after the selected delay
(in my case the option "lock the keyboard" is not enabled).
  On awakening, for example by using the shift touch, parts of the screen are 
blinking according to 1 second rate and 3 seconds cycle.
  Coming back to normal behavior needs to close and re-open windows (no!, not 
M$), etc...

  To help to reproduce:
  - edit a message with thunderbird;
  - select ubuntu "parameters";
  - select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
  - select "1 minute";
  - wait 1 minute and going into sleep state;
  - when in sleep state press the "shift" key;
  and then I have a blinking "Christmas tree", too complicated to be described.
  I tested it again 3 times why writing this post (firefox had also an opened 
window, under thunderbird; with firefox alone, the screen blinks only one time 
-should also not-).
  When the seconds are not displayed in the upper bar there is no problem.

  Please do not blame me if xorg is not involved. A way to post had to be found.
  'apt-cache policy pkgname' with or without sudo: 'Impossible de trouver le 
paquet pkgname'.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fb31]
  InstallationDate: Installed on 2017-06-29 (223 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: TOSHIBA SATELLITE PRO C850-1GR
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=7169ec32-1674-4c34-b45b-2001ed412887 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEPROC850-1GR:pvrPSCBXE-01T01GFR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-1GR
  dmi.product.version: PSCBXE-01T01GFR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1739322] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1739322/+attachment/5050643/+files/Lsusb.txt

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

Title:
  Hazardous displays when coming back from sleep state

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.3 LTS, every updates done.

  Conditions:
  - in the upper bar the display of the seconds must be enabled
(in my case the entire date-and-time is displayed, excepted the week 
number);
  - system has set himself automatically in sleep state after the selected delay
(in my case the option "lock the keyboard" is not enabled).
  On awakening, for example by using the shift touch, parts of the screen are 
blinking according to 1 second rate and 3 seconds cycle.
  Coming back to normal behavior needs to close and re-open windows (no!, not 
M$), etc...

  To help to reproduce:
  - edit a message with thunderbird;
  - select ubuntu "parameters";
  - select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
  - select "1 minute";
  - wait 1 minute and going into sleep state;
  - when in sleep state press the "shift" key;
  and then I have a blinking "Christmas tree", too complicated to be described.
  I tested it again 3 times why writing this post (firefox had also an opened 
window, under thunderbird; with firefox alone, the screen blinks only one time 
-should also not-).
  When the seconds are not displayed in the upper bar there is no problem.

  Please do not blame me if xorg is not involved. A way to post had to be found.
  'apt-cache policy pkgname' with or without sudo: 'Impossible de trouver le 
paquet pkgname'.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fb31]
  InstallationDate: Installed on 2017-06-29 (223 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: TOSHIBA SATELLITE PRO C850-1GR
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=7169ec32-1674-4c34-b45b-2001ed412887 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEPROC850-1GR:pvrPSCBXE-01T01GFR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-1GR
  dmi.product.version: PSCBXE-01T01GFR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1739322] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1739322/+attachment/5050649/+files/ProcModules.txt

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

Title:
  Hazardous displays when coming back from sleep state

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.3 LTS, every updates done.

  Conditions:
  - in the upper bar the display of the seconds must be enabled
(in my case the entire date-and-time is displayed, excepted the week 
number);
  - system has set himself automatically in sleep state after the selected delay
(in my case the option "lock the keyboard" is not enabled).
  On awakening, for example by using the shift touch, parts of the screen are 
blinking according to 1 second rate and 3 seconds cycle.
  Coming back to normal behavior needs to close and re-open windows (no!, not 
M$), etc...

  To help to reproduce:
  - edit a message with thunderbird;
  - select ubuntu "parameters";
  - select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
  - select "1 minute";
  - wait 1 minute and going into sleep state;
  - when in sleep state press the "shift" key;
  and then I have a blinking "Christmas tree", too complicated to be described.
  I tested it again 3 times why writing this post (firefox had also an opened 
window, under thunderbird; with firefox alone, the screen blinks only one time 
-should also not-).
  When the seconds are not displayed in the upper bar there is no problem.

  Please do not blame me if xorg is not involved. A way to post had to be found.
  'apt-cache policy pkgname' with or without sudo: 'Impossible de trouver le 
paquet pkgname'.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fb31]
  InstallationDate: Installed on 2017-06-29 (223 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: TOSHIBA SATELLITE PRO C850-1GR
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=7169ec32-1674-4c34-b45b-2001ed412887 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEPROC850-1GR:pvrPSCBXE-01T01GFR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-1GR
  dmi.product.version: PSCBXE-01T01GFR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1739322] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1739322/+attachment/5050647/+files/ProcInterrupts.txt

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

Title:
  Hazardous displays when coming back from sleep state

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04.3 LTS, every updates done.

  Conditions:
  - in the upper bar the display of the seconds must be enabled
(in my case the entire date-and-time is displayed, excepted the week 
number);
  - system has set himself automatically in sleep state after the selected delay
(in my case the option "lock the keyboard" is not enabled).
  On awakening, for example by using the shift touch, parts of the screen are 
blinking according to 1 second rate and 3 seconds cycle.
  Coming back to normal behavior needs to close and re-open windows (no!, not 
M$), etc...

  To help to reproduce:
  - edit a message with thunderbird;
  - select ubuntu "parameters";
  - select "Luminosité & verrouillage" ("Brightness & keyboard locking"?);
  - select "1 minute";
  - wait 1 minute and going into sleep state;
  - when in sleep state press the "shift" key;
  and then I have a blinking "Christmas tree", too complicated to be described.
  I tested it again 3 times why writing this post (firefox had also an opened 
window, under thunderbird; with firefox alone, the screen blinks only one time 
-should also not-).
  When the seconds are not displayed in the upper bar there is no problem.

  Please do not blame me if xorg is not involved. A way to post had to be found.
  'apt-cache policy pkgname' with or without sudo: 'Impossible de trouver le 
paquet pkgname'.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems 3rd Gen Core processor Graphics 
Controller [1179:fb31]
  InstallationDate: Installed on 2017-06-29 (223 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: TOSHIBA SATELLITE PRO C850-1GR
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=7169ec32-1674-4c34-b45b-2001ed412887 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/01/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 6.80
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PLCSF8
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr6.80:bd10/01/2013:svnTOSHIBA:pnSATELLITEPROC850-1GR:pvrPSCBXE-01T01GFR:rvnIntel:rnPLCSF8:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE PRO C850-1GR
  dmi.product.version: PSCBXE-01T01GFR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1739322] XorgLog.txt