[Touch-packages] [Bug 1831747] Re: fixrtc hook requires e2fsprogs package, but that is not a dependency

2023-12-02 Thread Helmut Grohne
This bug breaks migration of debvm into noble:

https://autopkgtest.ubuntu.com/results/autopkgtest-
noble/noble/amd64/d/debvm/20231126_114257_c885f@/log.gz

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

Title:
  fixrtc hook requires e2fsprogs package, but that is not a dependency

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Package "initramfs-tools-core" provides "/usr/share/initramfs-
  tools/hooks/fixrtc" which runs during the update or regeneration of
  the initramfs and requires the file "/sbin/dumpe2fs" (available from
  "e2fsprogs") to be present, otherwise it fails and aborts the whole
  process, leading e.g. to an inconsistent package system.

  The problem/cause seems to be that "initramfs-tools-core" package has
  no direct or indirect hard dependency on "e2fsprogs".

  I believe either the package dependency should be added, or the fixrtc
  hook script should be rewritten so that it just outputs a warning
  instead of aborting with a failure if missing "dumpe2fs" is not a
  critical problem.

  This issue seems to affect at least Ubuntu 16.04 and 18.04. It has
  been brought to my attention at https://askubuntu.com/q/1148791/367990

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831747/+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 1937304] Re: lspci spews "Unable to load libkmod resources: error -12" and returns zero error code after printing details correctly

2023-12-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  lspci spews "Unable to load libkmod resources: error -12" and returns
  zero error code after printing details correctly

Status in kmod package in Ubuntu:
  Confirmed
Status in pciutils package in Ubuntu:
  Confirmed

Bug description:
  lspci spews "Unable to load libkmod resources: error -12" and returns
  error code after printing details correctly

  # lspci
  ...
  0004:01:00.0 Ethernet controller: Aquantia Corp. AQC107 Ethernet Controller 
[AQtion] (rev 02)

  # lspci -v -s 0004:01:00.0
  lspci -v -s 0004:01:00.0
  0004:01:00.0 Ethernet controller: Aquantia Corp. AQC107 Ethernet Controller 
[AQtion] (rev 02)
  Subsystem: AQC107 Ethernet Controller [AQtion]
  Flags: bus master, fast devsel, latency 0, IRQ 69
  Memory at 174044 (64-bit, non-prefetchable) [size=64K]
  Memory at 174045 (64-bit, non-prefetchable) [size=4K]
  Memory at 174000 (64-bit, non-prefetchable) [size=4M]
  Expansion ROM at 174040 [virtual] [disabled] [size=256K]
  Capabilities: [40] Express Endpoint, MSI 00
  Capabilities: [80] Power Management version 3
  Capabilities: [90] MSI-X: Enable+ Count=32 Masked-
  Capabilities: [a0] MSI: Enable- Count=1/32 Maskable- 64bit+
  Capabilities: [100] Advanced Error Reporting
  Capabilities: [150] Vendor Specific Information: ID=0001 Rev=1 
Len=024 
  Capabilities: [180] Secondary PCI Express
  Kernel driver in use: atlantic
  lspci: Unable to load libkmod resources: error -12
  (returns zero error code)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1937304/+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 1937304] Re: lspci spews "Unable to load libkmod resources: error -12" and returns zero error code after printing details correctly

2023-12-02 Thread bhs
** No longer affects: ubuntu-default-settings

** No longer affects: kmod

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

Title:
  lspci spews "Unable to load libkmod resources: error -12" and returns
  zero error code after printing details correctly

Status in kmod package in Ubuntu:
  Confirmed
Status in pciutils package in Ubuntu:
  Confirmed

Bug description:
  lspci spews "Unable to load libkmod resources: error -12" and returns
  error code after printing details correctly

  # lspci
  ...
  0004:01:00.0 Ethernet controller: Aquantia Corp. AQC107 Ethernet Controller 
[AQtion] (rev 02)

  # lspci -v -s 0004:01:00.0
  lspci -v -s 0004:01:00.0
  0004:01:00.0 Ethernet controller: Aquantia Corp. AQC107 Ethernet Controller 
[AQtion] (rev 02)
  Subsystem: AQC107 Ethernet Controller [AQtion]
  Flags: bus master, fast devsel, latency 0, IRQ 69
  Memory at 174044 (64-bit, non-prefetchable) [size=64K]
  Memory at 174045 (64-bit, non-prefetchable) [size=4K]
  Memory at 174000 (64-bit, non-prefetchable) [size=4M]
  Expansion ROM at 174040 [virtual] [disabled] [size=256K]
  Capabilities: [40] Express Endpoint, MSI 00
  Capabilities: [80] Power Management version 3
  Capabilities: [90] MSI-X: Enable+ Count=32 Masked-
  Capabilities: [a0] MSI: Enable- Count=1/32 Maskable- 64bit+
  Capabilities: [100] Advanced Error Reporting
  Capabilities: [150] Vendor Specific Information: ID=0001 Rev=1 
