[Touch-packages] [Bug 2008541] [NEW] very high power draw from battery when watching videos

[alex valin]

Public bug reported:

when I watch a video in fullscreen, my laptop can draw as many as 25w.
For comparaison, on windows 11, a similar video will take only 8w from
the battery. obviously, the cpu temps and fan speed are much higher on
ubuntu tan on windows. Also, this might be unrelated, but when I plug in
or unplug the charger on my laptop, the power draw reported takes time
to climb up to the actual power draw/ charge rate ( up to 45 sec). In
this vase, my laptop can think that it still has a couple of days left
worth of battery life left

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 25 00:52:24 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 openrazer-driver/3.2.0, 5.15.0-60-generic, x86_64: installed
 openrazer-driver/3.2.0, 5.19.0-32-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] (rev 
d1) (prog-if 00 [VGA controller])
InstallationDate: Installed on 2022-12-03 (84 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: LENOVO 21CH000GUS
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic 
root=UUID=32b06683-a98d-4585-81c7-edb51198f58c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2022
dmi.bios.release: 1.32
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET62W (1.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CH000GUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.24:svnLENOVO:pn21CH000GUS:pvrThinkPadT16Gen1:rvnLENOVO:rn21CH000GUS:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CH_BU_Think_FM_ThinkPadT16Gen1:
dmi.product.family: ThinkPad T16 Gen 1
dmi.product.name: 21CH000GUS
dmi.product.sku: LENOVO_MT_21CH_BU_Think_FM_ThinkPad T16 Gen 1
dmi.product.version: ThinkPad T16 Gen 1
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
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

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


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

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

Title:
  very high power draw from battery when watching videos

Status in xorg package in Ubuntu:
  New

Bug description:
  when I watch a video in fullscreen, my laptop can draw as many as 25w.
  For comparaison, on windows 11, a similar video will take only 8w from
  the battery. obviously, the cpu temps and fan speed are much higher on
  ubuntu tan on windows. Also, this might be unrelated, but when I plug
  in or unplug the charger on my laptop, the power draw reported takes
  time to climb up to the actual power draw/ charge rate ( up to 45
  sec). In this vase, my laptop can think that it still has a couple of
  days left worth of battery life left

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 25 00:52:24 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   openrazer-driver/3.2.0, 5.15.0-60-generic, x86_64: installed
   openrazer-driver/3.2.0, 5.19.0-32-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [1002:1681] 
(rev d1) (prog-if 00 [VGA 

[Touch-packages] [Bug 2008141] Re: apt pattern to list packages from universe

[Seth Arnold]

Awesome! Thanks, I thought 'section' would have been something like libs
vs oldlibs in Debian, so I didn't even try it. Sorry.

apt list '?installed?section(^universe/)'  -- seems to work as I wanted.

Thanks

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

Title:
  apt pattern to list packages from universe

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Hello, a friend would like to remove all universe packages from their
  system but I do not know an easy way to discover which installed
  packages came from universe. I expected one of these two apt patterns
  to work:

 ?archive(REGEX), ~AREGEX
 Selects versions that come from the archive that matches
 the specified regular expression. Archive, here, means
 the values after a= in apt-cache policy.

 ?origin(REGEX), ~OREGEX
 Selects versions that come from the origin that matches
 the specified regular expression. Origin, here, means the
 values after o= in apt-cache policy.

  However, a quick check of my own system's apt-cache policy output
  shows the a= and o= values aren't helpful for determining universe
  from main:

  $ apt-cache policy | grep -A1 universe
   500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages
   release 
v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=universe,b=amd64
   origin security.ubuntu.com
  --
   400 http://192.168.0.27/ubuntu focal-proposed/universe amd64 Packages
   release 
v=20.04,o=Ubuntu,a=focal-proposed,n=focal,l=Ubuntu,c=universe,b=amd64
   origin 192.168.0.27
  --
   500 http://192.168.0.27/ubuntu focal-updates/universe amd64 Packages
   release 
v=20.04,o=Ubuntu,a=focal-updates,n=focal,l=Ubuntu,c=universe,b=amd64
   origin 192.168.0.27
  --
   500 http://192.168.0.27/ubuntu focal/universe amd64 Packages
   release v=20.04,o=Ubuntu,a=focal,n=focal,l=Ubuntu,c=universe,b=amd64
   origin 192.168.0.27

  Are there apt patterns that can select the c=universe state?

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2008141/+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 2008507] Re: package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade: unable to make backup link of './usr/bin/faillog' before installing new version: Input/output error

[Seth Arnold]

Hello, note the following lines from your dmesg:

[3.791052] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[3.791095] ata3.00: BMDMA stat 0x65
[3.791116] ata3.00: failed command: READ DMA
[3.791137] ata3.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 
in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 
(device error)
[3.791202] ata3.00: status: { DRDY ERR }
[3.791222] ata3.00: error: { ABRT }
[3.793984] ata3.00: configured for UDMA/133
[3.794009] ata3: EH complete
[3.806999] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[3.807047] ata3.00: BMDMA stat 0x65
[3.807068] ata3.00: failed command: READ DMA
[3.807089] ata3.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 
in
res 51/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 
(device error)
[3.807154] ata3.00: status: { DRDY ERR }
[3.807174] ata3.00: error: { ABRT }
[3.809935] ata3.00: configured for UDMA/133
[3.809961] ata3: EH complete


There's lots of these in your logs -- they indicate failure
communicating with the hard drive. This could be failing hard drive, bad
cables, bad power supply, bad motherboard, etc.

I suggest making backups if you don't already have some -- do not
overwrite old backups, you may need those. Then troubleshoot or replace
etc.

Thanks

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

Title:
  package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade:
  unable to make backup link of './usr/bin/faillog' before installing
  new version: Input/output error

Status in shadow package in Ubuntu:
  Invalid

Bug description:
  Not too sure what had happened.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: login 1:4.11.1+dfsg1-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Architecture: amd64
  Date: Fri Feb 24 16:25:41 2023
  Df:
   
  ErrorMessage: unable to make backup link of './usr/bin/faillog' before 
installing new version: Input/output error
  PythonDetails: N/A
  SourcePackage: shadow
  Title: package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade: 
unable to make backup link of './usr/bin/faillog' before installing new 
version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2008507/+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 2008507] Re: package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade: unable to make backup link of './usr/bin/faillog' before installing new version: Input/output error

[Seth Arnold]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment to this bug report it
seems that there may be a problem with your hardware.  I'd recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

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

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

** Tags added: hardware-error

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

Title:
  package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade:
  unable to make backup link of './usr/bin/faillog' before installing
  new version: Input/output error

Status in shadow package in Ubuntu:
  Invalid

Bug description:
  Not too sure what had happened.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: login 1:4.11.1+dfsg1-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Architecture: amd64
  Date: Fri Feb 24 16:25:41 2023
  Df:
   
  ErrorMessage: unable to make backup link of './usr/bin/faillog' before 
installing new version: Input/output error
  PythonDetails: N/A
  SourcePackage: shadow
  Title: package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade: 
unable to make backup link of './usr/bin/faillog' before installing new 
version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2008507/+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 2008530] [NEW] Perl 5.30.0 failed at debug mode

[Kaixiang Xie]

Public bug reported:

The system Perl (v5.30.0) failed at the debug mode when using
Getopt::Long and OpenGL::Array. Here is a sample code showing the
problem:


[Test file: t.pl]
#!/usr/bin/env perl
use Getopt::Long;
use OpenGL::Array;

print "hi\n";


[Test command]
$ perl -d t.pl 

Loading DB routines from perl5db.pl version 1.55
Editor support available.

Enter h or 'h h' for help, or 'man perldebug' for more help.

Invalid version format (non-numeric data) at 
/usr/lib/x86_64-linux-gnu/perl/5.30/DynaLoader.pm line 210.
Compilation failed in require at t.pl line 3.
 at t.pl line 3.
main::BEGIN() called at t.pl line 3
eval {...} called at t.pl line 3
BEGIN failed--compilation aborted at t.pl line 3.
 at t.pl line 3.
Debugged program terminated.  Use q to quit or R to restart,
use o inhibit_exit to avoid stopping after program termination,
h q, h R or h o to get additional info.


The system Perl version:
$ perl -v

This is perl 5, version 30, subversion 0 (v5.30.0) built for 
x86_64-linux-gnu-thread-multi
(with 57 registered patches, see perl -V for more detail)

Copyright 1987-2019, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.


It seems like the code works well on Perl v5.36.0. Here is my system info:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.5 LTS
Release:20.04
Codename:   focal

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

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

Title:
  Perl 5.30.0 failed at debug mode

Status in perl package in Ubuntu:
  New

Bug description:
  The system Perl (v5.30.0) failed at the debug mode when using
  Getopt::Long and OpenGL::Array. Here is a sample code showing the
  problem:

  
  [Test file: t.pl]
  #!/usr/bin/env perl
  use Getopt::Long;
  use OpenGL::Array;

  print "hi\n";

  
  [Test command]
  $ perl -d t.pl 

  Loading DB routines from perl5db.pl version 1.55
  Editor support available.

  Enter h or 'h h' for help, or 'man perldebug' for more help.

  Invalid version format (non-numeric data) at 
/usr/lib/x86_64-linux-gnu/perl/5.30/DynaLoader.pm line 210.
  Compilation failed in require at t.pl line 3.
   at t.pl line 3.
main::BEGIN() called at t.pl line 3
eval {...} called at t.pl line 3
  BEGIN failed--compilation aborted at t.pl line 3.
   at t.pl line 3.
  Debugged program terminated.  Use q to quit or R to restart,
  use o inhibit_exit to avoid stopping after program termination,
  h q, h R or h o to get additional info.


  The system Perl version:
  $ perl -v

  This is perl 5, version 30, subversion 0 (v5.30.0) built for 
x86_64-linux-gnu-thread-multi
  (with 57 registered patches, see perl -V for more detail)

  Copyright 1987-2019, Larry Wall

  Perl may be copied only under the terms of either the Artistic License or the
  GNU General Public License, which may be found in the Perl 5 source kit.

  Complete documentation for Perl, including FAQ lists, should be found on
  this system using "man perl" or "perldoc perl".  If you have access to the
  Internet, point your browser at http://www.perl.org/, the Perl Home Page.

  
  It seems like the code works well on Perl v5.36.0. Here is my system info:
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.5 LTS
  Release:  20.04
  Codename: focal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2008530/+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 1999285] Re: systemd-networkd constantly resets link on i350 when attempting to apply dhcp server provided MTU

