[Touch-packages] [Bug 1373448] Re: [ASUS X202E] Unable to set third button emulation on Atmel touchscreen

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [ASUS X202E] Unable to set third button emulation on Atmel touchscreen

Status in xorg package in Ubuntu:
  Expired

Bug description:
  My machine is ASUS X202E. It has an Atmel maXTouch Digitizer. I
  modified /usr/share/X11/xorg.conf.d/10-evdev.conf to add the following
  options to the touchscreen section:

  Option "EmulateThirdButton" "1"
  Option "EmulateThirdButtonButton" "3"
  Option "EmulateThirdButtonTimeout" "750"
  Option "EmulateThirdButtonThreshold" "50"

  and restarted X. Running xinput list-props shows that these properties
  are indeed set for the Atmel touchscreen device. However, when I touch
  and hold my finger in the same spot on the screen, nothing happens!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Sep 24 16:09:59 2014
  DistUpgraded: 2014-04-18 09:55:47,870 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:108d]
  InstallationDate: Installed on 2013-10-15 (343 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131007)
  MachineType: ASUSTeK COMPUTER INC. X202E
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic.efi.signed 
root=UUID=bcc104a1-a7cd-4485-b9ff-bf585e1eec22 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-04-18 (159 days ago)
  dmi.bios.date: 06/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X202E.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X202E
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX202E.210:bd06/20/2013:svnASUSTeKCOMPUTERINC.:pnX202E:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX202E:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X202E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Wed Sep 24 16:08:42 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12380 
   vendor AUO
  xserver.version: 2:1.15.1-0ubuntu2.1

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


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


[Touch-packages] [Bug 1490255] Re: changes in /etc/default/keyboard not loaded

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  changes in /etc/default/keyboard not loaded

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu 15.04
  Release:  15.04
  Variant:Xubuntu

  What you expected to happen:
  Changes in /etc/default/keyboard to be effective.

  What happened instead:
  Nothing.

  ex: 
   
  File : /etc/default/keyboard

  # KEYBOARD CONFIGURATION FILE

  # Consult the keyboard(5) manual page.

  XKBMODEL="pc105"
  XKBLAYOUT="fr"
  XKBVARIANT="latin9"
  XKBOPTIONS="altwin:ctrl_alt_win"

  BACKSPACE="guess"

  
  Nothing happens after boot.

  (but setxkbmap -option alt win:ctrl_alt_win does works)

  Suggestion : 
  -Remove /etc/default/keyboard as it doesn't seems to serve any purpose other 
than misleading people.
  -Make somehow working as it should.

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


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


[Touch-packages] [Bug 1682941] Re: graphics connection and resolution

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  graphics connection and resolution

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Please see bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Apr 14 17:22:54 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122] (prog-if 00 
[VGA controller])
 Subsystem: VIA Technologies, Inc. VX900 Graphics [Chrome9 HD] [1106:7122]
  InstallationDate: Installed on 2017-04-14 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  MachineType: Hewlett-Packard HP t5565z Thin Client
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=6ed5fed6-7449-44ca-b3be-da8be55b0514 ro quiet vesafb.invalid=1 splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 786R9 v1.04
  dmi.board.asset.tag: Astronaut
  dmi.board.name: 158Ch
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: MXL2150RT5
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr786R9v1.04:bd11/10/2011:svnHewlett-Packard:pnHPt5565zThinClient:pvr:rvnHewlett-Packard:rn158Ch:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP t5565z Thin Client
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Apr 14 16:18:30 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSleep Button KEYBOARD, id 8
   inputLogitech K400KEYBOARD, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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


[Touch-packages] [Bug 1665853] Re: HWE 16.04.2: Login Screen goes partially black after upgrade (Dual Screen)

