[Touch-packages] [Bug 1970523] Re: [Mesa Intel® HD Graphics 3000 (SNB GT2)] Cannot able to Change gamma on Inspiron 3520.

2022-04-26 Thread Daniel van Vugt
Thanks for the bug report.

Those gamma commands only support Xorg, but you are using a Wayland
session without any Xorg running. To use a Xorg session you need to log
out and then select 'Ubuntu on Xorg' on the login screen.


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

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

Title:
  [Mesa Intel® HD Graphics 3000 (SNB GT2)] Cannot able to Change gamma
  on Inspiron 3520.

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I am using Dell Inspiron 3520. It have Mesa Intel® HD Graphics 3000 (SNB GT2) 
Graphics.
  Problems I am facing:

  I am unable to change gamma via xgamma or randrx.

  It was working fine on ubuntu 20.04. After Upgrade it is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 10:36:19 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0555]
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 3520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=ea5b9322-6015-490d-b607-48fd6b6c04df ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
  dmi.product.name: Inspiron 3520
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970523/+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 1970471] Re: Changing applications bug 22.04LTS

2022-04-26 Thread Daniel van Vugt
If it's just displaying the wrong texture/window then that fix may be
one that's coming in mutter 42.1:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2278


** Package changed: xorg (Ubuntu) => gnome-shell (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/1970471

Title:
  Changing applications bug 22.04LTS

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I have Firefox and the android studio code opened at the same time.
  If I am using Firefox and want to move into studio code, I press the "super" 
key to show all the apps running and click with my mouse the studio code app. 
Instead of showing ASC it keeps showing me Firefox, but not the other way 
around, when I am in ASC and want to change to Firefox, it does change.
  This only happens when using the "super" key by itself, when using "super + 
tab" or "alt + tab" it does change.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 21:06:02 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Toshiba Corporation HD Graphics 5500 [1179:000a]
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
   |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 
480M
   |__ Port 8: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
   |__ Port 8: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
  MachineType: TOSHIBA Satellite Pro R50-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=b739b2dd-b328-4bee-a14e-8e1cc4583783 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2015
  dmi.bios.release: 1.20
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.20
  dmi.board.asset.tag: 00
  dmi.board.name: Satellite Pro R50-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.20:bd01/30/2015:br1.20:efr1.10:svnTOSHIBA:pnSatelliteProR50-B:pvrPSSG2E-00K004CE:rvnTOSHIBA:rnSatelliteProR50-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:skuPSSG2E:
  dmi.product.family: 00
  dmi.product.name: Satellite Pro R50-B
  dmi.product.sku: PSSG2E
  dmi.product.version: PSSG2E-00K004CE
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1970471/+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 1969901] Re: network-manager fails to renew ipv6 address

2022-04-26 Thread Håkan Kvist
** Description changed:

- We have experienced this issue on mixed ipv6/ipv4 corporate network on Ubuntu 
18.04.
- Unfortunately next LTS release is not yet an option for us.
+ [Impact]
  
- This is same as https://bugzilla.gnome.org/show_bug.cgi?id=783391
- This was fixed in 1.12.0.
+  * Network manager might kill dhclient(6) and fail to start it again
+causing the IPv6 address to be lost on a network that uses mixed
+IPv4/IPV6.
+The network status will still be seen as online in gnome since ipv4
+is still active.
+The user then have to manually remove the dhcpv6 lease files and
+restart ipv6 connection/restart network manager to regain IPv6
+connectivity.
  
- Could you consider including the below patch on ubuntu 18.04?
+  * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
+is based on 1.10.6):
+
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f
  
- 
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=17009ed91da8b3e0b10ee7e94d220be9bd3fa84c
+  * Upstream bug:
+https://bugzilla.gnome.org/show_bug.cgi?id=783391
  
- The patch can be applied with some adjustements on top of the version of
- network manager included in Bionic (pull-lp-source network-manager
- bionic). A function name has changed, changing the function name in the
- downloaded patch is enough to apply the patch.
+ [Test Plan]
  
- cat
- 
../57ab9fd60fc9ec3ab7bc3fcef40b1f003d614162..17009ed91da8b3e0b10ee7e94d220be9bd3fa84c.patch
- |sed
- 's|nm_dbus_object_clear_and_unexport|nm_exported_object_clear_and_unexport|g'
- > modified_patch.patch
+  * The exact conditions for reproducing this bug on mixed IPv4/IPv6
+networks are not known but includes using both IPv4 and IPv6,
+both using dhcp.
  
- This has been tested on some devices and so far we have not seen any problems
- ipv4 only network (cable/wifi)
- ipv6/ipv4 mixed network (cable/wifi)
+ [Where problems could occur]
+ 
+  * This patch could possibly break networking using and that would be bad.
+Network manager should be able to restart connection more properly with
+this patch though.
+ 
+ [Other Info]
+  * We have tested this patch on a couple of clients where we have seen this
+this problem. If this patch is feasible to include in Ubuntu 18.04 we
+could request more users to test.

** Patch added: "Debdiff against network-manager_1.10.6-2ubuntu1.5"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+attachment/5584241/+files/network-manager_1.10.6-2ubuntu1.6.debdiff

** Description changed:

  [Impact]
  
-  * Network manager might kill dhclient(6) and fail to start it again
-causing the IPv6 address to be lost on a network that uses mixed
-IPv4/IPV6.
-The network status will still be seen as online in gnome since ipv4
-is still active.
-The user then have to manually remove the dhcpv6 lease files and
-restart ipv6 connection/restart network manager to regain IPv6
-connectivity.
+  * This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
+ used.
  
-  * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
-is based on 1.10.6):
-
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f
+  * Network manager might kill dhclient(6) and fail to start it again
+    causing the IPv6 address to be lost on a network that uses mixed
+    IPv4/IPV6.
+    The network status will still be seen as online in gnome since ipv4
+    is still active.
+    The user then have to manually remove the dhcpv6 lease files and
+    restart ipv6 connection/restart network manager to regain IPv6
+    connectivity.
  
-  * Upstream bug:
-https://bugzilla.gnome.org/show_bug.cgi?id=783391
+  * This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
+    is based on 1.10.6):
+    
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f
+ 
+  * Upstream bug:
+    https://bugzilla.gnome.org/show_bug.cgi?id=783391
  
  [Test Plan]
  
-  * The exact conditions for reproducing this bug on mixed IPv4/IPv6
-networks are not known but includes using both IPv4 and IPv6,
-both using dhcp.
+  * The exact conditions for reproducing this bug on mixed IPv4/IPv6
+    networks are not known but includes using both IPv4 and IPv6,
+    both using dhcp.
  
  [Where problems could occur]
  
-  * This patch could possibly break networking using and that would be bad.
-Network manager should be able to restart connection more properly with
-this patch though.
+  * This patch could possibly break networking using and that would be bad.
+    Network manager should be able to restart connection more properly with
+    this patch though.
  
  [Other Info]
-  * We have tested this patch on a couple of clients where we have seen this
-this problem. If this pa

[Touch-packages] [Bug 1970473] Re: Xorg crash

2022-04-26 Thread Daniel van Vugt
It appears the problem started in the RADEON driver and then Xorg
crashed:

[   186.951] (EE) RADEON(0): drmmode_do_crtc_dpms cannot get last vblank counter
[   186.958] (II) RADEON(0): Allocate new frame buffer 1080x1920
[   186.963] (II) RADEON(0): VRAM usage limit set to 218116K
[   186.965] (EE) 
[   186.965] (EE) Backtrace:
[   186.966] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x563b05a0d2b9]
[   186.967] (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) 
[0x7f1b91765520]
[   186.968] (EE) 2: ? (?+0x0) [0x0]
[   186.968] (EE) 3: ? (?+0x0) [0x0]
[   186.968] (EE) 
[   186.968] (EE) Segmentation fault at address 0x0
[   186.968] (EE) 
Fatal server error:
[   186.968] (EE) Caught signal 11 (Segmentation fault). Server aborting
[   186.968] (EE) 

** Tags added: radeon

** Summary changed:

- Xorg crash
+ [radeon] Xorg crash

** Summary changed:

- [radeon] Xorg crash
+ [radeon] Xorg crash in the RADEON driver

** Package changed: xorg (Ubuntu) => xserver-xorg-video-ati (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/1970473

Title:
  [radeon] Xorg crashed with SIGSEGV when using the RADEON driver

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  When using Settings/Display/Orientation/Portret right and Apply then X
  crashes and login screen is displayed. Tested with 3 different AMD
  systems (older). Bug is not present with Intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:30:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2010
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: CZC1332VBJ
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1332VBJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Packard:pnHPCompaq6005ProMTPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:skuAT493AV:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq 6005 Pro MT PC
  dmi.product.sku: AT493AV
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1970473/+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 1970520] Re: [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing on Cirrus Logic CS4213 Chip

2022-04-26 Thread Sachin Arun Borkar
It was working fine on Ubuntu 20.04.

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing
  on Cirrus Logic CS4213 Chip

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am using Dell Inspiron 3520. It having Cirrus Logic CS4213 as chip.
  Problems I face:

  Whenever I connect headphones, sound comes from both speaker/headphones.
  I have to change Auto-Mute status every time when I connect headphones.
  It automatically changes it's status from Enable to disable after headphone 
disconnect.

  What I tried Yet:

  I changed file /var/lib/alsa/asound.state Auto_Mute state "Enable" from that 
was "disable" before.
  But still facing same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  borkarsachin97985 F pulseaudio
borkarsachin97   9437 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 10:17:00 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: No auto-mute between outputs
  Title: [HDA-Intel - HDA Intel PCH, playback] No automute
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
  dmi.product.name: Inspiron 3520
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970520/+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 1970523] [NEW] [Mesa Intel® HD Graphics 3000 (SNB GT2)] Cannot able to Change gamma on Inspiron 3520.

2022-04-26 Thread Sachin Arun Borkar
Public bug reported:

I am using Dell Inspiron 3520. It have Mesa Intel® HD Graphics 3000 (SNB GT2) 
Graphics.
Problems I am facing:

