date:20230104

Thanks for the bug report. Can you attach a photo or video of the
problem?

** Tags added: amdgpu

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

** Changed in: 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/2001721

Title:
  Ubuntu screen flickering

Status in Ubuntu:
  Incomplete

Bug description:
  Hi

  i did use ubuntu for more than a year on this laptop 
  last a few days i used HDMI cable, today for a few hours i did use a new 
cable "longer one"
  now suddenly my laptop display went green as you can see in the attachment   

  i did some search but can't find solution.

  
  
https://askubuntu.com/questions/1231441/ubuntu-screen-flickering/1250859#1250859
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534

  Ali

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  4 22:41:41 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev e2) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a]
  InstallationDate: Installed on 2021-12-20 (380 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 81N3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=52450c12-da25-47db-984c-a2036e93aff5 ro reboot=pci quiet splash 
acpi=force vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 1.20
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AYCN20WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S145-15AST
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrAYCN20WW:bd11/27/2019:br1.20:efr1.20:svnLENOVO:pn81N3:pvrLenovoIdeaPadS145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15AST:skuLENOVO_MT_81N3_BU_idea_FM_IdeaPadS145-15AST:
  dmi.product.family: IdeaPad S145-15AST
  dmi.product.name: 81N3
  dmi.product.sku: LENOVO_MT_81N3_BU_idea_FM_IdeaPad S145-15AST
  dmi.product.version: Lenovo IdeaPad S145-15AST
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2001721/+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 2000833] Re: graphic error

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 2000833

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: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (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/2000833

Title:
  graphic error

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  black glitch in every video playing such as youtube ,and blinkin in
  website when mouse move

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2000833/+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 2000835] Re: After resuming work, only the external screen works.

Thanks for the bug report. Next time the problem happens, please open a
terminal (Ctrl+Alt+T) and run:

  journalctl -b0 > journal.txt

and attach the resulting text file here.

I am wondering if this might be bug 1968040.

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

Title:
  After resuming work, only the external screen works.

Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  Work on two monitors - extended.
  After a certain period of time, the monitor automatically shuts down and 
locks the screen. Starting work turns on the external screen only. The built-in 
one is disabled. I can't see the window when entering the password. The only 
way is to switch to one monitor, then turn both back on. Sometimes the order of 
the displays is swapped (the main one becomes the external monitor)

  nvidia-driver-525 - current report
  nvidia-driver-525-open - not working

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-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  525.60.11  Wed Nov 23 
23:04:03 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan  1 13:45:23 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   linux-apfs-rw/0+git20220214+ds-1, 5.15.0-53-generic, x86_64: installed
   linux-apfs-rw/0+git20220214+ds-1, 5.15.0-56-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] CoffeeLake-H GT2 [UHD Graphics 630] 