[Nick Rosbrook]

I'm not sure it makes sense to SRU this to Jammy.

Firstly, there is an easy work around for this (see e.g.
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1881207/comments/5
for a way to avoid changing the DHCP server itself), and this bug does
not seem to affect a large number of users. Second, the PR that fixes
this upstream is fairly large for an SRU. We actually would need
https://github.com/systemd/systemd/pull/21344, and the commit you linked
is a follow-on to this. Finally, one of the patches does not apply
cleanly to Jammy.

If it's an option for your setup, this bug should not be present in
Kinetic.


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

** Also affects: systemd (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** No longer affects: systemd (Ubuntu Focal)

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

** Changed in: systemd (Ubuntu Jammy)
   Status: New => Won't Fix

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

Title:
  systemd-networkd constantly resets link on i350 when attempting to
  apply dhcp server provided MTU

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Won't Fix

Bug description:
  This is identical to:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1881207

  It just happens to affect 22.04.1.

  I can confirm that removing the `interface-mtu ` option from my
  dhcp server cures the issue.

  
  My netplan looks like:

  network:
ethernets:
  enp33s0f0:
dhcp4: true
dhcp6: false
  enp33s0f1:
dhcp4: true
dhcp6: false

  
  This snippet is from my test when I changed the dhcpd to no longer serve MTU:

  
  Dec 10 00:47:42 wiyuda-echo systemd[1]: Startup finished in 6min 14.070s 
(firmware) + 2.667s (loader) + 25.861s (kernel) + 3min 53.796s (userspace) = 
10min 36.395s.
  Dec 10 00:47:42 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
  Dec 10 00:47:42 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Lost carrier
  Dec 10 00:47:42 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCP lease lost
  Dec 10 00:47:42 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv6 lease 
lost
  Dec 10 00:47:43 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
  Dec 10 00:47:46 wiyuda-echo kernel: igb :21:00.0 enp33s0f0: igb: 
enp33s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
  Dec 10 00:47:46 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Gained carrier
  Dec 10 00:47:46 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
  Dec 10 00:47:51 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv4 address 
172.16.214.138/16 via 172.16.0.3
  Dec 10 00:47:51 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
  Dec 10 00:47:51 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Lost carrier
  Dec 10 00:47:51 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCP lease lost
  Dec 10 00:47:51 wiyuda-echo kernel: igb :21:00.0 enp33s0f0: Reset adapter
  Dec 10 00:47:52 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv6 lease 
lost
  Dec 10 00:47:52 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
  Dec 10 00:47:52 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
  Dec 10 00:47:55 wiyuda-echo kernel: igb :21:00.0 enp33s0f0: igb: 
enp33s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
  Dec 10 00:47:55 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Gained carrier
  Dec 10 00:47:55 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
  Dec 10 00:47:59 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv4 address 
172.16.214.138/16 via 172.16.0.3
  Dec 10 00:47:59 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
  Dec 10 00:47:59 wiyuda-echo systemd-networkd[4866]: enp33s0f0: Lost carrier
  Dec 10 00:47:59 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCP lease lost
  Dec 10 00:47:59 wiyuda-echo systemd-networkd[4866]: enp33s0f0: DHCPv6 lease 
lost
  Dec 10 00:47:59 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
  Dec 10 00:47:59 wiyuda-echo systemd-timesyncd[4418]: Network configuration 
changed, trying to establish connection.
  Dec 10 00:48:02 wiyuda-echo systemd[1]: systemd-timedated.service: 
Deactivated successfully.
  Dec 10 00:48:02 wiyuda-echo kernel: igb :21:00.0 enp33s0f0: igb: 
enp33s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
  Dec 10 00:48:02 wiyuda-echo 

[Touch-packages] [Bug 2003331] Re: Can't log in to lunar x11 session

[Gunnar Hjalmarsson]

On 2023-02-23 15:16, Gunnar Hjalmarsson wrote:
> The above observations are with virtualbox
> 6.1.38-dfsg-3~ubuntu1.22.04.1 on jammy.

But today I saw the same with virtualbox 7.0.6-dfsg-1 on lunar.

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

Title:
  Can't log in to lunar x11 session

Status in ubuntu-meta package in Ubuntu:
  New
Status in virtualbox package in Ubuntu:
  New

Bug description:
  On a freshly installed and updated lunar in VirtualBox it doesn't let
  me log in to Ubuntu on Xorg. I'm just bumped back to the login screen.
  journalctl extract attached.

  On my regular (updated) lunar install, logging in to Ubuntu on Xorg
  works fine. But that's anything but a fresh install.

  Missing dependency?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2003331/+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 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Henry Ward Hopeman Jr.]