I am unable to change gamma via xgamma or randrx.

It was working fine on ubuntu 20.04. After Upgrade it is not working.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 10:36:19 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0555]
InstallationDate: Installed on 2022-04-23 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Dell Inc. Inspiron 3520
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=ea5b9322-6015-490d-b607-48fd6b6c04df ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2018
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0486TW
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.ec.firmware.release: 1.2
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
dmi.product.name: Inspiron 3520
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

** Attachment added: "Screenshot after command."
   
https://bugs.launchpad.net/bugs/1970523/+attachment/5584194/+files/Screenshot%20from%202022-04-27%2010-44-01.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/1970523

Title:
  [Mesa Intel® HD Graphics 3000 (SNB GT2)] Cannot able to Change gamma
  on Inspiron 3520.

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using Dell Inspiron 3520. It have Mesa Intel® HD Graphics 3000 (SNB GT2) 
Graphics.
  Problems I am facing:

  I am unable to change gamma via xgamma or randrx.

  It was working fine on ubuntu 20.04. After Upgrade it is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 10:36:19 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0555]
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 3520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic 
root=UUID=ea5b9322-6015-490d-b607-48fd6b6c04df ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecifie

[Touch-packages] [Bug 1970520] [NEW] [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing on Cirrus Logic CS4213 Chip

2022-04-26 Thread Sachin Arun Borkar
Public bug reported:

I am using Dell Inspiron 3520. It having Cirrus Logic CS4213 as chip.
Problems I face:

Whenever I connect headphones, sound comes from both speaker/headphones.
I have to change Auto-Mute status every time when I connect headphones.
It automatically changes it's status from Enable to disable after headphone 
disconnect.

What I tried Yet:

I changed file /var/lib/alsa/asound.state Auto_Mute state "Enable" from that 
was "disable" before.
But still facing same issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  borkarsachin97985 F pulseaudio
  borkarsachin97   9437 F alsamixer
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 27 10:17:00 2022
InstallationDate: Installed on 2022-04-23 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Type: No auto-mute between outputs
Title: [HDA-Intel - HDA Intel PCH, playback] No automute
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/31/2018
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0486TW
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.ec.firmware.release: 1.2
dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
dmi.product.name: Inspiron 3520
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: Not Specified
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing
  on Cirrus Logic CS4213 Chip

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am using Dell Inspiron 3520. It having Cirrus Logic CS4213 as chip.
  Problems I face:

  Whenever I connect headphones, sound comes from both speaker/headphones.
  I have to change Auto-Mute status every time when I connect headphones.
  It automatically changes it's status from Enable to disable after headphone 
disconnect.

  What I tried Yet:

  I changed file /var/lib/alsa/asound.state Auto_Mute state "Enable" from that 
was "disable" before.
  But still facing same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  borkarsachin97985 F pulseaudio
borkarsachin97   9437 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 10:17:00 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: No auto-mute between outputs
  Title: [HDA-Intel - HDA Intel PCH, playback] No automute
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
  dmi.product.name: Inspiron 3520
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970520/+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 1970520] Re: [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing on Cirrus Logic CS4213 Chip

2022-04-26 Thread Sachin Arun Borkar
I Change Auto-Mute status using alsamixer.

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] Auto-Mute Status keeps Changing
  on Cirrus Logic CS4213 Chip

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am using Dell Inspiron 3520. It having Cirrus Logic CS4213 as chip.
  Problems I face:

  Whenever I connect headphones, sound comes from both speaker/headphones.
  I have to change Auto-Mute status every time when I connect headphones.
  It automatically changes it's status from Enable to disable after headphone 
disconnect.

  What I tried Yet:

  I changed file /var/lib/alsa/asound.state Auto_Mute state "Enable" from that 
was "disable" before.
  But still facing same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  borkarsachin97985 F pulseaudio
borkarsachin97   9437 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 27 10:17:00 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Type: No auto-mute between outputs
  Title: [HDA-Intel - HDA Intel PCH, playback] No automute
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/31/2018
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0486TW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd05/31/2018:br1.2:efr1.2:svnDellInc.:pnInspiron3520:pvrNotSpecified:rvnDellInc.:rn0486TW:rvrA12:cvnDellInc.:ct8:cvrNotSpecified:skuTobefilledbyO.E.M.:
  dmi.product.name: Inspiron 3520
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970520/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

2022-04-26 Thread Victor Hugo Schulz
I was also affected by this issue when updating from 21.10 to 22.04, not on 
eduroam but on my university's network.
Workaround from post #22 worked for me, but I simply modified the original file 
(/etc/ssl/openssl.cnf).
After reading other comments, I got confused. Is this a bug on Ubuntu's 
wpasupplicant or a problem with the university's infrastructure using old 
vulnerable authentication methods?
If the latter, how should I report it to university's sysadmin?

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]

2022-04-26 Thread Seth Arnold
Yes, managing the configurations for the huge variety of cryptography
toolkits on a Linux system is definitely something of a chore. It would
be nice to give people one command they could use to return to unsafe-
but-compatible cryptography -- or enforce only modern cryptography.

Our friends at Red Hat have prepared https://gitlab.com/redhat-
crypto/fedora-crypto-policies -- while a version of this is packaged:
https://launchpad.net/ubuntu/+source/crypto-policies -- I don't believe
it actually works on Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/crypto-policies/+bug/1926664

Maybe someday.

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

Title:
  openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]

Status in openssl package in Ubuntu:
  Won't Fix

Bug description:
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
   Table de version :
   *** 3.0.1-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  Using Ubuntu 22.04, I now get the following error message when
  attempting to connect to our office VPN using "gp-saml-gui
  (https://github.com/dlenski/gp-saml-gui)" :

  #
  dominique@Doombuntu:~$ .local/bin/gp-saml-gui  server_url
  Looking for SAML auth tags in response to 
https://server_url/global-protect/prelogin.esp...
  usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT] 
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f 
EXTRA] server [openconnect_extra ...]
  gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] 
unsafe legacy renegotiation disabled (_ssl.c:997)
  #
  #
  #

  gp-saml-gui uses python module requests.
  Using python ide, I can get the same results  :

  #
  >>> r = requests.get('https://server_url')
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, 
in urlopen
  httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382, 
in _make_request
  self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012, 
in _validate_conn
  conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in 
connect
  self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in 
ssl_wrap_socket
  ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in 
_ssl_wrap_socket_impl
  return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
  return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
  self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
  self._sslobj.do_handshake()
  ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy 
renegotiation disabled (_ssl.c:997)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in 
send
  resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, 
in urlopen
  retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in 
increment
  raise MaxRetryError(_pool, url, error or ResponseError(cause))
  urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url', 
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, 
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation 
disabled (_ssl.c:997)')))

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
  return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
  return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in 
request
  resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in 
send
  r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in 
send
  raise SSLError(e, request=request)
  requests.exceptions.SSLError: HTTPSConnectionPool(host='server_url', 
port=443): Max retries exc

[Touch-packages] [Bug 1963834] Re: openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]

2022-04-26 Thread Matthew Geier
It's a bit of an 'own goal' if this gets marked as 'won't fix'. As students 
upgrade to 22.04 where I work they will find they can't connect to the 
institutions or research centre wireless network. They won't care that the SSL 
change is protecting them from an old SSL bug, they will just come back 'it 
works in windows but not Ubuntu'. 
Central IT services who run the wireless will just shrug and say 'Linux not 
supported'.
Need to make it easier to find how to turn on the Legacy insecure mode.

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

Title:
  openssl 3.0 - SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED]

Status in openssl package in Ubuntu:
  Won't Fix

Bug description:
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  openssl:
Installé : 3.0.1-0ubuntu1
Candidat : 3.0.1-0ubuntu1
   Table de version :
   *** 3.0.1-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  Using Ubuntu 22.04, I now get the following error message when
  attempting to connect to our office VPN using "gp-saml-gui
  (https://github.com/dlenski/gp-saml-gui)" :

  #
  dominique@Doombuntu:~$ .local/bin/gp-saml-gui  server_url
  Looking for SAML auth tags in response to 
https://server_url/global-protect/prelogin.esp...
  usage: gp-saml-gui [-h] [--no-verify] [-C COOKIES | -K] [-g | -p] [-c CERT] 
[--key KEY] [-v | -q] [-x | -P | -S] [-u] [--clientos {Windows,Linux,Mac}] [-f 
EXTRA] server [openconnect_extra ...]
  gp-saml-gui: error: SSL error: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] 
unsafe legacy renegotiation disabled (_ssl.c:997)
  #
  #
  #

  gp-saml-gui uses python module requests.
  Using python ide, I can get the same results  :

  #
  >>> r = requests.get('https://server_url')
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 699, 
in urlopen
  httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 382, 
in _make_request
  self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 1012, 
in _validate_conn
  conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 411, in 