[1025:133a]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] TU117M [GeForce GTX 1650 Mobile / 
Max-Q] [1025:1337]
  InstallationDate: Installed on 2020-04-05 (1000 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: Acer Aspire A715-74G
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vg_ubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2020
  dmi.bios.release: 1.29
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.29
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Pidgey_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.29
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.29
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.29:bd04/09/2020:br1.29:efr1.27:svnAcer:pnAspireA715-74G:pvrV1.29:rvnCFL:rnPidgey_CFS:rvrV1.29:cvnAcer:ct10:cvrV1.29:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-74G
  dmi.product.sku: 
  dmi.product.version: V1.29
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  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.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/2000835/+subscriptions


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

[Touch-packages] [Bug 1997124] Re: Netplan/Systemd/Cloud-init/Dbus Race

2023-01-04 Thread Rod Smith

We've run into this in the Server Certification lab on mouser, a NEC
Express5800/R128h-1M server. In our testing, it's affected 50% (2 of 4)
Ubuntu 20.04 deployments, but not 18.04 or 22.04 deployments (0 of 3 for
each of those). These sample sizes are low, so this may be a
coincidence; but I'm mentioning it here in case it's not a coincidence.

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

Title:
  Netplan/Systemd/Cloud-init/Dbus Race

Status in cloud-init:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Cloud-init is seeing intermittent failures while running `netplan
  apply`, which appears to be caused by a missing resource at the time
  of call.

  The symptom in cloud-init logs looks like:

  Running ['netplan', 'apply'] resulted in stderr output: Failed to
  connect system bus: No such file or directory

  I think that this error[1] is likely caused by cloud-init running
  netplan apply too early in boot process (before dbus is active).

  Today I stumbled upon this error which was hit in MAAS[2]. We have
  also hit it intermittently during tests (we didn't have a reproducer).

  Realizing that this may not be a cloud-init error, but possibly a
  dependency bug between dbus/systemd we decided to file this bug for
  broader visibility to other projects.

  I will follow up this initial report with some comments from our
  discussion earlier.

  [1] https://github.com/canonical/netplan/blob/main/src/dbus.c#L801
  [2] 
https://discourse.maas.io/t/latest-ubuntu-20-04-image-causing-netplan-error/5970

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1997124/+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 2000798] Re: cannot connect to K380 bluetooth keyboard

If the machines are in different locations then they will experience
different interference. It might only fail in the presence of too much
2.4GHz noise like wifi networks or other Bluetooth devices. Such
interference will come and go over time.

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

Title:
  cannot connect to K380 bluetooth keyboard

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Had trouble connecting my K380 keyboard with the laptop (previously
  used it without issues), unpaired and now I can no longer pair it.

  Other bluetooth devices work with this particular laptop (mouse,
  earbuds), the keyboard works flawlessly with a different laptop
  (running the same Ubuntu 20.04 OS) and an Android phone.

  Used bluetoothctl to peek under the hood and got nowhere after turning scan 
on on the controller and activating the keyboard:
  [NEW] Device [...mac address of the keyboard...] Keyboard K380
  [CHG] Device [...mac address of the keyboard...] Connected: no
  [DEL] Device [...mac address of the keyboard...] Keyboard K380

  After this action, I get:

  # connect [...mac address of the keyboard...]
  Device [...mac address of the keyboard...] not available

  When I activate the keyboard (by pressing any key on it while it's
  turned on), in the bluetooth settings GUI tool I see the keyboard
  appear for a fraction of a second in the list of unpaired devices and
  then it disappears.

  Help?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 30 19:41:41 2022
  InstallationDate: Installed on 2022-11-03 (57 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems LAPKC71E
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCTGL357.0037.2021.0712.0948
  dmi.board.name: LAPKC71E
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M1-402
  dmi.chassis.type: 10
  dmi.chassis.vendor: Intel(R) Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000:
  dmi.product.family: KC
  dmi.product.name: LAPKC71E
  dmi.product.sku: BKC71EBFB6000
  dmi.product.version: M38559-402
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 20:1E:88:3C:4C:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:221779 acl:5063 sco:0 events:6018 errors:0
TX bytes:785416 acl:104 sco:0 commands:4168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 2000817] Re: Wrong SHA256-value computed on kinetic

2023-01-04 Thread Sergio Durigan Junior

** Changed in: openldap (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  Wrong SHA256-value computed on kinetic

Status in openldap package in Ubuntu:
  Triaged

Bug description:
  The OpenLDAP-contrib module sha2 (located in contrib/slapd-
  modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
  kinetic. This breaks our current password-authentication in ldap.

  
  The problematic computation:

  $ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
  {SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=

  The (correct) reference-value on the same system (or older ubuntu
  Versions):

  $ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
  K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=

  
  We nailed the problem down to a bug in the gcc-optimizer for strict-aliasing. 
so most probably the gcc-version on kinetic (v12.2.0) is the reason. The 
workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing". 
Then the correct value is computed. An example taken from a git-compiled 
version of OpenLDAP 2.5.13:

  $ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o 
module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs
  {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=


  
  Ubuntu:

  Description:Ubuntu 22.10
  Release:22.10

  OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2000817/+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 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate

2023-01-04 Thread Anti Mailer

Confirmed on Ubuntu 20.04 - kernel 5.4.0-135
The behaviour exits for about the last 5 kernel updates - but also a weak bios 
battery (wrong hw clock after resume) can be the reason for the problem.
Suggested solution: Forcing a time sync after resuming from hibernation.

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

Title:
  systemd-timesyncd doesn't sync time after resume from hibernate

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When resuming, the clock remains at the time when the hibernate
  happened, even if timedatectl claims that it is being synced:

  $ timedatectl status
Local time: Вс 2017-12-31 13:46:16 +05
Universal time: Вс 2017-12-31 08:46:16 UTC
  RTC time: Вс 2017-12-31 08:46:16
 Time zone: Asia/Yekaterinburg (+05, +0500)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  I've tried waiting a bit, but this persisted for some minutes, so I
  forced an update with

  systemctl restart systemd-timesyncd.service

  And afterwards the time was (apparently) correctly synced.

  Please, let me know what further informations are needed to debug the
  issue, and I would be happy to do some other test.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 31 13:41:51 2017
  InstallationDate: Installed on 2017-06-05 (208 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 
zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P35-DS3
  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.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740666/+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 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate

2023-01-04 Thread Anti Mailer

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

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

Title:
  systemd-timesyncd doesn't sync time after resume from hibernate

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When resuming, the clock remains at the time when the hibernate
  happened, even if timedatectl claims that it is being synced:

  $ timedatectl status
Local time: Вс 2017-12-31 13:46:16 +05
Universal time: Вс 2017-12-31 08:46:16 UTC
  RTC time: Вс 2017-12-31 08:46:16
 Time zone: Asia/Yekaterinburg (+05, +0500)
   Network time on: yes
  NTP synchronized: yes
   RTC in local TZ: no

  I've tried waiting a bit, but this persisted for some minutes, so I
  forced an update with

  systemctl restart systemd-timesyncd.service

  And afterwards the time was (apparently) correctly synced.

  Please, let me know what further informations are needed to debug the
  issue, and I would be happy to do some other test.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Dec 31 13:41:51 2017
  InstallationDate: Installed on 2017-06-05 (208 days ago)
  InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Gigabyte Technology Co., Ltd. P35-DS3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic 
root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 
zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F14
  dmi.board.name: P35-DS3
  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.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-DS3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740666/+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 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort

2023-01-04 Thread Matthew Ruffell

Performing verification for Bionic.

I started two instances on AWS, one c6g.medium (arm64) and a t2.micro
(amd64).

I went through the reproducer listed in the testcase with libunwind-dev
1.2.1-8 from -release.

$ wget 
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz
$ sudo apt install -y build-essential libunwind-dev
$ tar xvf libunwind.tar.gz && cd test
test/
test/lib.hpp
test/main.cpp
test/lib.cpp
test/Makefile
~/test$ make all
g++ -g -shared-libgcc -shared -fPIC -std=c++11 -o libtest.so lib.cpp
g++ -g -shared-libgcc -o main -L. -Wl,-rpath,. main.cpp -ltest
g++ -g -shared-libgcc -o main_unwind -L. -Wl,-rpath,.  main.cpp -ltest -lunwind

On arm64:

~/test$ ./main
int throws lib
int caught main
~/test$ ./main_unwind
terminate called after throwing an instance of 'int'
terminate called recursively
Aborted (core dumped)

On amd64:

~/test$ ./main
int throws lib
int caught main
~/test$ ./main_unwind
int throws lib
int caught main

As expected, we see arm64 abort the execution of the reproducer.

I then installed 1.2.1-8ubuntu0.1 from -proposed and rebuilt the
reproducers:

$ make clean
$ make all
g++ -g -shared-libgcc -shared -fPIC -std=c++11 -o libtest.so lib.cpp
g++ -g -shared-libgcc -o main -L. -Wl,-rpath,. main.cpp -ltest
g++ -g -shared-libgcc -o main_unwind -L. -Wl,-rpath,.  main.cpp -ltest -lunwind

On arm64:

$ ./main
int throws lib
int caught main
$ ./main_unwind
int throws lib
int caught main

On amd64:

~/test$ ./main
int throws lib
int caught main
~/test$ ./main_unwind
int throws lib
int caught main

We see that 1.2.1-8ubuntu0.1 from -proposed does not abort, and instead
runs as expected. There is no change in behaviour on amd64. The package
in -proposed fixes the problem, happy to mark as verified for Bionic.

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

Title:
  arm64: broken c++ exception handler support leads to std::terminate()
  being called and program abort

Status in libunwind package in Ubuntu:
  Fix Released
Status in libunwind source package in Bionic:
  Fix Committed
Status in libunwind source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  On architectures other than i386 and amd64, the C++ exception support
  in libunwind appears to be broken, always failing and calling
  std::terminate() which leads to the program aborting.

  (gdb) bt
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
  #1  0xf7c2daac in __GI_abort () at abort.c:79
  #2  0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #3  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #4  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #5  0xf7e1f5e0 in __cxa_rethrow ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #6  0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #7  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #8  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #9  0xf7e1f574 in __cxa_throw ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9
  #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9

  Compiling libunwind with --enable-cxx-exceptions enabled leads to
  _Unwind_RaiseException being called during __cxa_throw(), which fails
  to find a handler, and the generic std::terminate() is called instead,
  aborting the program.

  On i386 and amd64 this doesn't seem to be the case, and the libunwind
  handlers seem to be present.

  To fix, we only enable the configure option --enable-cxx-exceptions on
  i386 and amd64 only, in debian/rules. This lets other architectures
  fall back to the symbols provided by libgcc_s, which implementation
  works correctly.

  [Testcase]

  Ali Sadi has provided a reproducer program.

  Start an arm64 instance, for example, a c6g.medium instance on AWS,
  with either Bionic or Focal.

  $ wget 
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz
  $ sudo apt install -y build-essential libunwind-dev
  $ tar xvf libunwind.tar.gz && cd test
  $ make all

  There are two executable, main and main_unwind. main is not linked to
  libunwind, and main_unwind is linked to libunwind.

  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  terminate called after throwing an instance of 'int'
  terminate called recursively
  Aborted (core dumped)

  If you install the test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf350246-test

  $ make clean
  $ sudo apt install -y

[Touch-packages] [Bug 1999104] Re: arm64: broken c++ exception handler support leads to std::terminate() being called and program abort

2023-01-04 Thread Matthew Ruffell

Performing verification for Focal.

I started two instances on AWS, one c6g.medium (arm64) and a t2.micro
(amd64).

I went through the reproducer listed in the testcase with libunwind-dev
1.2.1-9build1 from -release.

$ wget 
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz
$ sudo apt install -y build-essential libunwind-dev
$ tar xvf libunwind.tar.gz && cd test
test/
test/lib.hpp
test/main.cpp
test/lib.cpp
test/Makefile
~/test$ make all
g++ -g -shared-libgcc -shared -fPIC -std=c++11 -o libtest.so lib.cpp
g++ -g -shared-libgcc -o main -L. -Wl,-rpath,. main.cpp -ltest
g++ -g -shared-libgcc -o main_unwind -L. -Wl,-rpath,.  main.cpp -ltest -lunwind

On arm64:

~/test$ ./main
int throws lib
int caught main
~/test$ ./main_unwind
terminate called after throwing an instance of 'int'
terminate called recursively
Aborted (core dumped)

On amd64:

~/test$ ./main
int throws lib
int caught main
~/test$ ./main_unwind
int throws lib
int caught main

As expected, we see arm64 abort the execution of the reproducer.

I then installed 1.2.1-9ubuntu0.1 from -proposed and rebuilt the
reproducers:

$ make clean
$ make all
g++ -g -shared-libgcc -shared -fPIC -std=c++11 -o libtest.so lib.cpp
g++ -g -shared-libgcc -o main -L. -Wl,-rpath,. main.cpp -ltest
g++ -g -shared-libgcc -o main_unwind -L. -Wl,-rpath,.  main.cpp -ltest -lunwind

On arm64:

$ ./main
int throws lib
int caught main
$ ./main_unwind
int throws lib
int caught main

On amd64:

~/test$ ./main
int throws lib
int caught main
~/test$ ./main_unwind
int throws lib
int caught main

We see that 1.2.1-9ubuntu0.1 from -proposed does not abort, and instead
runs as expected. There is no change in behaviour on amd64. The package
in -proposed fixes the problem, happy to mark as verified for Focal.

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

Title:
  arm64: broken c++ exception handler support leads to std::terminate()
  being called and program abort

Status in libunwind package in Ubuntu:
  Fix Released
Status in libunwind source package in Bionic:
  Fix Committed
Status in libunwind source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  On architectures other than i386 and amd64, the C++ exception support
  in libunwind appears to be broken, always failing and calling
  std::terminate() which leads to the program aborting.

  (gdb) bt
  #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
  #1  0xf7c2daac in __GI_abort () at abort.c:79
  #2  0xf7e21868 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #3  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #4  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #5  0xf7e1f5e0 in __cxa_rethrow ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #6  0xf7e21804 in __gnu_cxx::__verbose_terminate_handler() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #7  0xf7e1f21c in ?? () from /lib/aarch64-linux-gnu/libstdc++.so.6
  #8  0xf7e1f280 in std::terminate() ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #9  0xf7e1f574 in __cxa_throw ()
 from /lib/aarch64-linux-gnu/libstdc++.so.6
  #10 0xf7fb9f50 in function_throws_int () at lib.cpp:9
  #11 0x0d54 in main (argc=1, argv=0xfab8) at main.cpp:9

  Compiling libunwind with --enable-cxx-exceptions enabled leads to
  _Unwind_RaiseException being called during __cxa_throw(), which fails
  to find a handler, and the generic std::terminate() is called instead,
  aborting the program.

  On i386 and amd64 this doesn't seem to be the case, and the libunwind
  handlers seem to be present.

  To fix, we only enable the configure option --enable-cxx-exceptions on
  i386 and amd64 only, in debian/rules. This lets other architectures
  fall back to the symbols provided by libgcc_s, which implementation
  works correctly.

  [Testcase]

  Ali Sadi has provided a reproducer program.

  Start an arm64 instance, for example, a c6g.medium instance on AWS,
  with either Bionic or Focal.

  $ wget 
https://bugs.launchpad.net/ubuntu/+source/libunwind/+bug/1999104/+attachment/5635122/+files/libunwind.tar.gz
  $ sudo apt install -y build-essential libunwind-dev
  $ tar xvf libunwind.tar.gz && cd test
  $ make all

  There are two executable, main and main_unwind. main is not linked to
  libunwind, and main_unwind is linked to libunwind.

  $ ./main
  int throws lib
  int caught main
  $ ./main_unwind
  terminate called after throwing an instance of 'int'
  terminate called recursively
  Aborted (core dumped)

  If you install the test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf350246-test

  $ make clean
  $ sudo apt

[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

2023-01-04 Thread Gunnar Hjalmarsson

On 2023-01-04 18:46, Robie Basak wrote:
> What's the plan for Kinetic? Please see:
> https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases

The plan is to be lazy and skip kinetic. ;)

Actually, in this particular case it shouldn't be a problem. If a user
with an updated jammy (including this fix) upgrades to kinetic, they
will still have version 0.219.1 of the language-selector-* packages,
since the version string in kinetic is lower. So no regression.

I added a kinetic "Won't fix" bug task to clarify my intention.

> If the goal is to make Sinhala text more readable on Ubuntu, please
> could you make that an additional part of the Test Plan, instead of
> only checking the order of output in a font listing?

I expanded the test plan with that.

>> Where problems could occur
> 
> It sounds like font metrics are changing, so text might wrap
> differently, resulting in it no longer fitting, or change the size
> of windows, etc, in various user interface elements. It sounds like
> it's worth the change, but please look out for this during testing.

Please note that Sinhala is not well covered with respect to FOSS
(including Ubuntu) translations. If you use Sinhala as the display
language for menus and messages, you see Sinhala strings only
occasionally. So even if the risk you mention exists, it's a low risk
for this reason.

I'm assuming that the focus of the Sinhala speaking users is about web
browsing at first hand.

But I added a pointer to this aspect in the bug description.

** Description changed:

  [ Impact ]

  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.

  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than LKLUG, and
  that — together with installation of fonts-noto-core — seems to be
  sufficient to achieve the desired result.

  [ Test Plan ]

  * Install language-selector-[common,gnome] from jammy-proposed.

  * Open Language Support and install the Sinhala language.

  * Open a terminal window and run this command:

-   fc-match -a | grep -E 'LKLUG|Sinhala'
+   fc-match -a | grep -E 'LKLUG|Sinhala'

  * Confirm that Noto Sans Sinhala is listed before LKLUG.
+ 
+ * Close Firefox and re-open it.
+ 
+ * Visit e.g. https://si.wikipedia.org and confirm the
+   improvement. (Also I (Gunnar), who don't speak Sinhala,
+   notice a remarkable difference.)

  [ Where problems could occur ]

  No real problem in sight. Some Sinhala speaking users with fonts-noto-
  core installed will indeed see a surprise change when it starts to
  render Sinhala via Noto fonts instead of LKLUG. But that surprise ought
  to make them happy. :)
+ 
+ Please note Robie Basak's warning about the changed font metrics in
+ comment #7, though.

  [ Original description ]

  **What's the problem?**

  Currently ubuntu comes with LKLUG font for sinhala (si). it's not clear.
  e.g. we cannot recognize vowel signs and read websites using that font.
  We can change it manually but such changes do not apply to some
  applications or application types e.g. snap apps etc.

  LKLUG (last active: 2012) no one maintain it now.
  https://web.archive.org/web/202200*/http://www.lug.lk/
  http://www.lug.lk/fonts/lklug

  **What expected to happen?**

  We would like to see Noto serif sinhala as the default font for sinhala 
language
  https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala
  [Highlighs: clear (readable), thin, takes less space than sans sinhala]

  If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala 
https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala
  [Highlighs: clear (readable), thick, takes more space than serif sinhala]

  **Additional details**

  Screenshots (see the difference: LKLUG/Noto)

  LKLUG
  https://i.ibb.co/nbHM5Mw/lklug.jpg

  Noto Sinhala
  https://i.ibb.co/k9dbtYb/noto.jpg

  If you need more examples or clarifications, please add a comment

  Random posts
  1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g
  2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with 
some apps)
  3. 
https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/

  Also, some developers already have designed tools, scripts for that problem 
however many people do not try to find these scripts and switch to other OS
  1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache)
  2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79
  3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer

  Please review details, screenshots and posts. This is not a personal
  opinion and atleast, i expect to see this change in the next interim or
  LTS release.

  Furthermore, please let me know

[Touch-packages] [Bug 1993420] Re: Merge net-tools from Debian unstable for lunar

2023-01-04 Thread Lena Voytek

** Changed in: net-tools (Ubuntu)
   Status: New => In Progress

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

Title:
  Merge net-tools from Debian unstable for lunar

Status in net-tools package in Ubuntu:
  In Progress

Bug description:
  Scheduled-For: ubuntu-23.01
  Upstream: tbd
  Debian:   2.10-0.1
  Ubuntu:   1.60+git20181103.0eebece-1ubuntu5

  ### New Debian Changes ###

  net-tools (1.60+git20181103.0eebece-1) unstable; urgency=medium

    * New upstream version 1.60+git20181103.0eebece
  - Fix nstrcmp() to prevent ifconfig from showing
    duplicate interfaces. (Closes: #812886)
    * Fix d/watch to point to upstream git repository
    * Add patch to fix decoding of MII vendor ids. (Closes: #549397)
  - Thanks, Ben Hutchings, for the patch.
    * Add patch to fix Japanese translation which uses a wrong
  Kanji character. (Closes: #621752)
  - Thanks, Takeshi Hamasaki, for the patch.
    * Add patch to fix wrong indentation of 'collisions' in  the
  Japanese translation. (Closes: #653117)
  - Thanks, NODA, Kai, for the patch.
    * Fix Uploaders' field.
  - Add myself as an uploader.
  - Fix Tina's details.

   -- Utkarsh Gupta   Fri, 02 Oct 2020 15:01:04
  +0530

  net-tools (1.60+git20180626.aebd88e-1) unstable; urgency=medium

    * New upstream snapshot
    * Refresh patches.
    * Fix typos in German manpages. Thanks to Prof. Dr. Steffen Wendzel and
  Dr. Tobias Quathamer for the patch. Closes: #900962.

   -- Martín Ferrari   Mon, 24 Sep 2018 19:08:57
  +

  net-tools (1.60+git20161116.90da8a0-4) unstable; urgency=medium

    * Update maintainer email address. Closes: #899617.
    * Update Standards-Version with no changes.

   -- Martín Ferrari   Mon, 24 Sep 2018 17:16:31
  +

  net-tools (1.60+git20161116.90da8a0-3) unstable; urgency=medium

    * debian/control: Update Vcs-* and Standards-Version.
    * debian/control: remove references to ancient package ja-trans.
    * debian/gbp.conf: Update repo layout.

   -- Martín Ferrari   Tue, 31 Jul 2018 19:09:00
  +

  net-tools (1.60+git20161116.90da8a0-2) unstable; urgency=medium

    * Fix typo in French manpage. Thanks to  Michel Grigaut for the patch.
    * Add manpage for iptunnel, thanks to Sergio Durigan Junior.
  Closes: #88910
    * Rename patches so CME does not choke on them.
    * Automated cme fixes; packaging improvements.
    * Remove unused and ancient patch.

   -- Martín Ferrari   Sun, 11 Feb 2018 17:29:24
  +

  net-tools (1.60+git20161116.90da8a0-1) unstable; urgency=medium

    * New upstream snapshot.
    * Re-synced translations.patch.
    * Acknowledge NMUs. Thanks a lot to Andrey Rahmatullin for the
  fixes and uploads. Closes: 846509.
    * Fix FTCBFS, thanks to Helmut Grohne for the patch. Closes: #811561.
  + Really assign CC for cross compilation.
  + Use triplet prefixed pkg-config.
    * Add debian/NEWS warning about changing output in net-tools commands.
  Closing bugs that reported problems in 3rd-party scripts arising from 
these
  changes.  Closes: #845153, #843892, #820212.
    * Update Standards-Version, with no changes.

   -- Martín Ferrari   Mon, 26 Dec 2016 05:58:42
  +

  net-tools (1.60+git20150829.73cef8a-2.2) unstable; urgency=medium

    * Non-maintainer upload.
    * Apply an additional fix for the previous FTBFS for some architectures.

   -- Andrey Rahmatullin   Thu, 01 Dec 2016 22:49:27
  +0500

  net-tools (1.60+git20150829.73cef8a-2.1) unstable; urgency=medium

    * Non-maintainer upload.
    * Fix FTBFS by applying the upstream patch (Closes: #844073).

   -- Andrey Rahmatullin   Sun, 20 Nov 2016 15:23:12
  +0500

  net-tools (1.60+git20150829.73cef8a-2) unstable; urgency=medium

    [ Laurent Bigonville ]
    * Enable SELinux support. Closes: #666204.

    [ Martín Ferrari ]
    * Mark the package 'Multi-Arch: foreign', thanks to Frédéric Brière
  . Closes: #752584.
    * Fix bug in Portuguese man page, thanks to julianofisc...@gmail.com.
  Closes: #805377.

   -- Martín Ferrari   Thu, 19 Nov 2015 14:48:47
  +

  net-tools (1.60+git20150829.73cef8a-1) unstable; urgency=medium

  ### Old Ubuntu Delta ###

  net-tools (1.60+git20181103.0eebece-1ubuntu5) jammy; urgency=high

    * No change rebuild for ppc64el baseline bump.

   -- Julian Andres Klode   Thu, 24 Mar 2022
  17:20:48 +0100

  net-tools (1.60+git20181103.0eebece-1ubuntu4) jammy; urgency=low

    * Add new DEP8 tests for hostname and ifconfig (LP: #1679346):
  - d/t/control: add hostname-set-get and ifconfig-lo-info
  - d/t/hostname-set-get: new test
  - d/t/ifconfig-lo-info: new test

   -- Lena Voytek   Fri, 22 Oct 2021 07:49:06
  -0700

  net-tools (1.60+git20181103.0eebece-1ubuntu3) impish; urgency=medium

    * No-change rebuild to build packages with zstd compression.

   --

[Touch-packages] [Bug 2001721] [NEW] Ubuntu screen flickering

2023-01-04 Thread ali

Public bug reported:

Hi

i did use ubuntu for more than a year on this laptop 
last a few days i used HDMI cable, today for a few hours i did use a new cable 
"longer one"
now suddenly my laptop display went green as you can see in the attachment   

i did some search but can't find solution.


https://askubuntu.com/questions/1231441/ubuntu-screen-flickering/1250859#1250859
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534

Ali

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan  4 22:41:41 2023
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev e2) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a]
InstallationDate: Installed on 2021-12-20 (380 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: LENOVO 81N3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=52450c12-da25-47db-984c-a2036e93aff5 ro reboot=pci quiet splash 
acpi=force vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/27/2019
dmi.bios.release: 1.20
dmi.bios.vendor: LENOVO
dmi.bios.version: AYCN20WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-15AST
dmi.ec.firmware.release: 1.20
dmi.modalias: 
dmi:bvnLENOVO:bvrAYCN20WW:bd11/27/2019:br1.20:efr1.20:svnLENOVO:pn81N3:pvrLenovoIdeaPadS145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15AST:skuLENOVO_MT_81N3_BU_idea_FM_IdeaPadS145-15AST:
dmi.product.family: IdeaPad S145-15AST
dmi.product.name: 81N3
dmi.product.sku: LENOVO_MT_81N3_BU_idea_FM_IdeaPad S145-15AST
dmi.product.version: Lenovo IdeaPad S145-15AST
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal third-party-packages 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/2001721

Title:
  Ubuntu screen flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi

  i did use ubuntu for more than a year on this laptop 
  last a few days i used HDMI cable, today for a few hours i did use a new 
cable "longer one"
  now suddenly my laptop display went green as you can see in the attachment   

  i did some search but can't find solution.

  
  
https://askubuntu.com/questions/1231441/ubuntu-screen-flickering/1250859#1250859
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534

  Ali

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  4 22:41:41 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] 
[1002:98e4] (rev e2) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:3f1a]
  InstallationDate: Installed on 2021-12-20 (380 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: LENOVO 81N3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic 
root=UUID=52450c12-da25-47db-984c-a2036e93aff5 ro reboot=pci quiet splash 
acpi=force vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present

[Touch-packages] [Bug 1864424] Re: new vim version in 20.04 sets mouse=a by default

2023-01-04 Thread Simon Quigley

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

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

Title:
  new vim version in 20.04 sets mouse=a by default

Status in vim package in Ubuntu:
  Fix Released

Bug description:
  Upgrading vim in Focal from 2:8.1.0875-5ubuntu4 to 2:8.1.2269-1ubuntu1
  changed the default behavior.

  Old:
  :set mouse
   mouse=

  New:
  :set mouse
   mouse=a

  That new behavior prevents most peoples common 
  In fact that is one thing that always annoys me when working with a Debian 
VM/Container to have switch to mouse=v to get things working again.

  Issues:
  - marking something with the mouse does NOT copy it anymore
  - marking something with the mouse does not even allow right-click to copy
  - probably more

  Yes I know one could press shift to get the old behavior, but that
  isn't how the rest of the terminal works. I'd much prefer to "press
  shift for the uncommon/new behavior".

  We always had in the changelog:
   - debian/patches/ubuntu-mouse-off.patch:
 + Mouse mode is actively harmful in some chroots.
  Old bug 1661691 brought that delta in early 2017

  But this was dropped on the last merge:
  * Dropped changes, included upstream:
- debian/patches/ubuntu-mouse-off.patch:
  + Mouse mode is actively harmful in some chroots.
  Yet if this would be upstream then the behavior would not have changed right?

  Was this change intentional and is there a good reason that makes up for the 
drawback?
  Or is it a bug that was missed on the merge of the new version and should be 
resolved before 20.04 goes into FF?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1864424/+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 1981794] Re: Duplicate/retried DNS queries fail with REFUSED (Fixed in upstream)

2023-01-04 Thread Lena Voytek

** Description changed:

  [Impact]
  
  When a DNS query fails to complete and the system retries it, subsequent
  copies of the query will be refused by dnsmasq. The client will
  automatically receive the REFUSED return value without a retry attempt.
  
  Adding this fix will stop dnsmasq from unnecessarily breaking
  connections, especially for situations where an internet connection is
  flaky.
  
  This bug is fixed by patching in an upstream commit -
  https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=2561f9fe0eb9c0be
  - which allows retried DNS requests through rather than refusing them.
  
  [Test Plan]
  
  The fix can be tested using 2 lxd containers, 1 for running the fix, and
  1 for acting as a dns server.
  
  Start by setting up the dns server container:
  
  # lxc launch images:ubuntu/jammy dns-resolver
  # lxc exec dns-resolver bash
  
  # apt update && apt dist-upgrade -y
  # systemctl disable systemd-resolved
  # systemctl stop systemd-resolved
  # unlink /etc/resolv.conf
  # echo nameserver 8.8.8.8 | tee /etc/resolv.conf
  # apt install net-tools dnsmasq -y
  # systemctl enable dnsmasq
  
  Get the container's ip on lxd's network, in this case ifconfig is used,
  showing 10.62.42.157:
  
  # ifconfig
  eth0: flags=4163  mtu 1500
- inet 10.62.42.157  netmask 255.255.255.0  broadcast 10.62.42.255
- ...
+ inet 10.62.42.157  netmask 255.255.255.0  broadcast 10.62.42.255
+ ...
  
  Now set up the test container:
  
  # lxc launch images:ubuntu/jammy test-dnsmasq
  # lxc exec test-dnsmasq bash
  
  # apt update && apt dist-upgrade -y
  # systemctl disable systemd-resolved
  # systemctl stop systemd-resolved
  # unlink /etc/resolv.conf
  
  Use other container's ip here
  
  # echo "nameserver 10.62.42.157
  nameserver 127.0.0.1" | tee /etc/resolv.conf
  
  # apt install dnsmasq -y
  # systemctl enable dnsmasq
  
  Setup bind9 to delay ping resolution failure when testing
  
  # apt install bind9 -y
  
  # cat  swap containers
  
  # echo nameserver 8.8.8.8 | tee /etc/resolv.conf; systemctl restart
  dnsmasq
  
  Ping will continue to not pick up the domain and fails with:
  
  ping: ubuntu.com: Temporary failure in name resolution
  
  With the fix, ping should now pick up the new successful responses:
  
  PING ubuntu.com (185.125.190.29) 56(84) bytes of data.
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=1 ttl=48 time=165 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=2 ttl=48 time=162 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=3 ttl=48 time=166 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=4 ttl=48 time=164 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=5 ttl=48 time=163 ms
  64 bytes from website-content-cache-3.ps5.canonical.com (185.125.190.29): 
icmp_seq=6 ttl=48 time=163 ms
  ^C
  --- ubuntu.com ping statistics ---
  6 packets transmitted, 6 received, 0% packet loss, time 5005ms
  
+ Note: ping is used here instead of another dns tester such as dig
+ because it continues its dns resolution attempts with retry packets even
+ after receiving a REFUSED error. Other programs fail immediately on
+ REFUSED and are unable to send duplicate packets to reproduce the issue.
  
  [Where problems could occur]
  
  This change was added upstream in version 2.87, which means it has not
  been tested in many situations alongside 2.86. Allowing the retries
  could lead to a flood of requests to remote DNS servers if the replies
  are unable to make it back through dnsmasq to the user.
  
  [Other Info]
  
  This bug was fixed in Kinetic in version 2.86-1.1ubuntu2.
  
  [Original Description]
  
  Duplicate or retried DNS queries will return REFUSED for one of the
  queries causing intermittent failures in clients.
  
  This probably breaks lots of things, but for me is causing 22.04's
  internet

[Touch-packages] [Bug 2000551] Re: [System Fonts] Replace default sinhala font from LKLUG to Noto

Thank you for working on this!

What's the plan for Kinetic? Please see:
https://wiki.ubuntu.com/StableReleaseUpdates#Newer_Releases

If the goal is to make Sinhala text more readable on Ubuntu, please
could you make that an additional part of the Test Plan, instead of only
checking the order of output in a font listing? I appreciate that would
be subjective, but I think that with the screenshots given, asking
someone who can read Sinhala to just verify it's a substantial
improvement and matches expectations would be much better than not doing
that at all. In working to fix this we should ensure that we've actually
achieved the intended goal, rather than an intermediary technical step.

> Where problems could occur

It sounds like font metrics are changing, so text might wrap
differently, resulting in it no longer fitting, or change the size of
windows, etc, in various user interface elements. It sounds like it's
worth the change, but please look out for this during testing.

** Changed in: language-selector (Ubuntu Jammy)
   Status: In Progress => Incomplete

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

Title:
  [System Fonts] Replace default sinhala font from LKLUG to Noto

Status in language-selector package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Won't Fix
Status in language-selector source package in Jammy:
  Incomplete

Bug description:
  [ Impact ]

  The current default font for Sinhala (LKLUG) is unmaintained and comes
  with issues. Noto offers Sinhala fonts with significantly higher
  quality.

  fonts-lklug-sinhala is pulled by quite a few meta packages. Instead of
  changing that, the proposed change makes fontconfig give Noto Sans
  Sinhala respective Noto Serif Sinhala higher precedence than LKLUG,
  and that — together with installation of fonts-noto-core — seems to be
  sufficient to achieve the desired result.

  [ Test Plan ]

  * Install language-selector-[common,gnome] from jammy-proposed.

  * Open Language Support and install the Sinhala language.

  * Open a terminal window and run this command:

fc-match -a | grep -E 'LKLUG|Sinhala'

  * Confirm that Noto Sans Sinhala is listed before LKLUG.

  [ Where problems could occur ]

  No real problem in sight. Some Sinhala speaking users with fonts-noto-
  core installed will indeed see a surprise change when it starts to
  render Sinhala via Noto fonts instead of LKLUG. But that surprise
  ought to make them happy. :)

  [ Original description ]

  **What's the problem?**

  Currently ubuntu comes with LKLUG font for sinhala (si). it's not
  clear. e.g. we cannot recognize vowel signs and read websites using
  that font. We can change it manually but such changes do not apply to
  some applications or application types e.g. snap apps etc.

  LKLUG (last active: 2012) no one maintain it now.
  https://web.archive.org/web/202200*/http://www.lug.lk/
  http://www.lug.lk/fonts/lklug

  **What expected to happen?**

  We would like to see Noto serif sinhala as the default font for sinhala 
language
  https://fonts.google.com/noto/specimen/Noto+Serif+Sinhala
  [Highlighs: clear (readable), thin, takes less space than sans sinhala]

  If noto sans is more suitable for ubuntuOS, you can add noto sans sinhala 
https://fonts.google.com/noto/specimen/Noto+Sans+Sinhala
  [Highlighs: clear (readable), thick, takes more space than serif sinhala]

  **Additional details**

  Screenshots (see the difference: LKLUG/Noto)

  LKLUG
  https://i.ibb.co/nbHM5Mw/lklug.jpg

  Noto Sinhala
  https://i.ibb.co/k9dbtYb/noto.jpg

  If you need more examples or clarifications, please add a comment

  Random posts
  1. https://groups.google.com/g/Sinhala-Unicode/c/LYxuJ44dY3g
  2. https://twitter.com/thilinag/status/1598707165920825344#m (LKLUG bug with 
some apps)
  3. 
https://www.reddit.com/r/srilanka/comments/nzpl9p/change_sinhala_font_in_ubuntu/

  Also, some developers already have designed tools, scripts for that problem 
however many people do not try to find these scripts and switch to other OS
  1. https://github.com/IMS94/UbuntuSinhalaFont (developer: PMC chair @apache)
  2. https://gist.github.com/thilinag/66577033fafd00c3dfdaa898c2478c79
  3. https://github.com/hankyoTutorials/linux-system-sinhala-font-changer

  Please review details, screenshots and posts. This is not a personal
  opinion and atleast, i expect to see this change in the next interim
  or LTS release.

  Furthermore, please let me know if i can help to speed-up this
  replacement process

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


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

[Touch-packages] [Bug 1995247] Re: Leftover /tmp/apt-key.* files after updates with embedded gpg keys in deb822 sources

Hello Julian, or anyone else affected,

Accepted apt into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.4.9 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  Leftover /tmp/apt-key.* files after updates with embedded gpg keys in
  deb822 sources

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Jammy:
  Fix Committed
Status in apt source package in Kinetic:
  Fix Committed
Status in apt source package in Lunar:
  Fix Released

Bug description:
  [Impact]
  When keys are embedded into deb822 sources files as Signed-By, apt writes 
them to a temporary file, but the code to delete them accidentally had an if 
(0) in front of the deletion, so they don't get deleted and accumulate with 
each `apt update` run.

  [Test plan]
  Including a test case for this in our comprehensive integration test suite 
which runs as autopkgtest, so passing autopkgtest = good.

  [Where problems could occur]
  Files could end up being removed too soon if the code is otherwise wrong?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1995247/+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 1973788] Re: Merge findutils 4.9.0-3 from Debian

2023-01-04 Thread Julian Andres Klode

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

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

Title:
  Merge findutils 4.9.0-3 from Debian

Status in findutils package in Ubuntu:
  Fix Released

Bug description:
  Package the Debian upstream plus Ubuntu specific changes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1973788/+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 1988730] Re: package libsasl2-modules provides only unsafe SASL bind mechanims

2023-01-04 Thread Andreas Hasenack

** Description changed:

  [ Impact ]
  
  The SASL SCRAM mechanism is incorrectly part of the libsasl2-modules-
  gssapi-mit package. It has nothing to do with MIT or GSSAPI, and should
  be in libsasl2-modules.
  
  Normally this would just be an annoyance, but it just so happens that
  this also prevents to have the SCRAM mechanism coexist with the GSSAPI
  Heimdal one, because libsasl2-modules-gssapi-{mit,heimdal} conflict with
  each other.
  
  This change is moving a file from one package to another, so appropriate
  breaks/replaces changes have to be made. This move follows case #10 from
  the package transition table[1].
  
  [ Test Plan ]
  
  This test plan revolves around dependency checking and upgrades, to make sure 
we don't:
  - have conflicting files which would break an upgrade
  - have no loss of functionality after an upgrade (since a plugin moved 
between packages)
  
  a) SCRAM remains installed
  # Install the package that provides SCRAM in jammy
  
  $ sudo apt install libsasl2-modules-gssapi-mit
  
  # Confirm mechanism is there and belongs to libsasl2-modules-gssapi-mit:
  
  $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  lrwxrwxrwx 1 root root 18 Aug 16 20:08 
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
  
  $ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  libsasl2-modules-gssapi-mit:amd64: 
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  
  # list installed sasl2 packages:
  $ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
- libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1
- libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1
- libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1
- libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1
- 
- # dist-upgrade or install the new sasl2 packages from proposed
- # Confirm the same packages are installed as before the upgrade, just at 
their newer versions:
  libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
  libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
  libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
  libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.1
+ 
+ # dist-upgrade or install the new sasl2 packages from proposed
+ # Confirm the same packages are installed as before the upgrade, just at 
their newer versions:
+ libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
+ libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
+ libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2
+ libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.2
  
  # Confirm the scram mechanism is still there, as before:
  
  $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  lrwxrwxrwx 1 root root 18 Aug 16 20:08 
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
  
  # But now it belongs to the libsasl2-modules package:
  $ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  
  b) Following (a), perform a release-upgrade to kinetic, and confirm that
  the same sasl2 packages remain installed, but now at the kinetic
  version:
  
  $ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
  libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2
  libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2
  libsasl2-modules-db:amd64 2.1.28+dfsg-6ubuntu2
  libsasl2-modules-gssapi-mit:amd64 2.1.28+dfsg-6ubuntu2
  
  And that the scram mechanism is there, and still belongs to the
  libsasl2-modules package:
  
  $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  lrwxrwxrwx 1 root root 18 Aug 16 20:08 
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25
  
  $ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  
  c) A jammy system WITHOUT the SCRAM mechanism available (i.e.,
  libsasl2-modules-gssapi-mit is NOT installed), will get SCRAM available
  after the upgrade, but without installing any new package.
  
  # Start with these sasl2 packages installed on jammy:
  
- libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1
- libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1
- libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1
- 
- # Confirm SCRAM is not installed:
- $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
- ls: cannot access '/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2': No such 
file or directory
- 
- # Upgrade to the packages in proposed
- # Confirm no new sasl2 packages were installed:
- 
- $ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
  libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
  libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
  libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
  
+ # Confirm SCRAM is not installed:
+ $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
+ ls: cannot access '/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2': No such 
file or directory
+ 
+ # Upgrade to the packages in proposed
+ # Confirm no new sasl2 packages were installed:
+ 
+ $ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
+ libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
+ libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2

[Touch-packages] [Bug 1398805] Re: redshift fails to start geoclue provider after resuming network connection / hangs for 25s

2023-01-04 Thread Bryce Harrington

This link suggests redshift may now require installing geoclue-2:
https://askubuntu.com/questions/752406/is-it-possible-to-workaround-the-redshift-geoclue-bug?rq=1

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

Title:
  redshift fails to start geoclue provider after resuming network
  connection / hangs for 25s

Status in geoclue package in Ubuntu:
  Confirmed
Status in redshift package in Ubuntu:
  Confirmed

Bug description:
  `redshift -l geoclue -p` hangs after resuming network operation.

  This happens after resuming from hibernation, but can be reproduced by
  disabling and re-enabling the network via network-manager.

  strace shows:

  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\1\1\1\214\0\0\0\2\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0\6\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\2\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\3\1s\0\10\0\0\0AddMatch\0\0\0\0\0\0\0\0\10\1g\0\1s\0\0",
 144}, 
{"\207\0\0\0type='signal',sender='org.freedesktop.Geoclue.Master',path='/org/freedesktop/Geoclue/Master',interface='org.freedesktop.Geoclue.Master'\0",
 140}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 284
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\1\1\1\256\0\0\0\3\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0\6\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\2\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\3\1s\0\10\0\0\0AddMatch\0\0\0\0\0\0\0\0\10\1g\0\1s\0\0",
 144}, 
{"\251\0\0\0type='signal',sender='org.freedesktop.DBus',path='/org/freedesktop/DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0='org.freedesktop.Geoclue.Master'\0",
 174}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 318
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\1\0\1#\0\0\0\4\0\0\0\177\0\0\0\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0\6\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\2\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\3\1s\0\f\0\0\0GetNameOwner\0\0\0\0\10\1g\0\1s\0\0",
 144}, {"\36\0\0\0org.freedesktop.Geoclue.Master\0", 35}], msg_controllen=0, 