** Also affects: gpgme1.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

To manage notifications about this bug 

[Touch-packages] [Bug 1924623] Re: Bluetooth headset pairing issue (HOCO ES32 PLUS)

[Launchpad Bug Tracker]

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

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

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

Title:
  Bluetooth headset pairing issue (HOCO ES32 PLUS)

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I am unable to connect a HOCO ES32 PLUS bluetooth headset. Device is
  visible and in pairable mode, but after running:

  bluetoothctl

  [bluetooth]# show
  Controller 04:33:C2:AA:17:60 (public)
   Name: mykyt
   Alias: mykyt
   Class: 0x001c010c
   Powered: yes
   Discoverable: yes
   DiscoverableTimeout: 0x
   Pairable: yes
   UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: OBEX Object Push  (1105--1000-8000-00805f9b34fb)
   UUID: Message Access Server (1132--1000-8000-00805f9b34fb)
   UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
   UUID: IrMC Sync (1104--1000-8000-00805f9b34fb)
   UUID: Vendor specific   (5005--1000-8000-0002ee01)
   UUID: Headset AG(1112--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
   UUID: Phonebook Access Server   (112f--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
   UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb)
   Modalias: usb:v1D6Bp0246d0535
   Discovering: yes
  Advertising Features:
   ActiveInstances: 0x00
   SupportedInstances: 0x05
   SupportedIncludes: tx-power
   SupportedIncludes: appearance
   SupportedIncludes: local-name
   SupportedSecondaryChannels: 1M
   SupportedSecondaryChannels: 2M
   SupportedSecondaryChannels: Coded

  i get:

  Failed to pair: org.bluez.Error.AuthenticationTimeout

  or

  Failed to pair: org.bluez.Error.AuthenticationCanceled

  or

  Failed to pair: org.bluez.Error.Failed

  I tried every single solution i was able to find for similar problems,
  including changing controller mode to bredr, reinstalling pulseaudio,
  unblocking rfkill, checking if my device is in pairable mode, using
  blueman and so on.

  The fact is, bluetooth is working on my laptop (I can connect to my
  phone and my other bluetooth headset MEIZU EP51) and also my headset
  HOCO ES32 PLUS is working and is able to connect to my phone and my
  other laptop DELL INSPIRON 7359 which is running on ubuntu 18.04.

  I really hope you can help me. Please tell me if you need more information 
and I will provide it.
  Thank you!
  --

  lsb_release -rd

  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  apt-cache policy bluez

  bluez:
    Installed: 5.53-0ubuntu3
    Candidate: 5.53-0ubuntu3
    Version table:
   *** 5.53-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  --

  Expected behavior:

  After turning on bluetooth and clicking on device name in settings ->
  bluetooth device is connecting and pairing successfully.

  Current behavior:

  Pairing fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 16 00:28:19 2021
  InstallationDate: Installed on 2020-08-27 (231 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Acer Swift SF314-57G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic 
root=UUID=59c2b478-ae5a-4c28-8c13-6b3721fe1f3b ro nouveau.modeset=0 quiet 
splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/06/2020
  dmi.bios.release: 1.14
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Floris_IL
  dmi.board.vendor: IL
  dmi.board.version: V1.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 1.14
  dmi.modalias: 

[Touch-packages] [Bug 1988408] Re: bluetooth gaming controller

[Launchpad Bug Tracker]

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

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

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

Title:
  bluetooth gaming controller

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 2 different ubuntu machines (laptop and desktop, with same ubuntu
  version and bluez) I can pair my generic BT game controller without
  any issues except for the fact that I can't send or receive any input.

  This controller with the same bluetooth dongle connects perfectly on
  windows 10 and 11 (had to dual boot to test it).

  The laptop itself, via dongle or via integrated BT receiver, can also
  connect perfectly and use it for steam on windows. There's something
  wrong going on with Bluez stack.

  Tried to use jstest-gtk and install xbox-drv to no avail.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  1 10:41:31 2022
  InstallationDate: Installed on 2022-08-31 (1 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-47-generic 
root=UUID=4f492b24-bcc5-4d68-917d-b6fed9e56b0f ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/23/2015
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.asset.tag: BC5FF494092A
  dmi.board.name: 960GM-VGS3 FX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd07/23/2015:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn960GM-VGS3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 5C:F3:70:A8:A2:8B  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING 
RX bytes:1035 acl:0 sco:0 events:60 errors:0
TX bytes:3694 acl:0 sco:0 commands:60 errors:0
  rfkill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1988408/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

[Nick Rosbrook]

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

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

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

** Changed in: systemd (Ubuntu Focal)
   Status: New => Triaged

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

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

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  New
Status in systemd source package in Focal:
  Triaged

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 1632808] Re: Consider supporting IPv6 autoconf in configure_networking

[A Shah]

Is there any status updates on this ?

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

Title:
  Consider supporting IPv6 autoconf in configure_networking

Status in MAAS:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  Because DHCPv6 only does addresses, and not routes,
  configure_networking needs to wait for the kernel to process a router-
  advertisement before returning claiming an IPv6 config (since all it
  will have is a /128 and no routes, making for a pretty useless network
  stack.)  See Bug #1609898 for context.

  (The syntax for ip= should probably also be extended to allow SLAAC
  configuration.  If the user said "dhcp", then we should insist on
  getting our answer from DHCP.)

  On the bright side, iscsi retries, so after 1 or more failures to
  connect, the router-advertisement comes in and the connect succeeds.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1632808/+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 1991285] Re: systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

[Nick Rosbrook]

It appears the last time this worked was around linux 5.4.0-122-generic,
e.g. this test run: https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/armhf/s/systemd/20220907_155827_ae562@/log.gz.

Then we start seeing it around 5.4.0.128.129, e.g. this test run:
https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/armhf/s/systemd/20220922_145908_d6960@/log.gz.

In other words, it started failing with newer kernels but no changes to
systemd. I'm not sure this is having any real impact in the wild, but I
don't want actual armhf regressions to be lost due to this (britney does
not consider armhf failures a regression currently). I think we should
just ignore this failed service on armhf only.

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