connect
  self.sock = ssl_wrap_socket(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 449, in 
ssl_wrap_socket
  ssl_sock = _ssl_wrap_socket_impl(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 493, in 
_ssl_wrap_socket_impl
  return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
File "/usr/lib/python3.10/ssl.py", line 512, in wrap_socket
  return self.sslsocket_class._create(
File "/usr/lib/python3.10/ssl.py", line 1070, in _create
  self.do_handshake()
File "/usr/lib/python3.10/ssl.py", line 1341, in do_handshake
  self._sslobj.do_handshake()
  ssl.SSLError: [SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy 
renegotiation disabled (_ssl.c:997)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 439, in 
send
  resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 755, 
in urlopen
  retries = retries.increment(
File "/usr/lib/python3/dist-packages/urllib3/util/retry.py", line 574, in 
increment
  raise MaxRetryError(_pool, url, error or ResponseError(cause))
  urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='server_url', 
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, 
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation 
disabled (_ssl.c:997)')))

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/requests/api.py", line 76, in get
  return request('get', url, params=params, **kwargs)
File "/usr/lib/python3/dist-packages/requests/api.py", line 61, in request
  return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 542, in 
request
  resp = self.send(prep, **send_kwargs)
File "/usr/lib/python3/dist-packages/requests/sessions.py", line 655, in 
send
  r = adapter.send(request, **kwargs)
File "/usr/lib/python3/dist-packages/requests/adapters.py", line 514, in 
send
  raise SSLError(e, request=request)
  requests.exceptions.SSLError: HTTPSConnectionPool(host='server_url', 
port=443): Max retries exceeded with url: / (Caused by SSLError(SSLError(1, 
'[SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy 

[Touch-packages] [Bug 1970413] Re: Moving windows around is laggy

2022-04-26 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1799679 ***
https://bugs.launchpad.net/bugs/1799679

This is technically an old bug 1799679. It just became worse in 22.04
since GNOME started using GTK4, hence OpenGL, and so most apps are now
affected.

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510
(Ubuntu)

** This bug has been marked a duplicate of bug 1799679
   Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL 
app windows

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

Title:
  Moving windows around is laggy

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New

Bug description:
  When I move a window around, it's lagging and sometimes it's freezing
  for a second. This is happening after the upgrade to Ubuntu 22.04.
  Also, it happens all the time, even after I restart my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 15:09:42 2022
  DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed
   nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] 
[1458:3733]
  InstallationDate: Installed on 2021-11-08 (168 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  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.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970413/+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 1970459] Re: import of ca-certificate in browser does not work

2022-04-26 Thread Seth Arnold
I switched this from ca-certificates to firefox and chromium-browser,
since both browsers manage their own certificate lists and don't use the
system-provided ca-certificates. (You manage that with different tools,
see the first few lines of /etc/ca-certificates.conf for details.)

Thanks

** Package changed: ca-certificates (Ubuntu) => firefox (Ubuntu)

** Also affects: chromium-browser (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  import of ca-certificate in browser does not work

Status in chromium-browser package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  I tried to import a CA root certificate into both Firefox and Chrome.
  In Firefox, the import button just didn't do anything, in Chrome
  pressing "import" hangs up the browser. This means I can't reach the
  intranet of the company I work for.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ca-certificates 20211016
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:16:12 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970459/+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 1970471] Re: Changing applications bug 22.04LTS

2022-04-26 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/1970471

Title:
  Changing applications bug 22.04LTS

Status in xorg package in Ubuntu:
  New

Bug description:
  I have Firefox and the android studio code opened at the same time.
  If I am using Firefox and want to move into studio code, I press the "super" 
key to show all the apps running and click with my mouse the studio code app. 
Instead of showing ASC it keeps showing me Firefox, but not the other way 
around, when I am in ASC and want to change to Firefox, it does change.
  This only happens when using the "super" key by itself, when using "super + 
tab" or "alt + tab" it does change.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 21:06:02 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Toshiba Corporation HD Graphics 5500 [1179:000a]
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:07dc Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
   |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 
480M
   |__ Port 8: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
   |__ Port 8: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
  MachineType: TOSHIBA Satellite Pro R50-B
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=b739b2dd-b328-4bee-a14e-8e1cc4583783 ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/30/2015
  dmi.bios.release: 1.20
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.20
  dmi.board.asset.tag: 00
  dmi.board.name: Satellite Pro R50-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.ec.firmware.release: 1.10
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.20:bd01/30/2015:br1.20:efr1.10:svnTOSHIBA:pnSatelliteProR50-B:pvrPSSG2E-00K004CE:rvnTOSHIBA:rnSatelliteProR50-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:skuPSSG2E:
  dmi.product.family: 00
  dmi.product.name: Satellite Pro R50-B
  dmi.product.sku: PSSG2E
  dmi.product.version: PSSG2E-00K004CE
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970471/+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 1970471] [NEW] Changing applications bug 22.04LTS

2022-04-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have Firefox and the android studio code opened at the same time.
If I am using Firefox and want to move into studio code, I press the "super" 
key to show all the apps running and click with my mouse the studio code app. 
Instead of showing ASC it keeps showing me Firefox, but not the other way 
around, when I am in ASC and want to change to Firefox, it does change.
This only happens when using the "super" key by itself, when using "super + 
tab" or "alt + tab" it does change.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 21:06:02 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Toshiba Corporation HD Graphics 5500 [1179:000a]
InstallationDate: Installed on 2022-04-23 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:07dc Intel Corp. Bluetooth wireless interface
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M
 |__ Port 3: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M
 |__ Port 8: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
 |__ Port 8: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
MachineType: TOSHIBA Satellite Pro R50-B
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=b739b2dd-b328-4bee-a14e-8e1cc4583783 ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/30/2015
dmi.bios.release: 1.20
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.20
dmi.board.asset.tag: 00
dmi.board.name: Satellite Pro R50-B
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.ec.firmware.release: 1.10
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.20:bd01/30/2015:br1.20:efr1.10:svnTOSHIBA:pnSatelliteProR50-B:pvrPSSG2E-00K004CE:rvnTOSHIBA:rnSatelliteProR50-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:skuPSSG2E:
dmi.product.family: 00
dmi.product.name: Satellite Pro R50-B
dmi.product.sku: PSSG2E
dmi.product.version: PSSG2E-00K004CE
dmi.sys.vendor: TOSHIBA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
Changing applications bug 22.04LTS
https://bugs.launchpad.net/bugs/1970471
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 1970473] [NEW] Xorg crash

2022-04-26 Thread Daniel
Public bug reported:

When using Settings/Display/Orientation/Portret right and Apply then X
crashes and login screen is displayed. Tested with 3 different AMD
systems (older). Bug is not present with Intel graphics

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.470
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 19:30:33 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ro_RO.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/04/2010
dmi.bios.release: 1.11
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G6 v01.11
dmi.board.asset.tag: CZC1332VBJ
dmi.board.name: 3047h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC1332VBJ
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Packard:pnHPCompaq6005ProMTPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct6:cvr:skuAT493AV:
dmi.product.family: 103C_53307F
dmi.product.name: HP Compaq 6005 Pro MT PC
dmi.product.sku: AT493AV
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug crash jammy 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/1970473

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  When using Settings/Display/Orientation/Portret right and Apply then X
  crashes and login screen is displayed. Tested with 3 different AMD
  systems (older). Bug is not present with Intel graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:30:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1043:03da]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Hewlett-Packard HP Compaq 6005 Pro MT PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ro_RO.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/04/2010
  dmi.bios.release: 1.11
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786G6 v01.11
  dmi.board.asset.tag: CZC1332VBJ
  dmi.board.name: 3047h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC1332VBJ
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:br1.11:svnHewlett-Pa

[Touch-packages] [Bug 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade

2022-04-26 Thread Jeff White
I can confirm that the issue may be in qemu in 22.04.  A "real" s390x
running 22.04 does not have this issue and the same installation image
does not have this issue running on Windows 11, qemu version 7.0.0.

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

Title:
  "User process fault: interruption code 0011 ilc:3" on SSH
  client/server upon Jammy upgrade

Status in openssh package in Ubuntu:
  New

Bug description:
  This s390x VM has been upgraded to Jammy, including the host (qemu-
  system-s390x 1:6.2+dfsg-2ubuntu6).  Now any attempt to use ssh, or any
  incoming sshd attempt immediately results in e.g.:

  ryan@s390x-dev:~$ ssh g...@github.com
  [  433.672800] User process fault: interruption code 0011 ilc:3 in 
libc.so.6[3ffa6c0+1ca000]
  [  433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800
  [  433.672977] Fault in primary space mode while using user ASCE.
  [  433.673030] AS:02bc01c7 R3:087cc007 S:0798a000 
P:0400 
  Segmentation fault (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

2022-04-26 Thread Brian Murray
** Tags added: rls-jj-incoming

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

2022-04-26 Thread Alexander Browne
** Summary changed:

- "Connection failed" for WPA Enterprise network eduroam
+ "Connection failed" for WPA Enterprise network (e.g. eduroam)

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-04-26 Thread Clemens Lang
See also https://bugzilla.redhat.com/show_bug.cgi?id=2069239. For those
that have this problem with the "0A0C0103:SSL routines::internal error"
message, check whether your radius server possibly only supports TLS 1.1
or older. Those servers would default to rsa_pkcs1_md5_sha1 as TLS
signature algorithm, which does not meet the 80 bits of security
requirement of OpenSSL 3's default SECLEVEL of 1.

Try setting SECLEVEL to 0 to see if that fixes the issue for you. Talk
to your Radius server administrator to recommend they offer TLS 1.2 or
higher.

** Bug watch added: Red Hat Bugzilla #2069239
   https://bugzilla.redhat.com/show_bug.cgi?id=2069239

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1970459] [NEW] import of ca-certificate in browser does not work

2022-04-26 Thread Xtien
Public bug reported:

I tried to import a CA root certificate into both Firefox and Chrome. In
Firefox, the import button just didn't do anything, in Chrome pressing
"import" hangs up the browser. This means I can't reach the intranet of
the company I work for.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ca-certificates 20211016
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 19:16:12 2022
InstallationDate: Installed on 2022-04-23 (3 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: ca-certificates
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  import of ca-certificate in browser does not work

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  I tried to import a CA root certificate into both Firefox and Chrome.
  In Firefox, the import button just didn't do anything, in Chrome
  pressing "import" hangs up the browser. This means I can't reach the
  intranet of the company I work for.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ca-certificates 20211016
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 19:16:12 2022
  InstallationDate: Installed on 2022-04-23 (3 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1970459/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-04-26 Thread Christopher Barrington-Leigh
Whoops -- actually, my enterprise network was a university's main wifi
(wpa.mcgill.ca), not eduroam. I propose to generalize the title of this
bug by dropping eduroam or changing it to (e.g. eduroam)

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network eduroam

2022-04-26 Thread Christopher Barrington-Leigh
On a Thinkpad X230 I had this problem after upgrading to 22.04.

The recipe in comment 23 by nfalse solved the problem for me.

Thank you (though this is only a temporary workaround, given its use of
"UnsafeLegacyRenegotiation")

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

Title:
  "Connection failed" for WPA Enterprise network eduroam

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade

2022-04-26 Thread Ryan Finnie
I only have one s390x guest and adding another would be painful due to
the slowness of its emulation :)  but I have just tried removing all of
/etc/ssh and reinstalling openssh-client/openssh-server, same crash.

To be clear, this is only happening on my s390x guest.  I have a few
other non-x86 qemu guests (arm64, ppc64el, riscv64, etc) which have also
been upgraded to jammy, none of which have this problem.  So I'm willing
to bet this is more of a kernel or qemu problem and that openssh is just
a symptom.  (Though it seems to be a recurring indicative symptom...
ISTR openssh segfaults during the bootstrap of riscv64 on qemu; William
Grant may be able to chime in.)  I've attached my libvirt definition in
case it's relevant, but it's pretty standard.

** Attachment added: "s390x-dev.xml"
   
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+attachment/5584015/+files/s390x-dev.xml

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

Title:
  "User process fault: interruption code 0011 ilc:3" on SSH
  client/server upon Jammy upgrade

Status in openssh package in Ubuntu:
  New

Bug description:
  This s390x VM has been upgraded to Jammy, including the host (qemu-
  system-s390x 1:6.2+dfsg-2ubuntu6).  Now any attempt to use ssh, or any
  incoming sshd attempt immediately results in e.g.:

  ryan@s390x-dev:~$ ssh g...@github.com
  [  433.672800] User process fault: interruption code 0011 ilc:3 in 
libc.so.6[3ffa6c0+1ca000]
  [  433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800
  [  433.672977] Fault in primary space mode while using user ASCE.
  [  433.673030] AS:02bc01c7 R3:087cc007 S:0798a000 
P:0400 
  Segmentation fault (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+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 1967038] Autopkgtest regression report (systemd/249.11-0ubuntu3.1)

2022-04-26 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted systemd (249.11-0ubuntu3.1) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

exim4/4.95-4ubuntu2 (ppc64el)
linux-lowlatency/5.15.0-27.28 (amd64)
tinyssh/20220311-1 (amd64, arm64, ppc64el, s390x, armhf)
casper/1.470 (amd64)
libsoup3/3.0.5-1 (armhf)
linux-intel-iotg/5.15.0-1004.6 (amd64)
tang/11-1 (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

2022-04-26 Thread Olivier Gayot
** Description changed:

+ 
+ [Impact]
+ 
+  * If a system is using canonical livepatch, has it enabled, and patches
+ are applied, it could be confusing for a user to receive a "system
+ restart required" messages in the MOTD when logging in.
+ 
+  * Livepatch is available on LTS releases. Thus, the users can be
+ confused following a kernel update on 20.04.
+ 
+  * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
+ Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.
+ 
+ [Test Plan]
+ 
+  * how to reproduce the bug:
+ 
+1. Install and boot a 20.04 server VM
+2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
+3. Enable Livepatch using the following command:
+$ ua attach # replace  by an actual contract token
+4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
+5. Upon logging in again, the motd will show ***System restart required***.
+ 
+  * other testing appropriate to perform before landing this update:
+ 
+   * Making sure that the patch has no impact when livepatch is not enabled.
+   * The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.
+ 
+ [Where problems could occur]
+ 
+  * The change updates a hook script in /etc/kernel/postinst.d/. Scripts
+ in this directory are executing when upgrading / installing a kernel. If
+ somehow the script is broken, it can prevent dpkg for succeeding when
+ upgrading / installing the kernel.
+ 
+  * If the implementation is wrong, we might end up "losing" the
+ ***System restart required*** message when livepatch is disabled
+ 
+ [Original bug description]
+ 
  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.
  
  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly used
  in their updated versions. Examples that come to mind are libc and the
  kernel.
  
  There is a secondary file that can be created which says which packages
  requested the reboot. That would be /var/run/reboot-required.pkgs
  
  Ideally that script should not print out the reboot required message if
  a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.
  
  For (a), one can use the command "ubuntu-advantage is-livepatch-enabled"
  and check $?. That is in the ubuntu-advantage-tools package.

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  
  [Impact]

   * If a system is using canonical livepatch, has it enabled, and
  patches are applied, it could be confusing for a user to receive a
  "system restart required" messages in the MOTD when logging in.

   * Livepatch is available on LTS releases. Thus, the users can be
  confused following a kernel update on 20.04.

   * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
  Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.

  [Test Plan]

   * how to reproduce the bug:

 1. Install and boot a 20.04 server VM
 2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
 3. Enable Livepatch using the following command:
 $ ua attach # replace  by an actual contract token
 4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
 5. Upon logging in again, the motd will show ***System restart required***.

   * other testing appropriate to perform before landing this update:

* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.

  [Where problems could occur]

   * The change updates a hook script in /etc/kernel/postinst.d/.
  Scripts in this directory are executing when upgrading / installing a
  kernel. If somehow the script is broken, it can prevent dpkg for
  succeeding when upgrading / installing the kernel.

   * If the implementation is wro

[Touch-packages] [Bug 1747499] Re: 98-reboot-required and Interaction with livepatch

2022-04-26 Thread Ubuntu Foundations Team Bug Bot
The attachment "debdiff for unattended-upgrades (focal)" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

2022-04-26 Thread Olivier Gayot
** Patch added: "debdiff for update-notifier (focal)"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+attachment/5583992/+files/1-update-notifier-3.192.30.10.3.192.30.11.debdiff

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1747499] Re: 98-reboot-required and Interaction with livepatch

2022-04-26 Thread Olivier Gayot
** Patch added: "debdiff for unattended-upgrades (focal)"
   
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+attachment/5583991/+files/1-unattended-upgrades-2.3ubuntu0.1-2.3ubuntu1.debdiff

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed

Bug description:
  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+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 1970413] Re: Moving windows around is laggy

2022-04-26 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/1970413

Title:
  Moving windows around is laggy

Status in xorg package in Ubuntu:
  New

Bug description:
  When I move a window around, it's lagging and sometimes it's freezing
  for a second. This is happening after the upgrade to Ubuntu 22.04.
  Also, it happens all the time, even after I restart my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 15:09:42 2022
  DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed
   nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] 
[1458:3733]
  InstallationDate: Installed on 2021-11-08 (168 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  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.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970413/+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 1970413] [NEW] Moving windows around is laggy

2022-04-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

When I move a window around, it's lagging and sometimes it's freezing
for a second. This is happening after the upgrade to Ubuntu 22.04. Also,
it happens all the time, even after I restart my computer.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.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  510.60.02  Wed Mar 16 11:24:05 
UTC 2022
 GCC version:  gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 15:09:42 2022
DistUpgraded: 2022-04-25 15:08:16,726 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/510.60.02, 5.15.0-25-generic, x86_64: installed
 nvidia/510.60.02, 5.15.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050 Ti] 
[1458:3733]
InstallationDate: Installed on 2021-11-08 (168 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-04-25 (1 days ago)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
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.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy performance ubuntu
-- 
Moving windows around is laggy
https://bugs.launchpad.net/bugs/1970413
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 1970424] Re: firefox snap can not open any file dialogs

2022-04-26 Thread Jeremy Bicha
ubuntu-desktop-minimal Recommends xdg-desktop-portal-gnome and
Recommends are installed by default.

If you intentionally don't install Recommends, then your system will
have bugs like this.

But we can look at making the dependency stronger.

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

** Package changed: firefox (Ubuntu) => ubuntu-meta (Ubuntu)

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-meta (Ubuntu)
   Status: Invalid => Triaged

** Summary changed:

- firefox snap can not open any file dialogs
+ Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome

** Description changed:

+ I propose having ubuntu-desktop-minimal depend on
+ xdg-desktop-portal-gnome | xdg-desktop-portal-backend
+ 
+ Currently, there is only a Recommends on xdg-desktop-portal-gnome.
+ 
+ If a system doesn't have that dependency installed, then desktop snaps
+ including our critical Firefox and Chromium snaps have severe missing
+ functionality.
+ 
+ Original Bug Report
+ ---
  With ubuntu 22.04 firefox comes as snap package by default.
  
  it is not possible to open any file dialog. save graphics as, save html
  page, import certificate never opens a file dialog.
  
  firefox is completly useless without that file dialog.
  
  (the root case is ubuntu uses snap)
  
  further: in snap store firefox has no icon and it's called firefox not
  "Firefox".

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Medium => High

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

Title:
  Have ubuntu-desktop-minimal depend on xdg-desktop-portal-gnome

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  I propose having ubuntu-desktop-minimal depend on
  xdg-desktop-portal-gnome | xdg-desktop-portal-backend

  Currently, there is only a Recommends on xdg-desktop-portal-gnome.

  If a system doesn't have that dependency installed, then desktop snaps
  including our critical Firefox and Chromium snaps have severe missing
  functionality.

  Original Bug Report
  ---
  With ubuntu 22.04 firefox comes as snap package by default.

  it is not possible to open any file dialog. save graphics as, save
  html page, import certificate never opens a file dialog.

  firefox is completly useless without that file dialog.

  (the root case is ubuntu uses snap)

  further: in snap store firefox has no icon and it's called firefox not
  "Firefox".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1970424/+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 1970424] [NEW] firefox snap can not open any file dialogs

2022-04-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

With ubuntu 22.04 firefox comes as snap package by default.

it is not possible to open any file dialog. save graphics as, save html
page, import certificate never opens a file dialog.

firefox is completly useless without that file dialog.

(the root case is ubuntu uses snap)

further: in snap store firefox has no icon and it's called firefox not
"Firefox".

** Affects: ubuntu-meta (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: snap
-- 
firefox snap can not open any file dialogs
https://bugs.launchpad.net/bugs/1970424
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-meta 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 1970402] Re: Initrd out of memory error after upgrade to 22.04

2022-04-26 Thread Brian Murray
** Package changed: ubuntu => initramfs-tools (Ubuntu)

** Tags added: rls-jj-incoming

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

Title:
  Initrd out of memory error after upgrade to 22.04

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After upgrading to 22.04 system is unbootable because of "out of memory" 
error when loading initial ramdisk. I was able to fix it by editing cat 
/etc/initramfs-tools/initramfs.conf
  and changing configuration to:
  MODULES=dep
  COMPRESS=xz
  RUNSIZE=15%

  Not sure which one helped, but I can test it if needed.

  System information:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  initramfs-tools:
Installed: 0.140ubuntu13
Candidate: 0.140ubuntu13
Version table:
   *** 0.140ubuntu13 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1970402] [NEW] Initrd out of memory error after upgrade to 22.04

2022-04-26 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After upgrading to 22.04 system is unbootable because of "out of memory" error 
when loading initial ramdisk. I was able to fix it by editing cat 
/etc/initramfs-tools/initramfs.conf
and changing configuration to:
MODULES=dep
COMPRESS=xz
RUNSIZE=15%

Not sure which one helped, but I can test it if needed.

System information:
Description:Ubuntu 22.04 LTS
Release:22.04

initramfs-tools:
  Installed: 0.140ubuntu13
  Candidate: 0.140ubuntu13
  Version table:
 *** 0.140ubuntu13 500
500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages
100 /var/lib/dpkg/status

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: boot bot-comment
-- 
Initrd out of memory error after upgrade to 22.04
https://bugs.launchpad.net/bugs/1970402
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools 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 1952107] Re: Google Contacts API Deprecated

2022-04-26 Thread Jeremy Bicha
** Changed in: evolution (Ubuntu Focal)
   Status: Confirmed => Triaged

** Changed in: evolution-data-server (Ubuntu Focal)
   Status: Confirmed => Triaged

** Changed in: evolution-data-server (Ubuntu Focal)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: evolution (Ubuntu Focal)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Triaged
Status in evolution-data-server source package in Focal:
  Triaged
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+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 1953014] Re: Return code for unsolicited arping is 1 instead of 0

2022-04-26 Thread Sebastien Bacher
** Changed in: iputils (Ubuntu Focal)
   Status: Incomplete => New

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

Title:
  Return code for unsolicited arping is 1 instead of 0

Status in iputils package in Ubuntu:
  Fix Released
Status in iputils source package in Focal:
  New

Bug description:
  When running a gratuitous / unsolicited arp via "arping -U" on Ubuntu Focal
  a return code of 1 is given, instead of always 0 (as there is no arp reply 
expected).

  Focal:
  --- cut ---
  # arping -U -c1 -I eth0 127.0.0.1; echo "ReturnCode: $?"
  ARPING 127.0.0.1 from 127.0.0.1 eth0
  Sent 1 probes (1 broadcast(s))
  Received 0 response(s)
  ReturnCode: 1

  # arping -V
  arping from iputils s20190709
  --- cut ---

  see corresponding source at
  
https://github.com/iputils/iputils/blob/13e00847176aa23683d68fce1d17ffb523510946/arping.c#L302.


  On Ubuntu Bionic this worked fine (and also does on Ubuntu Hirsute again BTW):
  --- cut ---
  arping -U -c 1 -I eth0 127.0.0.1; echo "ReturnCode: $?"
  ARPING 127.0.0.1 from 127.0.0.1 eth0
  Sent 1 probes (1 broadcast(s))
  Received 0 response(s)
  ReturnCode: 0

  # arping -V
  arping utility, iputils-s20161105
  --- cut ---

  see corresponding source for that version at
  
https://github.com/iputils/iputils/blob/bffc0e957b98d626ab4cea218c89251201425442/arping.c#L329
  or for the version on Hirsute at
  
https://github.com/iputils/iputils/blob/cc16da6b574ce6637f3e6e9ab3c1a728663006ff/arping.c#L302


  As you can see by looking at the source arping always statically
  returns a "0" for unsolicited.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1953014/+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 1970442] [NEW] ubuntu-standard shouldn't depend on transitional mime-support package