msg_flags=0}, MSG_NOSIGNAL) = 179
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(2)=[{"l\1\0\1\0\0\0\0\5\0\0\0\207\0\0\0\1\1o\0\37\0\0\0/org/freedesktop/Geoclue/Master\0\6\1s\0\36\0\0\0org.freedesktop.Geoclue.Master\0\0\2\1s\0\36\0\0\0org.freedesktop.Geoclue.Master\0\0\3\1s\0\6\0\0\0Create\0\0",
 152}, {"", 0}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 152
  poll([{fd=3, events=POLLIN}], 1, 25000) = 1 ([{fd=3, revents=POLLIN}])
  recvmsg(3, {msg_name(0)=NULL, 
msg_iov(1)=[{"l\2\1\1\n\0\0\0\3\0\0\0=\0\0\0\6\1s\0\6\0\0\0:1.411\0\0\5\1u\0\4\0\0\0\10\1g\0\1s\0\0\7\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\5\0\0\0:1.43\0",
 2048}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 90
  write(4, "\1\0\0\0\0\0\0\0", 8) = 8
  recvmsg(3, 0x7fffcd24f170, MSG_CMSG_CLOEXEC) = -1 EAGAIN (Resource 
temporarily unavailable)
  poll([{fd=3, events=POLLIN}], 1, 25000

  # Here it hangs

  ) = 0 (Timeout)
  open("/usr/lib/x86_64-linux-gnu/charset.alias", O_RDONLY) = -1 ENOENT (No 
such file or directory)
  fstat(2, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 56), ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f3d2998c000
  write(2, "Unable to obtain master client: Did not receive a reply. 
Possible causes include: the remote application did not send a reply, the 
message bus security policy blocked the reply, the reply timeout expired, or 
the network connection was broken.\n", 243Unable to obtain master client: Did 
not receive a reply. Possible causes include: the remote application did not 
send a reply, the message bus security policy blocked the reply, the reply 
timeout expired, or the network connection was broken.
  ) = 243
  open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 5
  fstat(5, {st_mode=S_IFREG|0644, st_size=2570, ...}) = 0
  mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f3d2998b000
  read(5, "# Locale name alias data base.\n# Copyright (C) 
1996-2001,2003,2007 Free Software Foundation, Inc.\n#\n# This program is free 
software; you can redistribute it and/or modify\n# it under the terms of the 
GNU General Public License as published by\n# the Free Software Foundation; 
either version 2, or (at your option)\n# any later version.\n#\n# This program 
is distributed in the hope that it will be useful,\n# but WITHOUT ANY WARRANTY; 
without even the implied warranty of\n# MERCHANTABILITY or FITNESS FOR A 
PARTICULAR PURPOSE.  See the\n# GNU General Public License for more 
details.\n#\n# You should have received a copy of the GNU General Public 
License\n# along with this program; if not, write to the Free Software\n# 
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.\n\n# 
The format of this

[Touch-packages] [Bug 1912256] Update Released

The verification of the Stable Release Update for cyrus-sasl2 has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Missing channel binding prevents authentication to ActiveDirectory

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Jammy:
  Fix Released
Status in openldap source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  When attempting to authenticate against a Windows Active Directory
  server configured to require SASL channel binding over SSL/TLS ldap
  connections (ldaps), authentication will fail stating invalid
  credentials as the cause.

  This is due to cyrus-sasl2 missing the sasl channel binding feature of
  GSSAPI/GSS-SPNEGO.

  Furthermore, for interoperability with Windows Active Directory
  Server, it's necessary to be able to set the SASL SSF (security
  strength factor) to 0 (zero) when it's used over an already encrypted
  connection like ldaps.

  To fix these issues, these items are added as patches from a set of
  upstream commits.

  [Test Plan]

  To reproduce this issue, a machine running Windows with Active
  Directory must be available over the network. As an example, for
  Windows Server 2019 Evaluation:

  The ISO can be downloaded from 
https://www.microsoft.com/en-us/evalcenter/download-windows-server-2019
  Install Windows Server, Active Directory, and Certificate Services, then add 
the following registry changes from 
https://support.microsoft.com/en-us/topic/2020-ldap-channel-binding-and-ldap-signing-requirements-for-windows-kb4520412-ef185fb8-00f7-167d-744c-f299a66fc00a

  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters]
  "ldapserverintegrity"=dword:0002
  "LdapEnforceChannelBinding"=dword:0002

  Also enable LDAP logging for Active Directory:

  Reg Add
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics
  /v "16 LDAP Interface Events" /t REG_DWORD /d 2

  With the Windows machine available, set up an Ubuntu system on a
  network that can reach the Windows server. This works best and with
  less configuration needed if the Windows server is acting as DNS and
  DHCP server for that network.

  Install packages with:
  $ sudo apt install ldap-utils libsasl2-modules-gssapi-mit krb5-user
  When the Configuring Kerberos Authentication prompt shows up, use the realm 
of the Windows Server. If prompted, use the windows server IP for the Kerberos 
KDC and admin servers.

  Save the Windows Server AD CA certificate file as 
/usr/local/share/ca-certificates/ad-ca.crt then run
  $ sudo update-ca-certificates

  In /etc/ldap/ldap.conf set
  BASE dc={REALM NAME} # split the domain components like dc=example,dc=com
  URI ldaps://{WINDOWS SERVER MACHINE NAME}.{REALM NAME}

  With Ubuntu set up, the actual test can be run:

  $ kinit
  Enter Password
  $ ldapwhoami -Y GSSAPI -O maxssf=0 -o SASL_CBINDING=tls-endpoint

  Prior to the fix, this would display the following:

  SASL/GSSAPI authentication started
  ldap_sasl_interactive_bind_s: Invalid credentials (49)
  additional info: 80090346: LdapErr: DSID-..., comment: 
AcceptSecurityContext error, data 80090346, v4563

  With the fix, the authentication will display the user information.

  The same happens with
  $ ldapwhoami -Y GSS-SPNEGO -O maxssf=0 -o SASL_CBINDING=tls-endpoint

  SASL/GSS-SPNEGO authentication started
  ldap_sasl_interactive_bind_s: Invalid credentials (49)
  additional info: 80090346: LdapErr: DSID-..., comment: 
AcceptSecurityContext error, data 80090346, v4563

  [Where problems could occur]

  Based on the patches added, any problems that show up would likely
  occour either in the gssapi plugin or the SASL2 macros. The two files
  changed  are plugins/gssapi.c and m4/sasl2.m4, along with some tests.

  There are various situations apart from this one in which GSS-API can
  be used, and this change may affect the way some of these interactions
  over the network are handled.

  In parallel with this SRU, we tested, in jammy, cyrus-imapd server and
  gssapi authentication over tls, with and without this updated sasl
  package. Using as a client thunderbird, imtest (from cyrus-imapd-
  clients), curl (it has imap support), mutt, evolution. All
  authenticated without issues. Also postfix with gssapi authentication
  was tested, and also worked.

  [Other Info]

  This issue was fixed in

[Touch-packages] [Bug 1677781] Re: Missing dep8 tests

This bug was fixed in the package cyrus-sasl2 - 2.1.27+dfsg2-3ubuntu1.1

---
cyrus-sasl2 (2.1.27+dfsg2-3ubuntu1.1) jammy; urgency=medium

  * Add SASL channel binding support for GSSAPI and GSS-SPNEGO
(LP: #1912256):
- d/p/0034-channel-binding-gssapi-gss-spnego.patch: add SASL channel
  binding support for GSSAPI and GSS-SPNEGO
- d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-1.patch:
  allow setting maxssf to 0 when using GSS-SPNEGO inside SSL/TLS
- d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-2.patch:
  be more conformant to RFC4752
  * Add some DEP8 tests (LP: #1677781):
- d/t/{control,saslauthd}: saslauthd tests with multiple mechanisms
- d/t/{control,gssapi}: test for SASL GSSAPI using OpenLDAP
- d/t/{control,pluginviewer}: test available mechanisms
- d/t/{control,shared-secret-mechs}: test shared secret mechanisms

 -- Lena Voytek   Wed, 19 Oct 2022 14:06:40
-0700

** Changed in: cyrus-sasl2 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Missing dep8 tests

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Jammy:
  Fix Released

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source cyrus-sasl2 zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/cyrus-sasl2
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3XaTAAoJEIP8BxPaZgwlJr8P/j8yn8mXWnAIiXUgHX7jBIGj
  JuMQGO5wwcfHRxOwJEOlsO/SIATUN1L1BB84anP7Bp4cfLqXonF8eKFPkEotwaf1
  3wADCH98EwLuSyJOaKXsTQHppAKdJ6UEW4jHvfhYizenEWssPfCQdg68LSGZ2enR
  wD9ZhZgjwJIpLbqDTp7ygklR0htf4ZAFq/vIcyLykT6qagVE3xC8SAgd+7tb/fYe
  4PYfqgGso/qpL0v6JL+YkCKH/aiMYV+HD45o1NcUbGdoiuUa9jpeYSSTP/9OgWpY
  nALDXe/dJZT/wz5Zv0cy6sGRh7gtjVqI0608WAM00Jp8CmFX60z4yrq/3t37wKbz
  iDQF4HyltqfCNF5oQ6xva9xAq/c2tyP8nBHzQ+ZtH/o1hyS/JdgoR38OojldyUc5
  WzcTFL+h612ZVZVNm4lqBpg/0dpEkwXTE9KczyB5kSr5VVz0WXtjU5wFxKMdZpr5
  Gq9uM+fHU4YHQqfGGZxmHFOgz7tCAyEsZEzpnPiYvoSksj3tJMkQG7FbIISltort
  CBAwLIt1hLR9g4T3p0e4ipCJf6kL/yZR3kMGhsjbDe012bTaC8ZeLG7VYmWkBaxY
  ieFMZIxmGgCq7KjDfNPh9JEmCtNgenkEOu6BszZK+gwmhL/AxVuuNRdd5OeBGy3G
  WY9JzBOc6MUi46Hh9ZN5
  =szTz
  -END PGP SIGNATURE-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1677781/+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 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory

This bug was fixed in the package cyrus-sasl2 - 2.1.27+dfsg2-3ubuntu1.1

---
cyrus-sasl2 (2.1.27+dfsg2-3ubuntu1.1) jammy; urgency=medium

  * Add SASL channel binding support for GSSAPI and GSS-SPNEGO
(LP: #1912256):
- d/p/0034-channel-binding-gssapi-gss-spnego.patch: add SASL channel
  binding support for GSSAPI and GSS-SPNEGO
- d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-1.patch:
  allow setting maxssf to 0 when using GSS-SPNEGO inside SSL/TLS
- d/p/0035-Add-support-for-setting-max-ssf-0-to-GSS-SPNEGO-2.patch:
  be more conformant to RFC4752
  * Add some DEP8 tests (LP: #1677781):
- d/t/{control,saslauthd}: saslauthd tests with multiple mechanisms
- d/t/{control,gssapi}: test for SASL GSSAPI using OpenLDAP
- d/t/{control,pluginviewer}: test available mechanisms
- d/t/{control,shared-secret-mechs}: test shared secret mechanisms

 -- Lena Voytek   Wed, 19 Oct 2022 14:06:40
-0700

** Changed in: cyrus-sasl2 (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Missing channel binding prevents authentication to ActiveDirectory

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Jammy:
  Fix Released
Status in openldap source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  When attempting to authenticate against a Windows Active Directory
  server configured to require SASL channel binding over SSL/TLS ldap
  connections (ldaps), authentication will fail stating invalid
  credentials as the cause.

  This is due to cyrus-sasl2 missing the sasl channel binding feature of
  GSSAPI/GSS-SPNEGO.

  Furthermore, for interoperability with Windows Active Directory
  Server, it's necessary to be able to set the SASL SSF (security
  strength factor) to 0 (zero) when it's used over an already encrypted
  connection like ldaps.

  To fix these issues, these items are added as patches from a set of
  upstream commits.

  [Test Plan]

  To reproduce this issue, a machine running Windows with Active
  Directory must be available over the network. As an example, for
  Windows Server 2019 Evaluation:

  The ISO can be downloaded from 
https://www.microsoft.com/en-us/evalcenter/download-windows-server-2019
  Install Windows Server, Active Directory, and Certificate Services, then add 
the following registry changes from 
https://support.microsoft.com/en-us/topic/2020-ldap-channel-binding-and-ldap-signing-requirements-for-windows-kb4520412-ef185fb8-00f7-167d-744c-f299a66fc00a

  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters]
  "ldapserverintegrity"=dword:0002
  "LdapEnforceChannelBinding"=dword:0002

  Also enable LDAP logging for Active Directory:

  Reg Add
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics
  /v "16 LDAP Interface Events" /t REG_DWORD /d 2

  With the Windows machine available, set up an Ubuntu system on a
  network that can reach the Windows server. This works best and with
  less configuration needed if the Windows server is acting as DNS and
  DHCP server for that network.

  Install packages with:
  $ sudo apt install ldap-utils libsasl2-modules-gssapi-mit krb5-user
  When the Configuring Kerberos Authentication prompt shows up, use the realm 
of the Windows Server. If prompted, use the windows server IP for the Kerberos 
KDC and admin servers.

  Save the Windows Server AD CA certificate file as 
/usr/local/share/ca-certificates/ad-ca.crt then run
  $ sudo update-ca-certificates

  In /etc/ldap/ldap.conf set
  BASE dc={REALM NAME} # split the domain components like dc=example,dc=com
  URI ldaps://{WINDOWS SERVER MACHINE NAME}.{REALM NAME}

  With Ubuntu set up, the actual test can be run:

  $ kinit
  Enter Password
  $ ldapwhoami -Y GSSAPI -O maxssf=0 -o SASL_CBINDING=tls-endpoint

  Prior to the fix, this would display the following:

  SASL/GSSAPI authentication started
  ldap_sasl_interactive_bind_s: Invalid credentials (49)
  additional info: 80090346: LdapErr: DSID-..., comment: 
AcceptSecurityContext error, data 80090346, v4563

  With the fix, the authentication will display the user information.

  The same happens with
  $ ldapwhoami -Y GSS-SPNEGO -O maxssf=0 -o SASL_CBINDING=tls-endpoint

  SASL/GSS-SPNEGO authentication started
  ldap_sasl_interactive_bind_s: Invalid credentials (49)
  additional info: 80090346: LdapErr: DSID-..., comment: 
AcceptSecurityContext error, data 80090346, v4563

  [Where problems could occur]

  Based on the patches added, any problems that show up would likely
  occour either in the gssapi plugin or the SASL2 macros. The two files
  changed  are plugins/gssapi.c and m4/sasl2.m4, along with some tests.

  There are

[Touch-packages] [Bug 1677781] Update Released

The verification of the Stable Release Update for cyrus-sasl2 has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Missing dep8 tests

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Jammy:
  Fix Released

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

  As of March 29, 2017, this source package did not contain dep8 tests in
  the current development release of Ubuntu, named Zesty. This was
  determined by running `pull-lp-source cyrus-sasl2 zesty` and then
  checking for the existence of 'debian/tests/' and
  'debian/tests/control'.

  Test automation is essential to higher levels of quality and confidence
  in updates to packages. dep8 tests [1] specify how automatic testing can
  be integrated into packages and then run by package maintainers before
  new uploads.

  This defect is to report the absence of these tests and to report the
  opportunity as a potential item for development by both new and
  experienced contributors.

  [1] http://packaging.ubuntu.com/html/auto-pkg-test.html

   affects ubuntu/cyrus-sasl2
   status new
   importance wishlist
   tag needs-dep8

  - ---
  Joshua Powers
  Ubuntu Server
  Canonical Ltd

  -BEGIN PGP SIGNATURE-

  iQIcBAEBCAAGBQJY3XaTAAoJEIP8BxPaZgwlJr8P/j8yn8mXWnAIiXUgHX7jBIGj
  JuMQGO5wwcfHRxOwJEOlsO/SIATUN1L1BB84anP7Bp4cfLqXonF8eKFPkEotwaf1
  3wADCH98EwLuSyJOaKXsTQHppAKdJ6UEW4jHvfhYizenEWssPfCQdg68LSGZ2enR
  wD9ZhZgjwJIpLbqDTp7ygklR0htf4ZAFq/vIcyLykT6qagVE3xC8SAgd+7tb/fYe
  4PYfqgGso/qpL0v6JL+YkCKH/aiMYV+HD45o1NcUbGdoiuUa9jpeYSSTP/9OgWpY
  nALDXe/dJZT/wz5Zv0cy6sGRh7gtjVqI0608WAM00Jp8CmFX60z4yrq/3t37wKbz
  iDQF4HyltqfCNF5oQ6xva9xAq/c2tyP8nBHzQ+ZtH/o1hyS/JdgoR38OojldyUc5
  WzcTFL+h612ZVZVNm4lqBpg/0dpEkwXTE9KczyB5kSr5VVz0WXtjU5wFxKMdZpr5
  Gq9uM+fHU4YHQqfGGZxmHFOgz7tCAyEsZEzpnPiYvoSksj3tJMkQG7FbIISltort
  CBAwLIt1hLR9g4T3p0e4ipCJf6kL/yZR3kMGhsjbDe012bTaC8ZeLG7VYmWkBaxY
  ieFMZIxmGgCq7KjDfNPh9JEmCtNgenkEOu6BszZK+gwmhL/AxVuuNRdd5OeBGy3G
  WY9JzBOc6MUi46Hh9ZN5
  =szTz
  -END PGP SIGNATURE-

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1677781/+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 2000817] Re: Wrong SHA256-value computed on kinetic

** Tags removed: server-next
** Tags added: server-todo

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

Title:
  Wrong SHA256-value computed on kinetic

Status in openldap package in Ubuntu:
  Triaged

Bug description:
  The OpenLDAP-contrib module sha2 (located in contrib/slapd-
  modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
  kinetic. This breaks our current password-authentication in ldap.

  
  The problematic computation:

  $ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
  {SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=

  The (correct) reference-value on the same system (or older ubuntu
  Versions):

  $ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
  K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=

  
  We nailed the problem down to a bug in the gcc-optimizer for strict-aliasing. 
so most probably the gcc-version on kinetic (v12.2.0) is the reason. The 
workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing". 
Then the correct value is computed. An example taken from a git-compiled 
version of OpenLDAP 2.5.13:

  $ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o 
module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs
  {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=


  
  Ubuntu:

  Description:Ubuntu 22.10
  Release:22.10

  OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2000817/+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 2000868] Re: backport required for virtio_gpu_dri.so

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  backport required for virtio_gpu_dri.so

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  xorg crashing when using modsetting with virtio_gpu_dri as graphics
  driver in kvm guest. Kindly look into this conversation

  https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920

  I think we need to backport
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix
  this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2000868/+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 2000868] Re: backport required for virtio_gpu_dri.so

2023-01-04 Thread mohan43u

how can I get 22.2.5 in jammy? will it be pushed to jammy-updates or
jammy-backports?

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

Title:
  backport required for virtio_gpu_dri.so

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi,

  xorg crashing when using modsetting with virtio_gpu_dri as graphics
  driver in kvm guest. Kindly look into this conversation

  https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920

  I think we need to backport
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix
  this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2000868/+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 2000628] Re: The wifi password prompt disappear immediately after showing up on 22.04

2023-01-04 Thread Sharcoux

For information, I got this bug from a fresh install of 22.04. Also,
after a reboot, the prompt works as expected for a while, but I always
end up with the bug after a while.

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

Title:
  The wifi password prompt disappear immediately after showing up on
  22.04

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Some other people reported this bug
  [here](https://askubuntu.com/questions/1409433/22-04-cant-input-
  password-for-wifi)

  Basically, when you try to log into a network, there is no way to
  input your password. The only way to reach a visible network seems to
  be by one of the workarounds: use the "Connect to Hidden Network"
  option, or directly edit the network config files.

  It seems like a critical bug to me because it can demotivate new users
  of Ubuntu and Linux.

  I joined a screen record of the prompt blinking on screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2000628/+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 21741] Re: cdebconf: package is uninstallable

2023-01-04 Thread Bug Watch Updater

** Changed in: cdebconf (Debian)
   Status: New => Fix Released

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

Title:
  cdebconf: package is uninstallable

Status in cdebconf package in Ubuntu:
  Fix Released
Status in cdebconf package in Debian:
  Fix Released

Bug description:
  Automatically imported from Debian bug report #328498
  http://bugs.debian.org/328498

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cdebconf/+bug/21741/+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 2000628] Re: The wifi password prompt disappear immediately after showing up on 22.04

2023-01-04 Thread Alexander

Hi. I got the same problem when I tried to use the Wayland session. When I 
switched to Xorg - the problem has gone.
Besides, it's not a fresh install of Ubuntu. I firstly installed one of the 
previous editions of Kubuntu (KDE-based distro version), then upgraded to 
Kubuntu 22.04, and finally sometime later installed Gnome desktop and removed 
the KDE environment.

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

Title:
  The wifi password prompt disappear immediately after showing up on
  22.04

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Some other people reported this bug
  [here](https://askubuntu.com/questions/1409433/22-04-cant-input-
  password-for-wifi)

  Basically, when you try to log into a network, there is no way to
  input your password. The only way to reach a visible network seems to
  be by one of the workarounds: use the "Connect to Hidden Network"
  option, or directly edit the network config files.

  It seems like a critical bug to me because it can demotivate new users
  of Ubuntu and Linux.

  I joined a screen record of the prompt blinking on screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2000628/+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 2000628] Re: The wifi password prompt disappear immediately after showing up on 22.04

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  The wifi password prompt disappear immediately after showing up on
  22.04

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Some other people reported this bug
  [here](https://askubuntu.com/questions/1409433/22-04-cant-input-
  password-for-wifi)

  Basically, when you try to log into a network, there is no way to
  input your password. The only way to reach a visible network seems to
  be by one of the workarounds: use the "Connect to Hidden Network"
  option, or directly edit the network config files.

  It seems like a critical bug to me because it can demotivate new users
  of Ubuntu and Linux.

  I joined a screen record of the prompt blinking on screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2000628/+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 2000798] Re: cannot connect to K380 bluetooth keyboard

2023-01-04 Thread Tomislav

Thanks for responding, Daniel. If it was the driver, I don't know how
the keyboard would have worked until a week ago. If it was the hardware,
I imagine other BT devices wouldn't connect either, but they do (mouse,
earbuds). I might be wrong, of course.

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