Title:
  systemd/245.4-4ubuntu3.18 ADT test failure with linux/5.4.0-128.144

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20220929_122501_863cf@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991285/+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 2007837] Re: Regression in stderr handling in 3.2.3 breaks BackupPc on 22.04; fix available in 3.2.4

[Bryce Harrington]

** Summary changed:

- 22.04: Backport request from 3.2.4 for fix of 3.2.3 regression
+ Regression in stderr handling in 3.2.3 breaks BackupPc on 22.04; fix 
available in 3.2.4

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

Title:
  Regression in stderr handling in 3.2.3 breaks BackupPc on 22.04; fix
  available in 3.2.4

Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Jammy:
  Triaged
Status in rsync package in Debian:
  Unknown

Bug description:
  rsync 3.2.3 (packaged in Ubuntu 22.04) changes stderr handling,
  leading another bug in libfile-rsyncp-perl (in Ubuntu 18.04 and 20.04)
  to surface [1].

  It practically makes using BackupPC 3 impossible with clients using
  rsync 3.2.3, as is packaged for 22.04. The fact that BackupPC on 20.04
  can't be used to back up machines with 22.04 is rather surprising and
  has bitten other users [2].

  It's unclear whether the bug will be fixed in 18.04's and 20.04's
  libfile-rsyncp-perl package (for status, see [3]).

  Because of this, the rsync maintainer has included a patch in 3.2.4
  that fixes this regression [4] (even though not strictly an rsync
  bug). As a result, rsync 3.2.3 is the only affected version, which
  happens to be the one packaged in 22.04.

  This report is to request backporting that fix [4] to Ubuntu 22.04, so
  that things don't silently break in scenarios where the backup server
  is left at 20.04, and some backup clients happen to upgrade to 22.04.

  I'm not sure what the criteria for security releases are, but as the
  issue causes backup denial of service and has easy mitigation, I think
  it would make sense to put it through the security channel.

  [1]: https://github.com/WayneD/rsync/issues/95#issuecomment-699185358
  [2]: 
https://www.mail-archive.com/backuppc-users@lists.sourceforge.net/msg32673.html
  [3]: 
https://bugs.launchpad.net/ubuntu/+source/libfile-rsyncp-perl/+bug/2007833
  [4]: 
https://github.com/WayneD/rsync/commit/4adfdaaf12db26c348b4d6150119b377f9b622c8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2007837/+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 2008507] [NEW] package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade: unable to make backup link of './usr/bin/faillog' before installing new version: Input/output erro

[brando smi]

Public bug reported:

Not too sure what had happened.

ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: login 1:4.11.1+dfsg1-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Architecture: amd64
Date: Fri Feb 24 16:25:41 2023
Df:
 
ErrorMessage: unable to make backup link of './usr/bin/faillog' before 
installing new version: Input/output error
PythonDetails: N/A
SourcePackage: shadow
Title: package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade: unable 
to make backup link of './usr/bin/faillog' before installing new version: 
Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package kinetic

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

Title:
  package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade:
  unable to make backup link of './usr/bin/faillog' before installing
  new version: Input/output error

Status in shadow package in Ubuntu:
  New

Bug description:
  Not too sure what had happened.

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: login 1:4.11.1+dfsg1-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Architecture: amd64
  Date: Fri Feb 24 16:25:41 2023
  Df:
   
  ErrorMessage: unable to make backup link of './usr/bin/faillog' before 
installing new version: Input/output error
  PythonDetails: N/A
  SourcePackage: shadow
  Title: package login 1:4.11.1+dfsg1-2ubuntu1 failed to install/upgrade: 
unable to make backup link of './usr/bin/faillog' before installing new 
version: Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2008507/+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 1998111] Re: Quectel EM05-G not being unlocked

[Launchpad Bug Tracker]

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

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

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

Title:
  Quectel EM05-G not being unlocked