2022-04-26 Thread Jeremy Bicha
Public bug reported:

$ apt show mime-support
 This is a transitional package. It will be possible to remove it
 safely once its dependency chain has adjusted to depend on mailcap
 or media-types directly.

I didn't update this dependency because I don't know if we need mailcap
as an ubuntu-standard Depends or not. I believe we do want media-types.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Low
 Status: New


** Tags: kinetic

** Summary changed:

- ubuntu-standard shouldn't depend on transitional media-types package
+ ubuntu-standard shouldn't depend on transitional mime-support package

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

Title:
  ubuntu-standard shouldn't depend on transitional mime-support package

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  $ apt show mime-support
   This is a transitional package. It will be possible to remove it
   safely once its dependency chain has adjusted to depend on mailcap
   or media-types directly.

  I didn't update this dependency because I don't know if we need
  mailcap as an ubuntu-standard Depends or not. I believe we do want
  media-types.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1970442/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

2022-04-26 Thread Sebastien Bacher
** Changed in: libnotify (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  In Progress
Status in libnotify source package in Focal:
  New
Status in libnotify source package in Jammy:
  In Progress

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap (or install it from the attached files to this bug):
    git clone https://github.com/3v1n0/notify-send-test-snap
    snapcraft prime
    snap try prime

  To use the pre-built snap 
(https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7)
    snap install --dangerous notify-send-test-snap_*.snap

  Check that icons are shown when launching:
    notify-send-test-snap
    notify-send-test-snap.image-path
notify-send-test-snap.image-uri

  Ensure that desktop entry is correctly sent, monitoring the dbus
  session:

   In a terminal:
     dbus-monitor --session --monitor 
"interface='org.freedesktop.Notifications'"

   In the other:
     notify-send-test-snap.desktop-entry
     notify-send-test-snap.desktop-entry-explicit-id
     notify-send-test-snap.desktop-entry-explicit-file-name
     notify-send-test-snap.desktop-entry-explicit-path
     notify-send-test-snap.desktop-entry-explicit-uri
     notify-send-test-snap.desktop-entry-explicit-snapped-uri

  The
   `desktop-entry` value sent to dbus should be either:
     - A `notify-send-test-snap_`-prefixed desktop ID
     - A .desktop file path (readable from both inside and outside the snap)
     - A .desktop file uri (readable from both inside and outside the snap)

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1912687] Re: package linux-firmware 1.187.8 failed to install/upgrade: podproces zainstalowany pakiet linux-firmware skrypt post-installation zwrócił kod błędu 1