Title:
  cannot connect to K380 bluetooth keyboard

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Had trouble connecting my K380 keyboard with the laptop (previously
  used it without issues), unpaired and now I can no longer pair it.

  Other bluetooth devices work with this particular laptop (mouse,
  earbuds), the keyboard works flawlessly with a different laptop
  (running the same Ubuntu 20.04 OS) and an Android phone.

  Used bluetoothctl to peek under the hood and got nowhere after turning scan 
on on the controller and activating the keyboard:
  [NEW] Device [...mac address of the keyboard...] Keyboard K380
  [CHG] Device [...mac address of the keyboard...] Connected: no
  [DEL] Device [...mac address of the keyboard...] Keyboard K380

  After this action, I get:

  # connect [...mac address of the keyboard...]
  Device [...mac address of the keyboard...] not available

  When I activate the keyboard (by pressing any key on it while it's
  turned on), in the bluetooth settings GUI tool I see the keyboard
  appear for a fraction of a second in the list of unpaired devices and
  then it disappears.

  Help?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 30 19:41:41 2022
  InstallationDate: Installed on 2022-11-03 (57 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems LAPKC71E
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCTGL357.0037.2021.0712.0948
  dmi.board.name: LAPKC71E
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M1-402
  dmi.chassis.type: 10
  dmi.chassis.vendor: Intel(R) Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000:
  dmi.product.family: KC
  dmi.product.name: LAPKC71E
  dmi.product.sku: BKC71EBFB6000
  dmi.product.version: M38559-402
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 20:1E:88:3C:4C:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:221779 acl:5063 sco:0 events:6018 errors:0
TX bytes:785416 acl:104 sco:0 commands:4168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 2000800] Re: Bluetooth is not being activated, I have updated with sudo apt-get update and installed the program and restarted and it does not turn on

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

