[Touch-packages] [Bug 1856731] Re: Cannot add a Google accounts with GOA

2020-07-10 Thread Launchpad Bug Tracker
[Expired for gnome-online-accounts (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Cannot add a Google accounts with GOA

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

Bug description:
  On a freshly installed 20.04 system, going through the initial setup
  and I'm presented with the Online Accounts panel where I selected
  Google, entered my email and password. Then Google's 2-factor
  authentication kicks in and instructs me to check my phone. I do and
  approve the connection, but the online accounts page on the laptop
  never updates until it eventually asks if I want the authentication to
  be resent.

  There are two older bugs that looks like this - both are fix committed:
  - https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1687019
  - https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1175122

  Opening a new bug since the issue definitely exists and the other bugs
  have been fix committed for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 17 09:17:06 2019
  InstallationDate: Installed on 2019-12-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1857182] Re: Unable to Google Online Account in Kubuntu 19.10

2020-07-10 Thread Launchpad Bug Tracker
[Expired for signon-ui (Ubuntu) because there has been no activity for
60 days.]

** Changed in: signon-ui (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Unable to Google Online Account in Kubuntu 19.10

Status in signon-ui package in Ubuntu:
  Expired

Bug description:
  Adding Google Online account in Kubuntu, i am able to enter my google 
username and password after that a message is received: Sign in with Google 
temporarily disabled for this app
  This app has not been verified yet by Google in order to use Google Sign In.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: signon-ui-x11 0.17+18.04.20171027+really20160406-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Dec 21 01:17:36 2019
  ExecutablePath: /usr/bin/signon-ui
  InstallationDate: Installed on 2019-12-20 (1 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: signon-ui
  UpgradeStatus: No upgrade log present (probably fresh install)
  XsessionErrors:
   (pcmanfm:9039): Gtk-WARNING **: 23:27:13.685: Unable to locate theme engine 
in module_path: "adwaita",
   (pcmanfm:9039): Gtk-WARNING **: 23:27:13.691: Unable to locate theme engine 
in module_path: "adwaita",

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

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


[Touch-packages] [Bug 1877502] Re: package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado

2020-07-10 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade:
  problemas de dependência - deixando desconfigurado

Status in cups package in Ubuntu:
  Expired

Bug description:
  I don't know to tell you about the fail.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: cups-core-drivers 2.2.12-2ubuntu1.1
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Fri May  8 01:15:08 2020
  ErrorMessage: problemas de dependência - deixando desconfigurado
  InstallationDate: Installed on 2019-11-19 (170 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Inspiron 5437
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic 
root=UUID=d3150b7f-3c9a-4bc8-ac65-8e341339d22b ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: cups
  Title: package cups-core-drivers 2.2.12-2ubuntu1.1 failed to install/upgrade: 
problemas de dependência - deixando desconfigurado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 01PN4H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd09/09/2019:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn01PN4H:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5437
  dmi.product.sku: Inspiron 5437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1877542] Re: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver

2020-07-10 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253  alsa-driver

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Hello,
  After last general update sound stops working on all interfaces. speakers, 
headphones nor HDMI provide any sound output even bluetooth headphones can't be 
connected.
  It seems that interface is connected to HDMI
  aplay -l

   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3]
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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


[Touch-packages] [Bug 1877717] Re: [HP Envy] Sound stop working after wakeup

2020-07-10 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [HP Envy] Sound stop working after wakeup

Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  I don't know how to reproduce this bug. 
  Sometimes after notebook wakup sound stop working.
  pulseaudio -k fixes this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1925 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat May  9 15:43:32 2020
  InstallationDate: Installed on 2018-04-03 (766 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to focal on 2020-04-24 (14 days ago)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 83C9
  dmi.board.vendor: HP
  dmi.board.version: 32.59
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/29/2017:svnHP:pnHPEnvy:pvrType1ProductConfigId:rvnHP:rn83C9:rvr32.59:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV NOTEBOOK
  dmi.product.name: HP Envy
  dmi.product.sku: 2PQ29EA#ACB
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Touch-packages] [Bug 1878026] Re: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No sound at all

2020-07-10 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No
  sound at all

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  There is no sound at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  abhi   1362 F pulseaudio
   /dev/snd/controlC0:  abhi   1362 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 11 20:31:56 2020
  InstallationDate: Installed on 2020-05-06 (5 days ago)
  InstallationMedia: It
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  abhi   1362 F pulseaudio
   /dev/snd/controlC0:  abhi   1362 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP Pavilion 15 Notebook PC, Realtek ALC3241, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/11/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2281
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 77.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.06:bd06/11/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr097610405F1610180:rvnHewlett-Packard:rn2281:rvr77.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.sku: G8D90PA#ACJ
  dmi.product.version: 097610405F1610180
  dmi.sys.vendor: Hewlett-Packard

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

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


[Touch-packages] [Bug 1887207] Re: [Logitech USB Headset] Mute mic button does nothing

2020-07-10 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  [Logitech USB Headset] Mute mic button does nothing

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Pressing the headset button for muting the microphone does nothing (confirmed 
by xev).
  The volume control buttons from the headset work fine.
  Muting the mic from the settings panel or using the keyboard shortcut work 
fine.
  USB Headset model Logitech H390.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hausen 1143 F pulseaudio
   /dev/snd/pcmC1D0c:   hausen 1143 F...m pulseaudio
   /dev/snd/pcmC1D0p:   hausen 1143 F...m pulseaudio
   /dev/snd/controlC0:  hausen 1143 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 22:12:36 2020
  InstallationDate: Installed on 2020-06-27 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Headset 
successful
  Symptom_Card: Headset H390 - Logitech USB Headset
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Headset successful
  Symptom_Type: None of the above
  Title: [USB-Audio - Logitech USB Headset, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W110ER
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/25/2012:svnCLEVOCO.:pnW110ER:pvrN/A:rvnCLEVOCO.:rnW110ER:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: W110ER
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.

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

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


[Touch-packages] [Bug 1887208] Re: May be xorg

2020-07-10 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  May be xorg

Status in xorg package in Ubuntu:
  New

Bug description:
  My system reports something problem.
  Saying xorg crash

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
  Uname: Linux 4.15.0-109-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jul 11 10:45:09 2020
  DistUpgraded: 2020-07-05 12:47:35,837 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: ./xorg_fix_proprietary.py 
を子プロセスとして起動できませんでした: No such file or directory (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  InstallationDate: Installed on 2015-09-24 (1751 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Build amd64 LIVE Binary 
20140422-09:40
  MachineType: ASUS All Series
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic 
root=UUID=1f04dac6-7535-44a7-8ea2-e3d566af9feb ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2020-07-05 (5 days ago)
  dmi.bios.date: 04/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3602:bd04/08/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sun Jul  5 11:17:27 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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


[Touch-packages] [Bug 1887208] [NEW] May be xorg

2020-07-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

My system reports something problem.
Saying xorg crash

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18
Uname: Linux 4.15.0-109-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Jul 11 10:45:09 2020
DistUpgraded: 2020-07-05 12:47:35,837 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: ./xorg_fix_proprietary.py 
を子プロセスとして起動できませんでした: No such file or directory (8))
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
InstallationDate: Installed on 2015-09-24 (1751 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Build amd64 LIVE Binary 
20140422-09:40
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic 
root=UUID=1f04dac6-7535-44a7-8ea2-e3d566af9feb ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2020-07-05 (5 days ago)
dmi.bios.date: 04/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3602
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H97M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3602:bd04/08/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sun Jul  5 11:17:27 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
May be xorg
https://bugs.launchpad.net/bugs/1887208
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1887207] [NEW] [Logitech USB Headset] Mute mic button does nothing

2020-07-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Pressing the headset button for muting the microphone does nothing (confirmed 
by xev).
The volume control buttons from the headset work fine.
Muting the mic from the settings panel or using the keyboard shortcut work fine.
USB Headset model Logitech H390.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  hausen 1143 F pulseaudio
 /dev/snd/pcmC1D0c:   hausen 1143 F...m pulseaudio
 /dev/snd/pcmC1D0p:   hausen 1143 F...m pulseaudio
 /dev/snd/controlC0:  hausen 1143 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 22:12:36 2020
InstallationDate: Installed on 2020-06-27 (13 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:Headset successful
Symptom_Card: Headset H390 - Logitech USB Headset
Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Headset successful
Symptom_Type: None of the above
Title: [USB-Audio - Logitech USB Headset, recording] Recording problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/25/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: W110ER
dmi.board.vendor: CLEVO CO.
dmi.board.version: N/A
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: CLEVO CO.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/25/2012:svnCLEVOCO.:pnW110ER:pvrN/A:rvnCLEVOCO.:rnW110ER:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: W110ER
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: N/A
dmi.sys.vendor: CLEVO CO.

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


** Tags: amd64 apport-bug focal
-- 
[Logitech USB Headset] Mute mic button does nothing
https://bugs.launchpad.net/bugs/1887207
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver in Ubuntu.

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


[Touch-packages] [Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

2020-07-10 Thread Ramkumar Natarajan
*** This bug is a duplicate of bug 520546 ***
https://bugs.launchpad.net/bugs/520546

I had the same problem in Ubuntu 16.04.6 LTS 64-bit
running `sudo kbd_mode -s` solved it

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in console-setup package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

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

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


[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output

2020-07-10 Thread Hui Wang
Oh, got it, I put 2 whitespace before the email line. Will put 1 in the
future.

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

Title:
  [SRU] plug headset won't proper reconfig ouput to it on machine with
  default output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  This is for pulseaudio bionic:

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, the active profile is Off, after users plug a
  headset to it and users select the headset from the pop-up dialogue,
  users expect the profile changes to analog-stereo (headset is on it),
  but the active_profile is still Off.

  [Fix]
  Upstream already has a patch to fix it, cherrypiack that patch to bionic.
  And that patch is already in the eoan, focal, ...

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and select the headset from UI, the profile changes to
  analog-stereo, and play some sound, we could hear it from the headset

  [Regression Risk]
  Low, this patch is already in the upstream for a long time, and it is
  already in the eoan and focal.


  
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.

  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

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

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


[Touch-packages] [Bug 1887198] Re: Screen Freeze

2020-07-10 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Screen Freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  When changing user or logging off of ubuntu-desktop got a screen
  freeze that I can't get out of. No response from keyboard or mouse.
  After some time screen goes black with cursor flicking at the bottom.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-1013.13-raspi 5.4.44
  Uname: Linux 5.4.0-1013-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: arm64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  Date: Fri Jul 10 20:05:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   
  ImageMediaBuild: 20200423.1
  Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 
3.0 Host Controller
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 17ef:600e Lenovo 
   Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1920 
bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:7C:B3:EE 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  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 N/A
  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/1887198/+subscriptions

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


[Touch-packages] [Bug 1887198] [NEW] Screen Freeze

2020-07-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When changing user or logging off of ubuntu-desktop got a screen freeze
that I can't get out of. No response from keyboard or mouse. After some
time screen goes black with cursor flicking at the bottom.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-1013.13-raspi 5.4.44
Uname: Linux 5.4.0-1013-raspi aarch64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: arm64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
Date: Fri Jul 10 20:05:57 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 
ImageMediaBuild: 20200423.1
Lspci-vt: -[:00]---00.0-[01]00.0  VIA Technologies, Inc. VL805 USB 3.0 
Host Controller
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 17ef:600e Lenovo 
 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1920 
bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:7C:B3:EE 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
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 N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
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 N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: apport-bug arm64 focal ubuntu uec-images
-- 
Screen Freeze
https://bugs.launchpad.net/bugs/1887198
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 1827159] Re: check_all_disks includes squashfs /snap/* which are 100%

2020-07-10 Thread Bryce Harrington
df no longer shows squashfs mounts by default, as of today's coreutils
update

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

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

Title:
  check_all_disks includes squashfs /snap/* which are 100%

Status in Nagios Charm:
  Fix Released
Status in coreutils package in Ubuntu:
  Fix Released
Status in monitoring-plugins package in Ubuntu:
  Fix Released

Bug description:
  [Impact]
  False positive reports are generated in monitoring tools when artificial 
filesystems are mounted, since they show 100% disk utilization, and thus add 
unnecessary (but dire sounding) "DISK CRITICAL" noise.

  [Test Case]
  $ lxc create ubuntu-daily:19.10/amd64 lp1827159
  $ lxc exec lp1827159 bash
  # apt-get -y update
  # apt-get install monitoring-plugins
  # snap install gnome-calculator
  [...]
  # /usr/lib/nagios/plugins/check_disk -w 10 -c 10
  DISK CRITICAL - free space: / 1903 MB (1% inode=78%); /dev 0 MB (100% 
inode=99%); /dev/full 16018 MB (100% inode=99%); /dev/null 16018 MB (100% 
inode=99%); /dev/random 16018 MB (100% inode=99%); /dev/tty 16018 MB (100% 
inode=99%); /dev/urandom 16018 MB (100% inode=99%); /dev/zero 16018 MB (100% 
inode=99%); /dev/fuse 16018 MB (100% inode=99%); /dev/net/tun 16018 MB (100% 
inode=99%); /dev/lxd 0 MB (100% inode=99%); /dev/.lxd-mounts 0 MB (100% 
inode=99%); /dev/shm 16041 MB (100% inode=99%); /run 3208 MB (99% inode=99%); 
/run/lock 5 MB (100% inode=99%); /sys/fs/cgroup 16041 MB (100% inode=99%); 
/snap 1903 MB (1% inode=78%); /run/snapd/ns 3208 MB (99% inode=99%);| 
/=71MB;119160;119160;0;119170 /dev=0MB;-10;-10;0;0 
/dev/full=0MB;16008;16008;0;16018 /dev/null=0MB;16008;16008;0;16018 
/dev/random=0MB;16008;16008;0;16018 /dev/tty=0MB;16008;16008;0;16018 
/dev/urandom=0MB;16008;16008;0;16018 /dev/zero=0MB;16008;16008;0;16018 
/dev/fuse=0MB;16008;16008;0;16018 /dev/net/tun=0MB;16008;16008;0;16018 
/dev/lxd=0MB;-10;-10;0;0 /dev/.lxd-mounts=0MB;-10;-10;0;0 
/dev/shm=0MB;16031;16031;0;16041 /run=0MB;3198;3198;0;3208 
/run/lock=0MB;-5;-5;0;5 /sys/fs/cgroup=0MB;16031;16031;0;16041 
/snap=71MB;119160;119160;0;119170 /run/snapd/ns=0MB;3198;3198;0;3208

  # /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X squashfs
  DISK CRITICAL - free space: /dev 0 MB (100% inode=99%); /dev/lxd 0 MB (100% 
inode=99%); /dev/.lxd-mounts 0 MB (100% inode=99%); /run/lock 5 MB (100% 
inode=99%);| /=111392MB;119160;119160;0;119170 /dev=0MB;-10;-10;0;0 
/dev/full=0MB;16008;16008;0;16018 /dev/null=0MB;16008;16008;0;16018 
/dev/random=0MB;16008;16008;0;16018 /dev/tty=0MB;16008;16008;0;16018 
/dev/urandom=0MB;16008;16008;0;16018 /dev/zero=0MB;16008;16008;0;16018 
/dev/fuse=0MB;16008;16008;0;16018 /dev/net/tun=0MB;16008;16008;0;16018 
/dev/lxd=0MB;-10;-10;0;0 /dev/.lxd-mounts=0MB;-10;-10;0;0 
/dev/shm=0MB;16031;16031;0;16041 /run=0MB;3198;3198;0;3208 
/run/lock=0MB;-5;-5;0;5 /sys/fs/cgroup=0MB;16031;16031;0;16041 
/snap=111392MB;119160;119160;0;119170 /run/snapd/ns=0MB;3198;3198;0;3208

  # /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X tmpfs
  DISK OK| /=71MB;119160;119160;0;119170 /dev/full=0MB;16008;16008;0;16018 
/dev/null=0MB;16008;16008;0;16018 /dev/random=0MB;16008;16008;0;16018 
/dev/tty=0MB;16008;16008;0;16018 /dev/urandom=0MB;16008;16008;0;16018 
/dev/zero=0MB;16008;16008;0;16018 /dev/fuse=0MB;16008;16008;0;16018 
/dev/net/tun=0MB;16008;16008;0;16018 /snap=71MB;119160;119160;0;119170

  [Regression Potential]
  As this alters the logic of how out-of-space checks are handled, relevant 
issues to keep an eye out for would relate to filesystem checks reporting 
improperly.  These tools underlay a few different front-ends, so regression 
bugs may get filed in a few different places, however they will tend to display 
error messages involving check_disk, nagios, and either tmpfs or tracefs.

  Note that there are likely other synthetic filesystems beyond tmpfs
  and tracefs (e.g. udev, usbfs, devtmpfs, fuse.*, ...) which might also
  cause similar false positives; these should be handled as separate
  bugs, although they can likely be fixed the same way.

  [Fix]
  monitoring-plugins is modified to exclude the unwanted filesystems by 
default, in check_disk.c (see patch).

  [Discussion]
  There have been several bug reports filed about false positives with 
different synthetic file systems (see Dupes), including tracefs, squashfs, and 
tmpfs.  The commonly discussed workaround is to exclude these when running the 
tools (e.g. using the '-X ' parameter for check_all_disks).  Since wrappers 
are typically used for running the underlying tools, it is possible to add a 
string of -X... parameters.

  However, a cleaner solution is possible.  monitoring-plugins'
  check_disk.c maintains an internal exclusion list, fs_exclude_list,
  which already excludes iso9660, and can be 

[Touch-packages] [Bug 737617] Re: [USB-Audio - USB Audio DAC] FiiO E7/TI Burr-Brown: Volume control does not work

2020-07-10 Thread Linuxslate
This bug affects me with a PCM2706C bare DAC (USB Soundcard standalone
board).  I use 2 other very similar external USB DAC's (Different
chipsets) and the volume control works fine with them.  Also verified on
a laptop.  Both Laptop and Desktop are running 18.04.4.4

At anything above silent, I get full volume.  The volume for the
specific source (application) can be adjusted under the Playback tab
(software (ALSA) volume).

This is particularly obnoxious since each new sound begins playback at
full volume.

I believe this is a kernel bug for this particular USB DAC.

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

Title:
  [USB-Audio - USB Audio DAC] FiiO E7/TI Burr-Brown: Volume control does
  not work

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  The volume control for the FiiO E7 USB sound card doesn't work. Tested
  with the normal gnome volume control and in alsamixer. 0% mutes the
  audio, everything larger than 0% is full volume. Alsamixer only shows
  one control, labeled "PCM". The chipset is a TI Burr-Brown PCM2706.
  Might be related to #559939 (different chipset, though).

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: alsa-base 1.0.23+dfsg-1ubuntu4
  ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
  Uname: Linux 2.6.35-28-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  moritz 2265 F pulseaudio
   /dev/snd/pcmC1D0p:   moritz 2265 F...m pulseaudio
   /dev/snd/controlC0:  moritz 2265 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfbff4000 irq 51'
 Mixer name : 'Realtek ALC892'
 Components : 'HDA:10ec0892,1458a002,00100302'
 Controls  : 34
 Simple ctrls  : 18
  Card1.Amixer.info:
   Card hw:1 'default'/'Burr-Brown from TI   USB Audio DACat 
usb-:00:1a.1-1, full s'
 Mixer name : 'USB Mixer'
 Components : 'USB08bb:2706'
 Controls  : 2
 Simple ctrls  : 1
  Card2.Amixer.info:
   Card hw:2 'NVidia'/'HDA NVidia at 0xf9ffc000 irq 17'
 Mixer name : 'Nvidia GPU 12 HDMI/DP'
 Components : 'HDA:10de0012,10de0101,00100100'
 Controls  : 16
 Simple ctrls  : 4
  Date: Fri Mar 18 15:28:48 2011
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LC_MESSAGES=en_GB.UTF-8
   SHELL=/bin/bash
  SelectedCard: 1 default USB-Audio - USB Audio DAC
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [USB-Audio - USB Audio DAC   ] Playback problem
  dmi.bios.date: 08/20/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5
  dmi.board.name: H55N-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd08/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55N-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55N-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H55N-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect

2020-07-10 Thread John Erling Blad
Slightly different machine, running 20.04 LTS, but not too different I
guess. Uses the same BT-400 dongle as the other machine, the Hama dongle
seems to create additional problems even if it should use the same chip.

Also tried Fedora 32 from a live USB stick, it had the same problem.

I wonder if it somehow is triggered by sampling rate, number of bits,
encoding, or something similar as it wasn't triggered while I saw “The
Old Guard” but when I started “Nighfliers” it emerged pretty fast.

It seems to start with an increasing delay (lack of sync) until it
fails.

When it did fail before the apport report the sound in my Bluetooth
headphones stopped, but it was still connected in the Bluetooth pane in
“preference”. I turned the headphones off, but they were still listed as
connected. Turned them back on, still connected. Tried to manually set
the output device, no change. Then ran apport-collect.

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [

[Touch-packages] [Bug 1886714] Lsusb-v.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1886714/+attachment/5391484/+files/Lsusb-v.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | fgrep 

[Touch-packages] [Bug 1886714] ProcInterrupts.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1886714/+attachment/5391488/+files/ProcInterrupts.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg 

[Touch-packages] [Bug 1886714] rfkill.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1886714/+attachment/5391492/+files/rfkill.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | fgrep 'sound'
  

[Touch-packages] [Bug 1886714] getfacl.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1886714/+attachment/5391491/+files/getfacl.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | fgrep 

[Touch-packages] [Bug 1886714] syslog.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1886714/+attachment/5391493/+files/syslog.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | fgrep 'sound'
  

[Touch-packages] [Bug 1886714] UdevDb.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1886714/+attachment/5391490/+files/UdevDb.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | fgrep 'sound'
  

[Touch-packages] [Bug 1886714] ProcCpuinfoMinimal.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1886714/+attachment/5391486/+files/ProcCpuinfoMinimal.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  

[Touch-packages] [Bug 1886714] Lspci-vt.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1886714/+attachment/5391481/+files/Lspci-vt.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | fgrep 

[Touch-packages] [Bug 1886714] ProcModules.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1886714/+attachment/5391489/+files/ProcModules.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | 

[Touch-packages] [Bug 1886714] Lspci.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1886714/+attachment/5391480/+files/Lspci.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | fgrep 'sound'
  [ 

[Touch-packages] [Bug 1886714] Lsusb-t.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1886714/+attachment/5391483/+files/Lsusb-t.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | fgrep 

[Touch-packages] [Bug 1886714] Lsusb.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1886714/+attachment/5391482/+files/Lsusb.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | fgrep 'sound'
  [ 

[Touch-packages] [Bug 1886714] ProcEnviron.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1886714/+attachment/5391487/+files/ProcEnviron.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | 

[Touch-packages] [Bug 1886714] ProcCpuinfo.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1886714/+attachment/5391485/+files/ProcCpuinfo.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | 

[Touch-packages] [Bug 1886714] Dependencies.txt

2020-07-10 Thread John Erling Blad
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1886714/+attachment/5391479/+files/Dependencies.txt

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

Title:
  Bluetooth disconnects, and then sound fails on reconnect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.

  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover
  when it happen. I wonder if I started noticing the problem under
  Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x.
  I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record,
  the bug also persisted in Ubu 18.04 for as long as I was using it.)

  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably
  be replaced when I have time to rebuild everything. ;)

  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1
  (001.002.014) build 1467”. I have also used other dongles, but it
  seems like all of them has the same chipset.

  Now…

  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)

  It may take 5–10 minutes and up to several hours before it
  disconnects.

  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)

  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.

  Problem 1

  The dongle is rather hot when it disconnects. This is mere
  speculation, but I wonder if the disconnect happen because either the
  mainboard gives to little current and thus it fails due to voltage
  drop, or it fails due to overheating. It seems like the port should
  have enough current to sustain the dongle, but I wonder if the
  mainboard could let several ports share the same power source, and
  thus it fail to deliver enough current. There are other devices
  powered by the USB ports, and they don't seem to fail, which seems
  likely to happen if power is the issue.

  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like
  the issue can be triggered by moving away from the computer. That
  would give higher tx power, which could make the dongle overheat or
  mainboard could fail to provide enough current.

  Is there any way to get a more specific failure report from the
  dongle?

  Problem 2

  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been
  able to figure out what makes the sound system fail, and I have not
  been able to make it recover. Only way to recover seems to be to do a
  cold reboot. A simple warm reboot does not fix the problem, but this
  can be related to problem 1.

  A few dumps

  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11

  john@hydra:~$ dmesg | 

[Touch-packages] [Bug 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect

2020-07-10 Thread John Erling Blad
apport information

** Tags added: apport-collected focal

** Description changed:

  This bug has persisted over several years, and several versions, and
  after a lot of investigation I'm not really any closer on what's going
  on.
  
  I have two pretty old GA MA78gm S2H mainboards, configured slightly
  different, and otherwise working properly. Both of them have run both
  Ubuntu and Windows. The problem seems to have been minimized when
  running Win10, and even if it is there it seems like Win10 recover when
  it happen. I wonder if I started noticing the problem under Ubuntu 14.x,
  but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running
  Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also
  persisted in Ubu 18.04 for as long as I was using it.)
  
  It isn't really an option to switch the mainboards, as there are too
  much custom-builds running on them for the moment. They will probably be
  replaced when I have time to rebuild everything. ;)
  
  To make Bluetooth work I use an ASUS USB-BT400, which report as
  “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014)
  build 1467”. I have also used other dongles, but it seems like all of
  them has the same chipset.
  
  Now…
  
  Given I restart the computer
  And boot into Ubuntu 19.10
  And log in as myself
  And attach a pair of Sony MDR-ZX770BN
  When I listen to sound from a movie with A2DP
  Then at some random point it start to lag noticeably (sound becomes scratchy)
  And suddenly disconnects (at this point it seems like it is Bluetooth that 
disconnects)
  
  It may take 5–10 minutes and up to several hours before it disconnects.
  
  Given I turn the headphones off
  And back on
  When it reconnects to the computer
  Then the computer fails to enable the sound device (visible in the preference 
manager f.ex.)
  
  There are several reports of various equipments that disconnect, and I
  wonder if this could be the same problem.
  
  Problem 1
  
  The dongle is rather hot when it disconnects. This is mere speculation,
  but I wonder if the disconnect happen because either the mainboard gives
  to little current and thus it fails due to voltage drop, or it fails due
  to overheating. It seems like the port should have enough current to
  sustain the dongle, but I wonder if the mainboard could let several
  ports share the same power source, and thus it fail to deliver enough
  current. There are other devices powered by the USB ports, and they
  don't seem to fail, which seems likely to happen if power is the issue.
  
  The issue seems to be somewhat related to the quality of the audio,
  which makes me wonder whether higher quality gives more transferred
  data, which again gives higher power consumption. It also seems like the
  issue can be triggered by moving away from the computer. That would give
  higher tx power, which could make the dongle overheat or mainboard could
  fail to provide enough current.
  
  Is there any way to get a more specific failure report from the dongle?
  
  Problem 2
  
  After the headphone reconnects it seems like the sound system isn't
  working properly. I've been checking, and everything seems correct,
  still the headphone is missing as an output device. I have not been able
  to figure out what makes the sound system fail, and I have not been able
  to make it recover. Only way to recover seems to be to do a cold reboot.
  A simple warm reboot does not fix the problem, but this can be related
  to problem 1.
  
  A few dumps
  
  john@hydra:~$ dmesg | fgrep 'Blue'
  [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0
  [8.417252] Bluetooth: Core ver 2.22
  [8.417280] Bluetooth: HCI device and connection manager initialized
  [8.417284] Bluetooth: HCI socket layer initialized
  [8.417286] Bluetooth: L2CAP socket layer initialized
  [8.417301] Bluetooth: SCO socket layer initialized
  [8.779706] Bluetooth: hci0: BCM: chip id 63
  [8.780703] Bluetooth: hci0: BCM: features 0x07
  [8.796682] Bluetooth: hci0: hydra
  [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
  [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device
  [   10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   10.571442] Bluetooth: BNEP filters: protocol multicast
  [   10.571448] Bluetooth: BNEP socket layer initialized
  [  630.835385] Bluetooth: RFCOMM TTY layer initialized
  [  630.835393] Bluetooth: RFCOMM socket layer initialized
  [  630.835398] Bluetooth: RFCOMM ver 1.11
  
  john@hydra:~$ dmesg | fgrep 'sound'
  [7.920552] input: HDA ATI SB Rear Mic as 
/devices/pci:00/:00:14.2/sound/card0/input27
  [7.920612] input: HDA ATI SB Front Mic as 
/devices/pci:00/:00:14.2/sound/card0/input28
  [7.920657] input: HDA ATI SB Line as 
/devices/pci:00/:00:14.2/sound/card0/input29
  [7.920704] input: HDA ATI SB 

[Touch-packages] [Bug 1755138] Re: Update URL to project Homepage in package metadata

2020-07-10 Thread Hans Joachim Desserud
Thanks for reporting.

Looks like the home page link has been updated in Ubuntu 18.04 and newer
releases (https://packages.ubuntu.com/bionic/logrotate), so I'm marking
this as fixed. I've also linked the corresponding Debian bug report.

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

** Also affects: logrotate (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844578
   Importance: Unknown
   Status: Unknown

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

** Tags added: packaging string-fix xenial

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

Title:
  Update URL to project Homepage in package metadata

Status in logrotate package in Ubuntu:
  Fix Released
Status in logrotate package in Debian:
  Unknown

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  logrotate:
Installiert:   3.8.7-2ubuntu2.16.04.2
Installationskandidat: 3.8.7-2ubuntu2.16.04.2

  The URL to the project Homepage is wrong:

  ~~~
  Homepage: https://fedorahosted.org/logrotate/
  ~~~

  The URL leads to a page that informs you about the retirement of
  fedorahosted (see https://fedoraproject.org/wiki/Infrastructure
  /Fedorahosted-retirement). I think the correct URL should be
  https://github.com/logrotate/logrotate.

  This is only a minor flaw but still it would be nice if it gets fixed.

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

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


[Touch-packages] [Bug 1886835] Re: crashes to login screen, uvc related stuff blinks on console

2020-07-10 Thread jorge
I caught the console message on camera:

uvcvideo: Failed to query (GET_INFO) UVC control 15 on unit 1: -32 (exp.
1).

Googling around it seems this is a pretty spammy message, perhaps it is
unrelated to what is actually happening.

I can reproduce this crash putting my system under stress, opening a lot
of programs and making it swap. At some point it starts stuttering, then
crashes. It happens before the swap space is depleted, about 30% of a
2GB swap partition. It's a ThinkPad X1 laptop with SSD.

** Attachment added: "Screenshot_20200710-153131.png"
   
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1886835/+attachment/5391439/+files/Screenshot_20200710-153131.png

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

Title:
  crashes to login screen, uvc related stuff blinks on console

Status in lightdm package in Ubuntu:
  New

Bug description:
  I started getting random crashes to login screen, about twice a day.
  When crashes I briefly see some logging output to screen mentioning "UVC 
Control" or uvcview. I'm not using the webcam when the system crashes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-61-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Jul  8 11:55:34 2020
  InstallationDate: Installed on 2020-02-12 (146 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1868732] Re: Single Sign-on dialogue has no [OK] button

2020-07-10 Thread Steven Pemberton
For others who end up here unable to activate Livepatch because of this
bug, here is how you can activate it from the command line:

1. sudo snap install canonical-livepatch
2. go to https://auth.livepatch.canonical.com and generate a token.
3. sudo canonical-livepatch enable 

and you're done.

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

Title:
  Single Sign-on dialogue has no [OK] button

Status in gnome-online-accounts package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  1. Software updater says "You can use Livepatch to keep your computer up to 
date"
  2. I click on the Livepatch button
  3. Which says I have to log in to my Ubuntu One account
  4. Up pops a dialogue box, which allows me to fill in my email and password
  5. And no OK button. Hitting [return] doesn't help either. (See image)

  I can't log in to get Livepatch!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unity-control-center 15.04.0+18.04.20180216-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Tue Mar 24 15:09:09 2020
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-04-27 (1793 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to bionic on 2020-03-12 (11 days ago)

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

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


[Touch-packages] [Bug 1887186] Re: Please switch to nftables as the default backend

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

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

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

Title:
  Please switch to nftables as the default backend

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  The iptables package in Ubuntu already made the switch but it was
  reverted in LP: #1843468 due to breaking reverse dependencies and
  software not packaged in the Ubuntu Archive.

  The switch of the default backend is also a preparation for making the
  nftables frontend to be the preferred tool for interfacing the
  Netfilter framework, thus please Recommend: it.

  Inclusion of the netfilter package in main is traced at LP: #1887187.

  I've prepared a Bileto ticket for staging and testing the packages which need 
to be changed:
  https://bileto.ubuntu.com/#/ticket/4044

  The updated package break any package or project, please mark them
  affected and/or leave a commend in this bug.

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

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


[Touch-packages] [Bug 1886128] Re: systemd-resolved does not resolve address due to udp payload size.

2020-07-10 Thread Dan Streetman
Unfortunately, this is a bug in upstream systemd.

For some reason, resolved's current upstream code clamps the 'best'
server protocol level at 512-byte-sized EDNS0 if DNSSEC is disabled.
Since the default is for DNSSEC to be disabled, this means by default,
resolved will restrict its udp edns0 packets sent to upstream
nameservers at 512 bytes, as you indicated in the bug description.

normally, this is ok because most nameservers support TCP, and resolved
always falls back to TCP when it finds a truncated response.  However,
your upstream nameserver seems to either not support TCP DNS, or its
port 53 is firewalled for TCP.

This will take some time to open an upstream bug and investigate
patching. If you open an upstream bug please add a comment with the
link.

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

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

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

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

Title:
  systemd-resolved does not resolve address due to udp payload size.

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  systemd-resolve --version

  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid

  We met an error: on an attempt to resolve address, the following issue
  appears:

  ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mharder-formrec.cognitiveservices.azure.com. IN  A

  ;; Query time: 231 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Apr 28 20:47:14 UTC 2020
  ;; MSG SIZE  rcvd: 72

  Let me provide you important notes about the issue:
  1) It's not reproducing on Ubuntu 16;
  2) Bypassing systemd-resolve - everything works fine;
  3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE

  Successful query:

  113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
  Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0xc2d4
  Flags: 0x0120 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ..1.  = AD bit: Set
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 4096
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 12
  Option: COOKIE
  Unsuccessful query:

  112816:27:25.713886 10.1.0.4168.63.129.16   DNS 116
  Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0x198d
  Flags: 0x0100 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 512
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 0
  Notable 

[Touch-packages] [Bug 1887191] [NEW] autopkgtest always fail on i386 for f and later

2020-07-10 Thread Dan Streetman
Public bug reported:

[impact]

all autopkgtest runs fail for i386 arch for focal and later, since i386
is no longer a fully supported arch; the test run fails due to missing
test deps.

this is super annoying.

[test case]

run autopkgtest for i386 for f or g or later.

[regression potential]

as this only disables/skips all testing on i386 for f and later, any
regression would likely cause incorrectly failed or skipped autopkgtests
for non-i386 archs.

[scope]

this is needed for f and later.

i386 is a fully supported arch for b and earlier.

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

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

Title:
  autopkgtest always fail on i386 for f and later

Status in systemd package in Ubuntu:
  New

Bug description:
  [impact]

  all autopkgtest runs fail for i386 arch for focal and later, since
  i386 is no longer a fully supported arch; the test run fails due to
  missing test deps.

  this is super annoying.

  [test case]

  run autopkgtest for i386 for f or g or later.

  [regression potential]

  as this only disables/skips all testing on i386 for f and later, any
  regression would likely cause incorrectly failed or skipped
  autopkgtests for non-i386 archs.

  [scope]

  this is needed for f and later.

  i386 is a fully supported arch for b and earlier.

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

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


[Touch-packages] [Bug 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications

2020-07-10 Thread Joy Latten
** Description changed:

- In FIPS mode on Bionic MD5 is semi-disabled causing some applications to
- segfault.
+ [Impact]
+ In FIPS mode on Bionic MD5 is semi-disabled causing some applications to 
segfault.
  
+ ntpq uses crypto hashes to authenticate its requests. By default it appears 
to use an internal md5 implementation. However, when compiled with openssl it 
creates a lists of acceptable hashes from openssl that can be used. 
+  
+ [Test Steps]
  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)
  
  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.
  
  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());
  
  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);
  
  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif
  
  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence
  
  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).
  
  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.
+ 
+ [Regression Potential]
+ 
+ I believe the resolution to check the return code and if unsuccessful, do not 
include the hash algorithm in the internal ntpq digest list, should not 
introduce any regression.
+ It will simply not add md5 and md5_sha1 to its lists of digests when compiled 
with openssl. Instead it will add the others like sha1, sha2, and sha3.

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

Title:
  [fips] Not fully initialized digest segfaulting some client
  applications

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications to 
segfault.

  ntpq uses crypto hashes to authenticate its requests. By default it appears 
to use an internal md5 implementation. However, when compiled with openssl it 
creates a lists of acceptable hashes from openssl that can be used. 
   
  [Test Steps]
  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)

  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.

  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());

  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);

  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif

  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence

  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).

  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.

  [Regression Potential]

  I believe the resolution to check the return code and if unsuccessful, do not 
include the hash algorithm in the internal ntpq digest list, should not 
introduce any regression.
  It will simply not add md5 and md5_sha1 to its lists of digests when compiled 
with openssl. Instead it will add the others like sha1, sha2, and sha3.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1886128] Re: systemd-resolved does not resolve address due to udp payload size.

2020-07-10 Thread Dan Streetman
** Changed in: systemd (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  systemd-resolved does not resolve address due to udp payload size.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  systemd-resolve --version

  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
  +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
  -PCRE2 default-hierarchy=hybrid

  We met an error: on an attempt to resolve address, the following issue
  appears:

  ; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> 
mharder-formrec.cognitiveservices.azure.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44096
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;mharder-formrec.cognitiveservices.azure.com. IN  A

  ;; Query time: 231 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Tue Apr 28 20:47:14 UTC 2020
  ;; MSG SIZE  rcvd: 72

  Let me provide you important notes about the issue:
  1) It's not reproducing on Ubuntu 16;
  2) Bypassing systemd-resolve - everything works fine;
  3) Only the difference between systemd-resolve and END is UDP_PAYLOAD_SIZE

  Successful query:

  113516:27:25.964386 10.1.0.4168.63.129.16   DNS 128
  Standard query 0xc2d4 A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0xc2d4
  Flags: 0x0120 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ..1.  = AD bit: Set
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 4096
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 12
  Option: COOKIE
  Unsuccessful query:

  112816:27:25.713886 10.1.0.4168.63.129.16   DNS 116
  Standard query 0x198d A mharder-formrec.cognitiveservices.azure.com
  OPT

  Domain Name System (query)
  Transaction ID: 0x198d
  Flags: 0x0100 Standard query
  0...    = Response: Message is a query
  .000 0...   = Opcode: Standard query (0)
   ..0.   = Truncated: Message is not truncated
   ...1   = Recursion desired: Do query recursively
    .0..  = Z: reserved (0)
    ...0  = Non-authenticated data: Unacceptable
  Questions: 1
  Answer RRs: 0
  Authority RRs: 0
  Additional RRs: 1
  Queries
  mharder-formrec.cognitiveservices.azure.com: type A, class IN
  Additional records
  : type OPT
  Name: 
  Type: OPT (41)
  UDP payload size: 512
  Higher bits in extended RCODE: 0x00
  EDNS0 version: 0
  Z: 0x
  0...    = DO bit: Cannot handle DNSSEC security 
RRs
  .000    = Reserved: 0x
  Data length: 0
  Notable difference:

  Success:
  UDP payload size: 4096

  Failure:
  UDP payload size: 512
  And notable differences in the responses:

  Success:
  Flags: 0x8180 Standard query response, No error
   ..0.   = Truncated: Message is not truncated

  Failure:
  Flags: 0x8380 Standard query response, No error
   ..1.   = Truncated: Message is truncated

  Interestingly, systemd-resolved is setting the maximum payload size to 512 
regardless of whether EDNS0 is configured and regardless of what is sent to it 
for the payload size.
  I tried to found a way to change UDP_PAYLOAD_SIZE,but it seems it is only 
possible to change it only with direct code modifications.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1532314] Re: Buffer overflow in cgmanager

2020-07-10 Thread bahr alshooq
** Changed in: cgmanager (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Buffer overflow in cgmanager

Status in cgmanager package in Ubuntu:
  Fix Released
Status in libnih package in Ubuntu:
  Confirmed
Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  Host: Ubuntu 15.10
  lxc: 1.1.5-0ubuntu0.15.10.3
  cgmanager: 0.39-2ubuntu2
  Container: Ubuntu 15.10

  Got the following trace in syslog. Please let me know what other
  information will be useful for troubleshooting.

  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: *** buffer overflow 
detected ***: /sbin/cgmanager terminated
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: === Backtrace: 
=
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 
/lib/x86_64-linux-gnu/libc.so.6(+0x78c4e)[0x7f1929550c4e]
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x5c)[0x7f19295f0e8c]
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 
/lib/x86_64-linux-gnu/libc.so.6(+0x116e80)[0x7f19295eee80]
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 
/lib/x86_64-linux-gnu/libc.so.6(+0x118dd7)[0x7f19295f0dd7]
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 
/lib/x86_64-linux-gnu/libnih.so.1(nih_io_handle_fds+0xad)[0x7f1929d01b3d]
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 
/lib/x86_64-linux-gnu/libnih.so.1(nih_main_loop+0x13f)[0x7f1929d05faf]
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 
/sbin/cgmanager(+0x5145)[0x562d8fc75145]
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f19294f8a40]
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 
/sbin/cgmanager(+0x53d9)[0x562d8fc753d9]
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: === Memory map: 

  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d8fc7-562d8fc92000 
r-xp  ca:01 12884  /sbin/cgmanager
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d8fe92000-562d8fe94000 
r--p 00022000 ca:01 12884  /sbin/cgmanager
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d8fe94000-562d8fe95000 
rw-p 00024000 ca:01 12884  /sbin/cgmanager
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 562d915f8000-562d9203 
rw-p  00:00 0  [heap]
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927d44000-7f1927d5a000 
r-xp  ca:01 395872 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927d5a000-7f1927f59000 
---p 00016000 ca:01 395872 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f59000-7f1927f5a000 
r--p 00015000 ca:01 395872 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f5a000-7f1927f5b000 
rw-p 00016000 ca:01 395872 
/lib/x86_64-linux-gnu/libgcc_s.so.1
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f5b000-7f1927f67000 
r-xp  ca:01 403839 
/lib/x86_64-linux-gnu/libnss_files-2.21.so
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1927f67000-7f1928166000 
---p c000 ca:01 403839 
/lib/x86_64-linux-gnu/libnss_files-2.21.so
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928166000-7f1928167000 
r--p b000 ca:01 403839 
/lib/x86_64-linux-gnu/libnss_files-2.21.so
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928167000-7f1928168000 
rw-p c000 ca:01 403839 
/lib/x86_64-linux-gnu/libnss_files-2.21.so
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928168000-7f1928173000 
r-xp  ca:01 403823 
/lib/x86_64-linux-gnu/libnss_nis-2.21.so
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928173000-7f1928372000 
---p b000 ca:01 403823 
/lib/x86_64-linux-gnu/libnss_nis-2.21.so
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928372000-7f1928373000 
r--p a000 ca:01 403823 
/lib/x86_64-linux-gnu/libnss_nis-2.21.so
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928373000-7f1928374000 
rw-p b000 ca:01 403823 
/lib/x86_64-linux-gnu/libnss_nis-2.21.so
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f1928374000-7f192838b000 
r-xp  ca:01 403845 
/lib/x86_64-linux-gnu/libnsl-2.21.so
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f192838b000-7f192858a000 
---p 00017000 ca:01 403845 
/lib/x86_64-linux-gnu/libnsl-2.21.so
  Jan  8 19:29:24 ip-10-169-249-164 cgmanager[7725]: 7f192858a000-7f192858b000 
r--p 00016000 ca:01 

[Touch-packages] [Bug 1387825] Re: The default NAME_REGEX value in /etc/adduser.conf is incorrect

2020-07-10 Thread Andrew Meyer
This just bit me. It's especially confusing for beginners because the
config file syntax looks a lot like bash, and in bash that extra
backslash would be correct as it would simply prevent the proceeding
dollar symbol from being interpreted as an environment variable, and the
backslash wouldn't show up in the final regex.

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

Title:
  The default NAME_REGEX value in /etc/adduser.conf is incorrect

Status in adduser package in Ubuntu:
  Confirmed
Status in adduser package in Debian:
  New

Bug description:
  Refer the Debian bug report for more information.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: adduser 3.113+nmu3ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4
  Uname: Linux 3.16.0-22-lowlatency i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Oct 31 01:55:03 2014
  InstallationDate: Installed on 2013-03-08 (600 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  PackageArchitecture: all
  SourcePackage: adduser
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (194 days ago)

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

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


[Touch-packages] [Bug 1387825] Re: The default NAME_REGEX value in /etc/adduser.conf is incorrect

2020-07-10 Thread Andrew Meyer
Another example of someone getting confused by this bug:
https://askubuntu.com/q/892419/166655

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

Title:
  The default NAME_REGEX value in /etc/adduser.conf is incorrect

Status in adduser package in Ubuntu:
  Confirmed
Status in adduser package in Debian:
  New

Bug description:
  Refer the Debian bug report for more information.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: adduser 3.113+nmu3ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4
  Uname: Linux 3.16.0-22-lowlatency i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Oct 31 01:55:03 2014
  InstallationDate: Installed on 2013-03-08 (600 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  PackageArchitecture: all
  SourcePackage: adduser
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (194 days ago)

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

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


[Touch-packages] [Bug 1387825] Re: The default NAME_REGEX value in /etc/adduser.conf is incorrect

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

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

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

Title:
  The default NAME_REGEX value in /etc/adduser.conf is incorrect

Status in adduser package in Ubuntu:
  Confirmed
Status in adduser package in Debian:
  New

Bug description:
  Refer the Debian bug report for more information.
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: adduser 3.113+nmu3ubuntu3
  ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4
  Uname: Linux 3.16.0-22-lowlatency i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: i386
  CurrentDesktop: KDE
  Date: Fri Oct 31 01:55:03 2014
  InstallationDate: Installed on 2013-03-08 (600 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  PackageArchitecture: all
  SourcePackage: adduser
  UpgradeStatus: Upgraded to trusty on 2014-04-19 (194 days ago)

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

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


[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-10 Thread Noctis Bennington
Done. Here's the file.

PD: I was thinking the same when I read the "LSPCON" Intel's
funcionality

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1871721/+attachment/5391375/+files/dmesg

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  

[Touch-packages] [Bug 1887186] [NEW] Please switch to nftables as the default backend

2020-07-10 Thread Balint Reczey
Public bug reported:

The iptables package in Ubuntu already made the switch but it was
reverted in LP: #1843468 due to breaking reverse dependencies and
software not packaged in the Ubuntu Archive.

The switch of the default backend is also a preparation for making the
nftables frontend to be the preferred tool for interfacing the Netfilter
framework, thus please Recommend: it.

Inclusion of the netfilter package in main is traced at LP: #1887187.

I've prepared a Bileto ticket for staging and testing the packages which need 
to be changed:
https://bileto.ubuntu.com/#/ticket/4044

The updated package break any package or project, please mark them
affected and/or leave a commend in this bug.

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

** Description changed:

  The iptables package in Ubuntu already made the switch but it was
  reverted in LP: #1843468 due to breaking reverse dependencies and
  software not packaged in the Ubuntu Archive.
  
  The switch of the default backend is also a preparation for making the
  nftables frontend to be the preferred tool for interfacing the Netfilter
  framework, thus please Recommend: it.
  
- Inclusion of the netfilter package in main is traced at LP: #XXX.
+ Inclusion of the netfilter package in main is traced at LP: #1887187.
  
  I've prepared a Bileto ticket for staging and testing the packages which need 
to be changed:
  https://bileto.ubuntu.com/#/ticket/4044
  
  The updated package break any package or project, please mark them
  affected and/or leave a commend in this bug.

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

Title:
  Please switch to nftables as the default backend

Status in iptables package in Ubuntu:
  New

Bug description:
  The iptables package in Ubuntu already made the switch but it was
  reverted in LP: #1843468 due to breaking reverse dependencies and
  software not packaged in the Ubuntu Archive.

  The switch of the default backend is also a preparation for making the
  nftables frontend to be the preferred tool for interfacing the
  Netfilter framework, thus please Recommend: it.

  Inclusion of the netfilter package in main is traced at LP: #1887187.

  I've prepared a Bileto ticket for staging and testing the packages which need 
to be changed:
  https://bileto.ubuntu.com/#/ticket/4044

  The updated package break any package or project, please mark them
  affected and/or leave a commend in this bug.

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

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


[Touch-packages] [Bug 1219529] Re: df -x tmpfs fails to exclude udev (/dev)

2020-07-10 Thread Launchpad Bug Tracker
This bug was fixed in the package coreutils - 8.30-3ubuntu3

---
coreutils (8.30-3ubuntu3) groovy; urgency=medium

  * d/p/treat-devtmpfs-and-squashfs-as-dummy-filesystems.patch:
- Avoid displaying snaps in output from df and other tools, by
  excluding display of squashfs filesystems.
  (LP: #1219529, #1756595)
- Exclude devtmpfs filesystems in output from df and other tools
  since it is a dummy filesystem.
  (LP: #1219529)

 -- Bryce Harrington   Thu, 02 Jul 2020 02:30:48
+

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

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

Title:
  df -x tmpfs fails to exclude udev (/dev)

Status in coreutils:
  New
Status in coreutils package in Ubuntu:
  Fix Released

Bug description:
  The command:

  $ /bin/df -x tmpfs

  should exclude all filesystems of type tmpfs. The udev filesystem
  mounted at /dev is of this type:

  $ stat -f /dev
File: "/dev"
  ID: 0Namelen: 255 Type: tmpfs
  Block size: 4096   Fundamental block size: 4096
  Blocks: Total: 4109101Free: 4109098Available: 4109098
  Inodes: Total: 4109101Free: 4108501

  However, df still displays this filesystem:

  $ df -l -x tmpfs
  Filesystem  1K-blocks  Used  Available Use% Mounted on
  ...
  udev 1643640412   16436392   1% /dev
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: coreutils 8.20-3ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Sun Sep  1 15:05:40 2013
  InstallationDate: Installed on 2013-08-31 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1756595] Re: disk space info inadvertently provides all installed snaps

2020-07-10 Thread Launchpad Bug Tracker
This bug was fixed in the package coreutils - 8.30-3ubuntu3

---
coreutils (8.30-3ubuntu3) groovy; urgency=medium

  * d/p/treat-devtmpfs-and-squashfs-as-dummy-filesystems.patch:
- Avoid displaying snaps in output from df and other tools, by
  excluding display of squashfs filesystems.
  (LP: #1219529, #1756595)
- Exclude devtmpfs filesystems in output from df and other tools
  since it is a dummy filesystem.
  (LP: #1219529)

 -- Bryce Harrington   Thu, 02 Jul 2020 02:30:48
+

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

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

Title:
  disk space info inadvertently provides all installed snaps

Status in apt package in Ubuntu:
  Fix Released
Status in coreutils package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Disco:
  Fix Released
Status in apt source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  When apport is reporting a crash, it includes the output of the "df" utility, 
to list the free disk space information per mount point.

  That output nowadays will inadvertently include all snaps that the
  user may have installed, including their revision numbers.

  Here is a simple df output:
  andreas@nsn7:~$ df
  Filesystem  1K-blocksUsed Available Use% Mounted on
  udev  8119680   0   8119680   0% /dev
  tmpfs 16301561828   1628328   1% /run
  nsn7/ROOT/ubuntu433084288 2500608 430583680   1% /
  tmpfs 8150776   1   8131888   1% /dev/shm
  tmpfs5120   4  5116   1% /run/lock
  tmpfs 8150776   0   8150776   0% 
/sys/fs/cgroup
  nsn7/var/log430763136  179456 430583680   1% /var/log
  nsn7/var/tmp430583808 128 430583680   1% /var/tmp
  /dev/sda2 1032088  160336871752  16% /boot
  /dev/sda1  5232482720520528   1% /boot/efi
  nsn7/home   430651264   67584 430583680   1% /home
  nsn7/var/cache  430653312   69632 430583680   1% /var/cache
  nsn7/var/mail   430583808 128 430583680   1% /var/mail
  nsn7/var/spool  430583808 128 430583680   1% /var/spool
  tmpfs 1630152  16   1630136   1% /run/user/120
  tmpfs 100   0   100   0% 
/var/lib/lxd/shmounts
  tmpfs 100   0   100   0% 
/var/lib/lxd/devlxd
  tmpfs 1630152  36   1630116   1% 
/run/user/1000
  nsn7/lxd/containers/squid-ds216 431444096  860416 430583680   1% 
/var/lib/lxd/storage-pools/default/containers/squid-ds216
  /dev/loop0  83712   83712 0 100% 
/snap/core/4206
  /dev/loop1 102144  102144 0 100% 
/snap/git-ubuntu/402

  You can see I have the core snap at revision 4206, and git-ubuntu at
  revision 402.

  There are already many bug reports in launchpad where one can see this
  information.

  Granted, the user can review it, refuse to send this data, etc. This
  bug is about the unexpectedness of having that information in the disk
  space data.

  If the user sees a prompt like "Would you like to include disk free
  space information in your report?", or "Would you like to include the
  output of the df(1) command in your report?", that doesn't immediately
  translate to "Would you like to include disk free space information
  and a list of all installed snaps and their revision numbers in your
  report?".

  [Test case]
  Do something that triggers the apport hook and make sure you don't see snaps 
in there.

  For example, install xterm, then add exit 1 to the start of the prerm,
  then run apt remove xterm, and investigate /var/crash/xterm.0.crash
  after that (delete before running apt).

  [Regression potential]
  Fix consists of adding -x squashfs to df output, so might hide other non-snap 
squashfs images.

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

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


[Touch-packages] [Bug 1882248] Re: [SRU] plug headset won't proper reconfig ouput to it on machine with default output

2020-07-10 Thread Sebastien Bacher
@Hui, thanks, I uploaded to the bionic SRU queue now

One comment, the bottom entry of the changelog (the line with the name
of the uploader) has an extra trailing space, in git and in the debdiff,
which screws dpkg parsing utilities. Another of your changes this week
has the problem, could you check if there something buggy on your side
that leads to those problems?


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

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

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

** Changed in: pulseaudio (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  [SRU] plug headset won't proper reconfig ouput to it on machine with
  default output

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in linux-oem package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  This is for pulseaudio bionic:

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, the active profile is Off, after users plug a
  headset to it and users select the headset from the pop-up dialogue,
  users expect the profile changes to analog-stereo (headset is on it),
  but the active_profile is still Off.

  [Fix]
  Upstream already has a patch to fix it, cherrypiack that patch to bionic.
  And that patch is already in the eoan, focal, ...

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and select the headset from UI, the profile changes to
  analog-stereo, and play some sound, we could hear it from the headset

  [Regression Risk]
  Low, this patch is already in the upstream for a long time, and it is
  already in the eoan and focal.


  
  For linux kernel (oem-b):

  [Impact]
  On a Dell machine without internal spk and internal mic, after freshly
  install the bionic on it, and users plug a headset, the sound couldn't
  output from headset.

  [Fix]
  reverse the order of headset mic and headphone mic

  [Test Case]
  freshly install the bionic with this patch on that dell machine,
  plug headset and play sound, we could hear the sound from headset.

  [Regression Risk]
  Low, this patch only affects the machine without internal mic and
  internal spk, and I already tested this patch on the machine without
  internal mic and internal spk, it worked well.

  target machine does not have built-in speaker, and the monitor does
  not have an audio output (like d-sub VGA)

  As first boot, there will be a "dummy output" in g-c-c.

  After plug-in headset, there will be a headset appear in g-c-c, but it
  won't be automatically selected even it's chosen in the pop-up window.

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

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


[Touch-packages] [Bug 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications

2020-07-10 Thread Joy Latten
debdiff for bionic


** Attachment added: "debdiff.bionic"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1884265/+attachment/5391374/+files/debdiff.bionic

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

Title:
  [fips] Not fully initialized digest segfaulting some client
  applications

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Bionic:
  New

Bug description:
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications
  to segfault.

  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)

  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.

  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());

  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);

  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif

  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence

  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).

  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.

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

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


[Touch-packages] [Bug 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications

2020-07-10 Thread Joy Latten
Build log: 
https://launchpad.net/~j-latten/+archive/ubuntu/joyppa/+build/19570468

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

Title:
  [fips] Not fully initialized digest segfaulting some client
  applications

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Bionic:
  New

Bug description:
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications
  to segfault.

  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)

  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.

  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());

  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);

  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif

  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence

  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).

  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.

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

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


[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-10 Thread Kai-Heng Feng
Please test latest drm-tip kernel with kernel parameter "drm.debug=0xe 
log_buf_len=16M":
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/

...and attach dmesg here...

Hopefully this is not another LSPCON bug...

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend 

[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-10 Thread Noctis Bennington
I tried with Wayland but only with Intel (there's no option with
Nvidia), same result. Maybe 'cause's working under XWayland?

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
  

[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-10 Thread Kai-Heng Feng
Can you please try Wayland? Seems to be an X11 bug...

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 

[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)

2020-07-10 Thread Daniel Rodriguez
I remember having run firefox and chromium side-by-side once on the same
website and noticed the colors were off. The colors on firefox's images
matched eog and other local image viewers, while chromium's were skewed.
I googled it once and found that setting

chrome://flags/#force-color-profile

(setting srgb) fixed the issues. This was in like 2019, the flag is not
available anymore. Does that have anything to do with it? I believe the
chromium change that removed this flag was on the basis of chromium now
"properly" handling color profiles from the OS, so I wanted to bring it
up.

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

Title:
  Images are washed out or colors are skewed in some apps (particularly
  Image Viewer and Chrome)

Status in Eye of GNOME:
  New
Status in GNOME Shell:
  Unknown
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed
Status in inkscape package in Ubuntu:
  Confirmed

Bug description:
  Images are washed out or colors are skewed in some apps, notably
  Chrome/Chromium and Image Viewer (eog).

  Workaround:

  Settings > Devices > Colour >
  and disable or remove your monitor's colour profile

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

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


[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client

2020-07-10 Thread Mantas Kriaučiūnas
** Also affects: baltix-default-settings
   Importance: Undecided
   Status: New

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

Title:
  Netplan has no way to control DHCP client

Status in Default settings and artwork for Baltix OS:
  New
Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1759014/+subscriptions

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


[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-10 Thread Noctis Bennington
PD: The mesa driver of intel's working with the same version of git,
just trying to make it work. But with the stable version doesn't work
neither. Just in case you wanted to know.

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  

[Touch-packages] [Bug 1871721] xdpyinfo.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391359/+files/xdpyinfo.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] Lsusb.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1871721/+attachment/5391346/+files/Lsusb.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] Lsusb-t.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391347/+files/Lsusb-t.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] XorgLog.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391355/+files/XorgLog.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] UdevDb.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1871721/+attachment/5391354/+files/UdevDb.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] nvidia-settings.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "nvidia-settings.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391358/+files/nvidia-settings.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] Xrandr.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1871721/+attachment/5391357/+files/Xrandr.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] XorgLogOld.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391356/+files/XorgLogOld.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] ProcModules.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391353/+files/ProcModules.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] ProcInterrupts.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391352/+files/ProcInterrupts.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] NvidiaBugReportLog.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "NvidiaBugReportLog.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391349/+files/NvidiaBugReportLog.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset 

[Touch-packages] [Bug 1871721] ProcCpuinfo.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391350/+files/ProcCpuinfo.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] Lsusb-v.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391348/+files/Lsusb-v.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] ProcCpuinfoMinimal.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391351/+files/ProcCpuinfoMinimal.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset 

[Touch-packages] [Bug 1871721] DpkgLog.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391343/+files/DpkgLog.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] Lspci.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1871721/+attachment/5391344/+files/Lspci.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] Lspci-vt.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391345/+files/Lspci-vt.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] Dependencies.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391342/+files/Dependencies.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] BootLog.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391340/+files/BootLog.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] CurrentDmesg.txt

2020-07-10 Thread Noctis Bennington
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1871721/+attachment/5391341/+files/CurrentDmesg.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/1871721

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
  --- 
  ProblemType: Bug
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  

[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-10 Thread Noctis Bennington
apport information

** Tags added: apport-collected third-party-packages ubuntu

** Description changed:

  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.
  
  I tried with nouveau drivers and I have the same results btw.
  
  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300
  
  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.
  
  I have this with xrandr:
  
  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)
  
- PD: When you select a specific resolution, the second monitor "works",
- but it blinks, the image showed via HDMI on the second monitor blinks.
- So is impossible to work with it. Since all this time I was searching
- about this and I'm almost sure this is a problem of the GPU's Intel. But
- I saw this problem on askubuntu just with laptops with hybrid graphics.
- Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if
- they have the same problem here).
+ PD: When you select a specific resolution, the second monitor "works", but it 
blinks, the image showed via HDMI on the second monitor blinks. So is 
impossible to work with it. Since all this time I was searching about this and 
I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on 
askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. 
(Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here).
+ --- 
+ ProblemType: Bug
+ .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
+ .proc.driver.nvidia.registry: Binary: ""
+ .proc.driver.nvidia.suspend: suspend hibernate resume
+ .proc.driver.nvidia.suspend_depth: default modeset uvm
+ .proc.driver.nvidia.version:
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
+  GCC version:
+ ApportVersion: 

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

2020-07-10 Thread Launchpad Bug Tracker
** Merge proposal linked:
   https://code.launchpad.net/~paride/curtin/+git/curtin/+merge/387218

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

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd:
  Unknown
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in cloud-init source package in Disco:
  Won't Fix
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in cloud-init source package in Eoan:
  New
Status in netplan.io source package in Eoan:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in cloud-init source package in Focal:
  Confirmed
Status in netplan.io source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

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

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

[Touch-packages] [Bug 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications

2020-07-10 Thread Dariusz Gadomski
Oh, I have found it: ppa:j-latten/joydevppa

Works perfectly. Thanks!

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

Title:
  [fips] Not fully initialized digest segfaulting some client
  applications

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Bionic:
  New

Bug description:
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications
  to segfault.

  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)

  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.

  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());

  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);

  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif

  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence

  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).

  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.

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

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


[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-07-10 Thread Launchpad Bug Tracker
** Merge proposal linked:
   https://code.launchpad.net/~paride/curtin/+git/curtin/+merge/387217

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in bcache-tools source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in bcache-tools source package in Groovy:
  Triaged
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1884265] Re: [fips] Not fully initialized digest segfaulting some client applications

2020-07-10 Thread Dariusz Gadomski
Sure. Sounds good. Do you have it available in a ppa anywhere to give it
a try?

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

Title:
  [fips] Not fully initialized digest segfaulting some client
  applications

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Bionic:
  New

Bug description:
  In FIPS mode on Bionic MD5 is semi-disabled causing some applications
  to segfault.

  Test case:
  sudo apt install ntp
  ntpq -p
  Segmentation fault (core dumped)

  What happens there is ntpq wants to iterate all available digests
  (list_digest_names in ntpq.c). It uses EVP_MD_do_all_sorted for this
  task.

  EVP_MD_do_all_sorted eventually runs openssl_add_all_digests_int in c_alld.c.
  For FIPS mode it adds:
  EVP_add_digest(EVP_md5());

  What happens later in ntpq is (list_md_fn function inside ntpq.c):
  ctx = EVP_MD_CTX_new();
  EVP_DigestInit(ctx, EVP_get_digestbyname(name));
  EVP_DigestFinal(ctx, digest, _len);

  First digest it gets is MD5, but while running EVP_DigestInit for it, it gets 
to this point (openssl/crypto/evp/digest.c EVP_DigestInit_ex):
  #ifdef OPENSSL_FIPS
  if (FIPS_mode()) {
  if (!(type->flags & EVP_MD_FLAG_FIPS)
  && !(ctx->flags & EVP_MD_CTX_FLAG_NON_FIPS_ALLOW)) {
  EVPerr(EVP_F_EVP_DIGESTINIT_EX, EVP_R_DISABLED_FOR_FIPS);
  return 0;
  }
  }
  #endif

  Due to type->flags for MD5 being 0 there's an error set 
(EVP_R_DISABLED_FOR_FIPS).
  After getting back to ntpq.c:
  ctx->engine and ctx->digest are not set (due to the mentioned error), hence

  inside EVP_DigestFinal_ex (openssl/crypto/evp/digest.c)
  OPENSSL_assert(ctx->digest->md_size <= EVP_MAX_MD_SIZE);
  causes a segfault (ctx->digest is NULL).

  So either MD5 shouldn't be added in FIPS mode or it should have the
  EVP_MD_FLAG_FIPS to be properly initialized.

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

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


[Touch-packages] [Bug 1887161] [NEW] sound does not switch to bluetooth speakers automatically after connecting

2020-07-10 Thread Tomislav
Public bug reported:

I connect to a bluetooth speaker.

Observed behaviour: connection established, but sound still continues to
come from the built-in speakers and when looking at available sound
outputs in the gnome-control-center, there are no new outputs.

Expected behaviour: connection established, sound output switches to BT
speaker automatically, new sound output device visible in sound settings

Workaround: disconnect and reconnect a few times, after which everything
seems to work

The BT speaker is a actually the F900 2 Channel Amp Bluetooth Amplifier
feeding regular wired speakers behind it.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
Uname: Linux 4.15.0-108-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tnalfir2036 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 13:33:04 2020
InstallationDate: Installed on 2017-02-18 (1237 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: Upgraded to bionic on 2020-05-10 (60 days ago)
dmi.bios.date: 06/15/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.3
dmi.board.asset.tag: 201710275
dmi.board.name: 0R3VX4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: 201710275
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn0R3VX4:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5570
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  sound does not switch to bluetooth speakers automatically after
  connecting

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I connect to a bluetooth speaker.

  Observed behaviour: connection established, but sound still continues
  to come from the built-in speakers and when looking at available sound
  outputs in the gnome-control-center, there are no new outputs.

  Expected behaviour: connection established, sound output switches to
  BT speaker automatically, new sound output device visible in sound
  settings

  Workaround: disconnect and reconnect a few times, after which
  everything seems to work

  The BT speaker is a actually the F900 2 Channel Amp Bluetooth
  Amplifier feeding regular wired speakers behind it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18
  Uname: Linux 4.15.0-108-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tnalfir2036 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 13:33:04 2020
  InstallationDate: Installed on 2017-02-18 (1237 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to bionic on 2020-05-10 (60 days ago)
  dmi.bios.date: 06/15/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.3
  dmi.board.asset.tag: 201710275
  dmi.board.name: 0R3VX4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 201710275
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn0R3VX4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5570
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE

2020-07-10 Thread Stuart Langridge
I think the place to fix this may be in _spawn_goa_with_args in
https://git.launchpad.net/ubuntu/+source/software-properties/tree/softwareproperties/gtk/DialogAuth.py#n196.
 Perhaps that function should check for XDG_CURRENT_DESKTOP=GNOME and if it 
isn't GNOME, pop up a message window pointing to a wiki page which can then be 
edited by flavours to explain what to do to sign in to Ubuntu One and/or 
Livepatch in their desktops?

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

Title:
  Impossible to set up Livepatch on Ubuntu MATE

Status in Ubuntu MATE:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu MATEE 18.04, in the Software Properties window (available
  from Software Boutique > Preferences > Show Software Sources > Manage
  Repositories, among other places), there is a Livepatch tab. This tab
  says "To use Livepatch, you need to sign in" and provides a "Sign
  In..." button.

  This button launches an empty version of gnome-control-center with no
  icons in it.

  If one is technically adept, it is possible to do what (I think) that
  button is trying to do by launching g-c-c directly in a terminal and
  overriding the desktop, thus:

  env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts

  This online accounts window permits attempting to add an Ubuntu One
  account. However, when one tries, a window pops up with a place to add
  one's Ubuntu One username and password, but the window has no Submit
  button; there is no way to actually initiate sign in.

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

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


[Touch-packages] [Bug 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE

2020-07-10 Thread Paul White
Further to comment #4, this bug report should also be extended to cover
Kubuntu, Lubuntu, Xubuntu etc. which also won't include gnome-control-
center in a default installation.

If anyone really needs Livepatch then the work-around, as suggested by
Bill and confirmed by me, of installing Livepatch from the command line
will work. In the case of Xubuntu you even get an icon in the top bar to
confirm that Livepatch is enabled and running.

** Tags added: kubuntu lubuntu xubuntu

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

Title:
  Impossible to set up Livepatch on Ubuntu MATE

Status in Ubuntu MATE:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu MATEE 18.04, in the Software Properties window (available
  from Software Boutique > Preferences > Show Software Sources > Manage
  Repositories, among other places), there is a Livepatch tab. This tab
  says "To use Livepatch, you need to sign in" and provides a "Sign
  In..." button.

  This button launches an empty version of gnome-control-center with no
  icons in it.

  If one is technically adept, it is possible to do what (I think) that
  button is trying to do by launching g-c-c directly in a terminal and
  overriding the desktop, thus:

  env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts

  This online accounts window permits attempting to add an Ubuntu One
  account. However, when one tries, a window pops up with a place to add
  one's Ubuntu One username and password, but the window has no Submit
  button; there is no way to actually initiate sign in.

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

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


[Touch-packages] [Bug 1887150] Re: Fractional Scaling turns screen sideways

2020-07-10 Thread dryphi
Second screenshot in sequence of events.

** Attachment added: "Screenshot #2"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887150/+attachment/5391286/+files/Screenshot%20from%202020-07-10%2006-33-47.png

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

Title:
  Fractional Scaling turns screen sideways

Status in xorg package in Ubuntu:
  New

Bug description:
  I right-click on desktop, click Display Settings, and find the Fractional 
Scaling option.
  When I enable the option my screen rotates 90 degrees. It's as if the display 
thought I had rotated my device 90 degrees (but I hadn't I'm using a laptop).
  Can attach screenshots if possible.

  I just freshly installed Ubuntu 20.04 from a USB and ran sudo apt-get
  update and sudo apt-get upgrade for the first time literally minutes
  ago. Nothing else was installed except for Grub Customizer and

  EDIT: Turns out I can't attach three screenshots. I can only attach
  one. I attached the final screenshot. I took screenshots of the
  original rotation, then before I selected the Fractional Scaling
  option, then what happened after. But I can only attach one of them.
  Please allow us to attach more than one screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 06:34:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) 
[1043:19d1]
  InstallationDate: Installed on 2020-07-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b568 Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP412FA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=d20ac799-f93e-4aea-9632-495aa9132b04 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP412FA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP412FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP412FA.302:bd05/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP412FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP412FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook_ASUSLaptop TP412FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1887150] Re: Fractional Scaling turns screen sideways

2020-07-10 Thread dryphi
Final screenshot and result of enabling the Fractional Scaling option.
Note that to me this screen appears rotated 90 degrees.

** Attachment added: "Screenshot #3"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887150/+attachment/5391287/+files/Screenshot%20from%202020-07-10%2006-33-53.png

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

Title:
  Fractional Scaling turns screen sideways

Status in xorg package in Ubuntu:
  New

Bug description:
  I right-click on desktop, click Display Settings, and find the Fractional 
Scaling option.
  When I enable the option my screen rotates 90 degrees. It's as if the display 
thought I had rotated my device 90 degrees (but I hadn't I'm using a laptop).
  Can attach screenshots if possible.

  I just freshly installed Ubuntu 20.04 from a USB and ran sudo apt-get
  update and sudo apt-get upgrade for the first time literally minutes
  ago. Nothing else was installed except for Grub Customizer and

  EDIT: Turns out I can't attach three screenshots. I can only attach
  one. I attached the final screenshot. I took screenshots of the
  original rotation, then before I selected the Fractional Scaling
  option, then what happened after. But I can only attach one of them.
  Please allow us to attach more than one screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 06:34:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) 
[1043:19d1]
  InstallationDate: Installed on 2020-07-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b568 Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP412FA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=d20ac799-f93e-4aea-9632-495aa9132b04 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP412FA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP412FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP412FA.302:bd05/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP412FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP412FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook_ASUSLaptop TP412FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1887150] [NEW] Fractional Scaling turns screen sideways

2020-07-10 Thread dryphi
Public bug reported:

I right-click on desktop, click Display Settings, and find the Fractional 
Scaling option.
When I enable the option my screen rotates 90 degrees. It's as if the display 
thought I had rotated my device 90 degrees (but I hadn't I'm using a laptop).
Can attach screenshots if possible.

I just freshly installed Ubuntu 20.04 from a USB and ran sudo apt-get
update and sudo apt-get upgrade for the first time literally minutes
ago. Nothing else was installed except for Grub Customizer and

EDIT: Turns out I can't attach three screenshots. I can only attach one.
I attached the final screenshot. I took screenshots of the original
rotation, then before I selected the Fractional Scaling option, then
what happened after. But I can only attach one of them. Please allow us
to attach more than one screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 06:34:56 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:19d1]
InstallationDate: Installed on 2020-07-10 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b568 Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP412FA
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=d20ac799-f93e-4aea-9632-495aa9132b04 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/06/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: TP412FA.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: TP412FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP412FA.302:bd05/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP412FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP412FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: VivoBook Flip
dmi.product.name: VivoBook_ASUSLaptop TP412FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "Screenshot after spontaneous rotation"
   
https://bugs.launchpad.net/bugs/1887150/+attachment/5391268/+files/Screenshot%20from%202020-07-10%2006-33-53.png

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

Title:
  Fractional Scaling turns screen sideways

Status in xorg package in Ubuntu:
  New

Bug description:
  I right-click on desktop, click Display Settings, and find the Fractional 
Scaling option.
  When I enable the option my screen rotates 90 degrees. It's as if the display 
thought I had rotated my device 90 degrees (but I hadn't I'm using a laptop).
  Can attach screenshots if possible.

  I just freshly installed Ubuntu 20.04 from a USB and ran sudo apt-get
  update and sudo apt-get upgrade for the first time literally minutes
  ago. Nothing else was installed except for Grub Customizer and

  EDIT: Turns out I can't attach three screenshots. I can only attach
  one. I attached the final screenshot. I took screenshots of the
  original rotation, then before I selected the Fractional Scaling
  option, then what happened after. But I can only attach one of them.
  Please allow 

[Touch-packages] [Bug 1887150] Re: Fractional Scaling turns screen sideways

2020-07-10 Thread dryphi
Adding screenshots in sequence. First one.

** Attachment added: "Screenshot #1"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887150/+attachment/5391285/+files/Screenshot%20from%202020-07-10%2006-33-32.png

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

Title:
  Fractional Scaling turns screen sideways

Status in xorg package in Ubuntu:
  New

Bug description:
  I right-click on desktop, click Display Settings, and find the Fractional 
Scaling option.
  When I enable the option my screen rotates 90 degrees. It's as if the display 
thought I had rotated my device 90 degrees (but I hadn't I'm using a laptop).
  Can attach screenshots if possible.

  I just freshly installed Ubuntu 20.04 from a USB and ran sudo apt-get
  update and sudo apt-get upgrade for the first time literally minutes
  ago. Nothing else was installed except for Grub Customizer and

  EDIT: Turns out I can't attach three screenshots. I can only attach
  one. I attached the final screenshot. I took screenshots of the
  original rotation, then before I selected the Fractional Scaling
  option, then what happened after. But I can only attach one of them.
  Please allow us to attach more than one screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 10 06:34:56 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) 
[1043:19d1]
  InstallationDate: Installed on 2020-07-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b568 Chicony Electronics Co., Ltd USB2.0 VGA UVC 
WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP412FA
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=d20ac799-f93e-4aea-9632-495aa9132b04 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: TP412FA.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: TP412FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrTP412FA.302:bd05/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP412FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP412FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: VivoBook Flip
  dmi.product.name: VivoBook_ASUSLaptop TP412FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

2020-07-10 Thread Goran Josic
Same issue with kernel 5.6.10.

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

Title:
  Dualshock4 controller doesn't stay connected

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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


[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-10 Thread Kai-Heng Feng
Well, let's start from `apport-collect 1871721`.

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).

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

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


[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)

2020-07-10 Thread Noctis Bennington
I'm sure around 99% it's Intel.

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

Title:
  Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel &
  Ubuntu 20.04? (ASUS Laptop)

Status in kernel-package package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in nouveau-firmware package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary 
drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use 
it, but I saw that I cannot use it, I just see a blank screen. I tried with a 
TV of my room and same. The funny part is when I start the laptop to work, I 
can see the logo of my BIOS and the ASUS logo in the second monitor, even the 
grub, but after that I can't see nothing.
  When I reduce the resolution of the second monitor (800x600) then works, but 
even with that sometimes blinks to black again.
  On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI.

  I tried with nouveau drivers and I have the same results btw.

  Laptop Asus with:
  Graphic card  Nvidia GTX960M
  Processor  Intel i5 6300

  I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them
  works. All of them with Xorg.

  I have this with xrandr:

  Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384
  eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 344mm x 193mm
     1920x1080 60.00*+  59.9759.9659.93
     1680x1050 59.9559.88
     1600x1024 60.17
     1400x1050 59.98
     1600x900  59.9959.9459.9559.82
     1280x1024 60.02
     1440x900  59.89
     1400x900  59.9659.88
     1280x960  60.00
     1440x810  60.0059.97
     1368x768  59.8859.85
     1360x768  59.8059.96
     1280x800  59.9959.9759.8159.91
     1152x864  60.00
     1280x720  60.0059.9959.8659.74
     1024x768  60.0460.00
     960x720   60.00
     928x696   60.05
     896x672   60.01
     1024x576  59.9559.9659.9059.82
     960x600   59.9360.00
     960x540   59.9659.9959.6359.82
     800x600   60.0060.3256.25
     840x525   60.0159.88
     864x486   59.9259.57
     800x512   60.17
     700x525   59.98
     800x450   59.9559.82
     640x512   60.02
     720x450   59.89
     700x450   59.9659.88
     640x480   60.0059.94
     720x405   59.5158.99
     684x384   59.8859.85
     680x384   59.8059.96
     640x400   59.8859.98
     576x432   60.06
     640x360   59.8659.8359.8459.32
     512x384   60.00
     512x288   60.0059.92
     480x270   59.6359.82
     400x300   60.3256.34
     432x243   59.9259.57
     320x240   60.05
     360x202   59.5159.13
     320x180   59.8459.32
  DP-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-1 disconnected (normal left inverted right x axis y axis)
  HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 
1600mm x 900mm
     1920x1080 60.00 +  50.0059.9430.0025.0024.0029.97  
  23.98
     1920x1080i60.0050.0059.94
     1280x1024 60.02
     1360x768  60.02
     1152x864  59.97
     1280x720  59.8160.0050.0059.94
     1024x768  60.00
     800x600   60.32*
     720x576   50.00
     720x576i  50.00
     720x480   60.0059.94
     640x480   60.0059.94
     720x400   70.08
  DP-1-2 disconnected (normal left inverted right x axis y axis)
  HDMI-1-3 disconnected (normal left inverted right x axis y axis)

  PD: When you select a specific resolution, the second monitor "works",
  but it blinks, the image showed via HDMI on the second monitor blinks.
  So is impossible to work with it. Since all this time I was searching
  about this and I'm almost sure this is a problem of the GPU's Intel.
  But I saw this problem on askubuntu just with laptops with hybrid
  graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not
  sure if they have the same problem here).

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

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


[Touch-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

2020-07-10 Thread Rex Tsai
** Tags added: beaver-osp1-melisa

** Tags added: oem-priority

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

Title:
  Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8
  GT2)

Status in OEM Priority Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

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

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