2022-04-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-firmware 1.187.8 failed to install/upgrade: podproces
  zainstalowany pakiet linux-firmware skrypt post-installation zwrócił
  kod błędu 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Error while installing package during apt-get dist-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.8
  ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78
  Uname: Linux 5.4.0-59-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zolw   2916 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Thu Jan 21 20:45:57 2021
  Dependencies:
   
  ErrorMessage: podproces zainstalowany pakiet linux-firmware skrypt 
post-installation zwrócił kod błędu 1
  InstallationDate: Installed on 2019-08-01 (538 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20L7001SPB
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic 
root=/dev/mapper/vgroot-lvroot ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.7
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.8 failed to install/upgrade: podproces 
zainstalowany pakiet linux-firmware skrypt post-installation zwrócił kod błędu 1
  UpgradeStatus: Upgraded to focal on 2020-10-01 (112 days ago)
  dmi.bios.date: 02/18/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N22ET62W (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L7001SPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN22ET62W(1.39):bd02/18/2020:svnLENOVO:pn20L7001SPB:pvrThinkPadT480s:rvnLENOVO:rn20L7001SPB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480s
  dmi.product.name: 20L7001SPB
  dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s
  dmi.product.version: ThinkPad T480s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1912687/+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 1967038] Re: Add mic mute key for HP Elite x360 series

2022-04-26 Thread Andy Chi
** Changed in: oem-priority
   Status: Confirmed => Fix Committed

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

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+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 1965809] Re: 22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed with SIGSEGV in magazine_chain_pop_head()

2022-04-26 Thread djfake
Exact same issue.

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

Title:
  22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem
  crashed with SIGSEGV in magazine_chain_pop_head()

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Attempting to open videos in multiple formats (tried .webm and .mp4 so
  far) results in ‘specified movie could not be found’ errors in Videos.

  I’ve moved them into multiple folders with the same result. If I hit
  the upper left button ’ < ’ I can see the file just fine

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libgstreamer1.0-0 1.20.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 14:20:08 2022
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2022-02-17 (32 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f023771dd0c :mov
0x8(%r12),%rax
   PC (0x7f023771dd0c) ok
   source "0x8(%r12)" (0x55e51814962008) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: totem crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1965809/+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 1970418] [NEW] Whiptail no longer accepts input when in a pipe with sudo

2022-04-26 Thread Adam Baxter
Public bug reported:

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010059. Affects
Jammy and Bookworm as far as I can tell.

echo | sudo whiptail --msgbox test 20 20 #Can't select 'Ok'
echo | whiptail --msgbox test 20 20 #Can select 'Ok'


Tested on Ubuntu 22.04 LTS

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

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

Title:
  Whiptail no longer accepts input when in a pipe with sudo

Status in newt package in Ubuntu:
  New

Bug description:
  See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010059. Affects
  Jammy and Bookworm as far as I can tell.

  echo | sudo whiptail --msgbox test 20 20 #Can't select 'Ok'
  echo | whiptail --msgbox test 20 20 #Can select 'Ok'

  
  Tested on Ubuntu 22.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/newt/+bug/1970418/+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 1965809] Re: 22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem crashed with SIGSEGV in magazine_chain_pop_head()

2022-04-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  22.04 - Videos ‘cannot find’ any videos (VLC works fine) - totem
  crashed with SIGSEGV in magazine_chain_pop_head()

Status in gstreamer1.0 package in Ubuntu:
  Confirmed