Status in modemmanager package in Ubuntu:
  Confirmed

Bug description:
  Despite support being in fcc-unlock.d

  Bus 001 Device 003: ID 2c7c:030a Quectel Wireless Solutions Co., Ltd.
  Quectel EM05-G

  the modem remains locked and enabling it fails:

  jak@jak-t14-g3:~:master$ mmcli -m any -e
  error: couldn't enable the modem: 
'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition'

  
  Doing something like

  # modprobe -r cdc_mbim
  # modprobe cdc_mbim
  # mbimcli --device-open-proxy --device="/dev/wwan0mbim0" 
--quectel-set-radio-state=on 
  # systemctl RestartModemManager
  # mmcli -m any -e

  makes it work.

  Peculiar it seems that the mbim-proxy process that ModemManager
  started is hanging and causing the mbimcli command to time out (if I
  just run it manually).

  
  Further investigation warranted, tips welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: modemmanager 1.20.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Nov 28 13:54:07 2022
  InstallationDate: Installed on 2022-11-26 (1 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  SourcePackage: modemmanager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1998111/+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 2008489] [NEW] Unable to switch NVIDIA driver -- cryptic "OK" window pops up

[James Bowery]

Public bug reported:

See askubuntu.com question:

https://askubuntu.com/questions/1415167/what-does-the-software-updater-
popup-that-says-ok-with-a-circled-x-mean-when

tail -f /var/log/syslog

Feb 24 08:56:26 ML PackageKit: new install-packages transaction /9536_dadedeab 
scheduled from uid 1000
Feb 24 08:56:26 ML PackageKit: install-packages transaction /9536_dadedeab from 
uid 1000 finished with failed after 205ms
Feb 24 08:56:26 ML software-proper[115228]: Failed to set text 'Error 
while applying changes#012#012pk-client-error-quark: The following 
packages have unmet dependencies:#012  linux-modules-nvidia-525-generic: 
Depends: linux-modules-nvidia-525-5.15.0-60-generic (= 5.15.0-60.66) but it is 
not going to be installed#012Depends: 
nvidia-kernel-common-525 (<= 525.78.01-1) but it is not installable#012 
   Depends: nvidia-kernel-common-525 (>= 525.78.01) but 
it is not installable#012 (268)' from markup due to error parsing markup: Error 
on line 5 char 74: “=” is not a valid character following a “<” character; it 
may not begin an element name


$ lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-gtk 0.99.22.4
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 24 08:52:03 2023
ExecutablePath: /usr/bin/software-properties-gtk
InstallationDate: Installed on 2020-02-05 (1114 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
InterpreterPath: /usr/bin/python3.10
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy third-party-packages

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

Title:
  Unable to switch NVIDIA driver -- cryptic "OK" window pops up

Status in software-properties package in Ubuntu:
  New

Bug description:
  See askubuntu.com question:

  https://askubuntu.com/questions/1415167/what-does-the-software-
  updater-popup-that-says-ok-with-a-circled-x-mean-when

  tail -f /var/log/syslog

  Feb 24 08:56:26 ML PackageKit: new install-packages transaction 
/9536_dadedeab scheduled from uid 1000
  Feb 24 08:56:26 ML PackageKit: install-packages transaction /9536_dadedeab 
from uid 1000 finished with failed after 205ms
  Feb 24 08:56:26 ML software-proper[115228]: Failed to set text 'Error 
while applying changes#012#012pk-client-error-quark: The following 
packages have unmet dependencies:#012  linux-modules-nvidia-525-generic: 
Depends: linux-modules-nvidia-525-5.15.0-60-generic (= 5.15.0-60.66) but it is 
not going to be installed#012Depends: 
nvidia-kernel-common-525 (<= 525.78.01-1) but it is not installable#012 
   Depends: nvidia-kernel-common-525 (>= 525.78.01) but 
it is not installable#012 (268)' from markup due to error parsing markup: Error 
on line 5 char 74: “=” is not a valid character following a “<” character; it 
may not begin an element name


  $ lsb_release -rd
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.22.4
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 24 08:52:03 2023
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2020-02-05 (1114 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go 

[Touch-packages] [Bug 2008491] [NEW] Memory leak in pulseaudio

[Michał Fita]

Public bug reported:

This is very weird, but my pulseaudio uses 3.5GB as I type this. That
seems big for audio stuff.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
Uname: Linux 5.15.0-60-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 24 14:56:46 2023
InstallationDate: Installed on 2023-01-04 (51 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2022
dmi.bios.release: 1.32
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET62W (1.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CKCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: ThinkPad
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.23
dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1:
dmi.product.family: ThinkPad P16s Gen 1
dmi.product.name: 21CKCTO1WW
dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1
dmi.product.version: ThinkPad P16s Gen 1
dmi.sys.vendor: LENOVO

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


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

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

Title:
  Memory leak in pulseaudio

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is very weird, but my pulseaudio uses 3.5GB as I type this. That
  seems big for audio stuff.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 24 14:56:46 2023
  InstallationDate: Installed on 2023-01-04 (51 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2022
  dmi.bios.release: 1.32
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET62W (1.32 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CKCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: ThinkPad
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.23
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET62W(1.32):bd11/11/2022:br1.32:efr1.23:svnLENOVO:pn21CKCTO1WW:pvrThinkPadP16sGen1:rvnLENOVO:rn21CKCTO1WW:rvrThinkPad:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CK_BU_Think_FM_ThinkPadP16sGen1:
  dmi.product.family: ThinkPad P16s Gen 1
  dmi.product.name: 21CKCTO1WW
  dmi.product.sku: LENOVO_MT_21CK_BU_Think_FM_ThinkPad P16s Gen 1
  dmi.product.version: ThinkPad P16s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2008491/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~agherzan/+git/adt-matrix-hints/+merge/437889

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

Title:
  lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
  (device_add_remove_test)

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Bionic:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz

  The failing test seems to be:

  FAIL: lxc-tests: lxc-test-device-add-remove (0s)
  ---
  Adding /dev/network_latency to the container (device_add_remove_test) 
failed...
  ---

  This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note
  that this testcase is successful on Focal with the same kernel
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)

[Dimitri John Ledkov]

sponsored into unapproved queue

** Changed in: lxc (Ubuntu Bionic)
   Status: Triaged => In Progress

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

Title:
  lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
  (device_add_remove_test)

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Bionic:
  In Progress

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz

  The failing test seems to be:

  FAIL: lxc-tests: lxc-test-device-add-remove (0s)
  ---
  Adding /dev/network_latency to the container (device_add_remove_test) 
failed...
  ---

  This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note
  that this testcase is successful on Focal with the same kernel
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 2008393] Re: armhf dep8 failure due to restrictions changing apparmor profile status

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/rsyslog/+git/rsyslog/+merge/437884

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

Title:
  armhf dep8 failure due to restrictions changing apparmor profile
  status

Status in rsyslog package in Ubuntu:
  In Progress

Bug description:
  The armhf DEP8 testers in Ubuntu infrastructure have some restrictions
  and cannot change an apparmor profile. This is causing the tests to
  fail, because they try to make sure rsyslog is being tested in
  enforced mode:

  Enforcing the /etc/apparmor.d/usr.sbin.rsyslogd apparmor profile
  Setting /etc/apparmor.d/usr.sbin.rsyslogd to enforce mode.

  ERROR: /sbin/apparmor_parser: Unable to replace "rsyslogd".
  Permission denied; attempted to load a profile while confined?

  The package migrated to lunar even with this error because it never
  had DEP8 tests before, and the armhf baseline was born in this error
  state.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2008393/+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 2008466] Re: Will not wake up from suspend.

[Paul White]

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

Title:
  Will not wake up from suspend.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  HP laptop Ryzen 7 4700 with Renoir graphics.
  Close lid which puts system into suspend. After say 20 mins open laptop, 
keyboard backlight comes on but system does not wake up. Have to force a power 
off. It works OK after only a few mins in suspend. Sames on mains or battery.
  Problem does not exist using kernel 5.15.0-60-generic. Problem started on 
upgrade to 5.19.0-32-generic.
  Tried switching between X-org and Wayland and disabled TPM in BIOS without 
any change.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 24 09:32:13 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:876f]
  InstallationDate: Installed on 2022-09-12 (164 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP ENVY x360 Convertible 15-ee0xxx
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-mono
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=d3454052-ab9f-432c-88bb-477464dd3c93 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2022
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 876F
  dmi.board.vendor: HP
  dmi.board.version: 13.47
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 13.47
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd11/03/2022:br15.22:efr13.47:svnHP:pnHPENVYx360Convertible15-ee0xxx:pvrType1ProductConfigId:rvnHP:rn876F:rvr13.47:cvnHP:ct31:cvrChassisVersion:sku9QZ65EA#ABU:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-ee0xxx
  dmi.product.sku: 9QZ65EA#ABU
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  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/2008466/+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 2008466] Re: Will not wake up from suspend.

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  Will not wake up from suspend.

Status in xorg package in Ubuntu:
  New

Bug description:
  HP laptop Ryzen 7 4700 with Renoir graphics.
  Close lid which puts system into suspend. After say 20 mins open laptop, 
keyboard backlight comes on but system does not wake up. Have to force a power 
off. It works OK after only a few mins in suspend. Sames on mains or battery.
  Problem does not exist using kernel 5.15.0-60-generic. Problem started on 
upgrade to 5.19.0-32-generic.
  Tried switching between X-org and Wayland and disabled TPM in BIOS without 
any change.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-32-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 24 09:32:13 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Renoir [103c:876f]
  InstallationDate: Installed on 2022-09-12 (164 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP ENVY x360 Convertible 15-ee0xxx
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-mono
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=d3454052-ab9f-432c-88bb-477464dd3c93 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/03/2022
  dmi.bios.release: 15.22
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 876F
  dmi.board.vendor: HP
  dmi.board.version: 13.47
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 13.47
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd11/03/2022:br15.22:efr13.47:svnHP:pnHPENVYx360Convertible15-ee0xxx:pvrType1ProductConfigId:rvnHP:rn876F:rvr13.47:cvnHP:ct31:cvrChassisVersion:sku9QZ65EA#ABU:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-ee0xxx
  dmi.product.sku: 9QZ65EA#ABU
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  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/xorg/+bug/2008466/+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 2008466] [NEW] Will not wake up from suspend.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

HP laptop Ryzen 7 4700 with Renoir graphics.
Close lid which puts system into suspend. After say 20 mins open laptop, 
keyboard backlight comes on but system does not wake up. Have to force a power 
off. It works OK after only a few mins in suspend. Sames on mains or battery.
Problem does not exist using kernel 5.15.0-60-generic. Problem started on 
upgrade to 5.19.0-32-generic.
Tried switching between X-org and Wayland and disabled TPM in BIOS without any 
change.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 24 09:32:13 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company Renoir [103c:876f]
InstallationDate: Installed on 2022-09-12 (164 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: HP HP ENVY x360 Convertible 15-ee0xxx
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=xterm-mono
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic 
root=UUID=d3454052-ab9f-432c-88bb-477464dd3c93 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2022
dmi.bios.release: 15.22
dmi.bios.vendor: Insyde
dmi.bios.version: F.22
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 876F
dmi.board.vendor: HP
dmi.board.version: 13.47
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 13.47
dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd11/03/2022:br15.22:efr13.47:svnHP:pnHPENVYx360Convertible15-ee0xxx:pvrType1ProductConfigId:rvnHP:rn876F:rvr13.47:cvnHP:ct31:cvrChassisVersion:sku9QZ65EA#ABU:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY x360 Convertible 15-ee0xxx
dmi.product.sku: 9QZ65EA#ABU
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
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

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


** Tags: amd64 apport-bug jammy ubuntu
-- 
Will not wake up from suspend.
https://bugs.launchpad.net/bugs/2008466
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 2008470] Re: softwere not update

[Paul White]

Thank you for taking the time to report this issue and helping to make
Ubuntu better. Examining the information you have given us, this does
not appear to be a bug report so we are closing it and converting it to
a question in the support tracker.

Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.

We understand the difficulties you are facing, but it is better to raise
problems you are having in the support tracker at
https://answers.launchpad.net/ubuntu if you are uncertain if they are
bugs.

If you would prefer live chat support, you can find an IRC support
channel for your flavor of Ubuntu here:
https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with
your problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://ubuntuforums.org. For help on reporting bugs, see
https://help.ubuntu.com/community/ReportingBugs.

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

** Changed in: ubuntu
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+question/705158

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

Title:
  softwere not update

Status in Ubuntu:
  Invalid

Bug description:
  please provide proper guideline to update system softwere

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-142-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.30
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Feb 24 15:23:25 2023
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] 
[1002:130f] (rev d7) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Kaveri [Radeon R7 Graphics] 
[1019:99d3]
  InstallationDate: Installed on 2017-09-12 (1991 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Acer Veriton M2120G
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=UUID=87fc1860-ca1b-421a-b55b-66993f72cced ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2017
  dmi.bios.vendor: Acer
  dmi.bios.version: P21-A3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78F2P-M2/V1.0
  dmi.board.vendor: Acer
  dmi.board.version: P21-A3
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP21-A3:bd03/21/2017:svnAcer:pnVeritonM2120G:pvrP21-A3:rvnAcer:rnA78F2P-M2/V1.0:rvrP21-A3:cvnAcer:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Veriton M2120G
  dmi.product.version: P21-A3
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Feb 24 14:59:08 2023
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2008470/+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 2008469] [NEW] ubuntu jammy debug mirror out of sync

[Jan Feuchthofen]

Public bug reported:

Why dose the Ubuntu debug mirror is again out of sync how should it be
used in a productive environment when every month the mirror is for one
week broken.


libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 
2.7.4-1ubuntu3.1 is to be installed
 libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) 