Len=024 
  Capabilities: [180] Secondary PCI Express
  Kernel driver in use: atlantic
  lspci: Unable to load libkmod resources: error -12
  (returns zero error code)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1937304/+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 1937304] Re: lspci spews "Unable to load libkmod resources: error -12" and returns zero error code after printing details correctly

2023-12-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  lspci spews "Unable to load libkmod resources: error -12" and returns
  zero error code after printing details correctly

Status in kmod package in Ubuntu:
  Confirmed
Status in pciutils package in Ubuntu:
  Confirmed

Bug description:
  lspci spews "Unable to load libkmod resources: error -12" and returns
  error code after printing details correctly

  # lspci
  ...
  0004:01:00.0 Ethernet controller: Aquantia Corp. AQC107 Ethernet Controller 
[AQtion] (rev 02)

  # lspci -v -s 0004:01:00.0
  lspci -v -s 0004:01:00.0
  0004:01:00.0 Ethernet controller: Aquantia Corp. AQC107 Ethernet Controller 
[AQtion] (rev 02)
  Subsystem: AQC107 Ethernet Controller [AQtion]
  Flags: bus master, fast devsel, latency 0, IRQ 69
  Memory at 174044 (64-bit, non-prefetchable) [size=64K]
  Memory at 174045 (64-bit, non-prefetchable) [size=4K]
  Memory at 174000 (64-bit, non-prefetchable) [size=4M]
  Expansion ROM at 174040 [virtual] [disabled] [size=256K]
  Capabilities: [40] Express Endpoint, MSI 00
  Capabilities: [80] Power Management version 3
  Capabilities: [90] MSI-X: Enable+ Count=32 Masked-
  Capabilities: [a0] MSI: Enable- Count=1/32 Maskable- 64bit+
  Capabilities: [100] Advanced Error Reporting
  Capabilities: [150] Vendor Specific Information: ID=0001 Rev=1 
Len=024 
  Capabilities: [180] Secondary PCI Express
  Kernel driver in use: atlantic
  lspci: Unable to load libkmod resources: error -12
  (returns zero error code)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1937304/+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 1959439] Re: On Ubuntu 22.04 logrotate does not rotate syslog