Re comment #2, yes I can see the nouveau kernel driver is crashing a
lot. Please use the Additional Drivers app to replace it with the proper
Nvidia driver. But that's not what this bug is about...


** Summary changed:

- Bluetooth is not being activated, I have updated with sudo apt-get update and 
installed the program and restarted and it does not turn on
+ [mt7921e] Bluetooth is not being activated, I have updated with sudo apt-get 
update and installed the program and restarted and it does not turn on

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

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

Title:
  [mt7921e] Bluetooth is not being activated, I have updated with sudo
  apt-get update and installed the program and restarted and it does not
  turn on

Status in linux package in Ubuntu:
  New

Bug description:
  Bluetooth is not being activated, I have updated with sudo apt-get
  update and installed the program and restarted and it does not turn on

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 30 22:34:07 2022
  InstallationDate: Installed on 2022-12-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 82K2
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=UUID=94a2de4f-8565-4a45-8c72-872549f49fdb ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/23/2022
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H3CN32WW(V2.02)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Gaming 3 15ACH6
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrH3CN32WW(V2.02):bd02/23/2022:br1.32:efr1.32:svnLENOVO:pn82K2:pvrIdeaPadGaming315ACH6:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPadGaming315ACH6:skuLENOVO_MT_82K2_BU_idea_FM_IdeaPadGaming315ACH6:
  dmi.product.family: IdeaPad Gaming 3 15ACH6
  dmi.product.name: 82K2
  dmi.product.sku: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6
  dmi.product.version: IdeaPad Gaming 3 15ACH6
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:7 acl:0 sco:0 events:1 errors:0
TX bytes:61 acl:0 sco:0 commands:1 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2000800/+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 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q