Bug description:
  Attempting to open videos in multiple formats (tried .webm and .mp4 so
  far) results in ‘specified movie could not be found’ errors in Videos.

  I’ve moved them into multiple folders with the same result. If I hit
  the upper left button ’ < ’ I can see the file just fine

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: libgstreamer1.0-0 1.20.1-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 21 14:20:08 2022
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2022-02-17 (32 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  ProcCmdline: /usr/bin/totem --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f023771dd0c :mov
0x8(%r12),%rax
   PC (0x7f023771dd0c) ok
   source "0x8(%r12)" (0x55e51814962008) not located in a known VMA region 
(needed readable region)!
   destination "%rax" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: gstreamer1.0
  StacktraceTop:
   g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: totem crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1965809/+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 1970107] Re: [nouveau] Xorg crash / Graphics Issue

2022-04-26 Thread Daniel van Vugt
When you are returned to the login screen, does Ctrl+Alt+F2 fix it? If
not then:

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

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

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

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

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

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

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

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

Title:
  [nouveau] Xorg crash / Graphics Issue

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I am using a wayland display manager, an internal graphics / Dedicated
  Graphics laptop where the HDMI is controlled by the dedicated
  graphics. Currently, with proprietary drivers on ubuntu 22.04

  When I connect a display to the hdmi it only shows a white screen,
  when I try to change the projection to mirror, or external only, it
  crashes and goes back onto the logon screen. I currently cannot cast
  at all to a monitor. The monitor I am trying to connect is a 4k and my
  laptop screen is 1080p if that makes a difference. I am sure I am not
  the only one who uses this feature, but because I have a mixture of
  internal and dedicated control, it may have more an issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 09:30:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:08ea]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:08ea]
  InstallationDate: Installed on 2022-04-22 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. G5 5590
  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.15.0-25-generic 
root=UUID=03aed564-912f-48c9-972f-2517e41b2692 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0MXHK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd12/01/2021:br1.18:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0MXHK3:rvrA01:cvnDellInc.:ct10:cvr:sku08EA:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970107/+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 1970107] Re: Xorg crash / Graphics Issue

2022-04-26 Thread Daniel van Vugt
Thanks for the bug report.

The white screen problem is bug 1965882. But there are more reasons to
avoid the 'nouveau' driver and it's probably the cause of your other
issues too. Please open the 'Additional Drivers' app and install the
official Nvidia driver with that.

** Summary changed:

- Xorg crash / Graphics Issue
+ [nouveau] Xorg crash / Graphics Issue

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

Title:
  [nouveau] Xorg crash / Graphics Issue

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I am using a wayland display manager, an internal graphics / Dedicated
  Graphics laptop where the HDMI is controlled by the dedicated
  graphics. Currently, with proprietary drivers on ubuntu 22.04

  When I connect a display to the hdmi it only shows a white screen,
  when I try to change the projection to mirror, or external only, it
  crashes and goes back onto the logon screen. I currently cannot cast
  at all to a monitor. The monitor I am trying to connect is a 4k and my
  laptop screen is 1080p if that makes a difference. I am sure I am not
  the only one who uses this feature, but because I have a mixture of
  internal and dedicated control, it may have more an issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: fail
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 09:30:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:08ea]
   NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:08ea]
  InstallationDate: Installed on 2022-04-22 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. G5 5590
  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.15.0-25-generic 
root=UUID=03aed564-912f-48c9-972f-2517e41b2692 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2021
  dmi.bios.release: 1.18
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.18.0
  dmi.board.name: 0MXHK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.18.0:bd12/01/2021:br1.18:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0MXHK3:rvrA01:cvnDellInc.:ct10:cvr:sku08EA:
  dmi.product.family: GSeries
  dmi.product.name: G5 5590
  dmi.product.sku: 08EA
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970107/+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 1970131] Re: Can't rotate display with AMD graphics on 22.04 LTS

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

  apport-collect 1970131

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


** Tags added: jammy

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

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

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

Title:
  Can't rotate display with AMD graphics on 22.04 LTS

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When using Settings/Display/Orientation/Portret right and Apply then X
  crashes and login screen is displayed. Tested with 3 different AMD
  systems (older). Bug is not present with Intel graphics

  Ubuntu 22.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970131/+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 1624485] Re: Nettle: Enable AES-NI instructions on amd64.

2022-04-26 Thread Christian Ehrhardt 
Indeed (thanks Richard) that is enabled since 3.6-1.

It is unlikely though due to the associated symbol changes (see e.g. the
old changelogs) that this can be provided as an SRU for older releases.
I'm not saying impossible, just unlikely as that evaluation has to be
done and checked in depth for potential side-effects in regard to an
SRU.

** Also affects: nettle (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: nettle (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: nettle (Ubuntu)
   Status: Confirmed => Fix Released

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

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

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

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

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

Title:
  Nettle: Enable AES-NI instructions on amd64.

Status in nettle package in Ubuntu:
  Fix Released
Status in nettle source package in Bionic:
  Confirmed
Status in nettle source package in Focal:
  Confirmed

Bug description:
  The current build of libnettle6 does not have AES-NI enabled. There's
  two configure options for enabling it:

  --enable-x86-aesni: Use AES-NI instructions instead of the standard 
implementation. This will break on systems that don't have AES-NI.
  --enable-fat: Build a "fat" library that has the standard implementation and 
the AES-NI implementation. This allows the library to continue working on older 
systems while providing faster performance on systems that have AES-NI.

  Note that Nettle's AES-NI implementation as of v3.2 is only supported
  on amd64, not i386, so this would only affect the 64-bit package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1624485/+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 1970013] Re: Totem Video player play distroted video

2022-04-26 Thread Daniel van Vugt
This appears to be a bug rather than a question.

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

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

** Summary changed:

- Totem Video player play distroted video
+ Totem Video player displays distorted video

** Summary changed:

- Totem Video player displays distorted video
+ Totem Video player displays distorted video (Intel Ivy Bridge)

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

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

Title:
  Totem Video player displays distorted video (Intel Ivy Bridge)

Status in totem package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 freshly installed along with ubuntu-restricted-extra
  package. Default totem player unable to play videos properly. videos
  looks distorted. Forwarding videos does not work. Video get stopped
  once forwarded.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 23 11:02:49 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2022-04-22 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 34601F4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.release: 2.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34601F4
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460:
  dmi.product.family: ThinkPad X1 Carbon
  dmi.product.name: 34601F4
  dmi.product.sku: LENOVO_MT_3460
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1970013/+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 1970002] Re: Unknown resilution configration error

2022-04-26 Thread Daniel van Vugt
Thanks for the bug report.

Ubuntu 18.04 is too old to support this new computer, especially the
NVIDIA RTX 3060 card. Please install Ubuntu 22.04 instead:
https://ubuntu.com/download

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

** Changed in: ubuntu
   Status: New => Won't Fix

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

Title:
  Unknown resilution configration error

Status in Ubuntu:
  Won't Fix

Bug description:
  Display/audio not recognized at all.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-108.122~18.04.1-generic 5.4.178
  Uname: Linux 5.4.0-108-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  CasperVersion: 1.427
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Apr 23 04:21:01 2022
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-108-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:2504] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:3656]
  LiveMediaBuild: Linux 18.04 - Release amd64
  MachineType: Gigabyte Technology Co., Ltd. B560 DS3H AC-Y1
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt boot=casper quiet 
splash --
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B560 DS3H AC-Y1
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF4:bd06/18/2021:svnGigabyteTechnologyCo.,Ltd.:pnB560DS3HAC-Y1:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560DS3HAC-Y1:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B560 MB
  dmi.product.name: B560 DS3H AC-Y1
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1970002/+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 1970003] Re: Screen resolution and audio not recnognized by system

2022-04-26 Thread Daniel van Vugt
Thanks for the bug report.

Ubuntu 18.04 is too old to support this new computer, especially the
NVIDIA RTX 3060 card. Please install Ubuntu 22.04 instead:
https://ubuntu.com/download

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

Title:
  Screen resolution and audio not recnognized by system

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Screen resolution and audio not recognized by system, the system does
  not see the display or the audio output and defaults to an improper
  screen resolution size with no audio output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-108.122~18.04.1-generic 5.4.178
  Uname: Linux 5.4.0-108-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  CasperVersion: 1.427
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Apr 23 04:26:46 2022
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-108-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:2504] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: eVga.com. Corp. Device [3842:3656]
  LiveMediaBuild: Linux 18.04 - Release amd64
  MachineType: Gigabyte Technology Co., Ltd. B560 DS3H AC-Y1
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt boot=casper quiet 
splash --
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B560 DS3H AC-Y1
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF4:bd06/18/2021:svnGigabyteTechnologyCo.,Ltd.:pnB560DS3HAC-Y1:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB560DS3HAC-Y1:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B560 MB
  dmi.product.name: B560 DS3H AC-Y1
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.10
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970003/+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 1970144] Re: Qt windows don't render correctly, VMware 16 , ubuntu 22.04

2022-04-26 Thread Daniel van Vugt
** Summary changed:

- screen rendering confusion, VMware 16 , ubuntu 22.04
+ Qt windows don't render correctly, VMware 16 , ubuntu 22.04

** Tags added: vmwgfx

** Summary changed:

- Qt windows don't render correctly, VMware 16 , ubuntu 22.04
+ [vmwgfx] Qt windows don't render correctly, VMware 16, ubuntu 22.04

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

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

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- [vmwgfx] Qt windows don't render correctly, VMware 16, ubuntu 22.04
+ [vmwgfx] Qt Creator windows don't render correctly, VMware 16, Ubuntu 22.04

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