2022-12-21 Thread Launchpad Bug Tracker
[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HWE 16.04.2: Login Screen goes partially black after upgrade (Dual
  Screen)

Status in gnome-flashback package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Expired
Status in xorg package in Ubuntu:
  Expired

Bug description:
  I'm using ubuntu 16.04, up-to-date, HWE kernel 4.8.0-36-generic.

  On dual screen setup, during system login, the first screen stretches
  over a part of the second screen (about 25% of it), whereas the rest
  of the second screen is black. Like this:

  
   
  #  # #<<|...#
  # Login# #<<|.Black.#
  #  # #<<|...#
   

  The part marked with "<<" is the rightest part of the background image
  of the first screen. I've seen this after updating to xorg/xserver-
  hwe-16.04, whereas installing the hwe kernel alone did not make this
  happen.

  Nevertheless, I can login and everything is fine again. Both screens
  look as they should. (I had to reconfigure monitors once after
  updating to xorg/xserver-hwe-16.04).

  sylog shows:

  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not assign CRTC to outputs, ignoring configuration
  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not make default configuration for current output layout, leaving 
unconfigured

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-flashback 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Feb 18 07:46:46 2017
  InstallationDate: Installed on 2014-11-29 (812 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-flashback
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (247 days ago)

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


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


[Touch-packages] [Bug 1639581] Re: New_nvidia_driver.

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  New_nvidia_driver.

Status in xorg package in Ubuntu:
  Expired

Bug description:
  
  It has something to do with the NVIDIA driver that has just been updated.
  It starts in low resolution with startup.
  Can startup in recovery modus.
  My GPU is Nvidia GEFORCE GTX 970 desktop.
  If I disable bootloader graphics
  and disable VESA framebuffer driver
  and disable PAT memory I get a cursor and a blackscreen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.57  Mon Oct  3 20:37:01 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Nov  6 15:07:37 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-45-generic, x86_64: installed
   nvidia-367, 367.57, 4.4.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Elitegroup Computer Systems GM204 [GeForce GTX 970] [1019:1029]
  InstallationDate: Installed on 2016-11-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: MEDION Akoya P5332 I/C124
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 110EMW0X.102
  dmi.board.name: H110H4-EM
  dmi.board.vendor: MEDION
  dmi.board.version: 2.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDION
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr110EMW0X.102:bd03/04/2016:svnMEDION:pnAkoyaP5332I/C124:pvr1.0:rvnMEDION:rnH110H4-EM:rvr2.0:cvnMEDION:ct3:cvr:
  dmi.product.name: Akoya P5332 I/C124
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDION
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Nov  6 14:47:05 2016
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.1

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


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


[Touch-packages] [Bug 1645352] Re: No HDMI output after upgrade to 16.04!

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  No HDMI output after upgrade to 16.04!

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Running Ubuntu 16.04 64bit, 4.4.8 Kernel on an ASUS Trio with Intel® Haswell 
graphics card and using i915 driver. After upgrade there is no HDMI output to 
the external screen that I use daily. 
  I did the following:
  - Upgraded to  4.4.8 Kernel hoping that the issue would be resolved.
  - Checked for other reports of this issue and followed advise to use NVIDIA 
364 drivers. 
  - Checked Intel for the most recent driver which is already packaged with 
16.04;  it is the i915 driver which is in use.
  - Used Intel driver update tool to ensure that update is correct.
  - Purchased a HDMI adapter to use mini-display port; works and reports HDMI1 
is in use, but HDMI2 is not recognized (when monitor is plugged in to HDMI2)
  - Someone has assisted and has confirmed that there seems to be no hardware 
issues.

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


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


[Touch-packages] [Bug 1655436] Re: HDMI-display not working

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HDMI-display not working

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Hi!

  Since I upgraded to Ubuntu 16.04 my HDMI-display is not recognized.
  I'm on an HP laptop (dv7-1095) with an Nvidia 9600M GT graphics card.
  Does anyone know what might cause this problem? :)

  Regards
  Emil

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  304.134  Fri Dec  9 11:30:02 
PST 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jan 10 20:31:47 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed
   nvidia-304, 304.134, 4.4.0-59-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation G96M [GeForce 9600M GT] [10de:0649] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G96M [GeForce 9600M GT] [103c:30f4]
  InstallationDate: Installed on 2017-01-08 (2 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/17/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 30F4
  dmi.board.vendor: Compal
  dmi.board.version: 99.55
  dmi.chassis.type: 10
  dmi.chassis.vendor: Compal
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd07/17/2008:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.0A:rvnCompal:rn30F4:rvr99.55:cvnCompal:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv7 Notebook PC
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Jan 10 20:26:54 2017
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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


[Touch-packages] [Bug 1665853] Re: HWE 16.04.2: Login Screen goes partially black after upgrade (Dual Screen)

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HWE 16.04.2: Login Screen goes partially black after upgrade (Dual
  Screen)

Status in gnome-flashback package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Expired
Status in xorg package in Ubuntu:
  Expired

Bug description:
  I'm using ubuntu 16.04, up-to-date, HWE kernel 4.8.0-36-generic.

  On dual screen setup, during system login, the first screen stretches
  over a part of the second screen (about 25% of it), whereas the rest
  of the second screen is black. Like this:

  
   
  #  # #<<|...#
  # Login# #<<|.Black.#
  #  # #<<|...#
   

  The part marked with "<<" is the rightest part of the background image
  of the first screen. I've seen this after updating to xorg/xserver-
  hwe-16.04, whereas installing the hwe kernel alone did not make this
  happen.

  Nevertheless, I can login and everything is fine again. Both screens
  look as they should. (I had to reconfigure monitors once after
  updating to xorg/xserver-hwe-16.04).

  sylog shows:

  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not assign CRTC to outputs, ignoring configuration
  Feb 18 06:27:03 lat61 gnome-session[3242]: ** (gnome-flashback:3340): WARNING 
**: Could not make default configuration for current output layout, leaving 
unconfigured

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-flashback 3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Feb 18 07:46:46 2017
  InstallationDate: Installed on 2014-11-29 (812 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gnome-flashback
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (247 days ago)

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


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


[Touch-packages] [Bug 1659140] Re: x crashes when I log in and back out of a tty (console, cntrl-alt-F2 thing, whatever)

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  x crashes when I log in and back out of a tty (console, cntrl-alt-F2
  thing, whatever)

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Observed behavior:

  When I get an alternate tty, or whatever it's called, with cntrl-alt-
  FN, where N is any digit, 2-6, inclusive; log in as the same user on
  the console; do stuff; and then log out with "exit":

  I'm suddenly back in tty1 and X has crashed. There is no x on any
  console. I can start it again with startx.

  Expected behavior:

  As it does in 14.04, I should just get a login prompt and stay in the
  same console. X running in tty1 should be unaffected, like x in tty7
  would be unaffected in Trusty.

  
  This is 64 bit Xenial with a minimalist Openbox environment, built from the 
mini.iso. I start X with "startx".

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


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


[Touch-packages] [Bug 1686633] Re: Could not set the configuration for CRTC 64

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Could not set the configuration for CRTC 64

Status in xorg package in Ubuntu:
  Expired

Bug description:
  I am running on a dual screen installation with a razer blade laptop.
  At startup, I have a popup saying "Could not set the configuration for CRTC 
64".
  If I close the popup, I loose all of my screens.
  If I let the popup opened, everything works fine except that some ubuntu 
components doesn't show up with the usual visual style (i.e. no 3d effect and 
no fancy color for OS buttons).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  Uname: Linux 4.4.0-77-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Apr 27 10:27:02 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Razer USA Ltd. Skylake Integrated Graphics [1a58:674f]
   NVIDIA Corporation Device [10de:1c20] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Razer USA Ltd. Device [1a58:674f]
  InstallationDate: Installed on 2016-05-07 (355 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Razer Blade
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-77-generic 
root=UUID=78c70b10-8984-4954-bb25-3d374dd77dd6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/02/2016
  dmi.bios.vendor: Razer
  dmi.bios.version: E1.00
  dmi.board.name: Blade
  dmi.board.vendor: Razer
  dmi.board.version: Late 2016
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.chassis.version: Blade (Late 2016)
  dmi.modalias: 
dmi:bvnRazer:bvrE1.00:bd09/02/2016:svnRazer:pnBlade:pvr5.04:rvnRazer:rnBlade:rvrLate2016:cvnRazer:ct9:cvrBlade(Late2016):
  dmi.product.name: Blade
  dmi.product.version: 5.04
  dmi.sys.vendor: Razer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 27 10:22:39 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: modeset(G0): failed to set mode: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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


[Touch-packages] [Bug 1703129] Re: VCE init error and much more in my lappy please see it

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  VCE init error and much more in my lappy please see it

Status in xorg package in Ubuntu:
  Expired

Bug description:
  more errors see it

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  NonfreeKernelModules: openafs wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jul  8 20:48:24 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-81-generic, x86_64: installed
   openafs, 1.6.15, 4.4.0-79-generic, x86_64: installed
   openafs, 1.6.15, 4.4.0-81-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:80c2]
  InstallationDate: Installed on 2016-11-24 (225 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP Notebook
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic.efi.signed 
root=UUID=f110cba6-8b9c-4548-8ed4-f543954307e6 ro splash quiet vesafb.invalid=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.47
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd05/17/2016:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C2:rvr96.47:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sat Jul  8 17:29:30 2017
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   20049 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.2

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


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


[Touch-packages] [Bug 1708829] Re: Unable to detect correct resolution of external monitor

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Unable to detect correct resolution of external monitor

Status in xorg package in Ubuntu:
  Expired

Bug description:
  My system is unable to detect the correct resolution of the monitor.
  This problem is not consistent and happens randomly. I think its a
  driver issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-87.110-generic 4.4.73
  Uname: Linux 4.4.0-87-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Aug  5 17:51:25 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-87-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-89-generic, x86_64: installed
   nvidia-375, 375.66, 4.4.0-87-generic, x86_64: installed
   nvidia-375, 375.66, 4.4.0-89-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:380a]
 Subsystem: Lenovo GK208M [GeForce GT 740M] [17aa:380a]
  InstallationDate: Installed on 2015-12-21 (593 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20287
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-87-generic.efi.signed 
root=UUID=b2b670cf-975c-444c-b9be-75df78fb9323 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900059STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z510
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DCN40WW:bd10/24/2014:svnLENOVO:pn20287:pvrLenovoIdeaPadZ510:rvnLENOVO:rnVIUU4:rvr31900059STD:cvnLENOVO:ct10:cvrLenovoIdeaPadZ510:
  dmi.product.name: 20287
  dmi.product.version: Lenovo IdeaPad Z510
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Aug  4 23:58:05 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5565 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.3

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


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


[Touch-packages] [Bug 1732116] Re: HDMI device is not working / not found

2022-12-21 Thread Launchpad Bug Tracker
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  HDMI  device is not working / not found

Status in xorg package in Ubuntu:
  Expired

Bug description:
  after conecting TV over HDMI, Ubuntu doenst find the external display

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Nov 14 10:29:17 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G94GLM [Quadro FX 2700M] [103c:30ec]
  InstallationDate: Installed on 2017-09-10 (64 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 8730w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=95c3f524-8551-407a-91a0-65632f3854b3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PAD Ver. F.13
  dmi.board.name: 30EC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.25
  dmi.chassis.asset.tag: CNU911000L
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PADVer.F.13:bd12/03/2010:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.13:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8730w
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Nov 14 09:58:47 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: nouveau

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


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


[Touch-packages] [Bug 1912911] Re: When printing with my Brother hl-2170w printer I keep getting an invalid page range error on a blank page, after the desired pages are printed

2022-12-21 Thread sokolov
Is there a regression? I suddenly had this problem again. I wanted to
print a single page, but received three. Two of them say just this:

Invalid page range Drum \\\ Unit printer-state=3 printer-uri-
supported=ipp

uname -a:

Linux 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 20:19:22 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux

apt-cache policy cups
cups:
  Installed: 2.3.1-9ubuntu1.2
  Candidate: 2.3.1-9ubuntu1.2
  Version table:
 *** 2.3.1-9ubuntu1.2 500
 2.3.1-9ubuntu1 500
 
My computer has an Intel Xeon CPU.

My printer is a Dell E514dw, which is a rebadged Brother MFC-L5750DW
(except for the printer cartridges).

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

Title:
  When printing with my Brother hl-2170w printer I keep getting an
  invalid page range error on a blank page, after the desired pages are
  printed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I run uname -a, this is basically what I get:
  "5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux"

  apt-cache policy cups gives me the following:

  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
===

  4 and 5 are being answered together...

  Before the upgrade, I was able to print one or more pages, and not see the 
extra error page.
  This is the desired behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 23 13:15:24 2021
  InstallationDate: Installed on 2020-12-21 (33 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for SCRIBE: 
dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/
  MachineType: Dell Inc. Inspiron 7773
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/SCRIBE.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/SCRIBE.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=9899e123-f378-4328-a399-78cd6361f58e ro quiet splash 
resume=UUID=46e80ad1-16de-4fdf-b1f7-96f4f58b1c57
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0R58C3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd09/14/2017:br1.2:svnDellInc.:pnInspiron7773:pvr:rvnDellInc.:rn0R58C3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7773
  dmi.product.sku: 0809
  dmi.sys.vendor: Dell Inc.

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


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


[Touch-packages] [Bug 1567250] Re: ssh signin problem since OTA-10

2022-12-21 Thread api.ng
** Changed in: ubuntu-terminal-app
   Status: Incomplete => Confirmed

** Changed in: indicator-network (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: openssh (Ubuntu)
   Status: Invalid => Confirmed

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => api.ng (hektve)

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => api.ng (hektve)

** Changed in: gnome-keyring (Ubuntu)
 Assignee: (unassigned) => api.ng (hektve)

** Changed in: ubuntu-terminal-app
 Assignee: (unassigned) => api.ng (hektve)

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => api.ng (hektve)

** Package changed: indicator-network (Ubuntu) => indicator-network (PLD
Linux)

** Changed in: indicator-network (PLD Linux)
 Assignee: api.ng (hektve) => (unassigned)

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

Title:
  ssh signin problem since OTA-10

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Terminal App:
  Confirmed
Status in gnome-keyring package in Ubuntu:
  Confirmed
Status in openssh package in Ubuntu:
  Confirmed
Status in indicator-network package in PLD Linux:
  Confirmed

Bug description:
  Not sure if this is a terminal or image issue, but here goes.

  Since the update last night to OTA-10 I cannot ssh to a server
  anymore. Error message: "Agent Admitted Failure To Sign Using The Key"

  On server side and client side nothing changed to the user settings or
  keys.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1567250/+subscriptions


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


[Touch-packages] [Bug 2000276] [NEW] FIDO2 user verification impossible when using the ssh agent

2022-12-21 Thread Andrea Ieri
Public bug reported:

I am having trouble setting up FIDO2 ssh keys with my yubikey 5C NFC if
I want to enable user verification (user presence works fine).


Steps to reproduce:

= Prep work =

Client (kinetic):
* generate a key that requires user verification:
  $ ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_verify_sk -O verify-required 
-C "this key requires UV"
  [provide your authenticator PIN, touch it, and add an encryption password]

Server (jammy):
* add id_ed25519_verify_sk.pub to authorized_keys

= Symptoms =

Shell 1 (w/ssh agent):

$ eval $(ssh-agent)
Agent pid 3279738

$ ssh-add ~/.ssh/id_ed25519_verify_sk
Enter passphrase for /home/aieri/.ssh/id_ed25519_verify_sk: 
Identity added: /home/aieri/.ssh/id_ed25519_verify_sk (this key requires UV)

$ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 fails\!"
sign_and_send_pubkey: signing failed for ED25519-SK 
"/home/aieri/.ssh/id_ed25519_verify_sk" from agent: agent refused operation
ubuntu@10.35.202.231: Permission denied (publickey).

[note that the above is printed immediately, and that the yubikey does
not light up]

Shell 2 (no ssh agent):

$ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 works\!"
Enter passphrase for key '/home/aieri/.ssh/id_ed25519_verify_sk': 
Enter PIN for ED25519-SK key /home/aieri/.ssh/id_ed25519_verify_sk: 
Confirm user presence for key ED25519-SK 
SHA256:nhgS4c2rGtE7XKeez3rAsofrjJvsL6rmBLShZxfTXIY
User presence confirmed
FIDO2 works!


NOTE: 
* user _presence_ can be validated correctly with or without the ssh-agent: 
keys generated without `-O verify-required` work as expected (aside from bug 
1869897)

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

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

Title:
  FIDO2 user verification impossible when using the ssh agent

Status in openssh package in Ubuntu:
  New

Bug description:
  I am having trouble setting up FIDO2 ssh keys with my yubikey 5C NFC
  if I want to enable user verification (user presence works fine).

  
  Steps to reproduce:

  = Prep work =

  Client (kinetic):
  * generate a key that requires user verification:
$ ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_verify_sk -O 
verify-required -C "this key requires UV"
[provide your authenticator PIN, touch it, and add an encryption password]

  Server (jammy):
  * add id_ed25519_verify_sk.pub to authorized_keys

  = Symptoms =

  Shell 1 (w/ssh agent):

  $ eval $(ssh-agent)
  Agent pid 3279738

  $ ssh-add ~/.ssh/id_ed25519_verify_sk
  Enter passphrase for /home/aieri/.ssh/id_ed25519_verify_sk: 
  Identity added: /home/aieri/.ssh/id_ed25519_verify_sk (this key requires UV)

  $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 fails\!"
  sign_and_send_pubkey: signing failed for ED25519-SK 
"/home/aieri/.ssh/id_ed25519_verify_sk" from agent: agent refused operation
  ubuntu@10.35.202.231: Permission denied (publickey).

  [note that the above is printed immediately, and that the yubikey does
  not light up]

  Shell 2 (no ssh agent):

  $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 works\!"
  Enter passphrase for key '/home/aieri/.ssh/id_ed25519_verify_sk': 
  Enter PIN for ED25519-SK key /home/aieri/.ssh/id_ed25519_verify_sk: 
  Confirm user presence for key ED25519-SK 
SHA256:nhgS4c2rGtE7XKeez3rAsofrjJvsL6rmBLShZxfTXIY
  User presence confirmed
  FIDO2 works!


  NOTE: 
  * user _presence_ can be validated correctly with or without the ssh-agent: 
keys generated without `-O verify-required` work as expected (aside from bug 
1869897)

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


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


[Touch-packages] [Bug 1926802] Re: qt5-default package is missed in 21.04

2022-12-21 Thread Christian Lampe
But the package name says `qt5-*`. Are the `qt6-*` packages for Qt 5 ?!?

** Also affects: unity-linux
   Importance: Undecided
   Status: New

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

Title:
  qt5-default package is missed in 21.04

Status in qtbase-opensource-src package in Ubuntu:
  Invalid
Status in Unity Linux:
  New

Bug description:
  Previous 20.10 version has the qt5-default package in place (see
  https://packages.ubuntu.com/groovy/qt5-default ).

  Please upload the  qt5-default package for 21.04 Ubuntu version.

  What is interesting - all its dependencies can be simply installed
  with `sudo apt-get install qtbase5-dev qtchooser qt5-qmake
  qtbase5-dev-tools` .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1926802/+subscriptions


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


[Touch-packages] [Bug 2000062] Re: test-pivot_root_parse.py in apparmor failed with ImportError: No module named apparmor.aa

2022-12-21 Thread Po-Hsu Lin
Note that this issue was not uncovered when running the whole test suite
in test-apparmor.py from qa-regression-testing is because of bug 2000233

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

Title:
  test-pivot_root_parse.py in apparmor failed with ImportError: No
  module named apparmor.aa

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Bionic:
  New
Status in apparmor source package in Focal:
  New

Bug description:
  Steps to reproduce:
  # Via qa-regression-testing
  git clone --depth=1 git://git.launchpad.net/qa-regression-testing
  cd qa-regression-testing/scripts
  sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite

  == Update base on John's comment in #1
  Note that we cannot use apparmor cloned from launchpad directly, it requires 
some other local patches in qa-regression-testing:
  https://git.launchpad.net/qa-regression-testing/tree/scripts/apparmor/patches
  To experiment with the patched version via qa-regression-testing, comment out 
the following lines (1583, 1584) in tearDown():
  if os.path.exists(self.tmpdir):
  testlib.recursive_rm(self.tmpdir)
  And run:
  sudo python3 ./test-apparmor.py -v ApparmorTestsuites.test_utils_testsuite

  The patched apparmor can be found in /tmp, now it can be tested with things 
like:
  cd /tmp/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils
  export USE_SYSTEM=1
  make check
  == End of update

  
  Output:
  LANG=C podchecker -warning -warning *.pod
  aa-audit.pod pod syntax OK.
  aa-autodep.pod pod syntax OK.
  aa-cleanprof.pod pod syntax OK.
  aa-complain.pod pod syntax OK.
  aa-decode.pod pod syntax OK.
  aa-disable.pod pod syntax OK.
  aa-easyprof.pod pod syntax OK.
  aa-enforce.pod pod syntax OK.
  aa-genprof.pod pod syntax OK.
  aa-logprof.pod pod syntax OK.
  aa-mergeprof.pod pod syntax OK.
  aa-notify.pod pod syntax OK.
  aa-remove-unknown.pod pod syntax OK.
  aa-sandbox.pod pod syntax OK.
  aa-status.pod pod syntax OK.
  aa-unconfined.pod pod syntax OK.
  logprof.conf.pod pod syntax OK.
  aa-notify syntax OK
  Checking aa-easyprof
  Checking aa-genprof
  Checking aa-logprof
  Checking aa-cleanprof
  Checking aa-mergeprof
  Checking aa-autodep
  Checking aa-audit
  Checking aa-complain
  Checking aa-enforce
  Checking aa-disable
  Checking aa-status
  Checking aa-unconfined
  Checking apparmor
  Checking test/common_test.py
  Checking test/minitools_test.py
  Checking test/test-aa-decode.py
  Checking test/test-aa-easyprof.py
  Checking test/test-aa.py
  Checking test/test-aamode.py
  Checking test/test-aare.py
  Checking test/test-baserule.py
  Checking test/test-capability.py
  Checking test/test-change_profile.py
  Checking test/test-common.py
  Checking test/test-config.py
  Checking test/test-dbus.py
  Checking test/test-example.py
  Checking test/test-file.py
  Checking test/test-libapparmor-test_multi.py
  Checking test/test-logparser.py
  Checking test/test-mount_parse.py
  Checking test/test-network.py
  Checking test/test-parser-simple-tests.py
  Checking test/test-pivot_root_parse.py
  Checking test/test-profile-list.py
  Checking test/test-profile-storage.py
  Checking test/test-ptrace.py
  Checking test/test-regex_matches.py
  Checking test/test-rlimit.py
  Checking test/test-severity.py
  Checking test/test-signal.py
  Checking test/test-translations.py
  Checking test/test-unix_parse.py
  make[1]: Entering directory 
'/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test'

  === test-example.py ===
  ...
  --
  Ran 7 tests in 0.000s

  OK
  ...
  --
  Ran 7 tests in 0.000s

  OK

  === test-pivot_root_parse.py ===
  Traceback (most recent call last):
    File "test-pivot_root_parse.py", line 12, in 
  import apparmor.aa as aa
  ImportError: No module named apparmor.aa
  make[1]: *** [Makefile:81: check] Error 1
  make[1]: Leaving directory 
'/home/ubuntu/testlibwl29iqzr/source/focal/apparmor-2.13.3/utils/test'
  make: *** [Makefile:97: check] Error 2

  Issue found on B-ibm-gt-5.4, F-oem-5.14, F-aws-fips after we changed
  how we run the ubuntu_qrt_apparmor test in bug 1982439.

  Sub-test in ApparmorTestsuites.test_utils_testsuite will fail with
  this.

  After some inspection it is because the script is trying to use python2. This 
can be verified with:
  python2 -c "import apparmor.aa"
  python3 -c "import apparmor.aa"

  This appears to be a known issue.
  
https://gitlab.com/apparmor/apparmor/-/commit/af69088546d7d2f7188b9dec814f81721254964f

  And this patch has already landed in apparmor on Jammy, we will need this for 
Bionic / Focal as well. A temporary workaround is to