I have promised to actually test this on some older hardware but I want
to get through the past month's bug mail first...

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1972977/+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 2000791] Re: When my laptop wakes up from sleep, it displays a message each time

** Package changed: xorg (Ubuntu) => linux (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/2000791

Title:
  When my laptop wakes up from sleep, it displays a message each time

Status in linux package in Ubuntu:
  New

Bug description:
  When my laptop wakes up from sleep, it displays a message each time:

  Message 0002007 (seq 11) timeout
  PM: dpm_run_callback(): pci_pm_resume+0x0/0x110 return -110
  chip reset

  Every time my laptop wakes up from sleep, there are more messages, and
  the messages are reset when it is rebooted.

  I have an acer laptop,i updated the bios to the latest version, it
  didn't work and i have the latest version of ubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-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  525.60.11  Wed Nov 23 
23:04:03 UTC 2022
   GCC version:
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog:

  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 30 18:47:00 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus: openrazer-driver/3.4.0, 5.19.0-26-generic, x86_64: installed
  GraphicsCard:
   Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] 
[1025:1524]
   Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) 
(prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524]
  InstallationDate: Installed on 2022-12-07 (23 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Acer Aspire A715-42G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic 
root=UUID=7683ad64-565f-4b56-9d11-27156bba9f9f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2022
  dmi.bios.release: 1.10
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Azalea_CAS
  dmi.board.vendor: LN
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.ec.firmware.release: 1.3
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd07/28/2022:br1.10:efr1.3:svnAcer:pnAspireA715-42G:pvrV1.10:rvnLN:rnAzalea_CAS:rvrV1.10:cvnAcer:ct10:cvrV1.10:sku:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-42G
  dmi.product.sku: 
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  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.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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/2000791/+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 2000798] Re: cannot connect to K380 bluetooth keyboard

If the same keyboard works on a different 20.04 machine then it's likely
to be a difference in kernel driver (or associated hardware).

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

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

Title:
  cannot connect to K380 bluetooth keyboard

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Had trouble connecting my K380 keyboard with the laptop (previously
  used it without issues), unpaired and now I can no longer pair it.

  Other bluetooth devices work with this particular laptop (mouse,
  earbuds), the keyboard works flawlessly with a different laptop
  (running the same Ubuntu 20.04 OS) and an Android phone.

  Used bluetoothctl to peek under the hood and got nowhere after turning scan 
on on the controller and activating the keyboard:
  [NEW] Device [...mac address of the keyboard...] Keyboard K380
  [CHG] Device [...mac address of the keyboard...] Connected: no
  [DEL] Device [...mac address of the keyboard...] Keyboard K380

  After this action, I get:

  # connect [...mac address of the keyboard...]
  Device [...mac address of the keyboard...] not available

  When I activate the keyboard (by pressing any key on it while it's
  turned on), in the bluetooth settings GUI tool I see the keyboard
  appear for a fraction of a second in the list of unpaired devices and
  then it disappears.

  Help?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3.6
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 30 19:41:41 2022
  InstallationDate: Installed on 2022-11-03 (57 days ago)
  InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Intel(R) Client Systems LAPKC71E
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2021
  dmi.bios.release: 5.19
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCTGL357.0037.2021.0712.0948
  dmi.board.name: LAPKC71E
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M1-402
  dmi.chassis.type: 10
  dmi.chassis.vendor: Intel(R) Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 1.5
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCTGL357.0037.2021.0712.0948:bd07/12/2021:br5.19:efr1.5:svnIntel(R)ClientSystems:pnLAPKC71E:pvrM38559-402:rvnIntelCorporation:rnLAPKC71E:rvrM1-402:cvnIntel(R)Corporation:ct10:cvr2.0:skuBKC71EBFB6000:
  dmi.product.family: KC
  dmi.product.name: LAPKC71E
  dmi.product.sku: BKC71EBFB6000
  dmi.product.version: M38559-402
  dmi.sys.vendor: Intel(R) Client Systems
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 20:1E:88:3C:4C:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:221779 acl:5063 sco:0 events:6018 errors:0
TX bytes:785416 acl:104 sco:0 commands:4168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000798/+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 2000784] Re: booting issue snd_hda_ intel codec dummy and intel issue

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

** Also affects: pulseaudio (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/2000784

Title:
  booting issue snd_hda_ intel codec dummy and intel issue

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  booting delay
  nvidia-smi shows no usage with some memory usage

  errors :
  snd_hda_intel :01:00.1: no codecs found!
  acpi MSFT0101:00: platform device creation failed: -16
  ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog 
(20210730/psobject-220)
  Failed to load module "module-alsa-card" (argument: "device_id="1" 
name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" 
namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no 
deferred_volume=yes use_ucm=yes avoid_resampling=no 
card_properties="module-udev-detect.discovered=1""): initialization failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-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  470.161.03  Wed Oct 19 
00:10:36 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Fri Dec 30 17:58:15 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  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:3828]
 Subsystem: Lenovo GK208BM [GeForce 920M] [17aa:3829]
  InstallationDate: Installed on 2021-06-05 (573 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e360 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 5986:0670 Acer, Inc Lenovo EasyCamera
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Q3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=dca8371c-92df-441a-ba2f-acbb9bb611d3 ro quiet splash loglevel=3 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2018
  dmi.bios.release: 1.39
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D3CN39WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 500S-14ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 500S-14ISK
  dmi.ec.firmware.release: 1.26
  dmi.modalias: 
dmi:bvnLENOVO:bvrD3CN39WW:bd06/26/2018:br1.39:efr1.26:svnLENOVO:pn80Q3:pvrLenovoideapad500S-14ISK:rvnLENOVO:rnLenovoideapad500S-14ISK:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad500S-14ISK:skuLENOVO_MT_80Q3_BU_idea_FM_Lenovoideapad500S-14ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80Q3
  dmi.product.sku: LENOVO_MT_80Q3_BU_idea_FM_Lenovo ideapad 500S-14ISK
  dmi.product.version: Lenovo ideapad 500S-14ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.112+git2208190500.46d1e9~oibaf~j
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.3~git2208220600.7b81db~oibaf~j
  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.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/2000784/+subscriptions


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

[Touch-packages] [Bug 1972977] Re: gnome-shell crashed (out of memory) with SIGSEGV in crocus_begin_query() from crocus_begin_query() from crocus_end_query() from crocus_end_query() from tc_call_end_q

2023-01-04 Thread Timo Aaltonen

or just skip this and accept the kinetic backport which has the fix via
upstream

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

Title:
  gnome-shell crashed (out of memory) with SIGSEGV in
  crocus_begin_query() from crocus_begin_query() from crocus_end_query()
  from crocus_end_query() from tc_call_end_query()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  Gnome-shell is crashing on older gen Intel hw due to a memory leak.

  [Fix]
  An upstream commit that fixes the memleak in the crocus driver (which is only 
used on Intel 4th gen chips and older)

  [Test case]
  Either test this on an old Intel or see if there's a dent in the reported 
crashes.

  [Where things could go wrong]
  Mainly if this would not fix the crashes.

  --
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
42.0-2ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/d8aa1211f7e8b219a4ee6dcae294ac16decd7fe3 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1972977/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

2023-01-04 Thread Aminda Suomalainen

** Also affects: snapd (Fedora)
   Importance: Undecided
   Status: New

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in X2Go:
  New
Status in Xpra Terminal Server:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New
Status in snapd package in Fedora:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+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 2000775] Re: [Regression] Xorg server crashes from version 2:21.1.3-2ubuntu2.4

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1999008, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


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

** Tags added: regression-update

** This bug has been marked a duplicate of bug 1999008
   Xorg crashed with SIGABRT in xf86ModeVRefresh() from 
drmmode_output_add_gtf_modes() from drmmode_output_get_modes() from 
xf86ProbeOutputModes() from xf86InitialConfiguration()

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

Title:
  [Regression] Xorg server crashes from version 2:21.1.3-2ubuntu2.4

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Xorg server crashes on Dell Vostro V3750 notebook (integrated Intel
  GPU + Nvidia GeForce GT 525M) after upgrading xserver-xorg-core to
  2:21.1.3-2ubuntu2.4.

  After some testing we determined that the crash is caused by a patch
  re-calculate-the-clock-and-refresh-rate.diff added in version
  2:21.1.3-2ubuntu2.4 (LP: #1996490).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Dec 30 11:42:42 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:04c6]
   NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GF108M [GeForce GT 525M] [1028:04c6]
  MachineType: Dell Inc. Dell System Vostro 3750
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=en_US:en
   LANG=en_US.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-56-generic 
root=/dev/mapper/mobvad2--vg-root ro splash quiet vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2012
  dmi.bios.release: 0.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0RY9C2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd09/26/2012:br0.1:svnDellInc.:pnDellSystemVostro3750:pvr:rvnDellInc.:rn0RY9C2:rvrA00:cvnDellInc.:ct8:cvr0.1:skuSystemSKUNumber:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System Vostro 3750
  dmi.product.sku: System SKUNumber
  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.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  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-2ubuntu1
  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-server/+bug/2000775/+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 1901115] Re: package bluez failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.

** Tags added: kinetic

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

Title:
  package bluez failed to install/upgrade: installed bluez package post-
  installation script subprocess returned error exit status 1 [Failed to
  start Bluetooth service.]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct 23 07:08:46 2020
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3180
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10
  SourcePackage: bluez
  Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago)
  dmi.bios.date: 10/03/2019
  dmi.bios.release: 1.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 05YMV0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3180
  dmi.product.sku: 07B2
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 74:70:FD:58:F6:73  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:2712 acl:0 sco:0 events:305 errors:0
TX bytes:50942 acl:0 sco:0 commands:305 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901115/+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 2000714] Re: package bluez 5.65-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1901115, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1901115
   package bluez failed to install/upgrade: installed bluez package 