Title:
  [vmwgfx] Qt Creator windows don't render correctly, VMware 16, Ubuntu
  22.04

Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  xdpyinfo 
  name of display::0
  version number:11.0
  vendor string:The X.Org Foundation
  vendor release number:12201001
  X.Org version: 1.22.1.1
  maximum request size:  16777212 bytes
  motion buffer size:  256
  bitmap unit, bit order, padding:32, LSBFirst, 32
  image byte order:LSBFirst
  number of supported pixmap formats:7
  supported pixmap formats:
  depth 1, bits_per_pixel 1, scanline_pad 32
  depth 4, bits_per_pixel 8, scanline_pad 32
  depth 8, bits_per_pixel 8, scanline_pad 32
  depth 15, bits_per_pixel 16, scanline_pad 32
  depth 16, bits_per_pixel 16, scanline_pad 32
  depth 24, bits_per_pixel 32, scanline_pad 32
  depth 32, bits_per_pixel 32, scanline_pad 32
  keycode range:minimum 8, maximum 255
  focus:  None
  number of extensions:23
  BIG-REQUESTS
  Composite
  DAMAGE
  DOUBLE-BUFFER
  DRI3
  GLX
  Generic Event Extension
  MIT-SHM
  Present
  RANDR
  RECORD
  RENDER
  SHAPE
  SYNC
  X-Resource
  XC-MISC
  XFIXES
  XFree86-VidModeExtension
  XINERAMA
  XInputExtension
  XKEYBOARD
  XTEST
  XVideo
  default screen number:0
  number of screens:1

  screen #0:
dimensions:3838x1781 pixels (1015x471 millimeters)
resolution:96x96 dots per inch
depths (7):24, 1, 4, 8, 15, 16, 32
root window id:0x2bb
depth of root window:24 planes
number of colormaps:minimum 1, maximum 1
default colormap:0x43
default number of colormap cells:256
preallocated pixels:black 0, white 16777215
options:backing-store WHEN MAPPED, save-unders NO
largest cursor:3838x1781
current input event mask:0xda0030
  EnterWindowMask  LeaveWindowMask  StructureNotifyMask 
 
  SubstructureNotifyMask   SubstructureRedirectMask PropertyChangeMask  
 
  ColormapChangeMask

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 09:25:33 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=e6bcbb51-635a-42a1-ab99-75af8c14475f ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2020
  dmi.bios.release: 4.6
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDe

[Touch-packages] [Bug 1970155] Re: Suspend does not work

2022-04-26 Thread Daniel van Vugt
Thanks for the bug report.

Please try disabling Bluetooth AND unplugging your USB keyboard before
suspending. Does that avoid the bug?

** Summary changed:

- Suspend does not work
+ System wakes from suspend almost immediately

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

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

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

Title:
  System wakes from suspend almost immediately

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Suspend mode does not seems to work. Clicking on suspend button sends
  laptop in suspend mode and in few seconds laptop comes out of suspend
  mode and shows login screen again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 10:31:56 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9]
  InstallationDate: Installed on 2022-04-22 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: LENOVO 34601F4
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/19/2013
  dmi.bios.release: 2.59
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G6ET99WW (2.59 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34601F4
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.4
  dmi.modalias: 
dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460:
  dmi.product.family: ThinkPad X1 Carbon
  dmi.product.name: 34601F4
  dmi.product.sku: LENOVO_MT_3460
  dmi.product.version: ThinkPad X1 Carbon
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970155/+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 1970172] Re: External monitor switches to interlaced mode

2022-04-26 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510
(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/1970172

Title:
  External monitor switches to interlaced mode

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New

Bug description:
  After locking my screen and coming back (<1 min), the external monitor
  switched to 1080i instead of 1080p and all text gets blurry.
  Reconnection of the display did not solve the issue.  This has
  happened on either 20.04 or 21.04 when I was using X.org.  When using
  Wayland on Ubuntu 21.10, this issue never appeared.  Now it came back
  after Wayland disappearing (#1968929).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 00:26:03 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
 Subsystem: Hewlett-Packard Company TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [103c:8601]
  InstallationDate: Installed on 2022-04-23 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS 15 7590
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/vgroot-lvroot--ubuntu--22.04 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/09/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 018W12
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn018W12:rvrA02:cvnDellInc.:ct10:cvr:sku0905:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 7590
  dmi.product.sku: 0905
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1970172/+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 1970284] Re: Touch to click cannot be turned off when xserver-xorg-input-synaptics is installed

2022-04-26 Thread Daniel van Vugt
I'm guessing upstream gnome-control-center has retired support for
changing the Synaptics settings, in favor of libinput.

If so then we should drop Expose-touchpad-settings-if-synaptics-is-in-
use.patch so the user is not given touchpad controls.

** Summary changed:

- Touch to click cannot be turned off
+ Touch to click cannot be turned off when xserver-xorg-input-synaptics is 
installed

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

** Changed in: gnome-control-center (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Touch to click cannot be turned off when xserver-xorg-input-synaptics
  is installed

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

Bug description:
  Hi,
  Using xorg, I cannot turn touch to click off.  It can be turned off in 
wayland.
  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 15:52:04 2022
  DistUpgraded: 2022-04-25 14:40:40,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2237]
  InstallationDate: Installed on 2019-04-19 (1102 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  MachineType: LENOVO 20FES0EX00
  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.15.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (0 days ago)
  dmi.bios.date: 06/26/2018
  dmi.bios.release: 1.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET91W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES0EX00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET91W(1.70):bd06/26/2018:br1.70:efr1.27:svnLENOVO:pn20FES0EX00:pvrThinkPadYoga260:rvnLENOVO:rn20FES0EX00:rvrSDK0J40700WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20FE_BU_Think_FM_ThinkPadYoga260:
  dmi.product.family: ThinkPad Yoga 260
  dmi.product.name: 20FES0EX00
  dmi.product.sku: LENOVO_MT_20FE_BU_Think_FM_ThinkPad Yoga 260
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1970284/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)

2022-04-26 Thread Alkis Georgopoulos
I also see it on Ubuntu MATE Jammy.
Will the fix come from Xorg,
or should we add LightDM to the affected projects list?

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in gdm3 package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade

2022-04-26 Thread Christian Ehrhardt 
@Ryan - Before going deeper since I read
"readconf.c:read_config_file_depth" in there. Does the same happen on a
fresh Jammy guest that has all-default config files? Or only to this
particular guest that you have?

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

Title:
  "User process fault: interruption code 0011 ilc:3" on SSH
  client/server upon Jammy upgrade

Status in openssh package in Ubuntu:
  New

Bug description:
  This s390x VM has been upgraded to Jammy, including the host (qemu-
  system-s390x 1:6.2+dfsg-2ubuntu6).  Now any attempt to use ssh, or any
  incoming sshd attempt immediately results in e.g.:

  ryan@s390x-dev:~$ ssh g...@github.com
  [  433.672800] User process fault: interruption code 0011 ilc:3 in 
libc.so.6[3ffa6c0+1ca000]
  [  433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800
  [  433.672977] Fault in primary space mode while using user ASCE.
  [  433.673030] AS:02bc01c7 R3:087cc007 S:0798a000 
P:0400 
  Segmentation fault (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+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 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade

2022-04-26 Thread Christian Ehrhardt 
(gdb) bt
#0  __GI__IO_default_xsputn (n=, data=, 
f=) at libioP.h:947
#1  __GI__IO_default_xsputn (f=0x3ffcbc7c2e8, data=, 
n=2929360903402) at genops.c:370
#2  0x03ffa6c7896c in outstring_func (done=11, length=2929360903402, 
string=0x2aa0b841cea <__func__.3.lto_priv.14> "read_config_file_depth", 
s=0x3ffcbc7c2e8) at ../libio/libioP.h:947
#3  __vfprintf_internal (s=s@entry=0x3ffcbc7c2e8, format=, 
format@entry=0x2aa0b81dea2 "%.48s:%.48s():%d (pid=%ld)", 
ap=ap@entry=0x3ffcbc7c4d0, mode_flags=mode_flags@entry=2)
at vfprintf-internal.c:1517
#4  0x03ffa6c8a024 in __vsnprintf_internal (string=0x3ffcbc7c5c8 
"readconf.c:read_config_file_depth", maxlen=, 
format=0x2aa0b81dea2 "%.48s:%.48s():%d (pid=%ld)", 
args=args@entry=0x3ffcbc7c4d0, mode_flags=mode_flags@entry=2) at 
vsnprintf.c:114
#5  0x03ffa6d2053a in ___snprintf_chk (s=, maxlen=, flag=, slen=, format=) at 
snprintf_chk.c:38
#6  0x02aa0b7d1686 in snprintf (__fmt=0x2aa0b81dea2 "%.48s:%.48s():%d 
(pid=%ld)", __n=128, __s=0x3ffcbc7c5c8 "readconf.c:read_config_file_depth")
at /usr/include/s390x-linux-gnu/bits/stdio2.h:71
#7  sshlogv (file=, func=, line=, 
showfunc=, level=, suffix=0x0, 
fmt=0x2aa0b84162e "Reading configuration data %.200s", args=0x3ffcbc7d3b0) 
at ../../log.c:473
#8  0x02aa0b7d1b88 in sshlog (file=, func=, 
line=, showfunc=, level=SYSLOG_LEVEL_DEBUG1, 
suffix=0x0, 
fmt=0x2aa0b84162e "Reading configuration data %.200s") at ../../log.c:434
#9  0x02aa0b80dbb6 in read_config_file_depth.constprop.0 
(filename=0x2aa0b811b42 "/etc/ssh/ssh_config", pw=0x2aa0d3609d0, 
host=, original_host=, 
flags=, activep=0x3ffcbc7d64c, 
want_final_pass=0x3ffcbc7e7c4, depth=0, options=) at 
../../readconf.c:2326
#10 0x02aa0b793d62 in read_config_file (options=0x2aa0b8518e0 , 
want_final_pass=0x3ffcbc7e7c4, flags=0, original_host=0x2aa0d364bc0 
"github.com", host=, 
pw=0x2aa0d3609d0, filename=0x2aa0b811b42 "/etc/ssh/ssh_config") at 
../../readconf.c:2295
#11 process_config_files (host_name=host_name@entry=0x2aa0d364bc0 "github.com", 
pw=pw@entry=0x2aa0d3609d0, final_pass=final_pass@entry=0, 
want_final_pass=want_final_pass@entry=0x3ffcbc7e7c4)
at ../../ssh.c:569
#12 0x02aa0b78d572 in main (ac=, av=) at 
../../ssh.c:1148

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

Title:
  "User process fault: interruption code 0011 ilc:3" on SSH
  client/server upon Jammy upgrade