2023-12-02 Thread Nigel Winterbottom
root@nigel-Latitude-E6420:~# logrotate /etc/logrotate.d/rsyslog --debug
WARNING: logrotate in debug mode does nothing except ...
...
considering log /var/log/syslog
error: skipping "/var/log/syslog" because parent directory has insecure 
permissions (It's world writable or writable by group which is not "root") Set 
"su" directive in config file to tell logrotate which user/group should be used 
for rotation.

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

Title:
  On Ubuntu 22.04 logrotate does not rotate syslog

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  On my Ubuntu 22.04 Jammy installed 2022-01-03 /var/log/syslog is very
  big and was never rotated.

  corrado@corrado-n3-jj-0103:~$ stat /var/log/syslog
File: /var/log/syslog
Size: 77434065  Blocks: 151248 IO Block: 4096   regular file
  Device: 10303h/66307d Inode: 264672  Links: 1
  Access: (0640/-rw-r-)  Uid: (  104/  syslog)   Gid: (4/ adm)
  Access: 2022-01-28 16:35:50.408728666 +0100
  Modify: 2022-01-28 16:35:47.705029318 +0100
  Change: 2022-01-28 16:35:47.705029318 +0100
   Birth: 2022-01-03 14:31:29.195999321 +0100
  corrado@corrado-n3-jj-0103:~$ 

  looking to journalctl i see logrotate has been started on January 25
  but log file was not cut

  corrado@corrado-n3-jj-0103:~$ journalctl -b-18 | grep logrotate
  gen 25 07:58:01 corrado-n3-jj-0103 systemd[1]: logrotate.service: Deactivated 
successfully.
  gen 25 09:35:09 corrado-n3-jj-0103 systemd[1]: logrotate.timer: Deactivated 
successfully.
  corrado@corrado-n3-jj-0103:~$ 

  corrado@corrado-n3-jj-0103:~$ systemctl status logrotate.service
  ○ logrotate.service - Rotate log files
   Loaded: loaded (/lib/systemd/system/logrotate.service; static)
   Active: inactive (dead)
  TriggeredBy: ● logrotate.timer
 Docs: man:logrotate(8)
   man:logrotate.conf(5)
  corrado@corrado-n3-jj-0103:~$ 

  corrado@corrado-n3-jj-0103:~$ cat /etc/logrotate.conf
  # see "man logrotate" for details

  # global options do not affect preceding include directives

  # rotate log files weekly
  weekly

  # use the adm group by default, since this is the owning group
  # of /var/log/syslog.
  su root adm

  # keep 4 weeks worth of backlogs
  rotate 4

  # create new (empty) log files after rotating old ones
  create

  # use date as a suffix of the rotated file
  #dateext

  # uncomment this if you want your log files compressed
  #compress

  # packages drop log rotation information into this directory
  include /etc/logrotate.d

  # system-specific logs may also be configured here.
  corrado@corrado-n3-jj-0103:~$ 

  corrado@corrado-n3-jj-0103:~$ ls /var/log -lh
  total 108M
  -rw-r--r--  1 root  root  42K gen 27 21:20 
alternatives.log
  -rw-r-  1 root  adm  5,5K gen 28 17:32 apport.log
  drwxr-xr-x  2 root  root 4,0K gen 28 17:52 apt
  -rw-r-  1 syslogadm  762K gen 28 19:08 auth.log
  -rw---  1 root  root1019K gen 28 17:54 boot.log
  -rw-r--r--  1 root  root 105K gen  3 08:43 
bootstrap.log
  -rw-rw  1 root  utmp0 gen  3 08:42 btmp
  drwxr-xr-x  2 root  root 4,0K gen  3 14:31 cups
  drwxr-xr-x  2 root  root 4,0K ott 29 18:59 
dist-upgrade
  -rw-r-  1 root  adm   81K gen 28 17:55 dmesg
  -rw-r-  1 root  adm   80K gen 28 17:22 dmesg.0
  -rw-r-  1 root  adm   22K gen 28 17:02 dmesg.1.gz
  -rw-r-  1 root  adm   22K gen 28 16:01 dmesg.2.gz
  -rw-r-  1 root  adm   22K gen 28 10:29 dmesg.3.gz
  -rw-r-  1 root  adm   22K gen 28 08:54 dmesg.4.gz
  -rw-r--r--  1 root  root 1,4M gen 28 17:52 dpkg.log
  -rw-r--r--  1 root  root  32K gen  6 09:44 faillog
  -rw-r--r--  1 root  root  12K gen 28 15:32 
fontconfig.log
  drwx--x--x  2 root  gdm  4,0K gen  3 14:31 gdm3
  -rw-r--r--  1 root  root 1,5K gen 28 17:54 
gpu-manager.log
  drwxr-xr-x  3 root  root 4,0K gen  3 08:44 hp
  drwxr-xr-x  2 root  root 4,0K gen  3 13:59 installer
  -rw-r--r--  1 root  root 544K gen 11 08:33 
installer.zip
  -rw-r--r--  1 root  root 544K gen  3 21:25 inst.zip
  drwxr-sr-x+ 3 root  systemd-journal  4,0K gen  3 14:31 journal
  -rw-r-  1 syslogadm   27M gen 28 19:09 kern.log
  -rw-rw-r--  1 root  utmp 286K gen  6 09:44 lastlog
  drwxr-xr-x  2 root  

[Touch-packages] [Bug 1959439] Re: On Ubuntu 22.04 logrotate does not rotate syslog

2023-12-02 Thread Nigel Winterbottom
root@nigel-Latitude-E6420:~# ls -l /var | fgrep log
drwxrwxr-x 14 root syslog   4096 Dec  2 16:46 log

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

Title:
  On Ubuntu 22.04 logrotate does not rotate syslog

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  On my Ubuntu 22.04 Jammy installed 2022-01-03 /var/log/syslog is very
  big and was never rotated.

  corrado@corrado-n3-jj-0103:~$ stat /var/log/syslog
File: /var/log/syslog
Size: 77434065  Blocks: 151248 IO Block: 4096   regular file
  Device: 10303h/66307d Inode: 264672  Links: 1
  Access: (0640/-rw-r-)  Uid: (  104/  syslog)   Gid: (4/ adm)
  Access: 2022-01-28 16:35:50.408728666 +0100
  Modify: 2022-01-28 16:35:47.705029318 +0100
  Change: 2022-01-28 16:35:47.705029318 +0100
   Birth: 2022-01-03 14:31:29.195999321 +0100
  corrado@corrado-n3-jj-0103:~$ 

  looking to journalctl i see logrotate has been started on January 25
  but log file was not cut

  corrado@corrado-n3-jj-0103:~$ journalctl -b-18 | grep logrotate
  gen 25 07:58:01 corrado-n3-jj-0103 systemd[1]: logrotate.service: Deactivated 
successfully.
  gen 25 09:35:09 corrado-n3-jj-0103 systemd[1]: logrotate.timer: Deactivated 
successfully.
  corrado@corrado-n3-jj-0103:~$ 

  corrado@corrado-n3-jj-0103:~$ systemctl status logrotate.service
  ○ logrotate.service - Rotate log files
   Loaded: loaded (/lib/systemd/system/logrotate.service; static)
   Active: inactive (dead)
  TriggeredBy: ● logrotate.timer
 Docs: man:logrotate(8)
   man:logrotate.conf(5)
  corrado@corrado-n3-jj-0103:~$ 

  corrado@corrado-n3-jj-0103:~$ cat /etc/logrotate.conf
  # see "man logrotate" for details

  # global options do not affect preceding include directives

  # rotate log files weekly
  weekly

  # use the adm group by default, since this is the owning group
  # of /var/log/syslog.
  su root adm

  # keep 4 weeks worth of backlogs
  rotate 4

  # create new (empty) log files after rotating old ones
  create

  # use date as a suffix of the rotated file
  #dateext

  # uncomment this if you want your log files compressed
  #compress

  # packages drop log rotation information into this directory
  include /etc/logrotate.d

  # system-specific logs may also be configured here.
  corrado@corrado-n3-jj-0103:~$ 

  corrado@corrado-n3-jj-0103:~$ ls /var/log -lh
  total 108M
  -rw-r--r--  1 root  root  42K gen 27 21:20 
alternatives.log
  -rw-r-  1 root  adm  5,5K gen 28 17:32 apport.log
  drwxr-xr-x  2 root  root 4,0K gen 28 17:52 apt
  -rw-r-  1 syslogadm  762K gen 28 19:08 auth.log
  -rw---  1 root  root1019K gen 28 17:54 boot.log
  -rw-r--r--  1 root  root 105K gen  3 08:43 
bootstrap.log
  -rw-rw  1 root  utmp0 gen  3 08:42 btmp
  drwxr-xr-x  2 root  root 4,0K gen  3 14:31 cups
  drwxr-xr-x  2 root  root 4,0K ott 29 18:59 
dist-upgrade
  -rw-r-  1 root  adm   81K gen 28 17:55 dmesg
  -rw-r-  1 root  adm   80K gen 28 17:22 dmesg.0
  -rw-r-  1 root  adm   22K gen 28 17:02 dmesg.1.gz
  -rw-r-  1 root  adm   22K gen 28 16:01 dmesg.2.gz
  -rw-r-  1 root  adm   22K gen 28 10:29 dmesg.3.gz
  -rw-r-  1 root  adm   22K gen 28 08:54 dmesg.4.gz
  -rw-r--r--  1 root  root 1,4M gen 28 17:52 dpkg.log
  -rw-r--r--  1 root  root  32K gen  6 09:44 faillog
  -rw-r--r--  1 root  root  12K gen 28 15:32 
fontconfig.log
  drwx--x--x  2 root  gdm  4,0K gen  3 14:31 gdm3
  -rw-r--r--  1 root  root 1,5K gen 28 17:54 
gpu-manager.log
  drwxr-xr-x  3 root  root 4,0K gen  3 08:44 hp
  drwxr-xr-x  2 root  root 4,0K gen  3 13:59 installer
  -rw-r--r--  1 root  root 544K gen 11 08:33 
installer.zip
  -rw-r--r--  1 root  root 544K gen  3 21:25 inst.zip
  drwxr-sr-x+ 3 root  systemd-journal  4,0K gen  3 14:31 journal
  -rw-r-  1 syslogadm   27M gen 28 19:09 kern.log
  -rw-rw-r--  1 root  utmp 286K gen  6 09:44 lastlog
  drwxr-xr-x  2 root  root 4,0K nov 18 15:05 openvpn
  drwx--  2 root  root 4,0K gen  3 08:42 private
  drwx--  2 speech-dispatcher root 4,0K dic 11 23:07 
speech-dispatcher
  -rw-r-  1 syslogadm   76M gen 28 19:10 syslog
  -rw---  1 root  

[Touch-packages] [Bug 1959439] Re: On Ubuntu 22.04 logrotate does not rotate syslog

2023-12-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  On Ubuntu 22.04 logrotate does not rotate syslog

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  On my Ubuntu 22.04 Jammy installed 2022-01-03 /var/log/syslog is very
  big and was never rotated.

  corrado@corrado-n3-jj-0103:~$ stat /var/log/syslog
File: /var/log/syslog
Size: 77434065  Blocks: 151248 IO Block: 4096   regular file
  Device: 10303h/66307d Inode: 264672  Links: 1
  Access: (0640/-rw-r-)  Uid: (  104/  syslog)   Gid: (4/ adm)
  Access: 2022-01-28 16:35:50.408728666 +0100
  Modify: 2022-01-28 16:35:47.705029318 +0100
  Change: 2022-01-28 16:35:47.705029318 +0100
   Birth: 2022-01-03 14:31:29.195999321 +0100
  corrado@corrado-n3-jj-0103:~$ 

  looking to journalctl i see logrotate has been started on January 25
  but log file was not cut

  corrado@corrado-n3-jj-0103:~$ journalctl -b-18 | grep logrotate
  gen 25 07:58:01 corrado-n3-jj-0103 systemd[1]: logrotate.service: Deactivated 
successfully.
  gen 25 09:35:09 corrado-n3-jj-0103 systemd[1]: logrotate.timer: Deactivated 
successfully.
  corrado@corrado-n3-jj-0103:~$ 

  corrado@corrado-n3-jj-0103:~$ systemctl status logrotate.service
  ○ logrotate.service - Rotate log files
   Loaded: loaded (/lib/systemd/system/logrotate.service; static)
   Active: inactive (dead)
  TriggeredBy: ● logrotate.timer
 Docs: man:logrotate(8)
   man:logrotate.conf(5)
  corrado@corrado-n3-jj-0103:~$ 

  corrado@corrado-n3-jj-0103:~$ cat /etc/logrotate.conf
  # see "man logrotate" for details

  # global options do not affect preceding include directives

  # rotate log files weekly
  weekly

  # use the adm group by default, since this is the owning group
  # of /var/log/syslog.
  su root adm

  # keep 4 weeks worth of backlogs
  rotate 4

  # create new (empty) log files after rotating old ones
  create

  # use date as a suffix of the rotated file
  #dateext

  # uncomment this if you want your log files compressed
  #compress

  # packages drop log rotation information into this directory
  include /etc/logrotate.d

  # system-specific logs may also be configured here.
  corrado@corrado-n3-jj-0103:~$ 

  corrado@corrado-n3-jj-0103:~$ ls /var/log -lh
  total 108M
  -rw-r--r--  1 root  root  42K gen 27 21:20 
alternatives.log
  -rw-r-  1 root  adm  5,5K gen 28 17:32 apport.log
  drwxr-xr-x  2 root  root 4,0K gen 28 17:52 apt
  -rw-r-  1 syslogadm  762K gen 28 19:08 auth.log
  -rw---  1 root  root1019K gen 28 17:54 boot.log
  -rw-r--r--  1 root  root 105K gen  3 08:43 
bootstrap.log
  -rw-rw  1 root  utmp0 gen  3 08:42 btmp
  drwxr-xr-x  2 root  root 4,0K gen  3 14:31 cups
  drwxr-xr-x  2 root  root 4,0K ott 29 18:59 
dist-upgrade
  -rw-r-  1 root  adm   81K gen 28 17:55 dmesg
  -rw-r-  1 root  adm   80K gen 28 17:22 dmesg.0
  -rw-r-  1 root  adm   22K gen 28 17:02 dmesg.1.gz
  -rw-r-  1 root  adm   22K gen 28 16:01 dmesg.2.gz
  -rw-r-  1 root  adm   22K gen 28 10:29 dmesg.3.gz
  -rw-r-  1 root  adm   22K gen 28 08:54 dmesg.4.gz
  -rw-r--r--  1 root  root 1,4M gen 28 17:52 dpkg.log
  -rw-r--r--  1 root  root  32K gen  6 09:44 faillog
  -rw-r--r--  1 root  root  12K gen 28 15:32 
fontconfig.log
  drwx--x--x  2 root  gdm  4,0K gen  3 14:31 gdm3
  -rw-r--r--  1 root  root 1,5K gen 28 17:54 
gpu-manager.log
  drwxr-xr-x  3 root  root 4,0K gen  3 08:44 hp
  drwxr-xr-x  2 root  root 4,0K gen  3 13:59 installer
  -rw-r--r--  1 root  root 544K gen 11 08:33 
installer.zip
  -rw-r--r--  1 root  root 544K gen  3 21:25 inst.zip
  drwxr-sr-x+ 3 root  systemd-journal  4,0K gen  3 14:31 journal
  -rw-r-  1 syslogadm   27M gen 28 19:09 kern.log
  -rw-rw-r--  1 root  utmp 286K gen  6 09:44 lastlog
  drwxr-xr-x  2 root  root 4,0K nov 18 15:05 openvpn
  drwx--  2 root  root 4,0K gen  3 08:42 private
  drwx--  2 speech-dispatcher root 4,0K dic 11 23:07 
speech-dispatcher
  -rw-r-  1 syslogadm   76M gen 28 19:10 

[Touch-packages] [Bug 2045477] [NEW] Canon MF731 will not print

2023-12-02 Thread j gleacher
Public bug reported:

Printer works fine on other computers and worked on this one until I
reimaged it with new harddrive. Computer reports that printing is
successful, but nothing prints.

ping 192.168.1.19
PING 192.168.1.19 (192.168.1.19) 56(84) bytes of data.
64 bytes from 192.168.1.19: icmp_seq=1 ttl=64 time=100 ms

nmap 192.168.1.19
Starting Nmap 7.80 ( https://nmap.org ) at 2023-12-02 14:56 EST
Nmap scan report for 192.168.1.19
Host is up (0.049s latency).
Not shown: 995 closed ports
PORT STATE SERVICE
80/tcp   open  http
443/tcp  open  https
515/tcp  open  printer
631/tcp  open  ipp
9100/tcp open  jetdirect

/usr/lib/cups/backend/snmp
network socket://192.168.1.19 "Canon MF731C/733C UFR II" "Canon MF731C/733C" 
"MFG:Canon;MDL:MF731C/733C UFR II;CLS:PRINTER;DES:Canon MF731C/733C UFR 
II;CID:CA_XPS_OIP;CMD:LIPSLX,CPCA;PESP:V1;" ""

sudo /usr/lib/cups/backend/dnssd
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Ignoring local service Canon_MF731C_733C @ t420.
DEBUG: Querying "Canon\032MF731C\047733C._ipp._tcp.local"...
DEBUG: Querying "Canon\032MF731C\047733C._pdl-datastream._tcp.local"...
DEBUG: Querying "Canon\032MF731C\047733C._printer._tcp.local"...
DEBUG: sent=0, count=3
DEBUG2: query_callback(browser=0x5559d2370ef0, interfaceIndex=3, protocol=0, 
event=0, fullName="Canon\032MF731C\047733C._ipp._tcp.local", rrclass=1, 
rrtype=16, rdata=0x5559d237175c, rdlen=612, flags=5, context=0x5559d2370430)
DEBUG2: query_callback: "txtvers=1".
DEBUG2: query_callback: "rp=ipp/print".
DEBUG2: query_callback: "note=".
DEBUG2: query_callback: "qtotal=1".
DEBUG2: query_callback: "priority=10".
DEBUG2: query_callback: "ty=Canon MF731C/733C".
DEBUG2: query_callback: "product=(CNMF731C/733C)".
DEBUG2: query_callback: 
"pdl=application/octet-stream,image/urf,image/pwg-raster,image/jpeg,application/pdf".
DEBUG2: query_callback: "adminurl=http://Canone55576.local:80/airprint.html;.
DEBUG2: query_callback: "usb_MFG=Canon".
DEBUG2: query_callback: "usb_MDL=MF731C/733C".
DEBUG2: query_callback: "Transparent=F".
DEBUG2: query_callback: "Binary=F".
DEBUG2: query_callback: "TBCP=F".
DEBUG2: query_callback: "Color=T".
DEBUG2: query_callback: "Copies=T".
DEBUG2: query_callback: "Duplex=T".
DEBUG2: query_callback: "PaperCustom=T".
DEBUG2: query_callback: "Bind=F".
DEBUG2: query_callback: "Collate=F".
DEBUG2: query_callback: "Sort=F".
DEBUG2: query_callback: "Staple=F".
DEBUG2: query_callback: "Punch=0".
DEBUG2: query_callback: "PaperMax=legal-A4".
DEBUG2: query_callback: "UUID=6d4ff0ce-6b11-11d8-8020-f80d60e55576".
DEBUG2: query_callback: "usb_CMD=LIPSLX,CPCA".
DEBUG2: query_callback: "TLS=1.2".
DEBUG2: query_callback: "Scan=T".
DEBUG2: query_callback: "Fax=F".
DEBUG2: query_callback: 
"URF=ADOBERGB24,CP255,DM1,PQ4,RS300,SRGB24,W8-16,FN3,IS1-4,OB10-40,V1.4".
DEBUG2: query_callback: "kind=document,envelope,postcard".
DEBUG2: query_callback: "print_wfds=T".
DEBUG2: query_callback: "mopria-certified=1.2".
DEBUG2: query_callback(browser=0x5559d2370ef0, interfaceIndex=2, protocol=0, 
event=0, fullName="Canon\032MF731C\047733C._ipp._tcp.local", rrclass=1, 
rrtype=16, rdata=0x5559d237175c, rdlen=612, flags=5, context=0x5559d2370430)
DEBUG2: query_callback: "txtvers=1".
DEBUG2: query_callback: "rp=ipp/print".
DEBUG2: query_callback: "note=".
DEBUG2: query_callback: "qtotal=1".
DEBUG2: query_callback: "priority=10".
DEBUG2: query_callback: "ty=Canon MF731C/733C".
DEBUG2: query_callback: "product=(CNMF731C/733C)".
DEBUG2: query_callback: 
"pdl=application/octet-stream,image/urf,image/pwg-raster,image/jpeg,application/pdf".
DEBUG2: query_callback: "adminurl=http://Canone55576.local:80/airprint.html;.
DEBUG2: query_callback: "usb_MFG=Canon".
DEBUG2: query_callback: "usb_MDL=MF731C/733C".
DEBUG2: query_callback: "Transparent=F".
DEBUG2: query_callback: "Binary=F".
DEBUG2: query_callback: "TBCP=F".
DEBUG2: query_callback: "Color=T".
DEBUG2: query_callback: "Copies=T".
DEBUG2: query_callback: "Duplex=T".
DEBUG2: query_callback: "PaperCustom=T".
DEBUG2: query_callback: "Bind=F".
DEBUG2: query_callback: "Collate=F".
DEBUG2: query_callback: "Sort=F".
DEBUG2: query_callback: "Staple=F".
DEBUG2: query_callback: "Punch=0".
DEBUG2: query_callback: "PaperMax=legal-A4".
DEBUG2: query_callback: 

[Touch-packages] [Bug 2038998] Re: [amdgpu] Screen corruption, distorted geometry and misplaced triangles

2023-12-02 Thread Niklas Schmelzle
The graphic glitch just happened on my system (Ubuntu 23.10, Lenovo
ThinkPad T14 Gen 2a with AMD Ryzen™ 5 PRO 5650U with Radeon™ Graphics ×
12) again. I have `COGL_DEBUG=disable-batching` set in /etc/environment.
Furthermore all extensions are deactivated (however, not deleted).
System was also rebooted.

Interestingly, this time it did not occur to an XWayland window. I
configured chrome to run wayland directly (which decreased the frequency
of the error occuring, at least it seemed like it).

Here dmesg:

[70061.823842] amdgpu :07:00.0: amdgpu: [gfxhub0] no-retry page fault 
(src_id:0 ring:24 vmid:1 pasid:32771, for process chrome pid 5084 thread 
chrome:cs0 pid 5121)
[70061.823858] amdgpu :07:00.0: amdgpu:   in page starting at address 
0x000c5de7b000 from IH client 0x1b (UTCL2)
[70061.823865] amdgpu :07:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00100430
[70061.823869] amdgpu :07:00.0: amdgpu:  Faulty UTCL2 client ID: IA 
(0x2)
[70061.823873] amdgpu :07:00.0: amdgpu:  MORE_FAULTS: 0x0
[70061.823877] amdgpu :07:00.0: amdgpu:  WALKER_ERROR: 0x0
[70061.823880] amdgpu :07:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
[70061.823883] amdgpu :07:00.0: amdgpu:  MAPPING_ERROR: 0x0
[70061.823886] amdgpu :07:00.0: amdgpu:  RW: 0x0


I might try to set the kernel parameter next. For clarification: I would add 
amdgpu.mcb=0 to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and then run 
'sudo update-grub' (or update-grub2?). Afterwards I can just reboot?

BTW, just to rule other influences out: I do hibernate my system from
time to time. This should not have any influence, or?

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

Title:
  [amdgpu] Screen corruption, distorted geometry and misplaced triangles

Status in GNOME Shell:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Laptop is a Lenovo ThinkPad P14s Gen 2 AMD.
  Ryzen 7 PRO 5850U
  with Radeon (RX Vega 8?) integrated graphics
  16 GB RAM

  Running Ubuntu 23.10 (GNOME) from a clean install performed October 9,
  2023 from a daily-live/current .iso generated on October 4, 2023.

  Wayland
  Kernel 6.5.0-9-generic

  * * * * *

  Installed a pre-release build of Ubuntu 23.10 to my ThinkPad the other
  day, was going through setting up and testing the usual programs.

  Installed Steam through apt from the 'mantic' repositories. Installed
  Proton 8.0 and Steam Linux Runtime 3.0 (Sniper) alongside two
  compatible titles.

  Screen corruption (white and grey streaks) present in-game when GNOME
  UI elements appeared on-screen (e.g., volume, brightness, and keyboard
  backlight indicators) and omnipresent after closing either game.

  Artifacts remain on screen until log-out or reboot. Artifacts were not
  present beforehand.

  Artifacts only appeared in Wayland session; not X11/Xorg.

  I previously had been running the same games on Ubuntu 22.04 LTS
  (GNOME, Wayland) and Kubuntu 22.04 LTS (Plasma, X11/Xorg) on this
  computer without issue (kernel 6.2).

  * * * * *

  Please see subsequent posts for video/images.

  Happy to provide any other information as needed. Thanks!

  * * * * *

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 11 01:17:43 2023
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev d1) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Cezanne [Radeon Vega Series / Radeon Vega Mobile Series] 
[17aa:509b]
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A00068US
  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: 

[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads

2023-12-02 Thread brian mullan
Ubuntu 22.04.3 LTS

In an LXD VM also running Ubuntu 22.04.3 LTS I executed:

$ sudo apt install -f ./webmesh_0.17.1_linux_amd64.deb

and this is what displayed...

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'webmesh' instead of './webmesh_0.17.1_linux_amd64.deb'
The following additional packages will be installed:
  wireguard-tools
Suggested packages:
  openresolv | resolvconf
The following NEW packages will be installed:
  webmesh wireguard-tools
0 upgraded, 2 newly installed, 0 to remove and 1 not upgraded.
Need to get 86.9 kB/28.8 MB of archives.
After this operation, 56.5 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 /home/bmullan/webmesh/scripts/webmesh_0.17.1_linux_amd64.deb webmesh 
amd64 0.17.1 [28.8 MB]
Get:2 http://archive.ubuntu.com/ubuntu jammy/main amd64 wireguard-tools amd64 
1.0.20210914-1ubuntu2 [86.9 kB]
Fetched 86.9 kB in 1s (72.9 kB/s)  
Selecting previously unselected package webmesh.
(Reading database ... 56780 files and directories currently installed.)
Preparing to unpack .../webmesh_0.17.1_linux_amd64.deb ...
Unpacking webmesh (0.17.1) ...
Selecting previously unselected package wireguard-tools.
Preparing to unpack .../wireguard-tools_1.0.20210914-1ubuntu2_amd64.deb ...
Unpacking wireguard-tools (1.0.20210914-1ubuntu2) ...
Setting up webmesh (0.17.1) ...
Setting up wireguard-tools (1.0.20210914-1ubuntu2) ...
wg-quick.target is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.10.2-1) ...
Scanning processes...   

  
Scanning linux images...

  

Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this
host.

N: Download is performed unsandboxed as root as file
'/home/bmullan/webmesh/scripts/webmesh_0.17.1_linux_amd64.deb' couldn't
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

As with the others there seems to be a "permissions" problem?

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

Title:
  Warning messages about unsandboxed downloads

Status in apt package in Ubuntu:
  Fix Released
Status in aptitude package in Ubuntu:
  Fix Released
Status in synaptic package in Ubuntu:
  Triaged
Status in update-notifier package in Ubuntu:
  Fix Released
Status in aptitude source package in Xenial:
  Confirmed
Status in synaptic source package in Xenial:
  Confirmed
Status in update-notifier source package in Xenial:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in aptitude source package in Hirsute:
  Fix Released
Status in synaptic source package in Hirsute:
  Won't Fix
Status in update-notifier source package in Hirsute:
  Fix Released
Status in apt package in Debian:
  Fix Released
Status in aptitude package in Debian:
  Fix Released
Status in synaptic package in Debian:
  New

Bug description:
  READ ME FIRST
  =
  This is only a regression on a cosmetic level. Previous versions of apt did 
not have any sandboxing whatsoever, so this means apt reverted back to that old 
behavior.

  update-notifier SRU
  ---
  [Impact]
  Cosmetic. Warnings when installing packages using update-notifier downloading 
stuff

  [Test case]

  Install flashplugin-installer with apt and check that the output does
  not contain a message like this:

  W: Can't drop privileges for downloading as file '...' couldn't be
  accessed by user '_apt'

  [Regression Potential]

  It just chowns /var/lib/update-notifier/package-data-
  downloads/partial/ to _apt:root, there should not be any regression.

  Original report
  ---

  Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
  now get that error when installing/upgrading some packages:

  Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
  Processing triggers for libc-bin (2.21-0ubuntu5) ...
  W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)

  From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
  the folder is empty (no /.synaptic/ sub-folder or file), so the above
  error.

  oem@u64:~$ ls -l .synaptic
  total 4
  -rw-rw-r-- 1 oem oem   0 Aug 25 11:19 options
  -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf

  oem@u64:~$ ls -l /var/lib/apt/lists/
  
  -rw-r- 1