[Touch-packages] [Bug 1847527] Re: Backport systemd-journal-remote fix PR #11953

2024-02-13 Thread Jonathan Rosser
this issue does not appear related to openstack-ansible

** Changed in: openstack-ansible
   Status: New => 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/1847527

Title:
  Backport systemd-journal-remote fix PR #11953

Status in openstack-ansible:
  Invalid
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Invalid
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  upstream commit 7fdb237f5473cb8fc2129e57e8a0039526dcb4fd broke remote journal 
upload, because it added a check to verify the Content-Length header, but the 
upload may use Transfer-Encoding of 'chunked' which does
  not specify Content-Length.

  [test case]

  setup 2 systems, A and B.  Install systemd-journal-remote on both.

  On A:

  $ sudo systemctl edit systemd-journal-remote.service

  in the editor, add:

  [Service]
  ExecStart=
  ExecStart=/lib/systemd/systemd-journal-remote --listen-http=-3 
--output=/var/log/journal/remote/

  
  Then enable/start the socket:

  $ sudo systemctl enable systemd-journal-remote.socket
  $ sudo systemctl start systemd-journal-remote.socket

  Optionally, start the service and verify it is running (not required,
  since the socket will start the service):

  $ sudo systemctl start systemd-journal-remote.service
  $ sudo systemctl status systemd-journal-remote.service | grep Active
 Active: active (running) since Thu 2019-11-14 20:08:48 UTC; 7min ago

  
  On B:

  Edit the file /etc/systemd/journal-upload.conf:

  [Upload]
  URL=http://192.168.122.184:19532

  
  Replacing the IP address with the actual ip addr of node A.  Then 
enable/start the service:

  $ sudo systemctl enable systemd-journal-upload.service
  $ sudo systemctl start systemd-journal-upload.service

  Check for failure:

  ubuntu@lp1847527-d:~$ journalctl -b -u systemd-journal-upload.service 
  -- Logs begin at Thu 2019-11-14 16:34:08 UTC, end at Thu 2019-11-14 20:19:34 
UTC. --
  Nov 14 20:19:03 lp1847527-d systemd[1]: Started Journal Remote Upload Service.
  Nov 14 20:19:03 lp1847527-d systemd-journal-upload[721]: Upload to 
http://192.168.122.184:19532/upload failed with code 411: gth Required
  Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: Main 
process exited, code=exited, status=1/FAILURE
  Nov 14 20:19:03 lp1847527-d systemd[1]: systemd-journal-upload.service: 
Failed with result 'exit-code'.

  
  [regression potential]

  this limits the Transfer-Encoding to only be either unspecified, or
  'chunked'.  Any other value will fail.  However, journal-upload.c does
  not ever use any other Transfer-Encoding than 'chunked', and this fix
  comes from upstream and has not changed since applied there.

  Any regression would likely result in the failure to upload a remote
  journal.

  [other info]

  the commit that caused this is not included in Bionic, and the commit
  to fix this is already in Eoan; this is needed only in Disco.

  original description:
  --

  I'm requesting that systemd 240 receive the fix in upstream PR 11953
  found here https://github.com/systemd/systemd/pull/11953

  This fixes remote journal shipping using systemd components. I believe
  only Disco (19.04) is impacted by this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openstack-ansible/+bug/1847527/+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 2051045] [NEW] Xorg freeze

2024-01-23 Thread Jonathan Higdon
Public bug reported:

Freeze began after a system update

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 21:45:39 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) 
(prog-if 00 [VGA controller])
InstallationDate: Installed on 2022-02-09 (713 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset 
dis_ucode_ldr
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2018
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: INTEL H55
dmi.board.vendor: INTEL
dmi.board.version: INTEL
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.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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 false-gpu-hang freeze jammy ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freeze began after a system update

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 21:45:39 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2022-02-09 (713 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent

2023-11-12 Thread Jonathan Ferguson
https://charmhub.io/ntp/configure

ntp_package | string

If set to "ntp" the ntp package will be installed and configured, or if
set to "chrony" the chrony package will be installed and configured. If
unspecified the appropriate package will be selected based on the
operating system. Please note that the use of ntp on Ubuntu bionic or
later is not recommended as it does not receive security updates.

** Package changed: charms => ntp (Juju Charms Collection)

** Changed in: ntp (Juju Charms Collection)
   Status: New => Confirmed

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

Title:
  [needs-packaging] The packages ntp and ntpsec are not equivalent

Status in NTP:
  Confirmed
Status in ntp package in Ubuntu:
  Confirmed
Status in ntp package in Juju Charms Collection:
  Confirmed
Status in ntp package in Debian:
  Confirmed

Bug description:
  I recently did an install of Ubuntu 23.04 and then configured ntp as I have 
been doing so for more than 8 years.
  With previous versions of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
  I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with 
the new location of ntp.conf, after restarting I noticed that the resultant 
output was missing requisite details.

  
  Compare the following and the lack of ".MCST." and ".ACST.":

  Original ntp on Apollo-Lake-N3150
  jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
  Description:    Ubuntu 22.04.3 LTS
  Release:22.04
  jonathan@Apollo-Lake-N3450:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
   ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
   ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
   ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
  *time.cloudflare 10.242.8.77  3 u  469 1024  367  234.691   -0.929  67.380
  +2001-44b8-2100- 42.3.115.79  2 u  581 1024  377  487.209  +55.669  57.154
  +2001-44b8-2100- 4.179.66.17  3 u  215 1024  377  489.637  +57.002  35.399
  jonathan@Apollo-Lake-N3450:~$

  NTPsec on Braswell-N3150
  jonathan@Braswell-N3150:~$ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04
  jonathan@Braswell-N3150:~$ ntpq -p
   remote   refid  st t when poll reach 
  delay   offset   jitter
  
===
   0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
  +prod-ntp-5.ntp1.ps5.canonical.com   37.15.221.1892 u  141 1024  367 
383.4932 -19.6895  35.0534
  *time.tfmcloud.au203.35.83.2422 u  325 1024  367 
325.9317  -0.1496  43.0522
  +any.time.nl 133.243.238.243  2 u  158 1024  373 
300.7941 -20.8962 136.1422
  +ntp2.its.waikato.ac.nz  .GPS.1 u  363 1024  377 
356.5361 -18.2740 140.5984
  +2001-44b8-2100-3f00---007b-0004 42.3.115.79  2 u  214 1024  367 
490.3898  28.3416   2.7728
  +tic.ntp.telstra.net 203.35.83.2422 u   13 1024  367 
566.0744 -14.1332   6.0377
  +863xqmprtfqv69pv7nwc.ip6.superloop.au   192.168.1.1  2 u   79 1024  367 
330.2658 -14.3483  16.2172
  +gps-ads.10mrlp.juneks.com.au.PPS.1 u  271 1024  367 
443.4812 -71.8020  44.6332
  +x.ns.gin.ntt.net129.250.35.222   2 u   57 1024  367  
22.4974  41.3055   6.0639
  jonathan@Braswell-N3150:~$

  
  This behaviour will affect the following:
  Ubuntu 22.10, 23.04 and 23.10
  Debian 12, 13 and 14

  NTPsec have documented their reasoning for lacking support.
  https://docs.ntpsec.org/latest/discover.html
  http

[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent

2023-11-01 Thread Jonathan Ferguson
https://packages.ubuntu.com/noble/ntp
I now see that Noble has a package for ntp but it is a transitional package to 
ntpsec instead of the real ntp package. — This is an extremely dangerous 
situation for the Long Term Support release.

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

Title:
  [needs-packaging] The packages ntp and ntpsec are not equivalent

Status in NTP:
  Confirmed
Status in ntp package in Ubuntu:
  Confirmed
Status in Juju Charms Collection:
  New
Status in ntp package in Debian:
  Confirmed

Bug description:
  I recently did an install of Ubuntu 23.04 and then configured ntp as I have 
been doing so for more than 8 years.
  With previous versions of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
  I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with 
the new location of ntp.conf, after restarting I noticed that the resultant 
output was missing requisite details.

  
  Compare the following and the lack of ".MCST." and ".ACST.":

  Original ntp on Apollo-Lake-N3150
  jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  jonathan@Apollo-Lake-N3450:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
   ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
   ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
   ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
  *time.cloudflare 10.242.8.77  3 u  469 1024  367  234.691   -0.929  67.380
  +2001-44b8-2100- 42.3.115.79  2 u  581 1024  377  487.209  +55.669  57.154
  +2001-44b8-2100- 4.179.66.17  3 u  215 1024  377  489.637  +57.002  35.399
  jonathan@Apollo-Lake-N3450:~$

  NTPsec on Braswell-N3150
  jonathan@Braswell-N3150:~$ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04
  jonathan@Braswell-N3150:~$ ntpq -p
   remote   refid  st t when poll reach 
  delay   offset   jitter
  
===
   0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
  +prod-ntp-5.ntp1.ps5.canonical.com   37.15.221.1892 u  141 1024  367 
383.4932 -19.6895  35.0534
  *time.tfmcloud.au203.35.83.2422 u  325 1024  367 
325.9317  -0.1496  43.0522
  +any.time.nl 133.243.238.243  2 u  158 1024  373 
300.7941 -20.8962 136.1422
  +ntp2.its.waikato.ac.nz  .GPS.1 u  363 1024  377 
356.5361 -18.2740 140.5984
  +2001-44b8-2100-3f00---007b-0004 42.3.115.79  2 u  214 1024  367 
490.3898  28.3416   2.7728
  +tic.ntp.telstra.net 203.35.83.2422 u   13 1024  367 
566.0744 -14.1332   6.0377
  +863xqmprtfqv69pv7nwc.ip6.superloop.au   192.168.1.1  2 u   79 1024  367 
330.2658 -14.3483  16.2172
  +gps-ads.10mrlp.juneks.com.au.PPS.1 u  271 1024  367 
443.4812 -71.8020  44.6332
  +x.ns.gin.ntt.net129.250.35.222   2 u   57 1024  367  
22.4974  41.3055   6.0639
  jonathan@Braswell-N3150:~$

  
  This behaviour will affect the following:
  Ubuntu 22.10, 23.04 and 23.10
  Debian 12, 13 and 14

  NTPsec have documented their reasoning for lacking support.
  https://docs.ntpsec.org/latest/discover.html
  https://docs.ntpsec.org/latest/ntpsec.html
  https://docs.ntpsec.org/latest/assoc.html#broad
  https://docs.ntpsec.org/latest/assoc.html#many

  The issue remains that ntp and ntpsec are not capability equivalent.

  I foresee two means of rectifying this predicament, if NTPsec is going
  to be the default implementation of NTP then ntpsec need

[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent

2023-11-01 Thread Jonathan Ferguson
** Also affects: charms
   Importance: Undecided
   Status: New

** Changed in: ntp
   Status: New => Confirmed

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

Title:
  [needs-packaging] The packages ntp and ntpsec are not equivalent

Status in NTP:
  Confirmed
Status in ntp package in Ubuntu:
  Confirmed
Status in Juju Charms Collection:
  New
Status in ntp package in Debian:
  Confirmed

Bug description:
  I recently did an install of Ubuntu 23.04 and then configured ntp as I have 
been doing so for more than 8 years.
  With previous versions of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
  I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with 
the new location of ntp.conf, after restarting I noticed that the resultant 
output was missing requisite details.

  
  Compare the following and the lack of ".MCST." and ".ACST.":

  Original ntp on Apollo-Lake-N3150
  jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:    22.04
  jonathan@Apollo-Lake-N3450:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
   ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
   ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
   ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
  *time.cloudflare 10.242.8.77  3 u  469 1024  367  234.691   -0.929  67.380
  +2001-44b8-2100- 42.3.115.79  2 u  581 1024  377  487.209  +55.669  57.154
  +2001-44b8-2100- 4.179.66.17  3 u  215 1024  377  489.637  +57.002  35.399
  jonathan@Apollo-Lake-N3450:~$

  NTPsec on Braswell-N3150
  jonathan@Braswell-N3150:~$ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:    23.04
  jonathan@Braswell-N3150:~$ ntpq -p
   remote   refid  st t when poll reach 
  delay   offset   jitter
  
===
   0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
  +prod-ntp-5.ntp1.ps5.canonical.com   37.15.221.1892 u  141 1024  367 
383.4932 -19.6895  35.0534
  *time.tfmcloud.au203.35.83.2422 u  325 1024  367 
325.9317  -0.1496  43.0522
  +any.time.nl 133.243.238.243  2 u  158 1024  373 
300.7941 -20.8962 136.1422
  +ntp2.its.waikato.ac.nz  .GPS.1 u  363 1024  377 
356.5361 -18.2740 140.5984
  +2001-44b8-2100-3f00---007b-0004 42.3.115.79  2 u  214 1024  367 
490.3898  28.3416   2.7728
  +tic.ntp.telstra.net 203.35.83.2422 u   13 1024  367 
566.0744 -14.1332   6.0377
  +863xqmprtfqv69pv7nwc.ip6.superloop.au   192.168.1.1  2 u   79 1024  367 
330.2658 -14.3483  16.2172
  +gps-ads.10mrlp.juneks.com.au.PPS.1 u  271 1024  367 
443.4812 -71.8020  44.6332
  +x.ns.gin.ntt.net129.250.35.222   2 u   57 1024  367  
22.4974  41.3055   6.0639
  jonathan@Braswell-N3150:~$

  
  This behaviour will affect the following:
  Ubuntu 22.10, 23.04 and 23.10
  Debian 12, 13 and 14

  NTPsec have documented their reasoning for lacking support.
  https://docs.ntpsec.org/latest/discover.html
  https://docs.ntpsec.org/latest/ntpsec.html
  https://docs.ntpsec.org/latest/assoc.html#broad
  https://docs.ntpsec.org/latest/assoc.html#many

  The issue remains that ntp and ntpsec are not capability equivalent.

  I foresee two means of rectifying this predicament, if NTPsec is going
  to be the default implementation of NTP then ntpsec needs to implement
  all of the capabilities of ntp, or the easier alternative is that the
  real ntp https://www.ntp.org/downlo

[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent

2023-10-20 Thread Jonathan Ferguson
I found the thread on the Debian Developers' Mailing List that Richard
Laager (rlaager) mentioned.  https://lists.debian.org/debian-
devel/2022/01/msg00172.html

I read through all of the replies in the aforementioned thread.

There is this devastating nugget that is not expounded upon and is the same 
crux I am bringing to the Ubuntu community's attention:
"Sounds good, I'd like to have a few more reviewers though. ntp is aged, but 
according to popcon the transition could affect ~25% of the Debian 
installations."  https://lists.debian.org/debian-devel/2022/01/msg00211.html

I believe that it is critical that Ubuntu makes available the most
feature complete standards complying NTP daemon.  https://www.rfc-
editor.org/rfc/rfc5905

The present LTS, 22.04, has the original ntp package.  To advert
disaster for a substantial number of users, Ubuntu will need the
original ntp package available when 24.04LTS is released.

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

Title:
  [needs-packaging] The packages ntp and ntpsec are not equivalent

Status in NTP:
  New
Status in ntp package in Ubuntu:
  Confirmed
Status in ntp package in Debian:
  Confirmed

Bug description:
  I recently did an install of Ubuntu 23.04 and then configured ntp as I have 
been doing so for more than 8 years.
  With previous versions of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
  I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with 
the new location of ntp.conf, after restarting I noticed that the resultant 
output was missing requisite details.

  
  Compare the following and the lack of ".MCST." and ".ACST.":

  Original ntp on Apollo-Lake-N3150
  jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  jonathan@Apollo-Lake-N3450:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
   ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
   ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
   ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
  *time.cloudflare 10.242.8.77  3 u  469 1024  367  234.691   -0.929  67.380
  +2001-44b8-2100- 42.3.115.79  2 u  581 1024  377  487.209  +55.669  57.154
  +2001-44b8-2100- 4.179.66.17  3 u  215 1024  377  489.637  +57.002  35.399
  jonathan@Apollo-Lake-N3450:~$

  NTPsec on Braswell-N3150
  jonathan@Braswell-N3150:~$ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04
  jonathan@Braswell-N3150:~$ ntpq -p
   remote   refid  st t when poll reach 
  delay   offset   jitter
  
===
   0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
  +prod-ntp-5.ntp1.ps5.canonical.com   37.15.221.1892 u  141 1024  367 
383.4932 -19.6895  35.0534
  *time.tfmcloud.au203.35.83.2422 u  325 1024  367 
325.9317  -0.1496  43.0522
  +any.time.nl 133.243.238.243  2 u  158 1024  373 
300.7941 -20.8962 136.1422
  +ntp2.its.waikato.ac.nz  .GPS.1 u  363 1024  377 
356.5361 -18.2740 140.5984
  +2001-44b8-2100-3f00---007b-0004 42.3.115.79  2 u  214 1024  367 
490.3898  28.3416   2.7728
  +tic.ntp.telstra.net 203.35.83.2422 u   13 1024  367 
566.0744 -14.1332   6.0377
  +863xqmprtfqv69pv7nwc.ip6.superloop.au   192.168.1.1  2 u   79 1024  367 
330.2658 -14.3483  16.2172
  +gps-ads.10mrlp.juneks.com.au.PPS.1 u  271 1024  367 
443.4812 -71.8020  44.6332
  +x.ns.gin.ntt.net129.2

[Touch-packages] [Bug 2039252] Re: [needs-packaging] The packages ntp and ntpsec are not equivalent

2023-10-19 Thread Jonathan Ferguson
** Bug watch added: Email to rlaager@debian #
   mailto:rlaa...@debian.org

** Also affects: ntp via
   mailto:rlaa...@debian.org
   Importance: Undecided
   Status: New

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

Title:
  [needs-packaging] The packages ntp and ntpsec are not equivalent

Status in NTP:
  New
Status in ntp package in Ubuntu:
  Confirmed
Status in ntp package in Debian:
  Confirmed

Bug description:
  I recently did an install of Ubuntu 23.04 and then configured ntp as I have 
been doing so for more than 8 years.
  With previous versions of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
  I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with 
the new location of ntp.conf, after restarting I noticed that the resultant 
output was missing requisite details.

  
  Compare the following and the lack of ".MCST." and ".ACST.":

  Original ntp on Apollo-Lake-N3150
  jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  jonathan@Apollo-Lake-N3450:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
   ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
   ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
   ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
  *time.cloudflare 10.242.8.77  3 u  469 1024  367  234.691   -0.929  67.380
  +2001-44b8-2100- 42.3.115.79  2 u  581 1024  377  487.209  +55.669  57.154
  +2001-44b8-2100- 4.179.66.17  3 u  215 1024  377  489.637  +57.002  35.399
  jonathan@Apollo-Lake-N3450:~$

  NTPsec on Braswell-N3150
  jonathan@Braswell-N3150:~$ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04
  jonathan@Braswell-N3150:~$ ntpq -p
   remote   refid  st t when poll reach 
  delay   offset   jitter
  
===
   0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
  +prod-ntp-5.ntp1.ps5.canonical.com   37.15.221.1892 u  141 1024  367 
383.4932 -19.6895  35.0534
  *time.tfmcloud.au203.35.83.2422 u  325 1024  367 
325.9317  -0.1496  43.0522
  +any.time.nl 133.243.238.243  2 u  158 1024  373 
300.7941 -20.8962 136.1422
  +ntp2.its.waikato.ac.nz  .GPS.1 u  363 1024  377 
356.5361 -18.2740 140.5984
  +2001-44b8-2100-3f00---007b-0004 42.3.115.79  2 u  214 1024  367 
490.3898  28.3416   2.7728
  +tic.ntp.telstra.net 203.35.83.2422 u   13 1024  367 
566.0744 -14.1332   6.0377
  +863xqmprtfqv69pv7nwc.ip6.superloop.au   192.168.1.1  2 u   79 1024  367 
330.2658 -14.3483  16.2172
  +gps-ads.10mrlp.juneks.com.au.PPS.1 u  271 1024  367 
443.4812 -71.8020  44.6332
  +x.ns.gin.ntt.net129.250.35.222   2 u   57 1024  367  
22.4974  41.3055   6.0639
  jonathan@Braswell-N3150:~$

  
  This behaviour will affect the following:
  Ubuntu 22.10, 23.04 and 23.10
  Debian 12, 13 and 14

  NTPsec have documented their reasoning for lacking support.
  https://docs.ntpsec.org/latest/discover.html
  https://docs.ntpsec.org/latest/ntpsec.html
  https://docs.ntpsec.org/latest/assoc.html#broad
  https://docs.ntpsec.org/latest/assoc.html#many

  The issue remains that ntp and ntpsec are not capability equivalent.

  I foresee two means of rectifying this predicament, if NTPsec is going
  to be the default implementation of NTP then ntpsec needs to implement
  all of the capabilities of ntp, or the easier alternative is that the
  real ntp https://www.ntp.org/do

[Touch-packages] [Bug 2039252] Re: The packages ntp and ntpsec are not equivalent

2023-10-18 Thread Jonathan Ferguson
** Changed in: ntp (Ubuntu)
   Status: Invalid => Confirmed

** Tags added: needs-packaging

** Changed in: ntp (Debian)
   Status: Invalid => Confirmed

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

Title:
  The packages ntp and ntpsec are not equivalent

Status in ntp package in Ubuntu:
  Confirmed
Status in ntp package in Debian:
  Confirmed

Bug description:
  I recently did an install of Ubuntu 23.04 and then configured ntp as I have 
been doing so for more than 8 years.
  With previous versions of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
  I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with 
the new location of ntp.conf, after restarting I noticed that the resultant 
output was missing requisite details.

  
  Compare the following and the lack of ".MCST." and ".ACST.":

  Original ntp on Apollo-Lake-N3150
  jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  jonathan@Apollo-Lake-N3450:~$ ntpq -p
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
   ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
   ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
   ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
   ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
  *time.cloudflare 10.242.8.77  3 u  469 1024  367  234.691   -0.929  67.380
  +2001-44b8-2100- 42.3.115.79  2 u  581 1024  377  487.209  +55.669  57.154
  +2001-44b8-2100- 4.179.66.17  3 u  215 1024  377  489.637  +57.002  35.399
  jonathan@Apollo-Lake-N3450:~$

  NTPsec on Braswell-N3150
  jonathan@Braswell-N3150:~$ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04
  jonathan@Braswell-N3150:~$ ntpq -p
   remote   refid  st t when poll reach 
  delay   offset   jitter
  
===
   0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
   3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
  +prod-ntp-5.ntp1.ps5.canonical.com   37.15.221.1892 u  141 1024  367 
383.4932 -19.6895  35.0534
  *time.tfmcloud.au203.35.83.2422 u  325 1024  367 
325.9317  -0.1496  43.0522
  +any.time.nl 133.243.238.243  2 u  158 1024  373 
300.7941 -20.8962 136.1422
  +ntp2.its.waikato.ac.nz  .GPS.1 u  363 1024  377 
356.5361 -18.2740 140.5984
  +2001-44b8-2100-3f00---007b-0004 42.3.115.79  2 u  214 1024  367 
490.3898  28.3416   2.7728
  +tic.ntp.telstra.net 203.35.83.2422 u   13 1024  367 
566.0744 -14.1332   6.0377
  +863xqmprtfqv69pv7nwc.ip6.superloop.au   192.168.1.1  2 u   79 1024  367 
330.2658 -14.3483  16.2172
  +gps-ads.10mrlp.juneks.com.au.PPS.1 u  271 1024  367 
443.4812 -71.8020  44.6332
  +x.ns.gin.ntt.net129.250.35.222   2 u   57 1024  367  
22.4974  41.3055   6.0639
  jonathan@Braswell-N3150:~$

  
  This behaviour will affect the following:
  Ubuntu 22.10, 23.04 and 23.10
  Debian 12, 13 and 14

  NTPsec have documented their reasoning for lacking support.
  https://docs.ntpsec.org/latest/discover.html
  https://docs.ntpsec.org/latest/ntpsec.html
  https://docs.ntpsec.org/latest/assoc.html#broad
  https://docs.ntpsec.org/latest/assoc.html#many

  The issue remains that ntp and ntpsec are not capability equivalent.

  I foresee two means of rectifying this predicament, if NTPsec is going
  to be the default implementation of NTP then ntpsec needs to implement
  all of the capabilities of ntp, or the easier alternative is that the
  real ntp https://www.ntp.org/downloads/ is packaged as ntp-classic

[Touch-packages] [Bug 2039252] Re: The packages ntp and ntpsec are not equivalent

2023-10-13 Thread Jonathan Ferguson
** Description changed:

  I recently did an install of Ubuntu 23.04 and then configured ntp as I have 
been doing so for more than 8 years.
- With previous version of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
+ With previous versions of Debian and Ubuntu using the real ntp package, the 
details at https://wiki.ubuntu.com/JonathanFerguson/NTP?action=recall=38 
created the desired results.
  I updated the details at https://wiki.ubuntu.com/JonathanFerguson/NTP with 
the new location of ntp.conf, after restarting I noticed that the resultant 
output was missing requisite details.
- 
  
  Compare the following and the lack of ".MCST." and ".ACST.":
  
  Original ntp on Apollo-Lake-N3150
  jonathan@Apollo-Lake-N3450:~$ lsb_release -rd
  Description:Ubuntu 22.04.3 LTS
  Release:22.04
  jonathan@Apollo-Lake-N3450:~$ ntpq -p
-  remote   refid  st t when poll reach   delay   offset  jitter
+  remote   refid  st t when poll reach   delay   offset  jitter
  ==
-  0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
-  1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
-  2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
-  3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
-  ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
-  ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
-  ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
-  ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
-  ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
+  0.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
+  1.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
+  2.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
+  3.ubuntu.pool.n .POOL.  16 p-   6400.000   +0.000   0.000
+  ntp.ubuntu.com  .POOL.  16 p-   6400.000   +0.000   0.000
+  ntp.mcast.net   .MCST.  16 M-   6400.000   +0.000   0.000
+  ff0e::101   .MCST.  16 M-   6400.000   +0.000   0.000
+  ntp.mcast.net   .ACST.  16 a-   6400.000   +0.000   0.000
+  ff0e::101   .ACST.  16 a-   6400.000   +0.000   0.000
  *time.cloudflare 10.242.8.77  3 u  469 1024  367  234.691   -0.929  67.380
  +2001-44b8-2100- 42.3.115.79  2 u  581 1024  377  487.209  +55.669  57.154
  +2001-44b8-2100- 4.179.66.17  3 u  215 1024  377  489.637  +57.002  35.399
  jonathan@Apollo-Lake-N3450:~$
  
  NTPsec on Braswell-N3150
  jonathan@Braswell-N3150:~$ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04
  jonathan@Braswell-N3150:~$ ntpq -p
-  remote   refid  st t when poll reach 
  delay   offset   jitter
+  remote   refid  st t when poll reach 
  delay   offset   jitter
  
===
-  0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
-  1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
-  2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
-  3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
+  0.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
+  1.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
+  2.ubuntu.pool.ntp.org   .POOL.  16 p-  2560  
 0.   0.   0.0002
+  3.ubuntu.pool.ntp.org   .POOL.  16 p-   640  
 0.   0.   0.0002
  +prod-ntp-5.ntp1.ps5.canonical.com   37.15.221.1892 u  141 1024  367 
383.4932 -19.6895  35.0534
  *time.tfmcloud.au203.35.83.2422 u  325 1024  367 
325.9317  -0.1496  43.0522
  +any.time.nl 133.243.238.243  2 u  158 1024  373 
300.7941 -20.8962 136.1422
  +ntp2.its.waikato.ac.nz  .GPS.1 u  363 1024  377 
356.5361 -18.2740 140.5984
  +2001-44b8-2100-3f00---007b-0004 42.3.115.79  2 u  214 1024  367 
490.3898  28.3416   2.7728
  +tic.ntp.telstra.net 203.35.83.2422 u   13 1024  367 
566.0744 -14.1332   6.0377
  +863xqmprtfqv69pv7

[Touch-packages] [Bug 2033653] [NEW] can't report crash in /var/crash with ubuntu-bug, "Network problem"

2023-08-31 Thread Jonathan Kamens
Public bug reported:

Because of bug #2033652 I was trying to report a gdb crash from
/var/crash. It spent a long time uploading data, then and then popped up
an error dialog:

Network problem
Cannot connect to crash database, please check your internet connection.
HTTP Error ???: Bad gateway

(I don't remember the error code exactly)

I tried again and had a slightly different result: "HTTP Error 503:
Service Unavailable" instead of "Bad gateway".

So... First gimp crashes (bug #2031907). I can't report the crash
properly for it because gimp is wired to catch segfaults instead of
letting the OS handle them. Then gdb crashes (bug #2033652) while I'm
trying to debug the gimp issue. And then I can't report the gdb crash
properly because of THIS issue.

Jolly good all around.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: apport 2.27.0-0ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportLog:
 INFO: apport (pid 639437) 2023-08-31 09:09:01,286: called for pid 639344, 
signal 11, core limit 0, dump mode 1
 INFO: apport (pid 639437) 2023-08-31 09:09:01,288: executable: /usr/bin/gdb 
(command line "gdb /usr/bin/gimp")
 INFO: apport (pid 639437) 2023-08-31 09:09:26,678: wrote report 
/var/crash/_usr_bin_gdb.1000.crash
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 31 09:19:25 2023
InstallationDate: Installed on 2019-01-02 (1702 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apport
UpgradeStatus: Upgraded to mantic on 2023-05-20 (103 days ago)

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


** Tags: amd64 apport-bug mantic

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

Title:
  can't report crash in /var/crash with ubuntu-bug, "Network problem"

Status in apport package in Ubuntu:
  New

Bug description:
  Because of bug #2033652 I was trying to report a gdb crash from
  /var/crash. It spent a long time uploading data, then and then popped
  up an error dialog:

  Network problem
  Cannot connect to crash database, please check your internet connection.
  HTTP Error ???: Bad gateway

  (I don't remember the error code exactly)

  I tried again and had a slightly different result: "HTTP Error 503:
  Service Unavailable" instead of "Bad gateway".

  So... First gimp crashes (bug #2031907). I can't report the crash
  properly for it because gimp is wired to catch segfaults instead of
  letting the OS handle them. Then gdb crashes (bug #2033652) while I'm
  trying to debug the gimp issue. And then I can't report the gdb crash
  properly because of THIS issue.

  Jolly good all around.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   INFO: apport (pid 639437) 2023-08-31 09:09:01,286: called for pid 639344, 
signal 11, core limit 0, dump mode 1
   INFO: apport (pid 639437) 2023-08-31 09:09:01,288: executable: /usr/bin/gdb 
(command line "gdb /usr/bin/gimp")
   INFO: apport (pid 639437) 2023-08-31 09:09:26,678: wrote report 
/var/crash/_usr_bin_gdb.1000.crash
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 09:19:25 2023
  InstallationDate: Installed on 2019-01-02 (1702 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: Upgraded to mantic on 2023-05-20 (103 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2033653/+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 2033652] [NEW] gdb crashes when debugging gimp, can't report crash

2023-08-31 Thread Jonathan Kamens
Public bug reported:

I was debugging gimp when gdb to debug bug #2031907 when gdb crashed on
me and reported a useless backtrace followed by this:

---

A fatal error internal to GDB has been detected, further
debugging is not possible.  GDB will now terminate.

This is a bug, please report it.  For instructions, see:
.

Segmentation fault (core dumped)

---

I attempted to report the crash file in /var/crash rather than just
filing a bare bug like this without any crash info, but ubuntu-bug
failed to report the crash, about which I will file a separate bug
report because that's an apport bug rather than a gdb bug.

I imagine there must be a way to get the crash info to you but I don't
know what it is, so if you have any pointers that would be helpful.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gdb 14.0.50.20230810-0ubuntu1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 31 09:16:17 2023
InstallationDate: Installed on 2019-01-02 (1702 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gdb
UpgradeStatus: Upgraded to mantic on 2023-05-20 (103 days ago)

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


** Tags: amd64 apport-bug mantic

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

Title:
  gdb crashes when debugging gimp, can't report crash

Status in gdb package in Ubuntu:
  New

Bug description:
  I was debugging gimp when gdb to debug bug #2031907 when gdb crashed
  on me and reported a useless backtrace followed by this:

  ---

  A fatal error internal to GDB has been detected, further
  debugging is not possible.  GDB will now terminate.

  This is a bug, please report it.  For instructions, see:
  .

  Segmentation fault (core dumped)

  ---

  I attempted to report the crash file in /var/crash rather than just
  filing a bare bug like this without any crash info, but ubuntu-bug
  failed to report the crash, about which I will file a separate bug
  report because that's an apport bug rather than a gdb bug.

  I imagine there must be a way to get the crash info to you but I don't
  know what it is, so if you have any pointers that would be helpful.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gdb 14.0.50.20230810-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 31 09:16:17 2023
  InstallationDate: Installed on 2019-01-02 (1702 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gdb
  UpgradeStatus: Upgraded to mantic on 2023-05-20 (103 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2033652/+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 1990740] Re: laptop wouldn't wake from sleep

2023-07-06 Thread Jonathan Kamens
I do not see this issue often enough to be able to reproduce it for
troubleshooting purposes. Can't remember the last time I saw it.

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

Title:
  laptop wouldn't wake from sleep

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Shortly after upgrading from Jammy to Kinetic my laptop went to sleep
  after I was idle for 20 minutes, as it is configured to do. The lid
  was closed when the laptop went to sleep. I was unable to wake up the
  laptop. Opening the lid back up should have caused it to wake up but
  did not. Pressing the power button should have caused it to wake up
  but did not.

  Both the LED on the lid and the power button light were cycling on and
  off as they do when the laptop is sleeping.

  I had to hold down the power button for five seconds to power off the
  laptop completely and then power it back on to get it to come back up.

  Never saw this behavior even once with Jammy.

  After rebooting and logging in, I put the laptop to sleep by selecting
  Suspend from the menu, and after _that_ it woke up immediately when I
  pushed the power button.

  I am not sure yet how reproducible this is, but I thought that even a
  single incidence of something like this was worth reporting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu6
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 17:29:50 2022
  InstallationDate: Installed on 2019-08-16 (1135 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20KHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  dmi.bios.date: 04/20/2019
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET63W (1.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.13
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:br1.38:efr1.13:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KH_BU_Think_FM_ThinkPadX1Carbon6th:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.systemd.logind.conf: [modified]
  mtime.conffile..etc.systemd.logind.conf: 2022-09-24T15:20:56.088250

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1990740/+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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

2023-06-21 Thread Jonathan
This issue is also present on Bionic. Is there a chance that the network
manager would be fixed in Bionic, as part of Ubuntu Pro?

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

Title:
  NTP servers from DHCP are not propagated to timesyncd

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager source package in Focal:
  Confirmed

Bug description:
  Network manager gets NTP servers from DHCP but do not update timesyncd to use 
it which keeps using ntp.ubuntu.com.
   
  This is a problem on private networks which do not have access to public 
internet. On this type of network the configuration of timesyncd must be 
updated manually instead of inheriting the conf from the dhcp servers.

  This can be integrated with a NM dispatcher script such as below:

  etc/NetworkManager/dispatcher.d/10-update-timesyncd for example:

  ==8<=8<=8<=8<=8<==
  #! /usr/bin/bash

  [ -n "$CONNECTION_UUID" ] || exit

  INTERFACE=$1
  ACTION=$2

  case $ACTION in
  up | dhcp4-change | dhcp6-change)
  [ -n "$DHCP4_NTP_SERVERS" ] || exit
  mkdir -p /etc/systemd/timesyncd.conf.d/
  cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  [Time]
  NTP=$DHCP4_NTP_SERVERS
  RootDistanceMaxSec=15
  EOF
  systemctl restart systemd-timesyncd
 ;;
  down)
  rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  systemctl restart systemd-timesyncd
  ;;
  esac
  ==8<=8<=8<=8<=8<==

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 28 14:08:52 2021
  InstallationDate: Installed on 2020-05-31 (393 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  RebootRequiredPkgs:
   linux-image-5.11.0-20-generic
   linux-base
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933828/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

2023-05-12 Thread Jonathan Kamens
I mean, the bug is three years old and presumably by now the vast
majority of web sites have renewed their certificates and the new ones
are compatible with SECLEVEL=2 since all of the signing authorities
stopped issuing incompatible ones years ago, so it's kind of moot at
this point.

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

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in OpenSSL:
  Unknown
Status in openssl package in Ubuntu:
  Invalid

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/;)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1864689/+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 2008159] [NEW] `shutdown --show` says suspend is scheduled for (null) after system has suspended and been woken back up

2023-02-22 Thread Jonathan Kamens
Public bug reported:

If you suspend from GNOME, wake your machine back up, and then once it's
totally back up, run `shutdown --show` as root, it says "syspend is
scheduled for (null)". It shouldn't say (null) there, which I suppose is
a different bug, but the bug I'm concerned about is that the message
doesn't clear when the system is woken back up after the suspend.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: systemd-sysv 252.4-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.24.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 22 21:56:45 2023
InstallationDate: Installed on 2019-08-16 (1286 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: systemd
UpgradeStatus: Upgraded to lunar on 2022-11-24 (90 days ago)

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


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

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

Title:
  `shutdown --show` says suspend is scheduled for (null) after system
  has suspended and been woken back up

Status in systemd package in Ubuntu:
  New

Bug description:
  If you suspend from GNOME, wake your machine back up, and then once
  it's totally back up, run `shutdown --show` as root, it says "syspend
  is scheduled for (null)". It shouldn't say (null) there, which I
  suppose is a different bug, but the bug I'm concerned about is that
  the message doesn't clear when the system is woken back up after the
  suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: systemd-sysv 252.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 22 21:56:45 2023
  InstallationDate: Installed on 2019-08-16 (1286 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (90 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2008159/+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 2007413] Re: specifying number of copies doesn't work

2023-02-15 Thread Jonathan Kamens
** Attachment added: "printers.conf"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2007413/+attachment/5647479/+files/printers.conf

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

Title:
  specifying number of copies doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  When printing to the printer "m479" shown in the attached config
  files, specifying the number of copies to print doesn't work, i.e., I
  always get one copy. This is true both from GUI print dialogs and from
  lp on the command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: cups 2.4.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 15 11:18:58 2023
  InstallationDate: Installed on 2019-01-02 (1505 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for driverless: 
dnssd://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipp._tcp.local/?uuid=4fdf33cc-d7b2-45f9-9abe-dae7fdcadfd0
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for m479: 
dnssd://HP%20Color%20LaserJet%20Pro%20M478f-9f%20%5B3279B8%5D._ipp._tcp.local/?uuid=79d14a5b-3a77-5110-ffd7-f7efed848aa6
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/driverless.ppd', '/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/m479.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/driverless.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
   grep: /etc/cups/ppd/m479.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (82 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2007413/+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 2007413] [NEW] specifying number of copies doesn't work

2023-02-15 Thread Jonathan Kamens
Public bug reported:

When printing to the printer "m479" shown in the attached config files,
specifying the number of copies to print doesn't work, i.e., I always
get one copy. This is true both from GUI print dialogs and from lp on
the command line.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: cups 2.4.2-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.24.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 15 11:18:58 2023
InstallationDate: Installed on 2019-01-02 (1505 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lpstat:
 device for driverless: 
dnssd://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipp._tcp.local/?uuid=4fdf33cc-d7b2-45f9-9abe-dae7fdcadfd0
 device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
 device for m479: 
dnssd://HP%20Color%20LaserJet%20Pro%20M478f-9f%20%5B3279B8%5D._ipp._tcp.local/?uuid=79d14a5b-3a77-5110-ffd7-f7efed848aa6
 device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
MachineType: Acer Predator G6-710
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/driverless.ppd', '/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/m479.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/simplex.ppd: Permission denied
 grep: /etc/cups/ppd/driverless.ppd: Permission denied
 grep: /etc/cups/ppd/duplex.ppd: Permission denied
 grep: /etc/cups/ppd/m479.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
Snap.Changes: no changes found
SourcePackage: cups
UpgradeStatus: Upgraded to lunar on 2022-11-24 (82 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug lunar

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

Title:
  specifying number of copies doesn't work

Status in cups package in Ubuntu:
  New

Bug description:
  When printing to the printer "m479" shown in the attached config
  files, specifying the number of copies to print doesn't work, i.e., I
  always get one copy. This is true both from GUI print dialogs and from
  lp on the command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: cups 2.4.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.24.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 15 11:18:58 2023
  InstallationDate: Installed on 2019-01-02 (1505 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for driverless: 
dnssd://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipp._tcp.local/?uuid=4fdf33cc-d7b2-45f9-9abe-dae7fdcadfd0
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for m479: 
dnssd://HP%20Color%20LaserJet%20Pro%20M478f-9f%20%5B3279B8%5D._ipp._tcp.local/?uuid=79d14a5b-3a77-5110-ffd7-f7efed848aa6
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/driverless.ppd', '/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/m479.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/driverless.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
   grep: /etc/cups/ppd/m479.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Snap.Changes: no changes found
  SourcePackage: cups
  UpgradeStatus: Upgraded to lunar on 2022-11-24 (82 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  

[Touch-packages] [Bug 1844897] Re: wifi icon has question mark in it even though network is fine

2022-11-24 Thread Jonathan Kamens
Interestingly, the wifi icon is currently flapping back and forth
between the question mark and the fully connected symbol every few
seconds. If I run nmcli networking connection check in a loop it
switches to "full" when the fully connected symbol is showing and
"portal" when the question mark is showing.

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

Title:
  wifi icon has question mark in it even though network is fine

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After experiencing some "turbulence" in my wifi (I rebooted my primary
  wifi router, which caused my laptop to fallback onto a secondary
  access point which didn't have full connectivity until the primary
  router finished rebooting, then I rebooted the primary router a second
  time), the wifi icon in my top bar stayed as the question-mark icon
  (i.e., the icon that shows when Network Manager doesn't think you have
  full connectivity) even after everything was back up and in fact my
  connectivity was fine.

  Turning wifi off and back on did not cause the question mark to go
  away. Restarting Network Manager did not cause the question mark to go
  away. Switching to a different wifi network and then back to the
  previous one didn't cause the question mark to go away. I had to
  reboot my laptop to get the question mark to go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 21 18:35:48 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (9 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.4.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.4.103 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844897/+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 1844897] Re: wifi icon has question mark in it even though network is fine

2022-11-24 Thread Jonathan Kamens
jik@framework1l:~$ nmcli networking connectivity check
portal
jik@framework1l:~$ 


I'm not using a VPN.

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

Title:
  wifi icon has question mark in it even though network is fine

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After experiencing some "turbulence" in my wifi (I rebooted my primary
  wifi router, which caused my laptop to fallback onto a secondary
  access point which didn't have full connectivity until the primary
  router finished rebooting, then I rebooted the primary router a second
  time), the wifi icon in my top bar stayed as the question-mark icon
  (i.e., the icon that shows when Network Manager doesn't think you have
  full connectivity) even after everything was back up and in fact my
  connectivity was fine.

  Turning wifi off and back on did not cause the question mark to go
  away. Restarting Network Manager did not cause the question mark to go
  away. Switching to a different wifi network and then back to the
  previous one didn't cause the question mark to go away. I had to
  reboot my laptop to get the question mark to go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 21 18:35:48 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (9 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.4.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.4.103 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844897/+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 1990743] Re: resolvconf install fails upgrading from Jammy to Kinetic

2022-10-11 Thread Jonathan Kamens
Given your description, I don't think the upgrade left resolvconf
installed. I think I can my ansible playbook after running the upgrade
and it reinstalled resolvconf which had been uninstalled by the upgrade.
I guess if resolvconf can't be removed yet because of the reverse-
dependencies, then there's nothing more to be done here. :shrug:

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

Title:
  resolvconf install fails upgrading from Jammy to Kinetic

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original 
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1990743/+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 1992463] [NEW] Totem can't play video captured with the "Take a Screenshot" tool

2022-10-11 Thread Jonathan Kamens
Public bug reported:

If I create a 5-second video of my desktop with the "Take a Screenshot"
tool (as an aside, is that tool built into gnome-shell now or something?
I couldn't figure out what executable the app icon corresponds to, i.e.,
I couldn't find the desktop file for it :shrug:) and then open the
resulting webm file which causes it to be opened in the Videos app,
i.e., Totem, the video as shown on the screen is all scrunched up to the
left and in monochrome rather than color. If I play the same video in
mplayer it looks fine. See the attached screenshot which shows a Totem
window and an mplayer window with the same video file open in each.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: libgstreamer1.0-0 1.20.3-1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 11 09:21:21 2022
InstallationDate: Installed on 2022-09-17 (23 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: gstreamer1.0
UpgradeStatus: Upgraded to kinetic on 2022-10-02 (8 days ago)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "Screenshot from 2022-10-11 09-20-54.png"
   
https://bugs.launchpad.net/bugs/1992463/+attachment/5623010/+files/Screenshot%20from%202022-10-11%2009-20-54.png

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

Title:
  Totem can't play video captured with the "Take a Screenshot" tool

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  If I create a 5-second video of my desktop with the "Take a
  Screenshot" tool (as an aside, is that tool built into gnome-shell now
  or something? I couldn't figure out what executable the app icon
  corresponds to, i.e., I couldn't find the desktop file for it :shrug:)
  and then open the resulting webm file which causes it to be opened in
  the Videos app, i.e., Totem, the video as shown on the screen is all
  scrunched up to the left and in monochrome rather than color. If I
  play the same video in mplayer it looks fine. See the attached
  screenshot which shows a Totem window and an mplayer window with the
  same video file open in each.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libgstreamer1.0-0 1.20.3-1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 11 09:21:21 2022
  InstallationDate: Installed on 2022-09-17 (23 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: gstreamer1.0
  UpgradeStatus: Upgraded to kinetic on 2022-10-02 (8 days ago)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1992463/+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 1991598] Re: laptop not reliably going to sleep when lid closed on battery power

2022-10-06 Thread Jonathan Kamens
See: https://github.com/jikamens/remember-the-yubikey

The relevant part here is that the unit file just starts up a shell
script that checks if my YubiKey is plugged in, and if it isn't it
exits.

I don't keep my YubiKey plugged in when the laptop is closed and idle —
and it certainly wasn't plugged in when I observed it staying up for
hours despite being closed and idle before filing this ticket — so I
doubt this is relevant. Also, if it WERE relevant, the problem wouldn't
be intermittent.

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

Title:
  laptop not reliably going to sleep when lid closed on battery power

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

Bug description:
  I have the shell configured to lock the screen when I close the lid
  and go to sleep after 20 idle minutes on battery power.

  Immediately before I opened my laptop and unlocked it to submit this
  bug, the laptop was unplugged from battery power and sitting with the
  lid closed for hours and never went to sleep.

  When I opened the lid I found it locked as it should have been, so
  that's apparently not the issue. The issue is that it just never went
  to sleep even though it was idle for hours.

  This is a regression from Jammy.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  3 21:24:57 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-08-16 (1144 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  RelatedPackageVersions: mutter-common 43.0-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991598/+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 1990863] Re: conversion from sshd service to socket is too bumpy

2022-09-28 Thread Jonathan Kamens
Two ideas, one of which I've already mentioned above:

1) You could migrate the address and port settings from sshd_config to
listen.conf _before_ installing the new sshd_config, so that they will
be preserved even if the config gets replaced with the vendor version
because of a merge conflict like it was in my case.

2) You could have the preinst script detect if the service is currently
enabled and going to be switched to the socket, and if so, pop up an
interactive warning explaining the change and telling the user where to
look for more info, like many other packages do, e.g., the Docker
restart warning. If you'd like you can only display the warning if there
are address or port settings specified in the user's old sshd_config.

Finally, as I said in my original report, "I don't know what the right
answer is here." What I "expect [you] to do" when someone points out an
issue like this is to put some thought into how to make it better rather
than seeming to imply that the person who reported the issue is being
petulant. Putting it another way: neither of the ideas above is rocket
science, and I'm not sure why I should have to be the one to think of
them, rather than the people who are, you know, being paid to do that.

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

Title:
  conversion from sshd service to socket is too bumpy

Status in openssh package in Ubuntu:
  New

Bug description:
  During upgrade from Jammy to Kinetic, I get asked what to do because
  my sshd_config has been modified. I say to do a 3-way merge. It says
  3-way merge fails. I shrug, figure I'll just restore my customizations
  with Ansible after the upgrade like I always do, and tell it to use
  the vendor version of the file. This removes my custom Port settings,
  so they are not migrated over to the ssh.socket settings like
  https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-
  ubuntu-22-10-and-later/30189 says they would be. I subsequently run my
  Ansible which restores the customizations and enables the ssh service,
  but now ssh.service and ssh.socket are enabled at the same time, sshd
  isn't listening on my specified ports, and everything is a mess. I've
  never used socket-based activation before and have no idea how to
  configure it so now I have to go reading man pages, Googling all over
  the place, and generally struggle to figure out what the heck is going
  wrong.

  I don't know what the right answer is here, but I really feel like
  some effort needs to be put into figuring out a smoother transition
  for people who are upgrading to Kinetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1ubuntu6
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 11:41:58 2022
  InstallationDate: Installed on 2019-08-16 (1136 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863/+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 1990863] Re: conversion from sshd service to socket is too bumpy

2022-09-28 Thread Jonathan Kamens
1) Nobody reads the release notes.

2) I am not "overwriting configuration files with 'known good' ones," I
am making specific changes to the config files with ansible plays.
Specifically, before fixing my playbook for Kinetic, it looked like
this:

- name: enable root ssh public key authentication
  lineinfile:
dest: /etc/ssh/sshd_config
line: PermitRootLogin without-password
  register: rootsshyeskey
- name: disable root ssh non-key authentication
  replace:
dest: /etc/ssh/sshd_config
regexp: ^\s*PermitRootLogin(?!.*without-password).*\n?
  register: rootsshnopassword
- name: add default sshd port
  lineinfile:
dest: /etc/ssh/sshd_config
line: 'Port 22'
  when: extra_ssh_port is defined
- name: add additional sshd port
  lineinfile:
dest: /etc/ssh/sshd_config
line: 'Port {{extra_ssh_port}}'
  when: extra_ssh_port is defined
  register: sshdport

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

Title:
  conversion from sshd service to socket is too bumpy

Status in openssh package in Ubuntu:
  New

Bug description:
  During upgrade from Jammy to Kinetic, I get asked what to do because
  my sshd_config has been modified. I say to do a 3-way merge. It says
  3-way merge fails. I shrug, figure I'll just restore my customizations
  with Ansible after the upgrade like I always do, and tell it to use
  the vendor version of the file. This removes my custom Port settings,
  so they are not migrated over to the ssh.socket settings like
  https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-
  ubuntu-22-10-and-later/30189 says they would be. I subsequently run my
  Ansible which restores the customizations and enables the ssh service,
  but now ssh.service and ssh.socket are enabled at the same time, sshd
  isn't listening on my specified ports, and everything is a mess. I've
  never used socket-based activation before and have no idea how to
  configure it so now I have to go reading man pages, Googling all over
  the place, and generally struggle to figure out what the heck is going
  wrong.

  I don't know what the right answer is here, but I really feel like
  some effort needs to be put into figuring out a smoother transition
  for people who are upgrading to Kinetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1ubuntu6
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 11:41:58 2022
  InstallationDate: Installed on 2019-08-16 (1136 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863/+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 1990863] Re: conversion from sshd service to socket is too bumpy

2022-09-27 Thread Jonathan Kamens
Hello,

I am unclear about why you are asking for the contents of my sshd_config
file, given that the problem I described here isn't the merge conflict,
but rather what happens in terms of the migration from ssh service to
socket when the user opts to install the vendor version of sshd_config
as a result of the merge conflict. You're not going to be able to
entirely avoid merge conflicts, so you need to come up with a better way
to handle this conversion, e.g., by migrating the address and port
settings from sshd_config to listen.conf in a preinst script that runs
before dpkg tries to install the new sshd_config.

In any case, I can't tell you exactly what was in my sshd_config before
the problem occurred because, as I indicated, I've upgraded my machine
to Kinetic and in the process replaced sshd_config. However, I believe
it looked approximately like this:


# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options override the
# default value.

Include /etc/ssh/sshd_config.d/*.conf

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key

# Ciphers and keying
#RekeyLimit default none

# Logging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin prohibit-password
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#PubkeyAuthentication yes

# Expect .ssh/authorized_keys2 to be disregarded by default in future.
#AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2

#AuthorizedPrincipalsFile none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
KbdInteractiveAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the KbdInteractiveAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via KbdInteractiveAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and KbdInteractiveAuthentication to 'no'.
UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
PrintMotd no
#PrintLastLog yes
#TCPKeepAlive yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none

# no default banner path
#Banner none

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

# override default of no subsystems
Subsystem   sftp/usr/lib/openssh/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#   X11Forwarding no
#   AllowTcpForwarding no
#   PermitTTY no
#   ForceCommand cvs server
PermitRootLogin without-password
PasswordAuthentication no
Port 22
Port 2223


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

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

Title:
  conversion from sshd service to socket is too bumpy

Status in openssh package in Ubuntu:
  New

Bug description:
  During upgrade from Jammy to Kinetic, I get asked what to do because
  my sshd_config has been modified. I say to do a 3-way merge. It says
  3-way merge fails. I shrug, figure I'll just restore my customizations
  with Ansible after the upgrade like I always do, and tell it to use
  the vendor version of the file. This removes my custom Port settings,
  so they are not migrated 

[Touch-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless

2022-09-27 Thread Jonathan Kamens
It looks like in today's Kinetic update iwd was removed, perhaps because
of this bug?

If so then the removal caused another problem:
/etc/NetworkManager/conf.d/iwd.conf still existed after the iwd package
was removed (I don't understand why, honestly), so even after I unmasked
and re-enabled wpa_supplicant, NetworkManager still thought it was
supposed to be using iwd instead. I had to delete iwd.conf by hand and
restart NetworkManager to regain wifi connectivity.

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+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 1991029] [NEW] network-manager-config-connectivity-ubuntu trying to restart "network-manager" service instead of "NetworkManager"?

2022-09-27 Thread Jonathan Kamens
Public bug reported:

Setting up network-manager-config-connectivity-ubuntu (1.40.0-1ubuntu2) ...
Failed to restart network-manager.service: Unit network-manager.service not 
found.
invoke-rc.d: initscript network-manager, action "force-reload" failed.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: network-manager-config-connectivity-ubuntu 1.40.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 27 20:53:37 2022
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-08-16 (1138 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 192.168.4.1 dev wlan0 proto dhcp src 192.168.4.21 metric 600 
 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
 192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.21 metric 600
PackageArchitecture: all
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: network-manager
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (3 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic

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

Title:
  network-manager-config-connectivity-ubuntu trying to restart "network-
  manager" service instead of "NetworkManager"?

Status in network-manager package in Ubuntu:
  New

Bug description:
  Setting up network-manager-config-connectivity-ubuntu (1.40.0-1ubuntu2) ...
  Failed to restart network-manager.service: Unit network-manager.service not 
found.
  invoke-rc.d: initscript network-manager, action "force-reload" failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager-config-connectivity-ubuntu 1.40.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 27 20:53:37 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1138 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev wlan0 proto dhcp src 192.168.4.21 metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev wlan0 proto kernel scope link src 192.168.4.21 metric 600
  PackageArchitecture: all
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (3 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1991029/+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 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless

2022-09-27 Thread Jonathan Kamens
systemctl disable wpa_supplicant wasn't good enough. I had to mask it.
Before I masked it, something started it on reboot even when it was
disabled (I don't know what was starting it).

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+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 1990891] [NEW] after today's Kinetic updates, WiFi no longer working, so laptop basically useless

2022-09-26 Thread Jonathan Kamens
Public bug reported:

ThinkPad X1 Carbon 6th Gen
WiFi was working fine.
Installed today's batch of Kinetic updates.
Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB 
dongle and plug into my router to be able to submit this bug report).

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: network-manager 1.40.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 26 17:09:25 2022
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-08-16 (1137 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 100 
 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 metric 
100
SourcePackage: network-manager
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic

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

Title:
  after today's Kinetic updates, WiFi no longer working, so laptop
  basically useless

Status in network-manager package in Ubuntu:
  New

Bug description:
  ThinkPad X1 Carbon 6th Gen
  WiFi was working fine.
  Installed today's batch of Kinetic updates.
  Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad 
USB dongle and plug into my router to be able to submit this bug report).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: network-manager 1.40.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 17:09:25 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-16 (1137 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 
100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 
metric 100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.40.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+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 1990863] [NEW] conversion from sshd service to socket is too bumpy

2022-09-26 Thread Jonathan Kamens
Public bug reported:

During upgrade from Jammy to Kinetic, I get asked what to do because my
sshd_config has been modified. I say to do a 3-way merge. It says 3-way
merge fails. I shrug, figure I'll just restore my customizations with
Ansible after the upgrade like I always do, and tell it to use the
vendor version of the file. This removes my custom Port settings, so
they are not migrated over to the ssh.socket settings like
https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-
ubuntu-22-10-and-later/30189 says they would be. I subsequently run my
Ansible which restores the customizations and enables the ssh service,
but now ssh.service and ssh.socket are enabled at the same time, sshd
isn't listening on my specified ports, and everything is a mess. I've
never used socket-based activation before and have no idea how to
configure it so now I have to go reading man pages, Googling all over
the place, and generally struggle to figure out what the heck is going
wrong.

I don't know what the right answer is here, but I really feel like some
effort needs to be put into figuring out a smoother transition for
people who are upgrading to Kinetic.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: openssh-server 1:9.0p1-1ubuntu6
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 26 11:41:58 2022
InstallationDate: Installed on 2019-08-16 (1136 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssh
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago)

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


** Tags: amd64 apport-bug kinetic

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

Title:
  conversion from sshd service to socket is too bumpy

Status in openssh package in Ubuntu:
  New

Bug description:
  During upgrade from Jammy to Kinetic, I get asked what to do because
  my sshd_config has been modified. I say to do a 3-way merge. It says
  3-way merge fails. I shrug, figure I'll just restore my customizations
  with Ansible after the upgrade like I always do, and tell it to use
  the vendor version of the file. This removes my custom Port settings,
  so they are not migrated over to the ssh.socket settings like
  https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation-
  ubuntu-22-10-and-later/30189 says they would be. I subsequently run my
  Ansible which restores the customizations and enables the ssh service,
  but now ssh.service and ssh.socket are enabled at the same time, sshd
  isn't listening on my specified ports, and everything is a mess. I've
  never used socket-based activation before and have no idea how to
  configure it so now I have to go reading man pages, Googling all over
  the place, and generally struggle to figure out what the heck is going
  wrong.

  I don't know what the right answer is here, but I really feel like
  some effort needs to be put into figuring out a smoother transition
  for people who are upgrading to Kinetic.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: openssh-server 1:9.0p1-1ubuntu6
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 11:41:58 2022
  InstallationDate: Installed on 2019-08-16 (1136 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1990863/+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 1990743] Re: resolvconf install fails upgrading from Jammy to Kinetic

2022-09-25 Thread Jonathan Kamens
*shrug* I've had this computer since 2016 and when I first set it up I
used resolvconf to configure it and have continued to do that.

It's no skin off my nose—if it's deprecated I'll find something else to
use—but it seems to me that if you're going to keep the package in the
repository you should fix bugs in it. 路

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

Title:
  resolvconf install fails upgrading from Jammy to Kinetic

Status in resolvconf package in Ubuntu:
  Incomplete

Bug description:
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original 
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1990743/+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 1990743] [NEW] resolvconf install fails upgrading from Jammy to Kinetic

2022-09-24 Thread Jonathan Kamens
Public bug reported:

Setting up resolvconf (1.91ubuntu1) ...
cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
dpkg: error processing package resolvconf (--configure):
 installed resolvconf package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 resolvconf
E: Sub-process /usr/bin/dpkg returned an error code (1)
$ ls -l /etc/resolvconf/resolv.conf.d/original 
lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: resolvconf 1.91ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 24 18:48:31 2022
InstallationDate: Installed on 2019-01-02 (1361 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
PackageArchitecture: all
SourcePackage: resolvconf
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

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


** Tags: amd64 apport-bug kinetic

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

Title:
  resolvconf install fails upgrading from Jammy to Kinetic

Status in resolvconf package in Ubuntu:
  New

Bug description:
  Setting up resolvconf (1.91ubuntu1) ...
  cp: not writing through dangling symlink 
'/etc/resolvconf/resolv.conf.d/original'
  dpkg: error processing package resolvconf (--configure):
   installed resolvconf package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  $ ls -l /etc/resolvconf/resolv.conf.d/original 
  lrwxrwxrwx 1 root root 39 Jan  2  2019 /etc/resolvconf/resolv.conf.d/original 
-> ../run/systemd/resolve/stub-resolv.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: resolvconf 1.91ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 18:48:31 2022
  InstallationDate: Installed on 2019-01-02 (1361 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  modified.conffile..etc.resolvconf.resolv.conf.d.base: [modified]
  modified.conffile..etc.resolvconf.update.d.dnscache: [deleted]
  mtime.conffile..etc.resolvconf.resolv.conf.d.base: 2019-01-02T12:33:18.553144

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1990743/+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 1990740] [NEW] laptop wouldn't wake from sleep

2022-09-24 Thread Jonathan Kamens
Public bug reported:

Shortly after upgrading from Jammy to Kinetic my laptop went to sleep
after I was idle for 20 minutes, as it is configured to do. The lid was
closed when the laptop went to sleep. I was unable to wake up the
laptop. Opening the lid back up should have caused it to wake up but did
not. Pressing the power button should have caused it to wake up but did
not.

Both the LED on the lid and the power button light were cycling on and
off as they do when the laptop is sleeping.

I had to hold down the power button for five seconds to power off the
laptop completely and then power it back on to get it to come back up.

Never saw this behavior even once with Jammy.

After rebooting and logging in, I put the laptop to sleep by selecting
Suspend from the menu, and after _that_ it woke up immediately when I
pushed the power button.

I am not sure yet how reproducible this is, but I thought that even a
single incidence of something like this was worth reporting.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: systemd 251.4-1ubuntu6
ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
Uname: Linux 5.19.0-15-generic x86_64
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 24 17:29:50 2022
InstallationDate: Installed on 2019-08-16 (1135 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20KHCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
dmi.bios.date: 04/20/2019
dmi.bios.release: 1.38
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET63W (1.38 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.13
dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:br1.38:efr1.13:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KH_BU_Think_FM_ThinkPadX1Carbon6th:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO
modified.conffile..etc.systemd.logind.conf: [modified]
mtime.conffile..etc.systemd.logind.conf: 2022-09-24T15:20:56.088250

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


** Tags: amd64 apport-bug kinetic

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

Title:
  laptop wouldn't wake from sleep

Status in systemd package in Ubuntu:
  New

Bug description:
  Shortly after upgrading from Jammy to Kinetic my laptop went to sleep
  after I was idle for 20 minutes, as it is configured to do. The lid
  was closed when the laptop went to sleep. I was unable to wake up the
  laptop. Opening the lid back up should have caused it to wake up but
  did not. Pressing the power button should have caused it to wake up
  but did not.

  Both the LED on the lid and the power button light were cycling on and
  off as they do when the laptop is sleeping.

  I had to hold down the power button for five seconds to power off the
  laptop completely and then power it back on to get it to come back up.

  Never saw this behavior even once with Jammy.

  After rebooting and logging in, I put the laptop to sleep by selecting
  Suspend from the menu, and after _that_ it woke up immediately when I
  pushed the power button.

  I am not sure yet how reproducible this is, but I thought that even a
  single incidence of something like this was worth reporting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: systemd 251.4-1ubuntu6
  ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0
  Uname: Linux 5.19.0-15-generic x86_64
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 24 17:29:50 2022
  InstallationDate: Installed on 2019-08-16 (1135 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20KHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to kinetic on 2022-09-24 (0 days ago)
  dmi.bios.date: 04/20/2019
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET63W (1.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 

[Touch-packages] [Bug 1977512] [NEW] package linux-firmware 1.187.31 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2022-06-03 Thread Jonathan Baumann
Public bug reported:

Same issue as reported before for other versions.
Here 1.187.31

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.31
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gdm1265 F pulseaudio
  jomini 1780 F pulseaudio
 /dev/snd/controlC0:  gdm1265 F pulseaudio
  jomini 1780 F pulseaudio
CasperMD5CheckResult: skip
Date: Fri Jun  3 08:56:22 2022
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-12-03 (546 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20BECTO1WW
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-40-generic 
root=UUID=8977a535-929a-4a34-b7a2-2b906d8dd2d3 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.31 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: 06/03/2021
dmi.bios.release: 2.39
dmi.bios.vendor: LENOVO
dmi.bios.version: GMET91WW (2.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BECTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.15
dmi.modalias: 
dmi:bvnLENOVO:bvrGMET91WW(2.39):bd06/03/2021:br2.39:efr1.15:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20BE:
dmi.product.family: ThinkPad T540p
dmi.product.name: 20BECTO1WW
dmi.product.sku: LENOVO_MT_20BE
dmi.product.version: ThinkPad T540p
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package focal

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

Title:
  package linux-firmware 1.187.31 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Same issue as reported before for other versions.
  Here 1.187.31

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.31
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1265 F pulseaudio
jomini 1780 F pulseaudio
   /dev/snd/controlC0:  gdm1265 F pulseaudio
jomini 1780 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Jun  3 08:56:22 2022
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-12-03 (546 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20BECTO1WW
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-40-generic 
root=UUID=8977a535-929a-4a34-b7a2-2b906d8dd2d3 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.31 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: 06/03/2021
  dmi.bios.release: 2.39
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET91WW (2.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 

[Touch-packages] [Bug 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer

2022-05-07 Thread Jonathan Kamens
Yes, the print job in question works when I print it to the driverless printer.
I would not say that it is therefore reasonable to declare that this issue is 
resolved, but *shrug* whatever.

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

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  I have a printer named "duplex" configured to print through CUPS
  PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
  (recommended)", "DeviceURI
  socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
  same physical printer configured driverless in CUPS with a different
  name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
  1.28.15", "DeviceURI
  implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
  browsed-dest-printer "1625
  ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
  pdf 600dpi"") in printers.conf.

  The attached file prints just fine when sent to the latter printer,
  i.e., prints fine with driverless printing, but fails to print when
  sent through the CUPS Postscript renderer, i.e., the former printer.
  In particular, the file stops printing after four pages and then the
  printer spits out this error page:

  ERROR:
  typecheck
  OFFENDING-COMMAND:
  known

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 08:21:44 2022
  InstallationDate: Installed on 2019-01-02 (1195 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
   grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+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 1971232] [NEW] [Dell XPS 8940] [ALC3861] No audio from headset mic when plugged into front panel jack, works under Windows

2022-05-03 Thread Jonathan Yip
Public bug reported:

There is no audio coming from the headset mic when plugged into the
front panel headset jack (bog standard wired headphones with mic, Sony
MDR-EX15AP). Upon plugging in Gnome should offer a choice of "Headset"
amongst others, but the only ones available are "Headphones" and
"Microphone", neither of which enables the mic on the headset. The same
headset works under Windows, so it shouldn't be an issue of mismatching
TRRS.

I'm happy to provide any further details if needed.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jonathan   8896 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue May  3 13:54:25 2022
InstallationDate: Installed on 2021-08-16 (260 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jonathan   8896 F pulseaudio
Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all
UpgradeStatus: Upgraded to jammy on 2022-04-27 (5 days ago)
dmi.bios.date: 03/29/2022
dmi.bios.release: 2.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.5.1
dmi.board.name: 0427JK
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd03/29/2022:br2.5:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
dmi.product.family: XPS
dmi.product.name: XPS 8940
dmi.product.sku: 09C5
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.modprobe.d.alsa-base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-04-28T14:25:53.371743

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


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

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

Title:
  [Dell XPS 8940] [ALC3861] No audio from headset mic when plugged into
  front panel jack, works under Windows

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  There is no audio coming from the headset mic when plugged into the
  front panel headset jack (bog standard wired headphones with mic, Sony
  MDR-EX15AP). Upon plugging in Gnome should offer a choice of "Headset"
  amongst others, but the only ones available are "Headphones" and
  "Microphone", neither of which enables the mic on the headset. The
  same headset works under Windows, so it shouldn't be an issue of
  mismatching TRRS.

  I'm happy to provide any further details if needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jonathan   8896 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue May  3 13:54:25 2022
  InstallationDate: Installed on 2021-08-16 (260 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jonathan   8896 F pulseaudio
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, recording] No sound at all
  UpgradeStatus: Upgraded to jammy on 2022-04-27 (5 days ago)
  dmi.bios.date: 03/29/2022
  dmi.bios.release: 2.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.1
  dmi.board.name: 0427JK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.1:bd03/29/2022:br2.5:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
  dmi.product.family: XPS
  dmi.product.name: XPS 8940
  dmi.product.sku: 09C5
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.modprobe.d.alsa-base.conf: [modif

[Touch-packages] [Bug 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer

2022-04-12 Thread Jonathan Kamens
>Do you have cups-filter 1.28.15 installed

Yes, and I rebooted after installing it just to make sure. Problem
persists.

>Or did you try the option "pdftops-renderer=gs" as described there and
which you confirmed as fixing that bug?

I _also_ have this setting in my printers.conf. So clearly this bug is
different from that one.

> Generally, driverless printing is more reliable than PostScript
printing. PostScript interpreters in printers often have bugs.

These two statements seem to be contradictory. If driverless printing is
more reliable, that would seem to imply that files sent directly to the
printer print more reliably than files sent through the CUPS filters,
which would seem to imply that it is the filters, not the printer, that
have bugs.

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

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

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

Status in cups package in Ubuntu:
  New

Bug description:
  I have a printer named "duplex" configured to print through CUPS
  PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
  (recommended)", "DeviceURI
  socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
  same physical printer configured driverless in CUPS with a different
  name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
  1.28.15", "DeviceURI
  implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
  browsed-dest-printer "1625
  ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
  pdf 600dpi"") in printers.conf.

  The attached file prints just fine when sent to the latter printer,
  i.e., prints fine with driverless printing, but fails to print when
  sent through the CUPS Postscript renderer, i.e., the former printer.
  In particular, the file stops printing after four pages and then the
  printer spits out this error page:

  ERROR:
  typecheck
  OFFENDING-COMMAND:
  known

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 08:21:44 2022
  InstallationDate: Installed on 2019-01-02 (1195 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
   grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+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 1968722] Re: File fails to print when rendered with CUPS, prints fine when fed directly to printer

2022-04-12 Thread Jonathan Kamens
Here's my printers.conf, since it doesn't look like ubuntu-bug attached
it, and there's no sensitive information in it.


** Attachment added: "printers.conf"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+attachment/5579950/+files/printers.conf

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

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

Status in cups package in Ubuntu:
  New

Bug description:
  I have a printer named "duplex" configured to print through CUPS
  PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
  (recommended)", "DeviceURI
  socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
  same physical printer configured driverless in CUPS with a different
  name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
  1.28.15", "DeviceURI
  implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
  browsed-dest-printer "1625
  ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
  pdf 600dpi"") in printers.conf.

  The attached file prints just fine when sent to the latter printer,
  i.e., prints fine with driverless printing, but fails to print when
  sent through the CUPS Postscript renderer, i.e., the former printer.
  In particular, the file stops printing after four pages and then the
  printer spits out this error page:

  ERROR:
  typecheck
  OFFENDING-COMMAND:
  known

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 08:21:44 2022
  InstallationDate: Installed on 2019-01-02 (1195 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
   grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1968722/+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 1968722] [NEW] File fails to print when rendered with CUPS, prints fine when fed directly to printer

2022-04-12 Thread Jonathan Kamens
Public bug reported:

I have a printer named "duplex" configured to print through CUPS
PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
(recommended)", "DeviceURI socket://m551dn.kamens.brookline.ma.us:9100"
in printers.conf) and the same physical printer configured driverless in
CUPS with a different name ("MakeModel HP LaserJet 500 color M551,
driverless, cups-filters 1.28.15", "DeviceURI
implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
browsed-dest-printer "1625
ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
pdf 600dpi"") in printers.conf.

The attached file prints just fine when sent to the latter printer,
i.e., prints fine with driverless printing, but fails to print when sent
through the CUPS Postscript renderer, i.e., the former printer. In
particular, the file stops printing after four pages and then the
printer spits out this error page:

ERROR:
typecheck
OFFENDING-COMMAND:
known

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 12 08:21:44 2022
InstallationDate: Installed on 2019-01-02 (1195 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lpstat:
 device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
 device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
 device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
MachineType: Acer Predator G6-710
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
 grep: /etc/cups/ppd/duplex.ppd: Permission denied
 grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-02-20 (50 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug jammy

** Attachment added: "comics.pdf"
   https://bugs.launchpad.net/bugs/1968722/+attachment/5579931/+files/comics.pdf

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

Title:
  File fails to print when rendered with CUPS, prints fine when fed
  directly to printer

Status in cups package in Ubuntu:
  New

Bug description:
  I have a printer named "duplex" configured to print through CUPS
  PostScript rendering ("MakeModel HP LaserJet 500 color M551 Postscript
  (recommended)", "DeviceURI
  socket://m551dn.kamens.brookline.ma.us:9100" in printers.conf) and the
  same physical printer configured driverless in CUPS with a different
  name ("MakeModel HP LaserJet 500 color M551, driverless, cups-filters
  1.28.15", "DeviceURI
  implicitclass://HP_LaserJet_500_color_M551_1637DA/", "Option cups-
  browsed-dest-printer "1625
  ipps://HP%20LaserJet%20500%20color%20M551%20%5B1637DA%5D._ipps._tcp.local/
  pdf 600dpi"") in printers.conf.

  The attached file prints just fine when sent to the latter printer,
  i.e., prints fine with driverless printing, but fails to print when
  sent through the CUPS Postscript renderer, i.e., the former printer.
  In particular, the file stops printing after four pages and then the
  printer spits out this error page:

  ERROR:
  typecheck
  OFFENDING-COMMAND:
  known

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 12 08:21:44 2022
  InstallationDate: Installed on 2019-01-02 (1195 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex: 

[Touch-packages] [Bug 1967816] Re: PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it

2022-04-05 Thread Jonathan Kamens
The file prints with pdftops-renderer=gs.

I can fix this for me personally, but is there any way to adjust the
default CUPS configuration for the type of printer that I have to make
this setting the default for others with the same printer, so they don't
also run into this issue?


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

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

Title:
  PDF file completely silently fails to print, computer claims it
  printed, printer shows no trace of it

Status in cups package in Ubuntu:
  New

Bug description:
  I have an HP LaserJet M551dn printer which usually works just fine
  with CUPS. Tonight, however, I discovered that I was completely unable
  to print one particular PDF file (unfortunately I can't provide you
  with the file because it's a scan of a tax form with PII on it). CUPS
  claimed that it printed the file and there are no errors in the log.
  On the other side, the printer doesn't show any trace of the file
  haven't been sent to it. The print job isn't in the job log, and at no
  point while CUPS claims it's printing does the printer make any noise
  or any of its lights blink as they usually do when a job is being sent
  to it.

  I don't know how to debug this further. I'm attaching the section of
  /var/log/cups/error_log from the attempt to print the file.

  This is reproducible every time with this particular file, including
  immediately after updating to all current Jammy packages and
  rebooting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  4 20:51:23 2022
  InstallationDate: Installed on 2019-01-02 (1188 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
   grep: /etc/cups/ppd/duplex.ppd: Permission denied
   grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1967816/+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 1967816] [NEW] PDF file completely silently fails to print, computer claims it printed, printer shows no trace of it

2022-04-04 Thread Jonathan Kamens
Public bug reported:

I have an HP LaserJet M551dn printer which usually works just fine with
CUPS. Tonight, however, I discovered that I was completely unable to
print one particular PDF file (unfortunately I can't provide you with
the file because it's a scan of a tax form with PII on it). CUPS claimed
that it printed the file and there are no errors in the log. On the
other side, the printer doesn't show any trace of the file haven't been
sent to it. The print job isn't in the job log, and at no point while
CUPS claims it's printing does the printer make any noise or any of its
lights blink as they usually do when a job is being sent to it.

I don't know how to debug this further. I'm attaching the section of
/var/log/cups/error_log from the attempt to print the file.

This is reproducible every time with this particular file, including
immediately after updating to all current Jammy packages and rebooting.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: cups 2.4.1op1-1ubuntu4
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu80
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  4 20:51:23 2022
InstallationDate: Installed on 2019-01-02 (1188 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lpstat:
 device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
 device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
 device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
MachineType: Acer Predator G6-710
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', 
'/etc/cups/ppd/duplex.ppd', 
'/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/simplex.ppd: Permission denied
 grep: /etc/cups/ppd/duplex.ppd: Permission denied
 grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA.ppd: Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-23-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: Upgraded to jammy on 2022-02-20 (43 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:sku:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug jammy

** Attachment added: "/var/log/cups/error_log excerpt"
   https://bugs.launchpad.net/bugs/1967816/+attachment/5577050/+files/error_log

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

Title:
  PDF file completely silently fails to print, computer claims it
  printed, printer shows no trace of it

Status in cups package in Ubuntu:
  New

Bug description:
  I have an HP LaserJet M551dn printer which usually works just fine
  with CUPS. Tonight, however, I discovered that I was completely unable
  to print one particular PDF file (unfortunately I can't provide you
  with the file because it's a scan of a tax form with PII on it). CUPS
  claimed that it printed the file and there are no errors in the log.
  On the other side, the printer doesn't show any trace of the file
  haven't been sent to it. The print job isn't in the job log, and at no
  point while CUPS claims it's printing does the printer make any noise
  or any of its lights blink as they usually do when a job is being sent
  to it.

  I don't know how to debug this further. I'm attaching the section of
  /var/log/cups/error_log from the attempt to print the file.

  This is reproducible every time with this particular file, including
  immediately after updating to all current Jammy packages and
  rebooting.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  4 20:51:23 2022
  InstallationDate: Installed on 2019-01-02 (1188 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lpstat:
   device for duplex: socket://m551dn.kamens.brookline.ma.us:9100
   device for HP_LaserJet_500_color_M551_1637DA: 
implicitclass://HP_LaserJet_500_color_M551_1637DA/
   device for simplex: socket://m551dn.kamens.brookline.ma.us:9100
  MachineType: Acer Predator G6-710
  

[Touch-packages] [Bug 1967315] [NEW] package linux-firmware 1.187.29 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2022-03-31 Thread Jonathan Baumann
Public bug reported:

While installing full upgrade from terminal - sudo apt full-upgrade

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.29
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Mar 31 10:45:37 2022
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-12-03 (482 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20BECTO1WW
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic 
root=UUID=8977a535-929a-4a34-b7a2-2b906d8dd2d3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.29 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: 06/03/2021
dmi.bios.release: 2.39
dmi.bios.vendor: LENOVO
dmi.bios.version: GMET91WW (2.39 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BECTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.15
dmi.modalias: 
dmi:bvnLENOVO:bvrGMET91WW(2.39):bd06/03/2021:br2.39:efr1.15:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20BE:
dmi.product.family: ThinkPad T540p
dmi.product.name: 20BECTO1WW
dmi.product.sku: LENOVO_MT_20BE
dmi.product.version: ThinkPad T540p
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package focal

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

Title:
  package linux-firmware 1.187.29 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  While installing full upgrade from terminal - sudo apt full-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.29
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Mar 31 10:45:37 2022
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-12-03 (482 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: LENOVO 20BECTO1WW
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-35-generic 
root=UUID=8977a535-929a-4a34-b7a2-2b906d8dd2d3 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.29 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: 06/03/2021
  dmi.bios.release: 2.39
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET91WW (2.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET91WW(2.39):bd06/03/2021:br2.39:efr1.15:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20BE:
  dmi.product.family: ThinkPad T540p
  dmi.product.name: 20BECTO1WW
  dmi.product.sku: LENOVO_MT_20BE
  dmi.product.version: ThinkPad T540p
  

[Touch-packages] [Bug 1864215] Re: Please add webp loader to gdk-pixbuf

2022-03-09 Thread Jonathan Yip
In case you don't want to wait for aruiz's loader to be packaged in Debian (and 
then trickled down to Ubuntu), here's a PPA:
https://code.launchpad.net/~helkaluin/+archive/ubuntu/webp-pixbuf-loader

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

Title:
  Please add webp loader to gdk-pixbuf

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Confirmed
Status in gdk-pixbuf package in Baltix:
  Triaged
Status in Debian:
  New

Bug description:
  Attempting to load a webp image -- for instance, 

https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp
  or

https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg
  -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file 
format" error.

  Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in
  libwebp, but isn't this really a gdk-pixbuf issue? If it really does
  belong to libwebp, my apologies, please dup this bug to 1407644 (I'm
  confident it doesn't belong to eog since I don't use that program; I
  have other programs that use libgdk-pixbuf).

  You can probably use eog to test this, or run
  /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i 
webp
  (I assume the loader would mention webp if there was a loader for it).

  I have these packages installed in addition to libgdk-pixbuf2.0-0:
  libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes
  the format:

  $ file /tmp/FKK78W.jpg.webp
  /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 
1200x533, Scaling: [none]x[none], YUV color, decoders should clamp

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  Date: Fri Feb 21 08:48:36 2020
  InstallationDate: Installed on 2019-10-10 (133 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  SourcePackage: gdk-pixbuf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+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 1960508] [NEW] glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386

2022-02-10 Thread Jonathan Camara
Public bug reported:

After running "sudo apt upgrade" and approving the listed packages, the
following error occurred after unpacking a number of packages:

dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:

 
 libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however:

 
  Package libmount1:i386 is not configured yet.

output from "dpkg-reconfigure libmount1:i386":

/usr/sbin/dpkg-reconfigure: libmount1:i386 is broken or not fully
installed

output from "sudo apt install libmount1:i386":

Reading package lists... Done   

 
Building dependency tree... Done

 
Reading state information... Done   

 
libmount1:i386 is already the newest version (2.36.1-8ubuntu2.2).
...

output from "sudo apt reinstall libmount1:i386":

E: Internal Error, No file name for libmount1:i386

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: impish

** Tags added: impish

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

Title:
  glib2.0-0:i386 breaks installation due to unconfigured libmount1:i386

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  After running "sudo apt upgrade" and approving the listed packages,
  the following error occurred after unpacking a number of packages:

  dpkg: dependency problems prevent processing triggers for libglib2.0-0:i386:  

   
   libglib2.0-0:i386 depends on libmount1 (>= 2.35.2-7~); however:  

   
Package libmount1:i386 is not configured yet.

  output from "dpkg-reconfigure libmount1:i386":

  /usr/sbin/dpkg-reconfigure: libmount1:i386 is broken or not fully
  installed

  output from "sudo apt install libmount1:i386":

  Reading package lists... Done 

   
  Building dependency tree... Done  

   
  Reading state information... Done 

   
  libmount1:i386 is already the newest version (2.36.1-8ubuntu2.2).
  ...

  output from "sudo apt reinstall libmount1:i386":

  E: Internal Error, No file name for libmount1:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1960508/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

2021-10-03 Thread Jonathan White
To expand on the above, have the Firefox and snapd developers figured
out how to incorporate native messaging in a snap-based browser? You
guys are locking out a significant portion of useful extensions if not
figured out.

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

Title:
  [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Impish:
  Fix Released
Status in ubuntu-release-upgrader source package in Impish:
  Fix Released
Status in ubuntu-settings source package in Impish:
  Fix Released

Bug description:
  Per Canonical's distribution agreement with Mozilla, we're making the
  snap¹ the default installation of firefox on desktop ISOs starting
  with Ubuntu 21.10.

  The snap is built and published for amd64, armhf and arm64. It is
  jointly maintained by Mozilla and the Ubuntu desktop team, and
  published by Mozilla.

  This requires updating the desktop-minimal seed, as well as ubuntu-
  release-upgrader.

  ¹ https://snapcraft.io/firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1796758] Re: Because gnome-terminal-server is launched by systemd --user, logging out and back in doesn't reinit groups

2021-07-02 Thread Jonathan Kamens
This is still a problem but I'm not convinced it's enough of a problem
to warrant reopening the ticket.

I run into this because my `systemd --user` process persists between
logins because I have persistent service units running under it. For
most people `systemd --user` will exit when they log out, so for most
people, logging out and logging back in will indeed reset their groups.

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

Title:
  Because gnome-terminal-server is launched by systemd --user, logging
  out and back in doesn't reinit groups

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Since the beginning of time, the way to apply changes to one's group
  memberships in UNIX has been to log out and log back in again.

  In current Ubuntu, that doesn't work. When you add yourself to a
  group, close all of your windows, log out, log back in again, and open
  a new gnome-terminal window, and your group memberships will be the
  same as before.

  This is because gnome-terminal processes are launched by gnome-
  terminal-server, which is launched by systemd --user, which doesn't
  exit when you log out.

  One possible fix would be to have the systemd init process (i.e.,
  process 1) detect when group memberships have changed and re-launch
  the systemd --user processes for the users whose groups have changed.
  Another fix would be to kill systemd --user processes upon logout and
  have systemd re-launch them.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct  8 16:11:13 2018
  InstallationDate: Installed on 2018-09-27 (11 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/vgencrypted-lvencryptedroot ro quiet splash 
psmouse.synaptics_intertouch=1 vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET55W(1.30):bd08/31/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.systemd.logind.conf: [modified]
  mtime.conffile..etc.systemd.logind.conf: 2018-09-27T11:40:55.615410

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796758/+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 1916418] Re: Custom properties set with ENV{WHATEVER} in parent no longer imported with IMPORT{parent} in udev rule

2021-05-27 Thread Jonathan Kamens
This appears to no longer be an issue with the current versions of
systemd and udev in 21.04.


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

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

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

Title:
  Custom properties set with ENV{WHATEVER} in parent no longer imported
  with IMPORT{parent} in udev rule

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Invalid
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  DisplayLink uses these udev rules to start the displaylink service
  when a displaylink device is plugged in:

  ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
  ATTR{idVendor}=="17e9", IMPORT{builtin}="usb_id",
  ENV{DISPLAYLINK_DEVNAME}="$env{DEVNAME}",
  
ENV{DISPLAYLINK_DEVICE_ID}="$env{ID_BUS}-$env{BUSNUM}-$env{DEVNUM}-$env{ID_SERIAL}",
  ENV{REMOVE_CMD}="/opt/displaylink/udev.sh $root
  $env{DISPLAYLINK_DEVICE_ID} $env{DISPLAYLINK_DEVNAME}"

  ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
  ATTRS{idVendor}=="17e9", ATTR{bInterfaceClass}=="ff",
  ATTR{bInterfaceProtocol}=="03", IMPORT{parent}="DISPLAYLINK*",
  RUN+="/opt/displaylink/udev.sh $root $env{DISPLAYLINK_DEVICE_ID}
  $env{DISPLAYLINK_DEVNAME}"

  The important thing to note here is that the first rule is for the
  device that is the parent of the device triggers the second rule, and
  the first rule sets ENV{DISPLAYLINK_DEVNAME} and
  ENV{DISPLAYLINK_DEVICE_ID}, and the second rule attempts to import
  them with IMPORT{parent} and then use them.

  This worked fine in 20.04.

  It does not work in 21.04.

  When the second rule is triggered, DISPLAYLINK_DEVICE_ID and
  DISPLAYLINK_DEVNAME are not set.

  I have confirmed via udevadm monitor that the variables are getting
  set on the parent.

  I have confirmed via udevadm info --attribute-walk that the device
  triggering the second rule is the child of the device triggering the
  first one.

  I have tried to import the variables explicitly instead of using a
  glob pattern and that doesn't work either.

  When I modify the rule to import DEVNAME, ID_BUS, BUSNUM, DEVNUM, and
  ID_SERIAL directly, that works. The problem appears to be that these
  custom properties we are setting in the parent can't be imported in
  the child.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: udev 247.3-1ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 60-brother-libsane-type1.rules 99-displaylink.rules~ 
70-snap.core.rules 70-snap.snap-store.rules 99-x10.rules 
60-brother-brscan4-libsane-type1.rules 50-yubikey.rules 
70-snap.canonical-livepatch.rules 70-snap.gnome-system-monitor.rules 
70-snap.chromium.rules 99-displaylink.rules
  Date: Sun Feb 21 19:21:20 2021
  InstallationDate: Installed on 2019-01-02 (781 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to hirsute on 2021-02-21 (0 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1916418/+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 1916418] Re: Custom properties set with ENV{WHATEVER} in parent no longer imported with IMPORT{parent} in udev rule

2021-05-25 Thread Jonathan Kamens
Please tell me specifically how to enable debug and afterward capture
the logs that you want to see.

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

Title:
  Custom properties set with ENV{WHATEVER} in parent no longer imported
  with IMPORT{parent} in udev rule

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Focal:
  Invalid
Status in systemd source package in Groovy:
  Incomplete

Bug description:
  DisplayLink uses these udev rules to start the displaylink service
  when a displaylink device is plugged in:

  ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
  ATTR{idVendor}=="17e9", IMPORT{builtin}="usb_id",
  ENV{DISPLAYLINK_DEVNAME}="$env{DEVNAME}",
  
ENV{DISPLAYLINK_DEVICE_ID}="$env{ID_BUS}-$env{BUSNUM}-$env{DEVNUM}-$env{ID_SERIAL}",
  ENV{REMOVE_CMD}="/opt/displaylink/udev.sh $root
  $env{DISPLAYLINK_DEVICE_ID} $env{DISPLAYLINK_DEVNAME}"

  ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
  ATTRS{idVendor}=="17e9", ATTR{bInterfaceClass}=="ff",
  ATTR{bInterfaceProtocol}=="03", IMPORT{parent}="DISPLAYLINK*",
  RUN+="/opt/displaylink/udev.sh $root $env{DISPLAYLINK_DEVICE_ID}
  $env{DISPLAYLINK_DEVNAME}"

  The important thing to note here is that the first rule is for the
  device that is the parent of the device triggers the second rule, and
  the first rule sets ENV{DISPLAYLINK_DEVNAME} and
  ENV{DISPLAYLINK_DEVICE_ID}, and the second rule attempts to import
  them with IMPORT{parent} and then use them.

  This worked fine in 20.04.

  It does not work in 21.04.

  When the second rule is triggered, DISPLAYLINK_DEVICE_ID and
  DISPLAYLINK_DEVNAME are not set.

  I have confirmed via udevadm monitor that the variables are getting
  set on the parent.

  I have confirmed via udevadm info --attribute-walk that the device
  triggering the second rule is the child of the device triggering the
  first one.

  I have tried to import the variables explicitly instead of using a
  glob pattern and that doesn't work either.

  When I modify the rule to import DEVNAME, ID_BUS, BUSNUM, DEVNUM, and
  ID_SERIAL directly, that works. The problem appears to be that these
  custom properties we are setting in the parent can't be imported in
  the child.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: udev 247.3-1ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 60-brother-libsane-type1.rules 99-displaylink.rules~ 
70-snap.core.rules 70-snap.snap-store.rules 99-x10.rules 
60-brother-brscan4-libsane-type1.rules 50-yubikey.rules 
70-snap.canonical-livepatch.rules 70-snap.gnome-system-monitor.rules 
70-snap.chromium.rules 99-displaylink.rules
  Date: Sun Feb 21 19:21:20 2021
  InstallationDate: Installed on 2019-01-02 (781 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: Acer Predator G6-710
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to hirsute on 2021-02-21 (0 days ago)
  dmi.bios.date: 05/18/2016
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A4
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.family: Acer Desktop
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1916418/+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 1920067] Re: Xorg with EVDI can't start with Mesa 21.0

2021-03-19 Thread Jonathan Kamens
For those of you who landed here looking for how to use DisplayLink in
Hirsute, I wrote up a workaround here: https://blog.kamens.us/2021/03/19
/update-on-using-displaylink-with-ubuntu-21-04-hirsute-hippo/

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

Title:
  Xorg with EVDI can't start with Mesa 21.0

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  As I indicated in a bug report I filed earlier today,
  https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059, evdi-dkms
  can no longer compile the evdi kernel module with the 5.11 kernel. So,
  to work around this, I need to keep using the 5.10 kernel instead.

  But I can't, because when I boot with the 5.10 kernel this is what
  shows up in /var/log/Xorg.0.log when gdm3 tries to start up the login
  screen (note: I have an NVIDIA graphics card, which is why (I believe)
  Wayland isn't being used here):

  [   857.957] (EE) modeset(G0): drmSetMaster failed: Device or resource busy
  [   857.957] (EE) 
  Fatal server error:
  [   857.957] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1
  [   857.957] (EE) 
  [   857.957] (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  [   857.957] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [   857.957] (EE) 
  [   858.144] (EE) Server terminated with error (1). Closing log file.

  This is probably not what you will see in the Xorg.0.log (if any)
  attached automatically to this bug because I've completely wiped the
  evdi kernel module from my system since that was the only way I could
  get a display manager up so I could use ubuntu-bug to submit this bug.

  Here's what I updated today:

  2021-03-18 15:03:26 upgrade sysvinit-utils:amd64 2.96-5ubuntu1 2.96-6ubuntu1
  2021-03-18 15:03:27 upgrade cron:amd64 3.0pl1-136ubuntu1 3.0pl1-136ubuntu2
  2021-03-18 15:03:28 upgrade gpg-wks-client:amd64 2.2.20-1ubuntu2 
2.2.20-1ubuntu3
  2021-03-18 15:03:28 upgrade dirmngr:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:29 upgrade gpg-wks-server:amd64 2.2.20-1ubuntu2 
2.2.20-1ubuntu3
  2021-03-18 15:03:29 upgrade gnupg-utils:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:29 upgrade gpg-agent:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:30 upgrade gpg:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:30 upgrade gpgconf:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:30 upgrade gnupg-l10n:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:31 upgrade gnupg:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:31 upgrade gpgsm:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:31 upgrade gpgv:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:32 upgrade libjs-sphinxdoc:all 3.5.1-2 3.5.2-1
  2021-03-18 15:03:33 upgrade libnfsidmap2:amd64 0.25-5.1ubuntu2 0.25-6
  2021-03-18 15:03:33 install linux-modules-5.11.0-11-generic:amd64  
5.11.0-11.12
  2021-03-18 15:03:35 install linux-image-5.11.0-11-generic:amd64  
5.11.0-11.12
  2021-03-18 15:03:36 install linux-modules-extra-5.11.0-11-generic:amd64 
 5.11.0-11.12
  2021-03-18 15:03:40 upgrade linux-generic:amd64 5.10.0.14.16 5.11.0.11.12
  2021-03-18 15:03:40 upgrade linux-image-generic:amd64 5.10.0.14.16 
5.11.0.11.12
  2021-03-18 15:03:41 install linux-headers-5.11.0-11:all  5.11.0-11.12
  2021-03-18 15:03:44 install linux-headers-5.11.0-11-generic:amd64  
5.11.0-11.12
  2021-03-18 15:03:47 upgrade linux-headers-generic:amd64 5.10.0.14.16 
5.11.0.11.12
  2021-03-18 15:03:47 upgrade linux-libc-dev:amd64 5.10.0-14.15 5.11.0-11.12
  2021-03-18 15:03:48 upgrade slack-desktop:amd64 4.13.0 4.14.0
  2021-03-18 15:03:52 upgrade xwayland:amd64 2:1.20.10-3ubuntu3 
2:21.0.99.902-0ubuntu1
  2021-03-18 15:56:42 upgrade at:amd64 3.1.23-1.1ubuntu2 3.1.23-1.1ubuntu3

  At first glance I don't understand how any of these could be causing
  this behavior.

  Potentially relevant: I had to recompile and reinstall the evdi kernel
  module while booted into 5.10 because when I install the 5.11 kernel
  dkms removed the module from 5.10 and then failed to rebuild it
  because the 5.11 build failed (or something I don't really understand
  why dkms does what it does *sigh*). I don't see how that should matter
  because the recompiled version of the module should have been
  identical, but *shrug*.

  As noted above, when I remove the evdi kernel modules from
  /lib/modules and reboot with 5.10 the problem goes away, so this does
  appear to be an evdi issue.

  In short: despite the fact that it's not clear how upgrading any of
  the modules listed above would cause evdi that used to work to
  suddenly stop working, that appears to be the case. Any advice would
  be appreciated because now I can't use the displays connected to my
  DisplayLink hub with 

[Touch-packages] [Bug 1920067] Re: Xorg with EVDI can't start with Mesa 21.0

2021-03-18 Thread Jonathan Kamens
I performed the splash -> nosplash test described above; it made no
difference.

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

Title:
  Xorg with EVDI can't start with Mesa 21.0

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  As I indicated in a bug report I filed earlier today,
  https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059, evdi-dkms
  can no longer compile the evdi kernel module with the 5.11 kernel. So,
  to work around this, I need to keep using the 5.10 kernel instead.

  But I can't, because when I boot with the 5.10 kernel this is what
  shows up in /var/log/Xorg.0.log when gdm3 tries to start up the login
  screen (note: I have an NVIDIA graphics card, which is why (I believe)
  Wayland isn't being used here):

  [   857.957] (EE) modeset(G0): drmSetMaster failed: Device or resource busy
  [   857.957] (EE) 
  Fatal server error:
  [   857.957] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1
  [   857.957] (EE) 
  [   857.957] (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  [   857.957] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [   857.957] (EE) 
  [   858.144] (EE) Server terminated with error (1). Closing log file.

  This is probably not what you will see in the Xorg.0.log (if any)
  attached automatically to this bug because I've completely wiped the
  evdi kernel module from my system since that was the only way I could
  get a display manager up so I could use ubuntu-bug to submit this bug.

  Here's what I updated today:

  2021-03-18 15:03:26 upgrade sysvinit-utils:amd64 2.96-5ubuntu1 2.96-6ubuntu1
  2021-03-18 15:03:27 upgrade cron:amd64 3.0pl1-136ubuntu1 3.0pl1-136ubuntu2
  2021-03-18 15:03:28 upgrade gpg-wks-client:amd64 2.2.20-1ubuntu2 
2.2.20-1ubuntu3
  2021-03-18 15:03:28 upgrade dirmngr:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:29 upgrade gpg-wks-server:amd64 2.2.20-1ubuntu2 
2.2.20-1ubuntu3
  2021-03-18 15:03:29 upgrade gnupg-utils:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:29 upgrade gpg-agent:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:30 upgrade gpg:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:30 upgrade gpgconf:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:30 upgrade gnupg-l10n:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:31 upgrade gnupg:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:31 upgrade gpgsm:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:31 upgrade gpgv:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:32 upgrade libjs-sphinxdoc:all 3.5.1-2 3.5.2-1
  2021-03-18 15:03:33 upgrade libnfsidmap2:amd64 0.25-5.1ubuntu2 0.25-6
  2021-03-18 15:03:33 install linux-modules-5.11.0-11-generic:amd64  
5.11.0-11.12
  2021-03-18 15:03:35 install linux-image-5.11.0-11-generic:amd64  
5.11.0-11.12
  2021-03-18 15:03:36 install linux-modules-extra-5.11.0-11-generic:amd64 
 5.11.0-11.12
  2021-03-18 15:03:40 upgrade linux-generic:amd64 5.10.0.14.16 5.11.0.11.12
  2021-03-18 15:03:40 upgrade linux-image-generic:amd64 5.10.0.14.16 
5.11.0.11.12
  2021-03-18 15:03:41 install linux-headers-5.11.0-11:all  5.11.0-11.12
  2021-03-18 15:03:44 install linux-headers-5.11.0-11-generic:amd64  
5.11.0-11.12
  2021-03-18 15:03:47 upgrade linux-headers-generic:amd64 5.10.0.14.16 
5.11.0.11.12
  2021-03-18 15:03:47 upgrade linux-libc-dev:amd64 5.10.0-14.15 5.11.0-11.12
  2021-03-18 15:03:48 upgrade slack-desktop:amd64 4.13.0 4.14.0
  2021-03-18 15:03:52 upgrade xwayland:amd64 2:1.20.10-3ubuntu3 
2:21.0.99.902-0ubuntu1
  2021-03-18 15:56:42 upgrade at:amd64 3.1.23-1.1ubuntu2 3.1.23-1.1ubuntu3

  At first glance I don't understand how any of these could be causing
  this behavior.

  Potentially relevant: I had to recompile and reinstall the evdi kernel
  module while booted into 5.10 because when I install the 5.11 kernel
  dkms removed the module from 5.10 and then failed to rebuild it
  because the 5.11 build failed (or something I don't really understand
  why dkms does what it does *sigh*). I don't see how that should matter
  because the recompiled version of the module should have been
  identical, but *shrug*.

  As noted above, when I remove the evdi kernel modules from
  /lib/modules and reboot with 5.10 the problem goes away, so this does
  appear to be an evdi issue.

  In short: despite the fact that it's not clear how upgrading any of
  the modules listed above would cause evdi that used to work to
  suddenly stop working, that appears to be the case. Any advice would
  be appreciated because now I can't use the displays connected to my
  DisplayLink hub with either 5.10 or 5.11 kernels, despite the fact
  that they worked with the 5.10 kernel before today.

  Please let me know if 

[Touch-packages] [Bug 1920067] Re: Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel

2021-03-18 Thread Jonathan Kamens
** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Somehow today's Hirsute updates have broken evdi with Xorg even when I
  boot with the 5.10 kernel

Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  As I indicated in a bug report I filed earlier today,
  https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059, evdi-dkms
  can no longer compile the evdi kernel module with the 5.11 kernel. So,
  to work around this, I need to keep using the 5.10 kernel instead.

  But I can't, because when I boot with the 5.10 kernel this is what
  shows up in /var/log/Xorg.0.log when gdm3 tries to start up the login
  screen (note: I have an NVIDIA graphics card, which is why (I believe)
  Wayland isn't being used here):

  [   857.957] (EE) modeset(G0): drmSetMaster failed: Device or resource busy
  [   857.957] (EE) 
  Fatal server error:
  [   857.957] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1
  [   857.957] (EE) 
  [   857.957] (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  [   857.957] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [   857.957] (EE) 
  [   858.144] (EE) Server terminated with error (1). Closing log file.

  This is probably not what you will see in the Xorg.0.log (if any)
  attached automatically to this bug because I've completely wiped the
  evdi kernel module from my system since that was the only way I could
  get a display manager up so I could use ubuntu-bug to submit this bug.

  Here's what I updated today:

  2021-03-18 15:03:26 upgrade sysvinit-utils:amd64 2.96-5ubuntu1 2.96-6ubuntu1
  2021-03-18 15:03:27 upgrade cron:amd64 3.0pl1-136ubuntu1 3.0pl1-136ubuntu2
  2021-03-18 15:03:28 upgrade gpg-wks-client:amd64 2.2.20-1ubuntu2 
2.2.20-1ubuntu3
  2021-03-18 15:03:28 upgrade dirmngr:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:29 upgrade gpg-wks-server:amd64 2.2.20-1ubuntu2 
2.2.20-1ubuntu3
  2021-03-18 15:03:29 upgrade gnupg-utils:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:29 upgrade gpg-agent:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:30 upgrade gpg:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:30 upgrade gpgconf:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:30 upgrade gnupg-l10n:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:31 upgrade gnupg:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:31 upgrade gpgsm:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:31 upgrade gpgv:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
  2021-03-18 15:03:32 upgrade libjs-sphinxdoc:all 3.5.1-2 3.5.2-1
  2021-03-18 15:03:33 upgrade libnfsidmap2:amd64 0.25-5.1ubuntu2 0.25-6
  2021-03-18 15:03:33 install linux-modules-5.11.0-11-generic:amd64  
5.11.0-11.12
  2021-03-18 15:03:35 install linux-image-5.11.0-11-generic:amd64  
5.11.0-11.12
  2021-03-18 15:03:36 install linux-modules-extra-5.11.0-11-generic:amd64 
 5.11.0-11.12
  2021-03-18 15:03:40 upgrade linux-generic:amd64 5.10.0.14.16 5.11.0.11.12
  2021-03-18 15:03:40 upgrade linux-image-generic:amd64 5.10.0.14.16 
5.11.0.11.12
  2021-03-18 15:03:41 install linux-headers-5.11.0-11:all  5.11.0-11.12
  2021-03-18 15:03:44 install linux-headers-5.11.0-11-generic:amd64  
5.11.0-11.12
  2021-03-18 15:03:47 upgrade linux-headers-generic:amd64 5.10.0.14.16 
5.11.0.11.12
  2021-03-18 15:03:47 upgrade linux-libc-dev:amd64 5.10.0-14.15 5.11.0-11.12
  2021-03-18 15:03:48 upgrade slack-desktop:amd64 4.13.0 4.14.0
  2021-03-18 15:03:52 upgrade xwayland:amd64 2:1.20.10-3ubuntu3 
2:21.0.99.902-0ubuntu1
  2021-03-18 15:56:42 upgrade at:amd64 3.1.23-1.1ubuntu2 3.1.23-1.1ubuntu3

  At first glance I don't understand how any of these could be causing
  this behavior.

  Potentially relevant: I had to recompile and reinstall the evdi kernel
  module while booted into 5.10 because when I install the 5.11 kernel
  dkms removed the module from 5.10 and then failed to rebuild it
  because the 5.11 build failed (or something I don't really understand
  why dkms does what it does *sigh*). I don't see how that should matter
  because the recompiled version of the module should have been
  identical, but *shrug*.

  As noted above, when I remove the evdi kernel modules from
  /lib/modules and reboot with 5.10 the problem goes away, so this does
  appear to be an evdi issue.

  In short: despite the fact that it's not clear how upgrading any of
  the modules listed above would cause evdi that used to work to
  suddenly stop working, that appears to be the case. Any advice would
  be appreciated because now I can't use the displays connected to my
  DisplayLink hub with either 5.10 or 5.11 kernels, despite the fact
  that they worked with the 

[Touch-packages] [Bug 1920067] [NEW] Somehow today's Hirsute updates have broken evdi with Xorg even when I boot with the 5.10 kernel

2021-03-18 Thread Jonathan Kamens
Public bug reported:

As I indicated in a bug report I filed earlier today,
https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1920059, evdi-dkms
can no longer compile the evdi kernel module with the 5.11 kernel. So,
to work around this, I need to keep using the 5.10 kernel instead.

But I can't, because when I boot with the 5.10 kernel this is what shows
up in /var/log/Xorg.0.log when gdm3 tries to start up the login screen
(note: I have an NVIDIA graphics card, which is why (I believe) Wayland
isn't being used here):

[   857.957] (EE) modeset(G0): drmSetMaster failed: Device or resource busy
[   857.957] (EE) 
Fatal server error:
[   857.957] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1
[   857.957] (EE) 
[   857.957] (EE) 
Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
[   857.957] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
[   857.957] (EE) 
[   858.144] (EE) Server terminated with error (1). Closing log file.

This is probably not what you will see in the Xorg.0.log (if any)
attached automatically to this bug because I've completely wiped the
evdi kernel module from my system since that was the only way I could
get a display manager up so I could use ubuntu-bug to submit this bug.

Here's what I updated today:

2021-03-18 15:03:26 upgrade sysvinit-utils:amd64 2.96-5ubuntu1 2.96-6ubuntu1
2021-03-18 15:03:27 upgrade cron:amd64 3.0pl1-136ubuntu1 3.0pl1-136ubuntu2
2021-03-18 15:03:28 upgrade gpg-wks-client:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:28 upgrade dirmngr:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:29 upgrade gpg-wks-server:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:29 upgrade gnupg-utils:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:29 upgrade gpg-agent:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:30 upgrade gpg:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:30 upgrade gpgconf:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:30 upgrade gnupg-l10n:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:31 upgrade gnupg:all 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:31 upgrade gpgsm:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:31 upgrade gpgv:amd64 2.2.20-1ubuntu2 2.2.20-1ubuntu3
2021-03-18 15:03:32 upgrade libjs-sphinxdoc:all 3.5.1-2 3.5.2-1
2021-03-18 15:03:33 upgrade libnfsidmap2:amd64 0.25-5.1ubuntu2 0.25-6
2021-03-18 15:03:33 install linux-modules-5.11.0-11-generic:amd64  
5.11.0-11.12
2021-03-18 15:03:35 install linux-image-5.11.0-11-generic:amd64  
5.11.0-11.12
2021-03-18 15:03:36 install linux-modules-extra-5.11.0-11-generic:amd64  
5.11.0-11.12
2021-03-18 15:03:40 upgrade linux-generic:amd64 5.10.0.14.16 5.11.0.11.12
2021-03-18 15:03:40 upgrade linux-image-generic:amd64 5.10.0.14.16 5.11.0.11.12
2021-03-18 15:03:41 install linux-headers-5.11.0-11:all  5.11.0-11.12
2021-03-18 15:03:44 install linux-headers-5.11.0-11-generic:amd64  
5.11.0-11.12
2021-03-18 15:03:47 upgrade linux-headers-generic:amd64 5.10.0.14.16 
5.11.0.11.12
2021-03-18 15:03:47 upgrade linux-libc-dev:amd64 5.10.0-14.15 5.11.0-11.12
2021-03-18 15:03:48 upgrade slack-desktop:amd64 4.13.0 4.14.0
2021-03-18 15:03:52 upgrade xwayland:amd64 2:1.20.10-3ubuntu3 
2:21.0.99.902-0ubuntu1
2021-03-18 15:56:42 upgrade at:amd64 3.1.23-1.1ubuntu2 3.1.23-1.1ubuntu3

At first glance I don't understand how any of these could be causing
this behavior.

Potentially relevant: I had to recompile and reinstall the evdi kernel
module while booted into 5.10 because when I install the 5.11 kernel
dkms removed the module from 5.10 and then failed to rebuild it because
the 5.11 build failed (or something I don't really understand why dkms
does what it does *sigh*). I don't see how that should matter because
the recompiled version of the module should have been identical, but
*shrug*.

As noted above, when I remove the evdi kernel modules from /lib/modules
and reboot with 5.10 the problem goes away, so this does appear to be an
evdi issue.

In short: despite the fact that it's not clear how upgrading any of the
modules listed above would cause evdi that used to work to suddenly stop
working, that appears to be the case. Any advice would be appreciated
because now I can't use the displays connected to my DisplayLink hub
with either 5.10 or 5.11 kernels, despite the fact that they worked with
the 5.10 kernel before today.

Please let me know if there's any other info you need here.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xserver-xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.141  Mon Dec 28 16:21:32 
UTC 2020
 

[Touch-packages] [Bug 1917515] Re: System doesn't boot (root device never becomes available after entering encryption passphrase) after today's Hirsute updates

2021-03-02 Thread Jonathan Kamens
** Attachment added: "list of packages upgraded today from dpkg.log"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+attachment/5471986/+files/upgraded.txt

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

Title:
  System doesn't boot (root device never becomes available after
  entering encryption passphrase) after today's Hirsute updates

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Note: I'm guessing that lvm2 is the most likely culprit for this
  issue, but I don't know for certain.

  After today's Hirsute upgrades, my system won't boot. The boot gets to
  the point where it asks me for the passphrase for my encrypted root
  disk, and I enter it, and then it says that it was unlocked
  successfully, and then it spins for a while, and then I get the
  message shown in the attached photo.

  When I reboot with the older pre-Hirsute kernel (5.8.0-43-generic) I
  have installed the system boots successfully, but I don't think this
  is a kernel issue per se since I didn't upgrade the kernel today and
  my system has rebooted successfully before with the Hirsute kernel I
  currently have installed.

  Note: the two kernel messages shown at the beginning of the photo are
  not relevant; they occur even when I fall back to the old kernel and
  boot successfully.

  Attached: photo of console from failed boot, list of packages that
  were upgraded today.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lvm2 2.03.11-2ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  2 14:22:26 2021
  InstallationDate: Installed on 2019-01-02 (790 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to hirsute on 2021-02-21 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+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 1917515] [NEW] System doesn't boot (root device never becomes available after entering encryption passphrase) after today's Hirsute updates

2021-03-02 Thread Jonathan Kamens
Public bug reported:

Note: I'm guessing that lvm2 is the most likely culprit for this issue,
but I don't know for certain.

After today's Hirsute upgrades, my system won't boot. The boot gets to
the point where it asks me for the passphrase for my encrypted root
disk, and I enter it, and then it says that it was unlocked
successfully, and then it spins for a while, and then I get the message
shown in the attached photo.

When I reboot with the older pre-Hirsute kernel (5.8.0-43-generic) I
have installed the system boots successfully, but I don't think this is
a kernel issue per se since I didn't upgrade the kernel today and my
system has rebooted successfully before with the Hirsute kernel I
currently have installed.

Note: the two kernel messages shown at the beginning of the photo are
not relevant; they occur even when I fall back to the old kernel and
boot successfully.

Attached: photo of console from failed boot, list of packages that were
upgraded today.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: lvm2 2.03.11-2ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  2 14:22:26 2021
InstallationDate: Installed on 2019-01-02 (790 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
SourcePackage: lvm2
UpgradeStatus: Upgraded to hirsute on 2021-02-21 (9 days ago)

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


** Tags: amd64 apport-bug hirsute regression-release

** Attachment added: "photo of console after failed boot"
   
https://bugs.launchpad.net/bugs/1917515/+attachment/5471982/+files/PXL_20210302_191525480.jpg

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

Title:
  System doesn't boot (root device never becomes available after
  entering encryption passphrase) after today's Hirsute updates

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Note: I'm guessing that lvm2 is the most likely culprit for this
  issue, but I don't know for certain.

  After today's Hirsute upgrades, my system won't boot. The boot gets to
  the point where it asks me for the passphrase for my encrypted root
  disk, and I enter it, and then it says that it was unlocked
  successfully, and then it spins for a while, and then I get the
  message shown in the attached photo.

  When I reboot with the older pre-Hirsute kernel (5.8.0-43-generic) I
  have installed the system boots successfully, but I don't think this
  is a kernel issue per se since I didn't upgrade the kernel today and
  my system has rebooted successfully before with the Hirsute kernel I
  currently have installed.

  Note: the two kernel messages shown at the beginning of the photo are
  not relevant; they occur even when I fall back to the old kernel and
  boot successfully.

  Attached: photo of console from failed boot, list of packages that
  were upgraded today.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: lvm2 2.03.11-2ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  2 14:22:26 2021
  InstallationDate: Installed on 2019-01-02 (790 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  SourcePackage: lvm2
  UpgradeStatus: Upgraded to hirsute on 2021-02-21 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1917515/+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 1916418] [NEW] Custom properties set with ENV{WHATEVER} in parent no longer imported with IMPORT{parent} in udev rule

2021-02-21 Thread Jonathan Kamens
Public bug reported:

DisplayLink uses these udev rules to start the displaylink service when
a displaylink device is plugged in:

ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTR{idVendor}=="17e9",
IMPORT{builtin}="usb_id", ENV{DISPLAYLINK_DEVNAME}="$env{DEVNAME}",
ENV{DISPLAYLINK_DEVICE_ID}="$env{ID_BUS}-$env{BUSNUM}-$env{DEVNUM}-$env{ID_SERIAL}",
ENV{REMOVE_CMD}="/opt/displaylink/udev.sh $root
$env{DISPLAYLINK_DEVICE_ID} $env{DISPLAYLINK_DEVNAME}"

ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
ATTRS{idVendor}=="17e9", ATTR{bInterfaceClass}=="ff",
ATTR{bInterfaceProtocol}=="03", IMPORT{parent}="DISPLAYLINK*",
RUN+="/opt/displaylink/udev.sh $root $env{DISPLAYLINK_DEVICE_ID}
$env{DISPLAYLINK_DEVNAME}"

The important thing to note here is that the first rule is for the
device that is the parent of the device triggers the second rule, and
the first rule sets ENV{DISPLAYLINK_DEVNAME} and
ENV{DISPLAYLINK_DEVICE_ID}, and the second rule attempts to import them
with IMPORT{parent} and then use them.

This worked fine in 20.04.

It does not work in 21.04.

When the second rule is triggered, DISPLAYLINK_DEVICE_ID and
DISPLAYLINK_DEVNAME are not set.

I have confirmed via udevadm monitor that the variables are getting set
on the parent.

I have confirmed via udevadm info --attribute-walk that the device
triggering the second rule is the child of the device triggering the
first one.

I have tried to import the variables explicitly instead of using a glob
pattern and that doesn't work either.

When I modify the rule to import DEVNAME, ID_BUS, BUSNUM, DEVNUM, and
ID_SERIAL directly, that works. The problem appears to be that these
custom properties we are setting in the parent can't be imported in the
child.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: udev 247.3-1ubuntu2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu59
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 60-brother-libsane-type1.rules 99-displaylink.rules~ 
70-snap.core.rules 70-snap.snap-store.rules 99-x10.rules 
60-brother-brscan4-libsane-type1.rules 50-yubikey.rules 
70-snap.canonical-livepatch.rules 70-snap.gnome-system-monitor.rules 
70-snap.chromium.rules 99-displaylink.rules
Date: Sun Feb 21 19:21:20 2021
InstallationDate: Installed on 2019-01-02 (781 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: Acer Predator G6-710
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-14-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to hirsute on 2021-02-21 (0 days ago)
dmi.bios.date: 05/18/2016
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R01-A4
dmi.board.name: Predator G6-710
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:br5.11:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
dmi.product.family: Acer Desktop
dmi.product.name: Predator G6-710
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug hirsute regression-release third-party-packages

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

Title:
  Custom properties set with ENV{WHATEVER} in parent no longer imported
  with IMPORT{parent} in udev rule

Status in systemd package in Ubuntu:
  New

Bug description:
  DisplayLink uses these udev rules to start the displaylink service
  when a displaylink device is plugged in:

  ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
  ATTR{idVendor}=="17e9", IMPORT{builtin}="usb_id",
  ENV{DISPLAYLINK_DEVNAME}="$env{DEVNAME}",
  
ENV{DISPLAYLINK_DEVICE_ID}="$env{ID_BUS}-$env{BUSNUM}-$env{DEVNUM}-$env{ID_SERIAL}",
  ENV{REMOVE_CMD}="/opt/displaylink/udev.sh $root
  $env{DISPLAYLINK_DEVICE_ID} $env{DISPLAYLINK_DEVNAME}"

  ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb",
  ATTRS{idVendor}=="17e9", ATTR{bInterfaceClass}=="ff",
  ATTR{bInterfaceProtocol}=="03", IMPORT{parent}="DISPLAYLINK*",
  RUN+="/opt/displaylink/udev.sh $root $env{DISPLAYLINK_DEVICE_ID}
  $env{DISPLAYLINK_DEVNAME}"

  The important thing to note here is that the first rule is for the
  device that is the parent of the device triggers the second rule, and
  the first rule sets ENV{DISPLAYLINK_DEVNAME} and
  ENV{DISPLAYLINK_DEVICE_ID}, and the second rule attempts to import
  them with IMPORT{parent} and then use them.

  This worked fine in 20.04.

  It does not work in 21.04.

  When the second rule is triggered, DISPLAYLINK_DEVICE_ID and
  DISPLAYLINK_DEVNAME are not set.

  I have confirmed via udevadm monitor that the variables are 

[Touch-packages] [Bug 1644995] Re: specific SVG file breaks Ubuntu 16.04 desktop + nautilus

2020-07-28 Thread Jonathan B. Horen
10100727: The recent upgrade of librsvg2-2:i386 and librsvg2-common:i386
(from 2.40.20-2 to (2.40.20-2ubuntu0.1) "broke" the display of card
styles Anglo and Gnomeangelo, in the aisleriot "Klondike" solitaire
game. By "broke", I mean that the card faces displayed only in part --
elements were missing.

Reverting to the previous version solved the issue.

** Attachment added: "Klondike-librsvg.png"
   
https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1644995/+attachment/5396751/+files/Klondike-librsvg.png

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

Title:
  specific SVG file breaks Ubuntu 16.04 desktop + nautilus

Status in librsvg:
  Expired
Status in librsvg package in Ubuntu:
  Triaged

Bug description:
  Saving following file on Desktop (Ubuntu 16.04.1) results in:

  1. Wallpaper and all icons on the desktop disappear
  2. Nautilus starts for ~1sec then breaks with "Floating point exception"

  I suspect it's related to librsvg. In syslog I have many records
  similar to this one:

  kernel: [   20.076864] traps: nautilus[2270] trap divide error
  ip:7f63fbddf716 sp:7f63fad3f5b0 error:0 in
  librsvg-2.so.2.40.13[7f63fbdc9000+35000]

  Here is the file (I can't even attach it here with Firefox, because it
  makes it crash):

  http://www.w3.org/2000/svg; 
xmlns:xlink="http://www.w3.org/1999/xlink; 
xmlns:ev="http://www.w3.org/2001/xml-events;>
  

   

   
   https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcRiXhgkC523CD5DIdvfwFl3G_S1Hc3oHzh8NUTXPeRSfYv1i8rA;
 result="pattern" width="4" height="4"/>
 
 

  

  

  

   
  
   
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/librsvg/+bug/1644995/+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 1888065] Re: Screen dies/black after changing display orientation or enabling fractional scaling

2020-07-18 Thread Jonathan Watt
The issue seems gone after a reboot. Theming and colors are back to
normal.

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

Title:
  Screen dies/black after changing display orientation or enabling
  fractional scaling

Status in xorg package in Ubuntu:
  New

Bug description:
  I upgraded to 20.04 over a month ago and it's been working fine. I
  have one monitor (external). I tried turning on fractional scaling in
  the display settings and the screen immediately turned black. I
  waited, expecting the "confirm changes" prompt to timeout and restore
  the display. It never did.

  Next I hard rebooted, but as soon as I'd entered my password to login,
  the screen went black again. Tried this a few more times. I then
  booted to a root console and `apt update/upgrade` to get all updates.
  Rebooting, I had the same issue on logging in. I then used Ctrl+Alt+F1
  to get a virtual console, then back to F2, and a few other things. At
  some point I was able to log back in.

  Foolishly I assumed the issue was just with fractional scaling, and
  back in Display settings I for some reason decided to experiment
  further and flipped the display orientation to portrate. Immediately I
  got a black screen and ended back in the same reboot loop, always
  getting a black screen as soon as I tried to log back in. Searching
  online I couldn't seem to find a way to revert the display
  orientation. From another virtual console I was unable to run xrandr
  or start a wayland session to get to the settings panel. To do that I
  was trying to run:

dbus-run-session -- gnome-shell --display-server --wayland

  But that's just something I found on the Web, I have no idea what I'm
  doing there. It just gave the error:

  (gnome-shell:) mutter-warning: **:  Failed to 
open gpu 'dev/dri/card0 Failed to activate universal planes: Operation not 
permitted
  (gnome-shell:) mutter-warning: **:  Failed to 
create backend: No GPUs found

  Eventually I found a suggestion on the Web to unplug the cable to the
  display, and after experimenting with that a bit and switching between
  virtual consoles, at some point it was logged in with a working
  display ... well, sort of. The colors and icons are weird like it's
  lost theming or something. Going into the Display settings it seems
  that the orientation has also been reset to landscape.

  I'm filing this bug before restarting the machine so I can report the
  system scan it has taken. At this point I've no idea whether I'll be
  able to log back in again after a reboot. I'll try that now.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..21.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:21:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Jul 18 17:21:56 2020
  DistUpgraded: 2020-04-29 16:04:33,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.4.0-37-generic, x86_64: installed
   nvidia, 435.21, 5.4.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GP107GL [Quadro P400] [1028:11be]
  InstallationDate: Installed on 2019-11-03 (257 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: HP HP Z4 G4 Workstation
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=9586ebe6-be5f-4a32-b960-e129e9d98eb9 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to focal on 2020-04-29 (80 days ago)
  dmi.bios.date: 03/21/2019
  dmi.bios.vendor: HP
  dmi.bios.version: P62 v01.75
  dmi.board.name: 81C5
  dmi.board.vendor: HP
  dmi.board.version: MVB
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP62v01.75:bd03/21/2019:svnHP:pnHPZ4G4Workstation:pvr:rvnHP:rn81C5:rvrMVB:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53335X HP Workstation
  dmi.product.name: HP Z4 G4 Workstation
  dmi.product.sku: 5FN34US#ABA
  dmi.sys.vendor: HP
  version.compiz: 

[Touch-packages] [Bug 1888065] [NEW] Screen dies/black after changing display orientation or enabling fractional scaling

2020-07-18 Thread Jonathan Watt
Public bug reported:

I upgraded to 20.04 over a month ago and it's been working fine. I have
one monitor (external). I tried turning on fractional scaling in the
display settings and the screen immediately turned black. I waited,
expecting the "confirm changes" prompt to timeout and restore the
display. It never did.

Next I hard rebooted, but as soon as I'd entered my password to login,
the screen went black again. Tried this a few more times. I then booted
to a root console and `apt update/upgrade` to get all updates.
Rebooting, I had the same issue on logging in. I then used Ctrl+Alt+F1
to get a virtual console, then back to F2, and a few other things. At
some point I was able to log back in.

Foolishly I assumed the issue was just with fractional scaling, and back
in Display settings I for some reason decided to experiment further and
flipped the display orientation to portrate. Immediately I got a black
screen and ended back in the same reboot loop, always getting a black
screen as soon as I tried to log back in. Searching online I couldn't
seem to find a way to revert the display orientation. From another
virtual console I was unable to run xrandr or start a wayland session to
get to the settings panel. To do that I was trying to run:

  dbus-run-session -- gnome-shell --display-server --wayland

But that's just something I found on the Web, I have no idea what I'm
doing there. It just gave the error:

(gnome-shell:) mutter-warning: **:  Failed to open 
gpu 'dev/dri/card0 Failed to activate universal planes: Operation not permitted
(gnome-shell:) mutter-warning: **:  Failed to 
create backend: No GPUs found

Eventually I found a suggestion on the Web to unplug the cable to the
display, and after experimenting with that a bit and switching between
virtual consoles, at some point it was logged in with a working display
... well, sort of. The colors and icons are weird like it's lost theming
or something. Going into the Display settings it seems that the
orientation has also been reset to landscape.

I'm filing this bug before restarting the machine so I can report the
system scan it has taken. At this point I've no idea whether I'll be
able to log back in again after a reboot. I'll try that now.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..21.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:21:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Jul 18 17:21:56 2020
DistUpgraded: 2020-04-29 16:04:33,258 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.4.0-37-generic, x86_64: installed
 nvidia, 435.21, 5.4.0-40-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP107GL [Quadro P400] [10de:1cb3] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Dell GP107GL [Quadro P400] [1028:11be]
InstallationDate: Installed on 2019-11-03 (257 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: HP HP Z4 G4 Workstation
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=9586ebe6-be5f-4a32-b960-e129e9d98eb9 ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to focal on 2020-04-29 (80 days ago)
dmi.bios.date: 03/21/2019
dmi.bios.vendor: HP
dmi.bios.version: P62 v01.75
dmi.board.name: 81C5
dmi.board.vendor: HP
dmi.board.version: MVB
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrP62v01.75:bd03/21/2019:svnHP:pnHPZ4G4Workstation:pvr:rvnHP:rn81C5:rvrMVB:cvnHP:ct3:cvr:
dmi.product.family: 103C_53335X HP Workstation
dmi.product.name: HP Z4 G4 Workstation
dmi.product.sku: 5FN34US#ABA
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: 

[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight

2020-06-11 Thread Jonathan Kayne
This is still occuring in 20.04 along with the notification at bootup.
It has not been fixed.

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  Triaged

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1869981/+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 1864558] Re: Printer adds automatically at boot with notification or if printer deleted

2020-06-11 Thread Jonathan Kayne
So, something that is surprising me is that nobody has asked for any
type of report. I would love to share any diagnostic information I have,
just give me a terminal command or path to a text file and I will share
it.

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

Title:
  Printer adds automatically at boot with notification or if printer
  deleted

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When booting 20.04 I get a notification on the logon screen each time
  advising that my wireless printer has been setup. If I remove the
  printer via settings, then as soon as it's removed, it gets re-added
  and I see the same notification as I do on the logon screen about the
  printer having been setup. I've attached a screenshot of this
  notification.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.35.91-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 24 21:49:43 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-02-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+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 1864558] Re: Printer adds automatically at boot with notification or if printer deleted

2020-06-04 Thread Jonathan Kayne
It also seems that the notification repeats at midnight as well

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

Title:
  Printer adds automatically at boot with notification or if printer
  deleted

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When booting 20.04 I get a notification on the logon screen each time
  advising that my wireless printer has been setup. If I remove the
  printer via settings, then as soon as it's removed, it gets re-added
  and I see the same notification as I do on the logon screen about the
  printer having been setup. I've attached a screenshot of this
  notification.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.35.91-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 24 21:49:43 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-02-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+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 1864558] Re: Printer adds automatically at boot with notification or if printer deleted

2020-06-04 Thread Jonathan Kayne
I want to add that it seems rather widespread, as just about every in depth 
review I have seen of 20.04 on YouTube brings up this issue.
Also, disabling the notification does not work because of the fact that it 
occurs at first login.
Considering how widespread this is, shouldn't it be at a higher priority?

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

Title:
  Printer adds automatically at boot with notification or if printer
  deleted

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When booting 20.04 I get a notification on the logon screen each time
  advising that my wireless printer has been setup. If I remove the
  printer via settings, then as soon as it's removed, it gets re-added
  and I see the same notification as I do on the logon screen about the
  printer having been setup. I've attached a screenshot of this
  notification.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.35.91-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 24 21:49:43 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-02-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+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 1876670] Re: nfs does not mount at boot with bridge

2020-05-06 Thread Jonathan Van den Broeck
Same probleme with the modification you suggest.

root@bowser:~# cat /etc/systemd/system/mnt-nas.mount
[Unit]
Description=NAS devices
After=network-online.target

[Mount]
What=192.168.1.20:/volume2/media
Where=/mnt/nas
Type=nfs
Options=_netdev,auto

[Install]
WantedBy=multi-user.target
root@bowser:~# systemctl status mnt-nas.mount

● mnt-nas.mount - NAS devices
 Loaded: loaded (/etc/systemd/system/mnt-nas.mount; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Wed 2020-05-06 17:35:46 CEST; 
4min 59s ago
  Where: /mnt/nas
   What: 192.168.1.20:/volume2/media

May 06 17:35:45 bowser systemd[1]: Mounting NAS devices...
May 06 17:35:46 bowser mount[751]: mount.nfs: Network is unreachable
May 06 17:35:46 bowser systemd[1]: mnt-nas.mount: Mount process exited, 
code=exited, status=32/n/a
May 06 17:35:46 bowser systemd[1]: mnt-nas.mount: Failed with result 
'exit-code'.
May 06 17:35:46 bowser systemd[1]: Failed to mount NAS devices.

I also have done some more test. I only have this problem on a bare
metal installation (Lenovo M720q). If I do the same configuration on a
virtual machine, I do not have the problem. I do not have the problem
with a fedora server installation on bare metal.

I do not have enough knowledge to troubleshoot this problem but I am
fully available if you have some commands you want me to try.

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

Title:
  nfs does not mount at boot with bridge

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I am running a Ubuntu 20.04 server with lxd and kvm/qemu. 
  I try to connect a nfs share at boot. It is working while I do not configure 
any bridge with netplan. I am creating directly a systemd service for the NFS 
mount but I have the same problem if I edit the fstab file.

  #/etc/systemd/system/mnt-nas.mount
  [Unit]
  Description=NAS devices
  After=network.target

  [Mount]
  What=192.168.1.20:/volume2/media
  Where=/mnt/nas
  Type=nfs
  Options=_netdev,auto

  [Install]
  WantedBy=multi-user.target

  ## TEST WITHOUT BRIDGE

  #/etc/netplan/01-netcfg.yaml 
  network:
version: 2
renderer: networkd
ethernets:
  eno1:
dhcp4: yes

  root@bowser:~# ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: eno1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
  link/ether f8:75:a4:00:be:ad brd ff:ff:ff:ff:ff:ff
  inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic eno1
 valid_lft 86244sec preferred_lft 86244sec
  inet6 fe80::fa75:a4ff:fe00:bead/64 scope link 
 valid_lft forever preferred_lft forever
  3: wlp1s0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 60:f2:62:38:d7:c2 brd ff:ff:ff:ff:ff:ff

  root@bowser:~# journalctl -b
  ...
  May 04 08:58:08 bowser systemd-networkd[535]: eno1: Gained carrier
  May 04 08:58:08 bowser kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: None
  May 04 08:58:08 bowser kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link 
becomes ready
  May 04 08:58:08 bowser systemd[1]: systemd-rfkill.service: Succeeded.
  May 04 08:58:08 bowser set-cpufreq[795]: Setting powersave scheduler for all 
CPUs
  May 04 08:58:08 bowser systemd[1]: ondemand.service: Succeeded.
  May 04 08:58:08 bowser systemd[1]: dmesg.service: Succeeded.
  May 04 08:58:09 bowser systemd-networkd[535]: eno1: Gained IPv6LL
  May 04 08:58:09 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-networkd[535]: eno1: DHCPv4 address 
192.168.1.100/24 via 192.168.1.1
  May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
  May 04 08:58:10 bowser systemd-networkd-wait-online[611]: managing: eno1
  May 04 08:58:10 bowser systemd[1]: Finished Wait for Network to be Configured.
  May 04 08:58:10 bowser systemd[1]: Reached target Network is Online.
  May 04 08:58:10 bowser systemd[1]: Condition check resulted in Login to 
default iSCSI targets being skipped.
  May 04 08:58:10 bowser systemd[1]: Reached target Remote File Systems (Pre).
  May 04 08:58:10 bowser systemd[1]: Mounting NAS devices...
  May 04 08:58:10 bowser systemd[1]: Starting Availability of block devices...
  May 04 08:58:10 bowser systemd[1]: Condition check resulted in Pollinate to 
seed the 

[Touch-packages] [Bug 1864558] Re: Printer adds automatically at boot with notification or if printer deleted

2020-05-05 Thread Jonathan Kayne
I am not sure how widespread this is, but I can also confirm this happens on my 
laptop as well. Ever since updating to 20.04 I always get the "printer added" 
notification on bootup regardless of whether it was added already or not. 
On previous versions this would only happen on the first bootup or after 
install of operating systems (or the first time I connect to the network) and 
that was it.
If there is something I can do to help solve this, please advise me on how to 
do so. It is quite annoying to see this every time I boot my machine.

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

Title:
  Printer adds automatically at boot with notification or if printer
  deleted

Status in cups package in Ubuntu:
  New

Bug description:
  When booting 20.04 I get a notification on the logon screen each time
  advising that my wireless printer has been setup. If I remove the
  printer via settings, then as soon as it's removed, it gets re-added
  and I see the same notification as I do on the logon screen about the
  printer having been setup. I've attached a screenshot of this
  notification.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.35.91-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 24 21:49:43 2020
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2020-02-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200221)
  ProcEnviron:
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1864558/+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 1876670] [NEW] nfs does not mount at boot with bridge

2020-05-04 Thread Jonathan Van den Broeck
Public bug reported:

I am running a Ubuntu 20.04 server with lxd and kvm/qemu. 
I try to connect a nfs share at boot. It is working while I do not configure 
any bridge with netplan. I am creating directly a systemd service for the NFS 
mount but I have the same problem if I edit the fstab file.

#/etc/systemd/system/mnt-nas.mount
[Unit]
Description=NAS devices
After=network.target

[Mount]
What=192.168.1.20:/volume2/media
Where=/mnt/nas
Type=nfs
Options=_netdev,auto

[Install]
WantedBy=multi-user.target

## TEST WITHOUT BRIDGE

#/etc/netplan/01-netcfg.yaml 
network:
  version: 2
  renderer: networkd
  ethernets:
eno1:
  dhcp4: yes

root@bowser:~# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eno1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
link/ether f8:75:a4:00:be:ad brd ff:ff:ff:ff:ff:ff
inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic eno1
   valid_lft 86244sec preferred_lft 86244sec
inet6 fe80::fa75:a4ff:fe00:bead/64 scope link 
   valid_lft forever preferred_lft forever
3: wlp1s0:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
link/ether 60:f2:62:38:d7:c2 brd ff:ff:ff:ff:ff:ff

root@bowser:~# journalctl -b
...
May 04 08:58:08 bowser systemd-networkd[535]: eno1: Gained carrier
May 04 08:58:08 bowser kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full 
Duplex, Flow Control: None
May 04 08:58:08 bowser kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link 
becomes ready
May 04 08:58:08 bowser systemd[1]: systemd-rfkill.service: Succeeded.
May 04 08:58:08 bowser set-cpufreq[795]: Setting powersave scheduler for all 
CPUs
May 04 08:58:08 bowser systemd[1]: ondemand.service: Succeeded.
May 04 08:58:08 bowser systemd[1]: dmesg.service: Succeeded.
May 04 08:58:09 bowser systemd-networkd[535]: eno1: Gained IPv6LL
May 04 08:58:09 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
May 04 08:58:10 bowser systemd-networkd[535]: eno1: DHCPv4 address 
192.168.1.100/24 via 192.168.1.1
May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
May 04 08:58:10 bowser systemd-timesyncd[757]: Network configuration changed, 
trying to establish connection.
May 04 08:58:10 bowser systemd-networkd-wait-online[611]: managing: eno1
May 04 08:58:10 bowser systemd[1]: Finished Wait for Network to be Configured.
May 04 08:58:10 bowser systemd[1]: Reached target Network is Online.
May 04 08:58:10 bowser systemd[1]: Condition check resulted in Login to default 
iSCSI targets being skipped.
May 04 08:58:10 bowser systemd[1]: Reached target Remote File Systems (Pre).
May 04 08:58:10 bowser systemd[1]: Mounting NAS devices...
May 04 08:58:10 bowser systemd[1]: Starting Availability of block devices...
May 04 08:58:10 bowser systemd[1]: Condition check resulted in Pollinate to 
seed the pseudo random number generator being skipped.
May 04 08:58:10 bowser systemd[1]: Starting OpenBSD Secure Shell server...
May 04 08:58:10 bowser systemd[1]: Finished Availability of block devices.
May 04 08:58:10 bowser kernel: FS-Cache: Loaded
May 04 08:58:10 bowser sshd[952]: Server listening on 0.0.0.0 port 22.
May 04 08:58:10 bowser sshd[952]: Server listening on :: port 22.
May 04 08:58:10 bowser systemd[1]: Started OpenBSD Secure Shell server.
May 04 08:58:10 bowser kernel: FS-Cache: Netfs 'nfs' registered for caching
May 04 08:58:10 bowser kernel: NFS: Registering the id_resolver key type
May 04 08:58:10 bowser kernel: Key type id_resolver registered
May 04 08:58:10 bowser kernel: Key type id_legacy registered
May 04 08:58:10 bowser systemd[1]: /lib/systemd/system/rpc-statd.service:16: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/rpc.statd.pid → /run/rpc.statd.pid; please update the unit file 
accordingly.
May 04 08:58:10 bowser systemd[1]: Starting Preprocess NFS configuration...
May 04 08:58:10 bowser systemd[1]: nfs-config.service: Succeeded.
May 04 08:58:10 bowser systemd[1]: Finished Preprocess NFS configuration.
May 04 08:58:10 bowser systemd[1]: Starting Notify NFS peers of a restart...
May 04 08:58:10 bowser systemd[1]: Starting NFS status monitor for NFSv2/3 
locking
May 04 08:58:10 bowser sm-notify[962]: Version 1.3.3 starting
May 04 08:58:10 bowser systemd[1]: rpc-statd-notify.service: Succeeded.
May 04 08:58:10 bowser systemd[1]: Started Notify NFS peers of a restart.
May 04 08:58:10 bowser rpc.statd[964]: Version 1.3.3 starting
May 04 08:58:10 bowser rpc.statd[964]: Flags: TI-RPC
May 04 08:58:10 bowser systemd[1]: Started NFS status monitor for NFSv2/3 
locking..
May 04 08:58:10 

[Touch-packages] [Bug 1184178] Re: [MS-7698, ATI R6xx HDMI, Digital Out, HDMI] fails after a while

2020-03-05 Thread Jonathan Seder
Fixed long ago.

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  [MS-7698, ATI R6xx HDMI, Digital Out, HDMI] fails after a while

Status in alsa-driver package in Ubuntu:
  Fix Released

Bug description:
  Sound is available after booting but goes away after 5-120 minutes.
  Sound failure does not appear to be associated with anything other
  than the passage of time.

  This problem appeared after I ran an upgrade on 2013-05-18 which affected 82 
packages, notably
 alsa-utils:i386 (1.0.25-1ubuntu5, 1.0.25-1ubuntu5.2),
 libasound2:i386 (1.0.25-1ubuntu10.1, 1.0.25-1ubuntu10.2),
  Previously the system had worked flawlessly for many months.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-44.69-generic-pae 3.2.44
  Uname: Linux 3.2.0-44-generic-pae i686
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu17.2
  Architecture: i386
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfeb44000 irq 44'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 6
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'SB'/'HDA ATI SB at 0xfeb4 irq 16'
 Mixer name : 'Realtek ALC887-VD'
 Components : 'HDA:10ec0887,10ec0887,00100302'
 Controls  : 45
 Simple ctrls  : 21
  Date: Sat May 25 11:04:56 2013
  InstallationMedia: Mythbuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=cygwin
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: Sound works for a while, then breaks
  Title: [MS-7698, ATI R6xx HDMI, Digital Out, HDMI] fails after a while
  UpgradeStatus: Upgraded to precise on 2012-05-18 (372 days ago)
  dmi.bios.date: 03/14/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: E350IA-E45 (MS-7698)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.4:bd03/14/2011:svnMSI:pnMS-7698:pvr1.0:rvnMSI:rnE350IA-E45(MS-7698):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7698
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1184178/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

2020-02-28 Thread Jonathan Kamens
There is still something wrong here.

The site in question has fixed the issue in response to my query, and
SSL Labs now gives it an A grade:

https://www.ssllabs.com/ssltest/analyze.html?d=www.toodledo.com

According to SSL Labs, it supports these two ciphers for TLS 1.2:

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (0xc030)
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f)

According to openssl ciphers -s -V, both of these are supported by
openssl:

$ openssl ciphers -s -V | egrep '0xC0,0x(30|2F)'
  0xC0,0x30 - ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH Au=RSA 
Enc=AESGCM(256) Mac=AEAD
  0xC0,0x2F - ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH Au=RSA  
Enc=AESGCM(128) Mac=AEAD

And yet I'm still unable to connect to this server through openssl
unless I downgrade the security level to 1.

You mentioned there being an SHA1 certificate in the chain, but I don't
see one. The certs all seem to be SHA256.

I cannot find any evidence that security level 2 blocks the use of
certificates with lifetimes of more than a year. Is that an undocumented
"feature" of security level 2?

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

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in openssl package in Ubuntu:
  New

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/;)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

2020-02-26 Thread Jonathan Kamens
Fair enough, I will contact the web site maintainer. However, regarding
this:

>You can override this via command-line, a system config file, or a local 
>config file + environment variable pointing to it.
>
>On Ubuntu 20.04 LTS:
>
>man SSL_CTX_get_security_level.3ssl

1) I searched high, low, and sideways, and couldn't find any
documentation of how to override this via a config file or environment
variable. Regarding command line, I imagine that is going to be
different for each program, and I did manage to figure out how to do it
for curl, but it took a huge amount of educated effort that the vast
majority of users are not going to be able to figure out.

2) I don't know what deb the man pages for the OpenSSL API are in, but
whichever one it is, it's not in the package install set that most
people get. That man page is not available on my system, for example.

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

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in openssl package in Ubuntu:
  New

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/;)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

2020-02-25 Thread Jonathan Kamens
Aha! `curl -v --ciphers 'DEFAULT:@SECLEVEL=1' https://www.toodledo.com/`
works but `curl -v --ciphers 'DEFAULT:@SECLEVEL=2'
https://www.toodledo.com/` fails.

According to
https://www.openssl.org/docs/man1.1.0/man3/SSL_CTX_get_security_level.html,
the default security level for the library is 1 if it isn't specified at
compile time. Has Canonical made a decision to set a higher security
level by default?

Oh, wait, it appears that yes it has. `openssl version -a` says
`-DOPENSSL_TLS_SECURITY_LEVEL=2`.

It appears that this was an intentional change? I question the
advisability of this, especially since it doesn't appear that there's
any way to override it in a configuration file (is there?).

I am not sure it is advisable for command-line tools in the OS to have
stricter security level requirements than users' browsers?

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

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in openssl package in Ubuntu:
  New

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/;)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

2020-02-25 Thread Jonathan Kamens
I may be misunderstanding something, but as far as I can tell this is
not a cipher mismatch problem.

According to
https://www.ssllabs.com/ssltest/analyze.html?d=www.toodledo.com, the
site supports TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256. According to
"openssl ciphers", openssl supports ECDHE-RSA-AES128-GCM-SHA256, which
apperas to be the same thing. But `curl -v --ciphers ECDHE-RSA-AES128
-GCM-SHA256 --tlsv1.2 --tls-max 1.2 https://www.toodledo.com/` still
fails.

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

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in openssl package in Ubuntu:
  New

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/;)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+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 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

2020-02-25 Thread Jonathan Kamens
Example output:

jik@jik-x1:~$ curl -v https://www.toodledo.com/
*   Trying 146.20.52.175:443...
* TCP_NODELAY set
* Connected to www.toodledo.com (146.20.52.175) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, handshake failure (552):
* error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake 
failure

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

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in openssl package in Ubuntu:
  New

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/;)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+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 1864689] [NEW] openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox

2020-02-25 Thread Jonathan Kamens
Public bug reported:

openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
connect to.

Reproduce with: `curl -v https://www.toodledo.com/'

or: `openssl s_client -connect www.toodledo.com:443`

or: `python3 -c 'import requests;
requests.get("https://www.toodledo.com/;)'`

or: `wget https://www.toodledo.com/`

These worked in Ubuntu 19.10 and don't work in 20.04.

I've tried all sorts of things to debug this further and I've just run
into walls. I hope someone who understands more about this stuff will be
able to figure it out.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: openssl 1.1.1d-2ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 25 13:01:22 2020
InstallationDate: Installed on 2019-08-16 (192 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: openssl
UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

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


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

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

Title:
  openssl in 20.04 can't connect to site that was fine in 19.10 and is
  fine in Chrome and Firefox

Status in openssl package in Ubuntu:
  New

Bug description:
  openssl in Ubuntu 20.04 (focal) refuses to connect to a web site that
  openssl in Ubuntu 19.10 (eoan), Chrome, and Firefox are all happy to
  connect to.

  Reproduce with: `curl -v https://www.toodledo.com/'

  or: `openssl s_client -connect www.toodledo.com:443`

  or: `python3 -c 'import requests;
  requests.get("https://www.toodledo.com/;)'`

  or: `wget https://www.toodledo.com/`

  These worked in Ubuntu 19.10 and don't work in 20.04.

  I've tried all sorts of things to debug this further and I've just run
  into walls. I hope someone who understands more about this stuff will
  be able to figure it out.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openssl 1.1.1d-2ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 25 13:01:22 2020
  InstallationDate: Installed on 2019-08-16 (192 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to focal on 2020-01-31 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689/+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 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-02-12 Thread Jonathan Hartley
For others with similar problems, I'm keeping my findings up to date
here: https://www.tartley.com/dina-as-otf

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.

  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7

  I have always installed it using a script:

  # install dina
  sudo mkdir -p /usr/share/fonts/Dina
  cd /usr/share/fonts/Dina
  sudo unzip ~/Downloads/Dina.zip

  # enable bitmap fonts
  sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf

  # rebuild the cache
  fc-cache -f -v

  # Set as default mono font
  gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"

  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.

  I installed Focal today, using `sudo do-release-upgrade -d`.

  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)

  gnome-font-viewer does not list any of the installed bitmap fonts.

  While trying to find a fix, I tried a few changes to the above script,
  which did not help:

  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:

  (
  cd /etc/fonts/conf.d
  sudo rm -f 70-no-bitmaps.conf
  sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
  )

    (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

To manage notifications about this bug go to:
https://bugs.launchpad.net/pango/+bug/1861340/+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 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-02-05 Thread Jonathan Hartley
I succeeded with the process of converting a bitmap font into a vector
format with embedded bitmaps, which Pango will display. It took me hours
to figure out, so for anyone else:

Use fontforge, as described here:
https://gitlab.gnome.org/GNOME/pango/issues/386#note_570411

The gotcha is that once you've installed the resulting font, then it
displays invisibly in font selection dialogs. However, don't give up
there! If you click around blindly to select the font you want, then the
font displays correctly in gnome-terminal, including all size
variations, with bold and italic variants.

There is some residual weirdness in that selecting a font size that is
not defined in the bitmap (e.g. when using 'ctrl-+'), the terminal goes
completely blank instead of falling back to another font.

For me, using fonttosfnt, as also described in that thread, had many
serious issues (eg the resulting font only preserved the bitmap's
smallest size variant)

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.

  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7

  I have always installed it using a script:

  # install dina
  sudo mkdir -p /usr/share/fonts/Dina
  cd /usr/share/fonts/Dina
  sudo unzip ~/Downloads/Dina.zip

  # enable bitmap fonts
  sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf

  # rebuild the cache
  fc-cache -f -v

  # Set as default mono font
  gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"

  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.

  I installed Focal today, using `sudo do-release-upgrade -d`.

  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)

  gnome-font-viewer does not list any of the installed bitmap fonts.

  While trying to find a fix, I tried a few changes to the above script,
  which did not help:

  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:

  (
  cd /etc/fonts/conf.d
  sudo rm -f 70-no-bitmaps.conf
  sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
  )

    (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

To manage notifications about this bug go to:
https://bugs.launchpad.net/pango/+bug/1861340/+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 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-02-03 Thread Jonathan Hartley
Thanks for talking me through it Sebastien. Fair enough, I defer to your
experience on that.

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.

  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7

  I have always installed it using a script:

  # install dina
  sudo mkdir -p /usr/share/fonts/Dina
  cd /usr/share/fonts/Dina
  sudo unzip ~/Downloads/Dina.zip

  # enable bitmap fonts
  sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf

  # rebuild the cache
  fc-cache -f -v

  # Set as default mono font
  gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"

  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.

  I installed Focal today, using `sudo do-release-upgrade -d`.

  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)

  gnome-font-viewer does not list any of the installed bitmap fonts.

  While trying to find a fix, I tried a few changes to the above script,
  which did not help:

  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:

  (
  cd /etc/fonts/conf.d
  sudo rm -f 70-no-bitmaps.conf
  sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
  )

    (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

To manage notifications about this bug go to:
https://bugs.launchpad.net/pango/+bug/1861340/+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 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-02-02 Thread Jonathan Hartley
I don't think 'fix released' is the right status.

Could Focal use a slightly older version of Pango, to keep bitmap fonts
working for another 6 months, hoping it becomes clearer how to continue
supporting them going forward?

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

Status in Pango:
  Fix Released
Status in pango1.0 package in Ubuntu:
  Triaged

Bug description:
  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.

  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7

  I have always installed it using a script:

  # install dina
  sudo mkdir -p /usr/share/fonts/Dina
  cd /usr/share/fonts/Dina
  sudo unzip ~/Downloads/Dina.zip

  # enable bitmap fonts
  sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf

  # rebuild the cache
  fc-cache -f -v

  # Set as default mono font
  gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"

  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.

  I installed Focal today, using `sudo do-release-upgrade -d`.

  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)

  gnome-font-viewer does not list any of the installed bitmap fonts.

  While trying to find a fix, I tried a few changes to the above script,
  which did not help:

  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:

  (
  cd /etc/fonts/conf.d
  sudo rm -f 70-no-bitmaps.conf
  sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
  )

    (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

To manage notifications about this bug go to:
https://bugs.launchpad.net/pango/+bug/1861340/+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 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug

2020-02-02 Thread Jonathan Kamens
So, um, this has been broken since Bionic and still not fixed, despite
the fact that ubuntu-bug is the only supported way for reporting bugs?

This seems highly sub-optimal.

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

Title:
  turning off "Send error reports to Canonical" prevents using ubuntu-
  bug

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Bionic:
  Triaged
Status in apport source package in Disco:
  Triaged
Status in apport source package in Eoan:
  Triaged

Bug description:
  Impact
  --
  apport was modified (bug 1778497) to reduce the number of times people have 
to respond to crash reports, however the changes introduced a check to see if 
whoopsie is enabled. That check is done for any type of report, not just 
crashes, and subsequently people can not use ubuntu-bug to report bugs if 
whoopsie is disabled which is wrong as whoopsie is only for uploading crashes 
to the Error Tracker.

  Test Case
  -
  1) On a system with Gnome installed use the Privacy control panel and set 
"Send error reports to Canonical" to Off
  2) In a terminal run 'ubuntu-bug gnome-terminal'
  3) Click "Send" and observe nothing happening (if something does happen 
confirm that whoopsie is disabled via 'systemctl is-enabled whoopsie' - there 
may be a bug in the control panel)

  
  Original Description
  
  Ubuntu 18.04.1 LTS, X11 gnome session.

  For some reason ubuntu-bug  no longer opens a browser
  window, so it is not possible to enter useful bug detauls, or even
  know the bug number.

  After prompting whether or not to Send the report, clicking "Send"
  just closes appport and nothing else ever happens.  The exit status of
  "ubuntu-bug" is zero.

  This worked fine before, but it has been many months since I tried to
  submit a bug.

  strace shows many stat calls on plausible browser paths, including the
  one that is correct (/usr/bin/firefox, which returned a successful
  stat call).  I'll attach the trace output from

     strace -f -o /tmp/strace.log ubuntu-bug apport

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+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 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-01-31 Thread Jonathan Hartley
I'm speculating that pango 1.44 dropping support for bitmap fonts might
be a cause: https://gitlab.gnome.org/GNOME/pango/issues/386

** Package changed: fontconfig (Ubuntu) => pango1.0 (Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/pango/issues #386
   https://gitlab.gnome.org/GNOME/pango/issues/386

** Description changed:

  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.
  
  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7
  
  I have always installed it using a script:
  
  # install dina
  sudo mkdir -p /usr/share/fonts/Dina
  cd /usr/share/fonts/Dina
  sudo unzip ~/Downloads/Dina.zip
  
  # enable bitmap fonts
  sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf
  
  # rebuild the cache
  fc-cache -f -v
  
  # Set as default mono font
  gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"
  
  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.
  
  I installed Focal today, using `sudo do-release-upgrade -d`.
  
  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)
  
- I cannot run 'gnome-font-viewer' to check things out, presumably due to some 
variant of:
+ ~~I cannot run 'gnome-font-viewer' to check things out, presumably due to 
some variant of:
  https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819
- (the window displays but immediately locks up.)
+ (the window displays but immediately locks up.)~~
+ UPDATE: gnome-font-viewer runs fine today. All bitmap fonts are not present.
  
  While trying to find a fix, I tried a few changes to the above script,
  which did not help:
  
  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:
  
  (
  cd /etc/fonts/conf.d
  sudo rm -f 70-no-bitmaps.conf
  sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
  )
  
    (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

** Description changed:

  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.
  
  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7
  
  I have always installed it using a script:
  
  # install dina
  sudo mkdir -p /usr/share/fonts/Dina
  cd /usr/share/fonts/Dina
  sudo unzip ~/Downloads/Dina.zip
  
  # enable bitmap fonts
  sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf
  
  # rebuild the cache
  fc-cache -f -v
  
  # Set as default mono font
  gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"
  
  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.
  
  I installed Focal today, using `sudo do-release-upgrade -d`.
  
  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)
  
- ~~I cannot run 'gnome-font-viewer' to check things out, presumably due to 
some variant of:
- https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819
- (the window displays but immediately locks up.)~~
- UPDATE: gnome-font-viewer runs fine today. All bitmap fonts are not present.
+ gnome-font-viewer does not list any of the installed bitmap fonts.
  
  While trying to find a fix, I tried a few changes to the above script,
  which did not help:
  
  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:
  
  (
  cd /etc/fonts/conf.d
  sudo rm -f 70-no-bitmaps.conf
  sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
  )
  
    (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.

  The font is 'Dina', from here:
  

[Touch-packages] [Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)

2020-01-31 Thread Jonathan Hartley
I semi-guessed at package 'fontconfig' to associate. Advice welcome.

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

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

Title:
  All bitmap fonts no longer visible after upgrade 19.10 -> Focal
  (development)

Status in fontconfig package in Ubuntu:
  New

Bug description:
  For years I've installed a bitmap font for my terminals, but since I
  upgraded to Focal (development branch) today, it (and other bitmap
  fonts) no longer work.

  The font is 'Dina', from here:
  
http://www.dcmembers.com/jibsen/download/61/?unapproved=504=f1abb9d89caafa881dcfc05cd32372e7

  I have always installed it using a script:

  # install dina
  sudo mkdir -p /usr/share/fonts/Dina
  cd /usr/share/fonts/Dina
  sudo unzip ~/Downloads/Dina.zip

  # enable bitmap fonts
  sudo rm -f /etc/fonts/conf.d/70-no-bitmaps.conf

  # rebuild the cache
  fc-cache -f -v

  # Set as default mono font
  gsettings set org.gnome.desktop.interface monospace-font-name "Dina 8"

  This has always worked in the past, through many versions of Ubuntu,
  including 19.10.

  I installed Focal today, using `sudo do-release-upgrade -d`.

  Now the above script does not make Dina visible in font selectors such
  as that produced by the Tweaks / Fonts / [Monospace Text] button.
  Terminals that were previously configured to use that font now display
  the "box of hex digits" characters (what are they called?)

  I cannot run 'gnome-font-viewer' to check things out, presumably due to some 
variant of:
  https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1375819
  (the window displays but immediately locks up.)

  While trying to find a fix, I tried a few changes to the above script,
  which did not help:

  * Unzip to "$HOME/.fonts" instead
  * Trying other symlinks in the fonts config.d:

  (
  cd /etc/fonts/conf.d
  sudo rm -f 70-no-bitmaps.conf
  sudo ln -sf ../conf.avail/70-yes-bitmaps.conf
  )

    (tried with both 'yes-bitmaps' and 'force-bitmaps')
  * fc-cache -r # "really" force cache re-creation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1861340/+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 1860676] Re: apt-get dist-upgrade -y hangs during e2fsprogs update

2020-01-24 Thread Jonathan Kamens
I can no longer reproduce it either. *shrug*

P.S. Hi Ted long time no see.

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

Title:
  apt-get dist-upgrade -y hangs during e2fsprogs update

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  My recent apt-get dist-upgrade -y hung here:

  ...
  update-initramfs: deferring update (trigger activated)
  e2scrub_all.service is a disabled or a static unit not running, not starting 
it.

  I did a pstree on the apt-get process and saw this:

  apt-get(31290)───dpkg(562)───e2fsprogs.posti(587)───systemctl(722
  )───systemd-tty-ask(863)

  Relevant processes:

  root   863  0.0  0.0  15976  5996 pts/12   S+   09:13   0:00 
/bin/systemd-tty-ask-password-agent --watch
  root   722  0.0  0.0  19668  3672 pts/12   S+   09:13   0:00 
/bin/systemctl restart e2scrub_all.timer e2scrub_reap.service

  I killed the systemd-tty-ask-password-agent process, and it became
  defunct but didn't die. So I killed the systemctl restart process, and
  the upgrade continued, apparently without noticing that the systemctl
  restart failed, which is a separate issue.

  When I ran "sudo systemctl restart e2scrub_all.timer
  e2scrub_reap.service" from the command line after the upgrade, it also
  hung with systemd-tty-ask-password-agent apparently waiting for
  something, so this problem isn't unique to upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: e2fsprogs 1.45.3-4ubuntu2.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 09:37:04 2020
  InstallationDate: Installed on 2019-09-12 (132 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: e2fsprogs
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (125 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860676/+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 1860676] [NEW] apt-get dist-upgrade -y hangs during e2fsprogs update

2020-01-23 Thread Jonathan Kamens
Public bug reported:

My recent apt-get dist-upgrade -y hung here:

...
update-initramfs: deferring update (trigger activated)
e2scrub_all.service is a disabled or a static unit not running, not starting it.

I did a pstree on the apt-get process and saw this:

apt-get(31290)───dpkg(562)───e2fsprogs.posti(587)───systemctl(722
)───systemd-tty-ask(863)

Relevant processes:

root   863  0.0  0.0  15976  5996 pts/12   S+   09:13   0:00 
/bin/systemd-tty-ask-password-agent --watch
root   722  0.0  0.0  19668  3672 pts/12   S+   09:13   0:00 /bin/systemctl 
restart e2scrub_all.timer e2scrub_reap.service

I killed the systemd-tty-ask-password-agent process, and it became
defunct but didn't die. So I killed the systemctl restart process, and
the upgrade continued, apparently without noticing that the systemctl
restart failed, which is a separate issue.

When I ran "sudo systemctl restart e2scrub_all.timer
e2scrub_reap.service" from the command line after the upgrade, it also
hung with systemd-tty-ask-password-agent apparently waiting for
something, so this problem isn't unique to upgrades.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: e2fsprogs 1.45.3-4ubuntu2.1
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 23 09:37:04 2020
InstallationDate: Installed on 2019-09-12 (132 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: e2fsprogs
UpgradeStatus: Upgraded to eoan on 2019-09-20 (125 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

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


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

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

Title:
  apt-get dist-upgrade -y hangs during e2fsprogs update

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  My recent apt-get dist-upgrade -y hung here:

  ...
  update-initramfs: deferring update (trigger activated)
  e2scrub_all.service is a disabled or a static unit not running, not starting 
it.

  I did a pstree on the apt-get process and saw this:

  apt-get(31290)───dpkg(562)───e2fsprogs.posti(587)───systemctl(722
  )───systemd-tty-ask(863)

  Relevant processes:

  root   863  0.0  0.0  15976  5996 pts/12   S+   09:13   0:00 
/bin/systemd-tty-ask-password-agent --watch
  root   722  0.0  0.0  19668  3672 pts/12   S+   09:13   0:00 
/bin/systemctl restart e2scrub_all.timer e2scrub_reap.service

  I killed the systemd-tty-ask-password-agent process, and it became
  defunct but didn't die. So I killed the systemctl restart process, and
  the upgrade continued, apparently without noticing that the systemctl
  restart failed, which is a separate issue.

  When I ran "sudo systemctl restart e2scrub_all.timer
  e2scrub_reap.service" from the command line after the upgrade, it also
  hung with systemd-tty-ask-password-agent apparently waiting for
  something, so this problem isn't unique to upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: e2fsprogs 1.45.3-4ubuntu2.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 09:37:04 2020
  InstallationDate: Installed on 2019-09-12 (132 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: e2fsprogs
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (125 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860676/+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 1860676] Re: apt-get dist-upgrade -y hangs during e2fsprogs update

2020-01-23 Thread Jonathan Kamens
e2scrub_all.timer restarts just fine; it's the e2scrub_reap.service
restart that's hanging.

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

Title:
  apt-get dist-upgrade -y hangs during e2fsprogs update

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  My recent apt-get dist-upgrade -y hung here:

  ...
  update-initramfs: deferring update (trigger activated)
  e2scrub_all.service is a disabled or a static unit not running, not starting 
it.

  I did a pstree on the apt-get process and saw this:

  apt-get(31290)───dpkg(562)───e2fsprogs.posti(587)───systemctl(722
  )───systemd-tty-ask(863)

  Relevant processes:

  root   863  0.0  0.0  15976  5996 pts/12   S+   09:13   0:00 
/bin/systemd-tty-ask-password-agent --watch
  root   722  0.0  0.0  19668  3672 pts/12   S+   09:13   0:00 
/bin/systemctl restart e2scrub_all.timer e2scrub_reap.service

  I killed the systemd-tty-ask-password-agent process, and it became
  defunct but didn't die. So I killed the systemctl restart process, and
  the upgrade continued, apparently without noticing that the systemctl
  restart failed, which is a separate issue.

  When I ran "sudo systemctl restart e2scrub_all.timer
  e2scrub_reap.service" from the command line after the upgrade, it also
  hung with systemd-tty-ask-password-agent apparently waiting for
  something, so this problem isn't unique to upgrades.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: e2fsprogs 1.45.3-4ubuntu2.1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 23 09:37:04 2020
  InstallationDate: Installed on 2019-09-12 (132 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: e2fsprogs
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (125 days ago)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-10-23T16:51:18.143596

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860676/+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 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln

2019-11-14 Thread Jonathan
Installing ncsd worked well for me as well.

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

Title:
  [regression] systemd-logind crashed with SIGABRT in __libc_connect()
  from __GI_clnttcp_create() from __GI___libc_rpc_getport() from
  __GI_pmap_getport() from __GI_clnttcp_create()

Status in nis package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3

  ---

  configured system to use nis.  seems to be crashing when I attempt to
  use a NIS user account

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Fri Jan 26 13:45:06 2018
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
   Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z370 HD3
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at 
../sysdeps/unix/sysv/linux/connect.c:26
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, 
sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153
   __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, 
version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106
   __GI_pmap_getport (address=address@entry=0x7ffc27302060, 
program=program@entry=17, version=version@entry=2, 
protocol=protocol@entry=6) at pm_getport.c:154
   __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, 
prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, 
sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  Title: systemd-logind crashed with SIGABRT in __libc_connect()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys 
sysdesign tty uucp
  dmi.bios.date: 09/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 HD3-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 HD3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1745664/+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 1849545] [NEW] Graphics warning on restart

2019-10-23 Thread Jonathan
Public bug reported:

On restart it sometimes happens that I get a message to the effect that my 
graphics are operating in some kind of limited mode. An Xorg error is 
mentioned. On OK I get a few options such as 'try starting in default mode' and 
other options involving various possible tests, none of which seem to do much 
or have much effect.
Clicking on 'start in default mode' always (so far) allows me to continue 
normally however there follows a message 'ubuntu has experienced an error'
Wondering what's going on and whether I should be doing something different.
Somewhat ashamed of my ignorance. Been using Ubuntu for years but haven't 
bothered to delve into the OS :-)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-66-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Oct 23 19:22:45 2019
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
InstallationDate: Installed on 2019-04-20 (186 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
MachineType: LENOVO 2241WJE
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=aade17ba-9d15-4eac-86b2-2a2a6c6230bf ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/14/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET92WW (3.22 )
dmi.board.name: 2241WJE
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6FET92WW(3.22):bd12/14/2011:svnLENOVO:pn2241WJE:pvrThinkPadT500:rvnLENOVO:rn2241WJE:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T500
dmi.product.name: 2241WJE
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO
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: Wed Oct 23 19:13:21 2019
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2

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

Title:
  Graphics warning on restart

Status in xorg package in Ubuntu:
  New

Bug description:
  On restart it sometimes happens that I get a message to the effect that my 
graphics are operating in some kind of limited mode. An Xorg error is 
mentioned. On OK I get a few options such as 'try starting in default mode' and 
other options involving various possible tests, none of which seem to do much 
or have much effect.
  Clicking on 'start in default mode' always (so far) allows me to continue 
normally however there follows a message 'ubuntu has experienced an error'
  Wondering what's going on and whether I should be doing something different.
  Somewhat ashamed of my ignorance. Been using Ubuntu for years but haven't 
bothered to delve into the OS :-)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  

[Touch-packages] [Bug 1847651] [NEW] NetworkManager isn't pushing DNS server for openvpn connection to systemd-resolved

2019-10-10 Thread Jonathan Kamens
Public bug reported:

I imported an openvpn configuration with `nmcli c import type openvpn file 
config.ovpn`.
After doing that, I edited the IPv4 and IPv6 settings for the VPN to turn off 
automatic DNS servers and specify an IPv4 DNS server IP address explicitly.
I have /usr/lib/NetworkManager/conf.d/10-dns-resolved.conf which contains:

[main]
# We need to specify "dns=systemd-resolved" as for the time being our
# /etc/resolv.conf points to resolvconf's generated file instead of
# systemd-resolved's, so the auto-detection does not work.
dns=systemd-resolved

Given all this, what I believe _should_ happen is when I start the VPN,
/run/NetworkManager/no-stub-resolv.conf should be updated to list the
DNS server I've specified first, AND NetworkManager should tell systemd-
resolved to associate that DNS server with the tun0 network interface
created for the VPN.

The former happens, i.e., no-stub-resolv.conf is updated, but the latter
doesn't, i.e., systemd-reoslve --status and resolvectl status both do
not show the DNS server I've specified in the VPN settings.

As a result, my DNS server is not getting used.

I've hacked this all over the place and I can't figure out _any_ way,
when using systemd-resolved mode in NetworkManager, to get it to use my
VPN's DNS server when I enable the VPN.

Surely this behavior is not expected?

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: network-manager 1.20.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
Uname: Linux 5.3.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 10 14:19:17 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-09-12 (28 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 10.204.0.1 dev wlp0s20f3 proto dhcp metric 600 
 10.204.0.0/21 dev wlp0s20f3 proto kernel scope link src 10.204.3.73 metric 600 
 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to eoan on 2019-09-20 (20 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.20.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  NetworkManager isn't pushing DNS server for openvpn connection to
  systemd-resolved

Status in network-manager package in Ubuntu:
  New

Bug description:
  I imported an openvpn configuration with `nmcli c import type openvpn file 
config.ovpn`.
  After doing that, I edited the IPv4 and IPv6 settings for the VPN to turn off 
automatic DNS servers and specify an IPv4 DNS server IP address explicitly.
  I have /usr/lib/NetworkManager/conf.d/10-dns-resolved.conf which contains:

  [main]
  # We need to specify "dns=systemd-resolved" as for the time being our
  # /etc/resolv.conf points to resolvconf's generated file instead of
  # systemd-resolved's, so the auto-detection does not work.
  dns=systemd-resolved

  Given all this, what I believe _should_ happen is when I start the
  VPN, /run/NetworkManager/no-stub-resolv.conf should be updated to list
  the DNS server I've specified first, AND NetworkManager should tell
  systemd-resolved to associate that DNS server with the tun0 network
  interface created for the VPN.

  The former happens, i.e., no-stub-resolv.conf is updated, but the
  latter doesn't, i.e., systemd-reoslve --status and resolvectl status
  both do not show the DNS server I've specified in the VPN settings.

  As a result, my DNS server is not getting used.

  I've hacked this all over the place and I can't figure out _any_ way,
  when using systemd-resolved mode in NetworkManager, to get it to use
  my VPN's DNS server when I enable the VPN.

  Surely this behavior is not expected?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 10 14:19:17 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (28 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
 

[Touch-packages] [Bug 1843630] Re: ubuntu-bug not opening anything in the browser

2019-09-25 Thread Jonathan Kamens
jik@jik5:~$ sudo systemctl is-enabled whoopsie
disabled

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

Title:
  ubuntu-bug not opening anything in the browser

Status in apport package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to
  the developers?" with the "Don't send" and "Send" buttons, but when I
  click on "Send" nothing happens.

  I have the "problem_types" line commented out in
  /etc/apport/crashdb.conf, though I don't know if that's relevant when
  I'm trying to report a bug, not a crash.

  I have no idea how to troubleshoot this further. Please advise.

  The same problem occurs for "ubuntu-bug needrestart".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+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 1843630] Re: ubuntu-bug not opening anything in the browser

2019-09-24 Thread Jonathan Kamens
** Attachment added: "crashdb.conf"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+attachment/5290988/+files/crashdb.conf

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

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

Title:
  ubuntu-bug not opening anything in the browser

Status in apport package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to
  the developers?" with the "Don't send" and "Send" buttons, but when I
  click on "Send" nothing happens.

  I have the "problem_types" line commented out in
  /etc/apport/crashdb.conf, though I don't know if that's relevant when
  I'm trying to report a bug, not a crash.

  I have no idea how to troubleshoot this further. Please advise.

  The same problem occurs for "ubuntu-bug needrestart".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+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 1844897] [NEW] wifi icon has question mark in it even though network is fine

2019-09-21 Thread Jonathan Kamens
Public bug reported:

After experiencing some "turbulence" in my wifi (I rebooted my primary
wifi router, which caused my laptop to fallback onto a secondary access
point which didn't have full connectivity until the primary router
finished rebooting, then I rebooted the primary router a second time),
the wifi icon in my top bar stayed as the question-mark icon (i.e., the
icon that shows when Network Manager doesn't think you have full
connectivity) even after everything was back up and in fact my
connectivity was fine.

Turning wifi off and back on did not cause the question mark to go away.
Restarting Network Manager did not cause the question mark to go away.
Switching to a different wifi network and then back to the previous one
didn't cause the question mark to go away. I had to reboot my laptop to
get the question mark to go away.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: network-manager 1.20.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 21 18:35:48 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2019-09-12 (9 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IpRoute:
 default via 192.168.4.1 dev wlp0s20f3 proto dhcp metric 600 
 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
 192.168.4.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.4.103 metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: Upgraded to eoan on 2019-09-20 (1 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.20.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  wifi icon has question mark in it even though network is fine

Status in network-manager package in Ubuntu:
  New

Bug description:
  After experiencing some "turbulence" in my wifi (I rebooted my primary
  wifi router, which caused my laptop to fallback onto a secondary
  access point which didn't have full connectivity until the primary
  router finished rebooting, then I rebooted the primary router a second
  time), the wifi icon in my top bar stayed as the question-mark icon
  (i.e., the icon that shows when Network Manager doesn't think you have
  full connectivity) even after everything was back up and in fact my
  connectivity was fine.

  Turning wifi off and back on did not cause the question mark to go
  away. Restarting Network Manager did not cause the question mark to go
  away. Switching to a different wifi network and then back to the
  previous one didn't cause the question mark to go away. I had to
  reboot my laptop to get the question mark to go away.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 21 18:35:48 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-09-12 (9 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  IpRoute:
   default via 192.168.4.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   192.168.4.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.4.103 
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to eoan on 2019-09-20 (1 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.2   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844897/+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 1843630] [NEW] ubuntu-bug not opening anything in the browser

2019-09-11 Thread Jonathan Kamens
Public bug reported:

Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to
the developers?" with the "Don't send" and "Send" buttons, but when I
click on "Send" nothing happens.

I have the "problem_types" line commented out in
/etc/apport/crashdb.conf, though I don't know if that's relevant when
I'm trying to report a bug, not a crash.

I have no idea how to troubleshoot this further. Please advise.

The same problem occurs for "ubuntu-bug needrestart".

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

** Package changed: linphone (Ubuntu) => apport (Ubuntu)

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

Title:
  ubuntu-bug not opening anything in the browser

Status in apport package in Ubuntu:
  New

Bug description:
  Ubuntu 19.04, "ubuntu-bug apport" pops up the "Send problem report to
  the developers?" with the "Don't send" and "Send" buttons, but when I
  click on "Send" nothing happens.

  I have the "problem_types" line commented out in
  /etc/apport/crashdb.conf, though I don't know if that's relevant when
  I'm trying to report a bug, not a crash.

  I have no idea how to troubleshoot this further. Please advise.

  The same problem occurs for "ubuntu-bug needrestart".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1843630/+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 1822261] [NEW] Upgrade of procps disables net.ipv4.ip_forward=1

2019-03-29 Thread Jonathan Kaulard
Public bug reported:

Expected behavior:
Settings in /etc/sysctl.conf won't be changed by an upgrade or there will be a 
prompt if the original file should be overwritten.

What happened:
After performing an upgrade of package procps IPv4Forwarding was disabled in 
/etc/sysctl.conf without asking:

# Uncomment the next line to enable packet forwarding for IPv4
#net.ipv4.ip_forward=1

I was able to reproduce this behavior by using unattended-upgrades and
also by upgrading manually (apt-get upgrade)

My system:

lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04

apt-cache policy procps
procps:
  Installed: 2:3.3.12-3ubuntu1.1
  Candidate: 2:3.3.12-3ubuntu1.1
  Version table:
 *** 2:3.3.12-3ubuntu1.1 500
500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 2:3.3.12-3ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

** Affects: procps (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Description changed:

  Expected behavior:
  Settings in /etc/sysctl.conf won't be changed by an upgrade or there will be 
a prompt if the original file should be overwritten.
  
  What happened:
  After performing an upgrade of package procps IPv4Forwarding was disabled in 
/etc/sysctl.conf without asking:
  
  # Uncomment the next line to enable packet forwarding for IPv4
- net.ipv4.ip_forward=1
+ #net.ipv4.ip_forward=1
  
  I was able to reproduce this behavior by using unattended-upgrades and
  also by upgrading manually (apt-get upgrade)
  
  My system:
  
  lsb_release -rd
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  
  apt-cache policy procps
  procps:
-   Installed: 2:3.3.12-3ubuntu1.1
-   Candidate: 2:3.3.12-3ubuntu1.1
-   Version table:
-  *** 2:3.3.12-3ubuntu1.1 500
- 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  2:3.3.12-3ubuntu1 500
- 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+   Installed: 2:3.3.12-3ubuntu1.1
+   Candidate: 2:3.3.12-3ubuntu1.1
+   Version table:
+  *** 2:3.3.12-3ubuntu1.1 500
+ 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  2:3.3.12-3ubuntu1 500
+ 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

Title:
  Upgrade of procps disables net.ipv4.ip_forward=1

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Expected behavior:
  Settings in /etc/sysctl.conf won't be changed by an upgrade or there will be 
a prompt if the original file should be overwritten.

  What happened:
  After performing an upgrade of package procps IPv4Forwarding was disabled in 
/etc/sysctl.conf without asking:

  # Uncomment the next line to enable packet forwarding for IPv4
  #net.ipv4.ip_forward=1

  I was able to reproduce this behavior by using unattended-upgrades and
  also by upgrading manually (apt-get upgrade)

  My system:

  lsb_release -rd
  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  apt-cache policy procps
  procps:
    Installed: 2:3.3.12-3ubuntu1.1
    Candidate: 2:3.3.12-3ubuntu1.1
    Version table:
   *** 2:3.3.12-3ubuntu1.1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2:3.3.12-3ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1822261/+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 1819969] Re: gdb-multiarch does not include RISC-V architecture

2019-03-22 Thread Jonathan Behrens
As per http://packaging.ubuntu.com/html/fixing-a-bug.html, I'm directly
including a patch. I've tested this locally and confirmed that these
changes enable debugging RISC-V programs running inside very recent
versions of QEMU. As noted before, it has also already been applied to
the Debian version of the package.

** Patch added: "patch.diff"
   
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1819969/+attachment/5248684/+files/patch.diff

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

Title:
  gdb-multiarch does not include RISC-V architecture

Status in gdb package in Ubuntu:
  New

Bug description:
  This issue was recently fixed in Debian, but seems to have not been
  pulled into Ubuntu: https://salsa.debian.org/gdb-
  team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175

  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  gdb-multiarch:
Installed: 8.2.90-0ubuntu1
Candidate: 8.2.90-0ubuntu1
Version table:
   *** 8.2.90-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1819969/+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 1819969] [NEW] gdb-multiarch does not include RISC-V architecture

2019-03-13 Thread Jonathan Behrens
Public bug reported:

This issue was recently fixed in Debian, but seems to have not been
pulled into Ubuntu: https://salsa.debian.org/gdb-
team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175

Description:Ubuntu Disco Dingo (development branch)
Release:19.04

gdb-multiarch:
  Installed: 8.2.90-0ubuntu1
  Candidate: 8.2.90-0ubuntu1
  Version table:
 *** 8.2.90-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages
100 /var/lib/dpkg/status

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

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

Title:
  gdb-multiarch does not include RISC-V architecture

Status in gdb package in Ubuntu:
  New

Bug description:
  This issue was recently fixed in Debian, but seems to have not been
  pulled into Ubuntu: https://salsa.debian.org/gdb-
  team/gdb/commit/e59e4e54af0fbe9086c40ab80a1000d5c50c7175

  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  gdb-multiarch:
Installed: 8.2.90-0ubuntu1
Candidate: 8.2.90-0ubuntu1
Version table:
   *** 8.2.90-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1819969/+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 1777994] Re: the header xcb/xinput.h is missing

2019-03-04 Thread Jonathan Riddell
testing on bionic with bionic-proposed enabled

I can successfully install libxcb-xinput-dev and libxcb-xinput0 and they
contain the necessary files.  I can install libxcb* and it includes the
same files as before.


** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  the header xcb/xinput.h is missing

Status in libxcb package in Ubuntu:
  Fix Released
Status in libxcb source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Allow Qt 5.12 to be compiled with full input support.  This allows 
applications to be built using complex input devices such as drawing pads.  
This is used in e.g Krita which KDE builds into a Snap package for 
distribution.  Currently Krita does not work with pen input devices with 
pressure sensitivity.

  [Test Case]
  Install Krita with Qt 5.12 from current Snap and note how pressure 
sensitivity does not work.

  [Regression Potential] 
  None that I can see, it's just packaging a few new header files.

  

  
  I suspect this means there should be another package, libxcb-xinput-dev 
perhaps?

  I already did sudo apt install "libxcb*dev" to get all related dev
  packages, but none of them provide xcb/xinput.h.

  The result is that when building Qt from source, it's necessary to use
  a copy of this file which Qt provides
  (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing
  from the system.  So if you don't give the option -qt-xcb to
  configure, then Qt will be built without multi-touch support.

  https://bugreports.qt.io/browse/QTBUG-69045

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libxcb1-dev 1.13-1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 21 08:32:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:3802]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc.
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc.
   Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Y7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  SourcePackage: libxcb
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
  dmi.product.family: YOGA 920-13IKB
  dmi.product.name: 80Y7
  dmi.product.version: Lenovo YOGA 920-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994/+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 1818250] Re: No HDMI Showing

2019-03-01 Thread Jonathan Whitney
So this was caused because I still had "nomodeset" in my grub, which I
had needed for the monitor to work after the initial install. Once I
took it out, everything works fine. Oops.

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

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

Title:
  No HDMI Showing

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 18.04, Dell Inspiron 14 with Intel graphics. HDMI worked fine
  when I had Windows on the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Fri Mar  1 23:45:17 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:06ac]
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 14-3452
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=c0f6a434-daaf-4365-8d4e-fe4ca37a190f ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.3.0
  dmi.board.name: 0TCR6W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.3.0:bd02/01/2018:svnDellInc.:pnInspiron14-3452:pvr4.3.0:rvnDellInc.:rn0TCR6W:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 14-3452
  dmi.product.sku: 06AC
  dmi.product.version: 4.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1818250/+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 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

2019-03-01 Thread Jonathan Kamens
I called Lenovo and asked and the support rep I spoke with said that the
X1 Carbon's fingerprint reader isn't supported in Linux yet.

I don't know whether to trust that information as accurate, but that's
what he said.

I don't know whether that's worthy of a separate bug report or not. I
mean, there's lots of unsupported hardware out there, right, does the
fact that a particular device is not supported by Ubuntu deserve a bug
report?

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1817897/+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 1818250] [NEW] No HDMI Showing

2019-03-01 Thread Jonathan Whitney
Public bug reported:

Ubuntu 18.04, Dell Inspiron 14 with Intel graphics. HDMI worked fine
when I had Windows on the machine.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: LXQt
Date: Fri Mar  1 23:45:17 2019
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
   Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:06ac]
InstallationDate: Installed on 2019-02-20 (8 days ago)
InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
MachineType: Dell Inc. Inspiron 14-3452
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=c0f6a434-daaf-4365-8d4e-fe4ca37a190f ro quiet splash nomodeset 
vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 4.3.0
dmi.board.name: 0TCR6W
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvr4.3.0:bd02/01/2018:svnDellInc.:pnInspiron14-3452:pvr4.3.0:rvnDellInc.:rn0TCR6W:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 14-3452
dmi.product.sku: 06AC
dmi.product.version: 4.3.0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


** Tags: amd64 apport-bug cosmic 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/1818250

Title:
  No HDMI Showing

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04, Dell Inspiron 14 with Intel graphics. HDMI worked fine
  when I had Windows on the machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: LXQt
  Date: Fri Mar  1 23:45:17 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [1028:06ac]
  InstallationDate: Installed on 2019-02-20 (8 days ago)
  InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 14-3452
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=c0f6a434-daaf-4365-8d4e-fe4ca37a190f ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 4.3.0
  dmi.board.name: 0TCR6W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr4.3.0:bd02/01/2018:svnDellInc.:pnInspiron14-3452:pvr4.3.0:rvnDellInc.:rn0TCR6W:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 14-3452
  dmi.product.sku: 06AC
  dmi.product.version: 4.3.0
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: 

[Touch-packages] [Bug 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

2019-02-27 Thread Jonathan Kamens
As far as I can tell, the BIOS is able to see the fingerprint reader --
I just booted into the BIOS and told it to reset the fingerprint data,
and it said that it had done so successfully -- so this appears to be a
Linux-specific issue.

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1817897/+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 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

2019-02-27 Thread Jonathan Kamens
I have a new Thinkpad X1 Carbon 6th generation. I can see the
fingerprint reader right next to the trackpad, and the specs say that it
has one, but I don't see it showing up in the output of lspci or lsusb.
Maybe I'm missing it? Maybe it's not supported? Or maybe there's a
hardware issue? I'm not sure how to tell.

lsusb output:

Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0bda:0328 Realtek Semiconductor Corp. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 06cb:009a Synaptics, Inc. 
Bus 001 Device 005: ID 04f2:b614 Chicony Electronics Co., Ltd 
Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
Bus 001 Device 003: ID 04f2:b615 Chicony Electronics Co., Ltd 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1817897/+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 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

2019-02-27 Thread Jonathan Kamens
So, whether or not I needed to run pam-auth-update, doing so and
enabling fingerprint authentication there should not cause GDM to break,
nor should the other weird behavior I described above be happening.

Having said that, yes, I was trying to enable login with fingerprint. I
googled how to do that on Ubuntu and found this page,
https://help.ubuntu.com/stable/ubuntu-help/session-fingerprint.html.en.
But when I followed the instructions there and opened the Users panel,
there was nothing there about fingerprint login. So I googled more and
found this page, https://askubuntu.com/questions/1049526/fingerprint-
activation-on-ubuntu-18-04, which mentioned using pam-auth-update to
ensure that fingerprint authentication was enabled. So I ran pam-auth-
update and found that it wasn't enabled and enabled it, which led to the
problems described above.

If I shouldn't have had to do any of that to be able to configure
fingerprint login, then something else is wrong and I don't even know
where to start looking to figure out what, but regardless of that, the
issues that I encountered with pam-auth-update behaving poorly are still
real.

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1817897/+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 1817897] Re: attempting to enable fingerprint with pam-auth-update breaks gdm

2019-02-27 Thread Jonathan Kamens
Actually, it's even weirder than that.

I went through all this several times while trying to narrow down the
repro steps, and it's all very bizarre. Somehow I managed to get gdm
working again, and then in a logged in gdm session, I enabled
fingerprint, and exited from pam-auth-update, then ran pam-auth-update
again and disabled fingerprint and re-enabled register user sessions
which had once again somehow magically gotten disabled, but then I ran
pam-auth-update a third time and register user sessions was STILL
disabled even though I'd just enabled it, and then when I rebooted GDM
wouldn't work again. So at that point I logged in on a VT and ran pam-
auth-update again and selected register user sessions again, and then
just out of curiosity ran pam-auth-update again and this time register
user sessions was still selected, so I exited and rebooted and GDM
worked again.

There is something very bizarre going on here.

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

Title:
  attempting to enable fingerprint with pam-auth-update breaks gdm

Status in pam package in Ubuntu:
  New

Bug description:
  I ran sudo pam-auth-update, enabled "Fingerprint authentication",
  selected "OK", and then rebooted.

  GDM wouldn't start after the reboot:

  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activating service 
name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 
comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined")
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: 
dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 
'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with 
status 1
  Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to 
register display with display manager

  I logged in on a VT and ran pam-auth-update again. I observed that
  "Register user sessions in the systemd control group" was not
  selected, even though my recollection was that it had been selected
  before I enabled fingerprint authentication, and I didn't disable it.

  I unselected fingerprint authentication and selected "Register user
  sessions in the systemd control group" and rebooted again. GDM started
  working again.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: libpam-runtime 1.3.1-5ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
  Uname: Linux 4.19.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 27 06:31:32 2019
  InstallationDate: Installed on 2019-02-26 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: pam
  UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)

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


  1   2   3   4   5   >