Status in openssh package in Ubuntu:
  New

Bug description:
  This s390x VM has been upgraded to Jammy, including the host (qemu-
  system-s390x 1:6.2+dfsg-2ubuntu6).  Now any attempt to use ssh, or any
  incoming sshd attempt immediately results in e.g.:

  ryan@s390x-dev:~$ ssh g...@github.com
  [  433.672800] User process fault: interruption code 0011 ilc:3 in 
libc.so.6[3ffa6c0+1ca000]
  [  433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800
  [  433.672977] Fault in primary space mode while using user ASCE.
  [  433.673030] AS:02bc01c7 R3:087cc007 S:0798a000 
P:0400 
  Segmentation fault (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+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 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade

2022-04-26 Thread Christian Ehrhardt 
Hi,
for comparison on another system I've taken a Host (was impish before upgrade) 
and created guests with Xenial, Bionic, Focal, Jammy.
All worked fine at this stage - ssh login and health of guests/hosts was good.
Then I upgraded the Host to Jammy (as the reporter did).

Example of the simple tests made:
#log into jammy, from there log into focal
ssh -t ubuntu@192.168.122.177 "ssh ubuntu@192.168.122.39"
#log into focal, from there log into jammy
ssh -t ubuntu@192.168.122.39 "ssh ubuntu@192.168.122.177"

=> That was all fine initially (impish)
=> That was all still fine after the upgrade to jammy
=> And it was still fine after restarting the guests (to use the new qemu)

So it can't be reproduced easily, this would need to go into analyzing
the ssh crash dump file that is attached.

@Ryan - if you have any further insight on how/why your config might be
special let us know.

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

Title:
  "User process fault: interruption code 0011 ilc:3" on SSH
  client/server upon Jammy upgrade

Status in openssh package in Ubuntu:
  New

Bug description:
  This s390x VM has been upgraded to Jammy, including the host (qemu-
  system-s390x 1:6.2+dfsg-2ubuntu6).  Now any attempt to use ssh, or any
  incoming sshd attempt immediately results in e.g.:

  ryan@s390x-dev:~$ ssh g...@github.com
  [  433.672800] User process fault: interruption code 0011 ilc:3 in 
libc.so.6[3ffa6c0+1ca000]
  [  433.672946] Failing address: 02aa0b84d000 TEID: 02aa0b84d800
  [  433.672977] Fault in primary space mode while using user ASCE.
  [  433.673030] AS:02bc01c7 R3:087cc007 S:0798a000 
P:0400 
  Segmentation fault (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+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 1970031] Re: Instead of gray, my monitor displays pink-gray. Ubuntu 22.04

2022-04-26 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Tags added: hybrid i915 nvidia

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

Title:
  Instead of gray, my monitor displays pink-gray. Ubuntu 22.04

Status in mutter package in Ubuntu:
  New

Bug description:
  i have GPU: NVIDIA GeForce MX150, instead of the usual gray color, my
  monitor started showing a gray-pink color. I can't take a screenshot
  because it will just be gray on your monitor (i checked the screenshot
  in windows 11). Did the developers break something in the video card
  driver or why did it happen?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  Date: Sat Apr 23 19:54:00 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
 Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
  InstallationDate: Installed on 2022-04-23 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Timi TM1701
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=907bba42-0e12-469a-9f3b-62991b70869f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.release: 106.121
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: XMAKB5R0P0603
  dmi.board.asset.tag: Any
  dmi.board.name: TM1701
  dmi.board.vendor: Timi
  dmi.board.version: MP
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.3
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
  dmi.product.family: Timibook
  dmi.product.name: TM1701
  dmi.sys.vendor: Timi
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970031/+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 1970279] Re: My monitor image turned yellow.

2022-04-26 Thread Daniel van Vugt
Thanks for the bug report.

> I had to switch from Wayland to Xorg on the login screen, and
> after login the screen had a yellow filter.

Does that mean the bug is in Wayland or Xorg sessions?

** Tags added: amdgpu

** Summary changed:

- My monitor image turned yellow.
+ [amdgpu] My monitor image turned yellow.

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

** Also affects: xserver-xorg-video-amdgpu (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Incomplete

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

Title:
  [amdgpu] My monitor image turned yellow.

Status in mutter package in Ubuntu:
  Incomplete
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  I had to switch from Wayland to Xorg on the login screen, and after
  login the screen had a yellow filter.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 25 18:59:04 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8]
  InstallationDate: Installed on 2022-04-23 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=6abdccf1-2e9d-4265-a466-6dcef0abc427 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P5.40
  dmi.board.name: A320M-HD
  dmi.board.vendor: ASRock
  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.:bvrP5.40:bd07/09/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HD:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970279/+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 1955997] Re: The airplane hotkey has no function on a HP platform

2022-04-26 Thread jeremyszu
** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Impish:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1969959] Re: Weird colors after startup (Ubuntu 22.04)

2022-04-26 Thread Daniel van Vugt
** Tags added: nouveau

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

** Summary changed:

- Weird colors after startup (Ubuntu 22.04)
+ [nouveau] Weird colors after startup (Ubuntu 22.04)

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

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [nouveau] Weird colors after startup (Ubuntu 22.04)

Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1969853] Re: Bluetooth doesn't work but seems active

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

apport-collect 1969853

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

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

** Summary changed:

- Bluetooth doesn't work but seems active
+ No Bluetooth Found

** Tags added: jammy

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

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

Title:
  No Bluetooth Found

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After updating to version 22.04, with kernel 5.15.0-25, Bluettoth
  stopped working via menu. Before I used versions 20.04 and 21.10, the
  latter with kernel 5.13, and Bluetooth was recognized normally. The
  bluetooth status in the terminal is this:

  diego@diego-Inspiron:~$ sudo systemctl status bluetooth.service
  ● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2022-04-21 18:16:17 -03; 16min ago
 Docs: man:bluetoothd(8)
 Main PID: 1100 (bluetoothd)
   Status: "Running"
Tasks: 1 (limit: 18808)
   Memory: 1.8M
  CPU: 66ms
   CGroup: /system.slice/bluetooth.service
   └─1100 /usr/lib/bluetooth/bluetoothd

  abr 21 18:16:16 diego-Inspiron systemd[1]: Starting Bluetooth service...
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth daemon 5.64
  abr 21 18:16:17 diego-Inspiron systemd[1]: Started Bluetooth service.
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Starting SDP server
  abr 21 18:16:17 diego-Inspiron bluetoothd[1100]: Bluetooth management 
interface 1.21 initialized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969853/+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 1965439] Re: software-properties-qt can no longer launch when called by pkexec

2022-04-26 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  software-properties-qt can no longer launch when called by pkexec

Status in kdesu package in Ubuntu:
  Confirmed
Status in kubuntu-settings package in Ubuntu:
  In Progress
Status in policykit-1 package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in kdesu source package in Jammy:
  Confirmed
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in policykit-1 source package in Jammy:
  Confirmed
Status in software-properties source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)

2022-04-26 Thread Norbert
Still happens on UM Jammy.

How Long?

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in gdm3 package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1955135] Re: multiple issues with /etc/X11/Xsession.d/ - "has_option: command not found"

2022-04-26 Thread Norbert
*** This bug is a duplicate of bug 1922414 ***
https://bugs.launchpad.net/bugs/1922414

Still happens on UM Jammy.

How Long?

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

Title:
  multiple issues with /etc/X11/Xsession.d/ - "has_option: command not
  found"

Status in dbus package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Boot 20211217 Ubuntu MATE daily ISO
  2. Open ~/.xsession-errors

  Expected results:
  * no errors and warnings 

  Actual results:
  * there are two errors about xorg:

  /etc/X11/Xsession.d/30x11-common_xresources: line 16: has_option: command not 
found
  /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: x11-common 1:7.7+23ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Dec 17 14:22:15 2021
  Dependencies: lsb-base 11.1.0ubuntu3
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF108M [GeForce GT 425M] [10de:0df0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Sony Corporation GF108M [GeForce GT 425M] [104d:907a]
  LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211217)
  MachineType: Sony Corporation VPCF13Z1R
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2010
  dmi.bios.release: 1.90
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y9
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 1.90
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y9:bd10/20/2010:br1.90:efr1.90:svnSonyCorporation:pnVPCF13Z1R:pvrC606GZYK:skuN/A:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCF13Z1R
  dmi.product.sku: N/A
  dmi.product.version: C606GZYK
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955135/+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 1948882] Re: PulseEffects does not properly initialize on startup

2022-04-26 Thread Roman
Just confirming that the issue moved to Ubuntu Jammy stable relese. The
workaround with downgrading DConf to the Hirsute version still works.

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+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 1955136] Re: /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command not found

2022-04-26 Thread Norbert
Still happens on UM Jammy.

How Long?

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

Title:
  /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command
  not found

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  teps to reproduce:
  1. Boot 20211217 Ubuntu MATE daily ISO
  2. Open ~/.xsession-errors

  Expected results:
  * no errors and warnings

  Actual results:
  * there are two errors about dbus:

  /etc/X11/Xsession.d/75dbus_dbus-launch: line 9: has_option: command
  not found

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dbus-x11 1.12.20-2ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: MATE
  Date: Fri Dec 17 14:28:01 2021
  LiveMediaBuild: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 
(20211217)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1955136/+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 1970379] [NEW] package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-04-26 Thread Miro Stanik
Public bug reported:

I have fresh installation Ubuntu 22.04. When suspend my laptop, poer led
still light and there is much power consuption. I want to install acpi-
override-initramfs, but install crash.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu13
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
AptOrdering:
 acpi-override-initramfs:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Apr 26 08:49:32 2022
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2022-04-24 (1 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt  2.4.5
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I have fresh installation Ubuntu 22.04. When suspend my laptop, poer
  led still light and there is much power consuption. I want to install
  acpi-override-initramfs, but install crash.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  AptOrdering:
   acpi-override-initramfs:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Apr 26 08:49:32 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-04-24 (1 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2
   apt  2.4.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970379/+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