but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed
 libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 
1:15.99.1+dfsg1-1ubuntu2 is to be installed
 libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 
2.1.27+dfsg2-3ubuntu1.1 is to be installed
 libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 
2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed
 libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 
7:4.4.2-0ubuntu0.22.04.1 is to be installed
 libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 
249.11-0ubuntu3.6 is to be installed
 libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 
is to be installed
 libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 
2:1.0.25-1ubuntu2 is to be installed
 E: Unable to correct problems, you have held broken packages.

** Affects: ubuntu-keyring (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: grub2-signed (Ubuntu) => ubuntu-keyring (Ubuntu)

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

Title:
  ubuntu jammy debug mirror out of sync

Status in ubuntu-keyring package in Ubuntu:
  New

Bug description:
  Why dose the Ubuntu debug mirror is again out of sync how should it be
  used in a productive environment when every month the mirror is for
  one week broken.

  
  libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 
2.7.4-1ubuntu3.1 is to be installed
   libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) 
but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed
   libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 
1:15.99.1+dfsg1-1ubuntu2 is to be installed
   libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 
2.1.27+dfsg2-3ubuntu1.1 is to be installed
   libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 
2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed
   libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 
7:4.4.2-0ubuntu0.22.04.1 is to be installed
   libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 
249.11-0ubuntu3.6 is to be installed
   libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 
249.11-0ubuntu3.6 is to be installed
   libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 
2:1.0.25-1ubuntu2 is to be installed
   E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/2008469/+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 2008470] [NEW] softwere not update

[kartar singh]

Public bug reported:

please provide proper guideline to update system softwere

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-142-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.30
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Feb 24 15:23:25 2023
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:130f] 
(rev d7) (prog-if 00 [VGA controller])
   Subsystem: Elitegroup Computer Systems Kaveri [Radeon R7 Graphics] 