post-installation script subprocess returned error exit status 1 [Failed to 
start Bluetooth service.]

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

Title:
  package bluez 5.65-0ubuntu1 failed to install/upgrade: installed bluez
  package post-installation script subprocess returned error exit status
  1

Status in bluez package in Ubuntu:
  New

Bug description:
  Failed to start bluetooth generally
  It also failed to upgrade because bluetooth timedout

  Also, loading Settings menu taking around 1-2mn to load up

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: bluez 5.65-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Dec 29 11:20:21 2022
  ErrorMessage: installed bluez package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2021-11-07 (417 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude 7520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=9b404c17-8df7-4455-9565-d88ae66441b9 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.9ubuntu1
   apt  2.5.3
  SourcePackage: bluez
  Title: package bluez 5.65-0ubuntu1 failed to install/upgrade: installed bluez 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to kinetic on 2022-12-29 (0 days ago)
  dmi.bios.date: 11/15/2022
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 0CVCMK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd11/15/2022:br1.22:svnDellInc.:pnLatitude7520:pvr:rvnDellInc.:rn0CVCMK:rvrA01:cvnDellInc.:ct10:cvr:sku0A38:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7520
  dmi.product.sku: 0A38
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 48:51:C5:06:6C:87  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:35379 acl:639 sco:0 events:3462 errors:0
TX bytes:817060 acl:45 sco:0 commands:3339 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2000714/+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 2000649] Re: Xorg crashes or freezes

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.

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

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

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

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

Title:
  Xorg crashes or freezes

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, (I wasn't able to reproduce it) xorg just hangs or
  crashes to the log screen. It happens about every two weeks,
  especially if I don't reboot often (However doesn't matter much, I
  think, because it also happens on "fresh" boot).

  I use bspwm (version from the jammy repository), on Lubuntu 22.04.1
  (fresh install, not upgrade from 22.04, nor 20.04).

  Freezes occur when I switch between desktops, just hangs and that's
  it, no response to the keyboard, however mouse is usually usable and
  screen keeps updating.

  Crashes occur when I switch between windows or desktops (I use
  shortcuts for this), xorg just goes black and prints my shortcut to
  the screen; waits for a few secs and opens login screen.

  I don't know why it is happening, before 22.04 I was using 16.04 never
  had any problems.

  I tried google it, use some intel video card in /etc/X11/xorg.conf.d
  directory, but it makes system unusable at all, just type is super
  slow and I gave up experimenting with different flags ...

  I really hope you can tell me something, because this bug is really
  annoying, especially when I have a lot of windows open and I have to
  open them all again and again. Thank you in advance and have a nice
  day!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Wed Dec 28 23:59:36 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:5062]
  InstallationDate: Installed on 2022-12-24 (3 days ago)
  InstallationMedia: Lubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:7066 Lite-On Technology Corp. Integrated Camera
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HMS6XX00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=f9dce324-12ce-4b50-8ea8-12ef027dadd8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2022
  dmi.bios.release: 1.47
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0IET69W (1.47 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HMS6XX00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.18
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0IET69W(1.47):bd11/18/2022:br1.47:efr1.18:svnLENOVO:pn20HMS6XX00:pvrThinkPadX270:rvnLENOVO:rn20HMS6XX00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20HM_BU_Think_FM_ThinkPadX270:
  dmi.product.family: ThinkPad X270
  dmi.product.name: 20HMS6XX00
  dmi.product.sku: LENOVO_MT_20HM_BU_Think_FM_ThinkPad X270
  dmi.product.version: ThinkPad X270
  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.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5ppa5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati

[Touch-packages] [Bug 2000637] Re: Xorg freeze

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-470
(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/2000637

Title:
  Xorg freeze

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

Bug description:
  Since a fresh install of Xubuntu 22.04 sometimes X launches to a white
  screen, other times I get a black screen.  Restarting X seems to help
  sometimes.  I turned display power management off and the problem
  persists.  The system is responsive and usually I can still get to the
  text console.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-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..02.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  470.161.03  Wed Oct 19 
00:10:36 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Dec 28 09:43:46 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GK208B [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK208B [GeForce GT 730] [1043:881a]
  InstallationDate: Installed on 2022-12-17 (11 days ago)
  InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7508
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=2725c865-441b-4349-8465-3d167dcfc812 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/30/2010
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V3.7
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: K9N2GM-FIH(MS-7508)
  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.:bvrV3.7:bd06/30/2010:br8.15:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7508:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnK9N2GM-FIH(MS-7508):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-7508
  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.5-0ubuntu0.1
  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.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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-470/+bug/2000637/+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 2000487] Re: Monitor não puxa a resolução padrão e Gravação de Tela sem Vídeo

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

Hello! Those are two unrelated bugs...

The issue with screen recording in Kazam doesn't seem to be a bug...
Kazam appears to be an old X11 app and so cannot read the Wayland
screen. This is a security feature and not a bug. If you need to record
the screen using old software like Kazam then please select 'Ubuntu on
Xorg' from the login screen.

The issue with failing to detect the native screen resolution appears to
be a kernel problem relating to analog VGA connections.

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

** Summary changed:

- Monitor não puxa a resolução padrão e Gravação de Tela sem Vídeo
+ [i915] Native monitor resolution not detected over VGA

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

Title:
[i915] Native monitor resolution not detected over VGA

Status in linux package in Ubuntu:
New

Bug description:

Olá,
gostaria de relatar alguns problemas que estou sofrendo nesta versão (Ubuntu
22.04) e sofria na versão anterior (Ubuntu 20.04).
Na versão anterior não consegui por padrão fazer uso da resolução padrão,
mais consegui através de um script que criei pesquisando no Google logo usava a
resolução padrão desta forma.
Mais infelizmente nessa atual não consigo fazer uso do mesmo script e estou
sofrendo as consequencias.
Sobre a gravação de Tela sempre que faço uso do software Kazam as gravações
saem com a tela preta sem vídeo ou som.
Esses são meus problemas e pelo que pesquisei pelo Google de outros usuários,
infelizmente.
(Pt-Br)

Hello,
I would like to report some problems that I am suffering from in this version
(Ubuntu 22.04) and suffered from in the previous version (Ubuntu 20.04).
In the previous version, I was not able to make use of the default resolution
by default, but I managed through a script that I created by searching Google,
so it used the default resolution in this way.
More unfortunately in this current one I can't make use of the same script
and I'm suffering the consequences.
About Screen recording whenever I use the Kazam software the recordings come
out with a black screen without video or sound.
Those are my issues and from what I've googled from other users,
unfortunately.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
Uname: Linux 5.15.0-56-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 26 19:51:46 2022
DistUpgraded: 2022-11-21 13:11:29,776 DEBUG icon theme changed, re-reading
DistroCodename: jammy
DistroVariant: ubuntu
GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics
Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller])
InstallationDate: Installed on 2022-11-19 (37 days ago)
InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831)
MachineType: OEM To Be Filled By O.E.M.
ProcEnviron:
LANGUAGE=pt_BR:pt:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=pt_BR.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic
root=UUID=22e65828-ac26-41d7-9a63-906dfc5b772b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-11-21 (35 days ago)
dmi.bios.date: 10/12/2019
dmi.bios.release: 1.20
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G4177L0D
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: OEM G41 775 ICH7 8712
dmi.board.vendor: OEM
dmi.board.version: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG4177L0D:bd10/12/2019:br1.20:svnOEM:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnOEM:rnOEMG41775ICH78712:rvrTobefilledbyO.E.M.:cvnOEM: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: OEM
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau:

[Touch-packages] [Bug 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

See also bug 1878076

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in Mozilla Firefox:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed
Status in gtk+3.0 source package in Jammy:
  New
Status in gtk4 source package in Jammy:
  Triaged
Status in gtk+3.0 source package in Kinetic:
  New
Status in gtk4 source package in Kinetic:
  Triaged

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1949340/+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 2000336] Re: save-as procedure is non-intuitive

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

Sounds like a duplicate of bug 1878076, but see also bug 1949340.

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

** This bug has been marked a duplicate of bug 1878076
   GTK save-dialogs input-focus moves from filename to file search if a folder 
is selected

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

Title:
  save-as procedure is non-intuitive

Status in Ubuntu:
  New

Bug description:
  originally posted at bugzilla 
https://bugzilla.mozilla.org/show_bug.cgi?id=1803706
  but rejected as an "OS-default filepicker" problem.
  The report was as follows:

  User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:107.0)
  Gecko/20100101 Firefox/107.0

  Steps to reproduce:

  I had a pdf open and wished to save it (download)

  Actual results:

  I was presented with a panel that had the name of the pdf at the top and a 
list of file-type compatible files in a box below.
  I tried to modify the name of the pdf, but my modification was interpreted as 
a search term.

  this is not just non-intuitive, but idiotic behavior

  Expected results:

  my modification should have been accepted

  
---

  bugzilla's response was

  Off-hand it sounds like the OS-default filepicker is not intuitive,
  which isn't something we can fix, but something to take up with the
  relevant linux distribution and/or window manager folks.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Dec 23 12:18:08 2022
  DistUpgraded: 2022-11-26 15:02:34,980 INFO cache.commit()
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.38, 5.15.0-53-generic, x86_64: installed
   virtualbox/6.1.38, 5.15.0-56-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054]
  InstallationDate: Installed on 2021-01-14 (708 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) 
USB 2.0 Hub
   Bus 001 Device 003: ID 0592:0002 Powerware Corp. UPS (X-Slot)
   Bus 001 Device 002: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   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/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 2: Dev 3, If 0, Class=Vendor Specific Class, Driver=usbfs, 1.5M
   |__ Port 5: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
  MachineType: HP HP EliteDesk 800 G2 SFF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=9dd289f2-eb84-4c73-92fb-e6050acc143d ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to jammy on 2022-11-26 (26 days ago)
  dmi.bios.date: 07/14/2020
  dmi.bios.release: 2.48
  dmi.bios.vendor: HP
  dmi.bios.version: N01 Ver. 02.48
  dmi.board.name: 8054
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 05.39
  dmi.chassis.type: 4
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 5.57
  dmi.modalias: 
dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr:skuL1G76AV:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP EliteDesk 800 G2 SFF
  dmi.product.sku: L1G76AV
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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:

[Touch-packages] [Bug 2000173] Re: [amdgpu] Monitor does not wake from sleep unless power cycled