[1019:99d3]
InstallationDate: Installed on 2017-09-12 (1991 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Acer Veriton M2120G
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=UUID=87fc1860-ca1b-421a-b55b-66993f72cced ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2017
dmi.bios.vendor: Acer
dmi.bios.version: P21-A3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A78F2P-M2/V1.0
dmi.board.vendor: Acer
dmi.board.version: P21-A3
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAcer:bvrP21-A3:bd03/21/2017:svnAcer:pnVeritonM2120G:pvrP21-A3:rvnAcer:rnA78F2P-M2/V1.0:rvrP21-A3:cvnAcer:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Veriton M2120G
dmi.product.version: P21-A3
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Feb 24 14:59:08 2023
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  softwere not update

Status in xorg package in Ubuntu:
  New

Bug description:
  please provide proper guideline to update system softwere

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-142-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.30
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Feb 24 15:23:25 2023
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] 
[1002:130f] (rev d7) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Kaveri [Radeon R7 Graphics] 
[1019:99d3]
  InstallationDate: Installed on 2017-09-12 (1991 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Acer Veriton M2120G
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic 
root=UUID=87fc1860-ca1b-421a-b55b-66993f72cced ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2017
  dmi.bios.vendor: Acer
  dmi.bios.version: P21-A3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A78F2P-M2/V1.0
  dmi.board.vendor: Acer
  dmi.board.version: P21-A3
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAcer:bvrP21-A3:bd03/21/2017:svnAcer:pnVeritonM2120G:pvrP21-A3:rvnAcer:rnA78F2P-M2/V1.0:rvrP21-A3:cvnAcer:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Veriton M2120G
  dmi.product.version: P21-A3
  dmi.sys.vendor: 

[Touch-packages] [Bug 2008141] Re: apt pattern to list packages from universe

[Julian Andres Klode]

You can only query '?section(^universe/)'

** Changed in: apt (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: apt (Ubuntu)
   Status: New => Triaged

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

Title:
  apt pattern to list packages from universe

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Hello, a friend would like to remove all universe packages from their
  system but I do not know an easy way to discover which installed
  packages came from universe. I expected one of these two apt patterns
  to work:

 ?archive(REGEX), ~AREGEX
 Selects versions that come from the archive that matches
 the specified regular expression. Archive, here, means
 the values after a= in apt-cache policy.

 ?origin(REGEX), ~OREGEX
 Selects versions that come from the origin that matches
 the specified regular expression. Origin, here, means the
 values after o= in apt-cache policy.

  However, a quick check of my own system's apt-cache policy output
  shows the a= and o= values aren't helpful for determining universe
  from main:

  $ apt-cache policy | grep -A1 universe
   500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages
   release 
v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=universe,b=amd64
   origin security.ubuntu.com
  --
   400 http://192.168.0.27/ubuntu focal-proposed/universe amd64 Packages
   release 
v=20.04,o=Ubuntu,a=focal-proposed,n=focal,l=Ubuntu,c=universe,b=amd64
   origin 192.168.0.27
  --
   500 http://192.168.0.27/ubuntu focal-updates/universe amd64 Packages
   release 
v=20.04,o=Ubuntu,a=focal-updates,n=focal,l=Ubuntu,c=universe,b=amd64
   origin 192.168.0.27
  --
   500 http://192.168.0.27/ubuntu focal/universe amd64 Packages
   release v=20.04,o=Ubuntu,a=focal,n=focal,l=Ubuntu,c=universe,b=amd64
   origin 192.168.0.27

  Are there apt patterns that can select the c=universe state?

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2008141/+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 2008469] [NEW] ubuntu jammy debug mirror out of sync

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Why dose the Ubuntu debug mirror is again out of sync how should it be
used in a productive environment when every month the mirror is for one
week broken.


libharfbuzz0b-dbgsym : Depends: libharfbuzz0b (= 2.7.4-1ubuntu3) but 
2.7.4-1ubuntu3.1 is to be installed
 libldap-2.5-0-dbgsym : Depends: libldap-2.5-0 (= 2.5.11+dfsg-1~exp1ubuntu3) 
but 2.5.13+dfsg-0ubuntu0.22.04.1 is to be installed
 libpulse0-dbgsym : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 
1:15.99.1+dfsg1-1ubuntu2 is to be installed
 libsasl2-2-dbgsym : Depends: libsasl2-2 (= 2.1.27+dfsg2-3ubuntu1) but 
2.1.27+dfsg2-3ubuntu1.1 is to be installed
 libsdl2-2.0-0-dbgsym : Depends: libsdl2-2.0-0 (= 2.0.20+dfsg-2build1) but 
2.0.20+dfsg-2ubuntu1.22.04.1 is to be installed
 libswresample3-dbgsym : Depends: libswresample3 (= 7:4.4.1-3ubuntu5) but 
7:4.4.2-0ubuntu0.22.04.1 is to be installed
 libsystemd0-dbgsym : Depends: libsystemd0 (= 249.11-0ubuntu3) but 
249.11-0ubuntu3.6 is to be installed
 libudev1-dbgsym : Depends: libudev1 (= 249.11-0ubuntu3) but 249.11-0ubuntu3.6 
is to be installed
 libusb-1.0-0-dbgsym : Depends: libusb-1.0-0 (= 2:1.0.25-1ubuntu1) but 
2:1.0.25-1ubuntu2 is to be installed
 E: Unable to correct problems, you have held broken packages.

** Affects: ubuntu-keyring (Ubuntu)
 Importance: Undecided
 Status: New

-- 
ubuntu jammy debug mirror out of sync
https://bugs.launchpad.net/bugs/2008469
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-keyring in Ubuntu.

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

[Touch-packages] [Bug 2003016] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.9 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-firmware 20220329.git681281e4-0ubuntu3.9 failed to
  install/upgrade: installed linux-firmware package post-installation
  script subprocess returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  dpkg: dependency problems prevent configuration of 
linux-image-generic-hwe-22.04:
   linux-image-generic-hwe-22.04 depends on linux-firmware; however:
Package linux-firmware is not configured yet.

  dpkg: error processing package linux-image-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of linux-generic-hwe-22.04:
   linux-generic-hwe-22.04 depends on linux-image-generic-hwe-22.04 (= 
5.15.0.58.56); however:
Package linux-image-generic-hwe-22.04 is not configured yet.

  dpkg: error processing package linux-generic-hwe-22.04 (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.

No apport report written because the error message 
indicates its a followup error from a previous failure.
  Setting up 
openssh-sftp-server (1:8.9p1-3ubuntu0.1) ...

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-firmware 20220329.git681281e4-0ubuntu3.9
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  liangkung   3376 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Mon Jan 16 11:13:50 2023
  Dependencies: firmware-sof-signed 2.0-1ubuntu4
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-07-03 (197 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. Inspiron 13-7353
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_saa1lv@/vmlinuz-5.15.0-56-generic 
root=ZFS=rpool/ROOT/ubuntu_saa1lv ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.1
  SourcePackage: initramfs-tools
  Title: package linux-firmware 20220329.git681281e4-0ubuntu3.9 failed to 
install/upgrade: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 1.22
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.22.0
  dmi.board.name: 00FG87
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.22.0:bd01/25/2019:br1.22:svnDellInc.:pnInspiron13-7353:pvr:rvnDellInc.:rn00FG87:rvrA00:cvnDellInc.:ct9:cvr:sku06FE:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 13-7353
  dmi.product.sku: 06FE
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2003016/+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 2007124] Re: Move available config files from /etc to /usr

[Sebastien Bacher]

Thanks, I had no objection so let's see how it's going

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

Title:
  Move available config files from /etc to /usr

Status in fontconfig package in Ubuntu:
  Fix Committed

Bug description:
  At the upgrade to fontconfig 2.10 a decade ago, the directory for
  storing available config files was changed from /etc/fonts/conf.avail
  to /usr/share/fontconfig/conf.avail. It was done upstream as well as
  in Debian, but Ubuntu delayed the transition for some reason. I think
  we should do that transition in Ubuntu too. That will get Ubuntu in
  sync with the upstream documentation and the delta to Debian gets
  reduced a little.

  The changes needed are straightforward. I put a proposed upload in
  this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/fontconfig

  and I would appreciate someone's eyes on it.

  So, what's the caveat? The only thing I can think of is that distros,
  system admins and individual users may have tweaked the font
  configuration by including symlinks which point to the moved files.
  While I don't have the impression that such symlinks are very frequent
  — custom conf files put directly in /etc/fonts/conf.d or equivalent
  places in $HOME seem to be more common — to the extent they exist,
  they will be silently disabled.

  Bug #2005124 revealed an example of a symlink which pointed to a file
  which will be moved if we do this. OTOH, in that case upstream added a
  symlink with the very same name, so we had to deal with that conflict.
  If the name of Kubuntu's link had been something else, we might not be
  aware of it yet.

  The changelog for this upload:

  https://launchpad.net/ubuntu/+source/fontconfig/2.10.1-0ubuntu1

  states that the transition will be done "later with another upload
  once the details are sorted". Are there other details which I have
  missed? If not, I suppose that the potential inconvenience is
  approximately as big today as it was 2012. And since next LTS release
  is more than one year ahead, this ought to be an appropriate time to
  make the change.

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