[Touch-packages] [Bug 1956845] [NEW] Xorg crash

2022-01-08 Thread pigs-on-the-swim
Public bug reported:

this is additional information related to [Bug 1955049] about amdgpu kernel 
errors. 
The test of kernel 5.16.0-051600rc8drmtip20220105-generic is quite promising: 
This is the first crash after several hours of use. So this report is related 
to Bug 1955049. 
This report is created using SSH connection to the machine because the GUI did 
not "come back" after the crash. A subsequent reboot will be conducted soon 
after submitting this report.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
Uname: Linux 5.16.0-051600rc8drmtip20220105-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Jan  9 00:29:39 2022
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus: vhba, 20211218: added
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 
00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8]
InstallationDate: Installed on 2020-12-16 (388 days ago)
InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.16.0-051600rc8drmtip20220105-generic 
root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "InputClass"
 Identifier "middle button emulation class"
 MatchIsPointer "on"
 Option "Emulate3Buttons" "on"
 EndSection
dmi.bios.date: 06/18/2020
dmi.bios.release: 5.14
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.20
dmi.board.name: B450 Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929
version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1
xserver.bootTime: Sat Jan  8 22:03:14 2022
xserver.configfile: /etc/X11/xorg.conf
xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.11-1ubuntu1.2
xserver.video_driver: amdgpu

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


** Tags: amd64 apport-bug crash hirsute third-party-packages ubuntu

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  this is additional information related to [Bug 1955049] about amdgpu kernel 
errors. 
  The test of kernel 5.16.0-051600rc8drmtip20220105-generic is quite promising: 
This is the first crash after several hours of use. So this report is related 
to Bug 1955049. 
  This report is created using SSH connection to the machine because the GUI 
did not "come back" after the crash. A subsequent reboot will be conducted soon 
after submitting this report.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  Uname: Linux 5.16.0-051600rc8drmtip20220105-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.11-0ubuntu65.4
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jan  9 00:29:39 2022
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus: vhba, 20211218: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) 

[Touch-packages] [Bug 1956833] Re: No GSS-SPNEGO support in jammy

2022-01-08 Thread Andreas Hasenack
** Bug watch added: Debian Bug tracker #1003355
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003355

** Also affects: cyrus-sasl2 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003355
   Importance: Unknown
   Status: Unknown

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

Title:
  No GSS-SPNEGO support in jammy

Status in cyrus-sasl2 package in Ubuntu:
  In Progress
Status in cyrus-sasl2 package in Debian:
  Unknown

Bug description:
  In jammy:
  root@j1:~# saslpluginviewer | head | grep SPNEGO
  root@j1:~# 

  Confirming against a windows 2016 active directory server, fully patched:
  root@j1:~# ldapwhoami -Y GSS-SPNEGO
  ldap_sasl_interactive_bind: Unknown authentication method (-6)
  additional info: SASL(-4): no mechanism available: No worthy mechs 
found

  
  gssapi (kerberos) works:
  root@j1:~# ldapwhoami -Y GSSAPI
  SASL/GSSAPI authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

  root@j1:~# klist
  Ticket cache: FILE:/tmp/krb5cc_0
  Default principal: administra...@internal.example.fake

  Valid starting ExpiresService principal
  01/08/22 22:31:48  01/09/22 08:31:48  
krbtgt/internal.example.f...@internal.example.fake
  renew until 01/09/22 22:31:45
  01/08/22 22:34:53  01/09/22 08:31:48  
ldap/win-kriet1e5elo.internal.example.fake@
  renew until 01/09/22 22:31:45
  Ticket server: 
ldap/win-kriet1e5elo.internal.example.f...@internal.example.fake

  
  In focal, GSS-SPNEGO works:
  root@f1:~# saslpluginviewer | head | grep SPNEGO
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
EXTERNAL NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS

  Confirming with ldapwhoami:
  root@f1:~# ldapwhoami -Y GSS-SPNEGO
  SASL/GSS-SPNEGO authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1956833/+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 1956833] Re: No GSS-SPNEGO support in jammy

2022-01-08 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/cyrus-sasl2/+git/cyrus-sasl2/+merge/413832

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

Title:
  No GSS-SPNEGO support in jammy

Status in cyrus-sasl2 package in Ubuntu:
  In Progress

Bug description:
  In jammy:
  root@j1:~# saslpluginviewer | head | grep SPNEGO
  root@j1:~# 

  Confirming against a windows 2016 active directory server, fully patched:
  root@j1:~# ldapwhoami -Y GSS-SPNEGO
  ldap_sasl_interactive_bind: Unknown authentication method (-6)
  additional info: SASL(-4): no mechanism available: No worthy mechs 
found

  
  gssapi (kerberos) works:
  root@j1:~# ldapwhoami -Y GSSAPI
  SASL/GSSAPI authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

  root@j1:~# klist
  Ticket cache: FILE:/tmp/krb5cc_0
  Default principal: administra...@internal.example.fake

  Valid starting ExpiresService principal
  01/08/22 22:31:48  01/09/22 08:31:48  
krbtgt/internal.example.f...@internal.example.fake
  renew until 01/09/22 22:31:45
  01/08/22 22:34:53  01/09/22 08:31:48  
ldap/win-kriet1e5elo.internal.example.fake@
  renew until 01/09/22 22:31:45
  Ticket server: 
ldap/win-kriet1e5elo.internal.example.f...@internal.example.fake

  
  In focal, GSS-SPNEGO works:
  root@f1:~# saslpluginviewer | head | grep SPNEGO
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
EXTERNAL NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS

  Confirming with ldapwhoami:
  root@f1:~# ldapwhoami -Y GSS-SPNEGO
  SASL/GSS-SPNEGO authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1956833/+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 1956833] Re: No GSS-SPNEGO support in jammy

2022-01-08 Thread Andreas Hasenack
Nice discussion at
https://bugzilla.redhat.com/show_bug.cgi?format=multiple=1943013

Fix: https://github.com/cyrusimap/cyrus-sasl/pull/644

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

** Changed in: cyrus-sasl2 (Ubuntu)
   Importance: Undecided => High

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: New => In Progress

** Changed in: cyrus-sasl2 (Ubuntu)
 Assignee: (unassigned) => Andreas Hasenack (ahasenack)

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

Title:
  No GSS-SPNEGO support in jammy

Status in cyrus-sasl2 package in Ubuntu:
  In Progress

Bug description:
  In jammy:
  root@j1:~# saslpluginviewer | head | grep SPNEGO
  root@j1:~# 

  Confirming against a windows 2016 active directory server, fully patched:
  root@j1:~# ldapwhoami -Y GSS-SPNEGO
  ldap_sasl_interactive_bind: Unknown authentication method (-6)
  additional info: SASL(-4): no mechanism available: No worthy mechs 
found

  
  gssapi (kerberos) works:
  root@j1:~# ldapwhoami -Y GSSAPI
  SASL/GSSAPI authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

  root@j1:~# klist
  Ticket cache: FILE:/tmp/krb5cc_0
  Default principal: administra...@internal.example.fake

  Valid starting ExpiresService principal
  01/08/22 22:31:48  01/09/22 08:31:48  
krbtgt/internal.example.f...@internal.example.fake
  renew until 01/09/22 22:31:45
  01/08/22 22:34:53  01/09/22 08:31:48  
ldap/win-kriet1e5elo.internal.example.fake@
  renew until 01/09/22 22:31:45
  Ticket server: 
ldap/win-kriet1e5elo.internal.example.f...@internal.example.fake

  
  In focal, GSS-SPNEGO works:
  root@f1:~# saslpluginviewer | head | grep SPNEGO
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
EXTERNAL NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS

  Confirming with ldapwhoami:
  root@f1:~# ldapwhoami -Y GSS-SPNEGO
  SASL/GSS-SPNEGO authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1956833/+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 1956833] Re: No GSS-SPNEGO support in jammy

2022-01-08 Thread Andreas Hasenack
In the jammy build log
(https://launchpadlibrarian.net/570726294/buildlog_ubuntu-jammy-
amd64.cyrus-sasl2_2.1.27+dfsg2-2build1_BUILDING.txt.gz), we have this
error which is not present in the impish build for example:

checking for SPNEGO support in GSSAPI libraries... ../configure: line 18854: 
ac_fn_c_try_run: command not found
no

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

Title:
  No GSS-SPNEGO support in jammy

Status in cyrus-sasl2 package in Ubuntu:
  New

Bug description:
  In jammy:
  root@j1:~# saslpluginviewer | head | grep SPNEGO
  root@j1:~# 

  Confirming against a windows 2016 active directory server, fully patched:
  root@j1:~# ldapwhoami -Y GSS-SPNEGO
  ldap_sasl_interactive_bind: Unknown authentication method (-6)
  additional info: SASL(-4): no mechanism available: No worthy mechs 
found

  
  gssapi (kerberos) works:
  root@j1:~# ldapwhoami -Y GSSAPI
  SASL/GSSAPI authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

  root@j1:~# klist
  Ticket cache: FILE:/tmp/krb5cc_0
  Default principal: administra...@internal.example.fake

  Valid starting ExpiresService principal
  01/08/22 22:31:48  01/09/22 08:31:48  
krbtgt/internal.example.f...@internal.example.fake
  renew until 01/09/22 22:31:45
  01/08/22 22:34:53  01/09/22 08:31:48  
ldap/win-kriet1e5elo.internal.example.fake@
  renew until 01/09/22 22:31:45
  Ticket server: 
ldap/win-kriet1e5elo.internal.example.f...@internal.example.fake

  
  In focal, GSS-SPNEGO works:
  root@f1:~# saslpluginviewer | head | grep SPNEGO
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
EXTERNAL NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS

  Confirming with ldapwhoami:
  root@f1:~# ldapwhoami -Y GSS-SPNEGO
  SASL/GSS-SPNEGO authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1956833/+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 1956835] [NEW] package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

2022-01-08 Thread Alistair
Public bug reported:

After updating the system, rebooted and this error appeared.
Fixed a problem related to /boot/grub/grubenv - "Error in environment" and 
grub-common.service
by providing absolute path to grub-editenv.  /boot/grub/grubenv was full of 
0x0, rather than 0x2323 as it has now.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.24
ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-44-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alistair   3520 F pulseaudio
CasperMD5CheckResult: skip
Date: Sat Jan  8 17:37:06 2022
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-11-12 (422 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Hewlett-Packard HP EliteBook 8470p
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x1by5v@/vmlinuz-5.11.0-44-generic 
root=ZFS=rpool/ROOT/ubuntu_x1by5v ro quiet splash vt.handoff=1
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: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.24 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: 04/12/2018
dmi.bios.release: 15.113
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68ICF Ver. F.71
dmi.board.name: 179B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 42.38
dmi.chassis.asset.tag: CNU3109W10
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.ec.firmware.release: 66.56
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68ICFVer.F.71:bd04/12/2018:br15.113:efr66.56:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:skuC3Q91UC#ABU:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook 8470p
dmi.product.sku: C3Q91UC#ABU
dmi.product.version: A1029D1102
dmi.sys.vendor: Hewlett-Packard

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

Title:
  package linux-firmware 1.187.24 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:
  After updating the system, rebooted and this error appeared.
  Fixed a problem related to /boot/grub/grubenv - "Error in environment" and 
grub-common.service
  by providing absolute path to grub-editenv.  /boot/grub/grubenv was full of 
0x0, rather than 0x2323 as it has now.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.24
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alistair   3520 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 17:37:06 2022
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-11-12 (422 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Hewlett-Packard HP EliteBook 8470p
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x1by5v@/vmlinuz-5.11.0-44-generic 
root=ZFS=rpool/ROOT/ubuntu_x1by5v ro quiet splash vt.handoff=1
  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: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.187.24 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error 

[Touch-packages] [Bug 1956833] Re: No GSS-SPNEGO support in jammy

2022-01-08 Thread Andreas Hasenack
Impish also works:

root@i1:~# saslpluginviewer | head | grep SPNEGO
  SCRAM-SHA-1 SCRAM-SHA-256 GS2-IAKERB GS2-KRB5 GSSAPI GSS-SPNEGO DIGEST-MD5 
EXTERNAL CRAM-MD5 NTLM PLAIN LOGIN ANONYMOUS
  SCRAM-SHA-1 SCRAM-SHA-256 GS2-IAKERB GS2-KRB5 GSSAPI GSS-SPNEGO DIGEST-MD5 
CRAM-MD5 NTLM PLAIN LOGIN ANONYMOUS


root@i1:~# ldapwhoami -Y GSS-SPNEGO
SASL/GSS-SPNEGO authentication started
SASL username: administra...@internal.example.fake
SASL SSF: 256
SASL data security layer installed.
u:INTEXAMPLE\Administrator

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

Title:
  No GSS-SPNEGO support in jammy

Status in cyrus-sasl2 package in Ubuntu:
  New

Bug description:
  In jammy:
  root@j1:~# saslpluginviewer | head | grep SPNEGO
  root@j1:~# 

  Confirming against a windows 2016 active directory server, fully patched:
  root@j1:~# ldapwhoami -Y GSS-SPNEGO
  ldap_sasl_interactive_bind: Unknown authentication method (-6)
  additional info: SASL(-4): no mechanism available: No worthy mechs 
found

  
  gssapi (kerberos) works:
  root@j1:~# ldapwhoami -Y GSSAPI
  SASL/GSSAPI authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

  root@j1:~# klist
  Ticket cache: FILE:/tmp/krb5cc_0
  Default principal: administra...@internal.example.fake

  Valid starting ExpiresService principal
  01/08/22 22:31:48  01/09/22 08:31:48  
krbtgt/internal.example.f...@internal.example.fake
  renew until 01/09/22 22:31:45
  01/08/22 22:34:53  01/09/22 08:31:48  
ldap/win-kriet1e5elo.internal.example.fake@
  renew until 01/09/22 22:31:45
  Ticket server: 
ldap/win-kriet1e5elo.internal.example.f...@internal.example.fake

  
  In focal, GSS-SPNEGO works:
  root@f1:~# saslpluginviewer | head | grep SPNEGO
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
EXTERNAL NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS

  Confirming with ldapwhoami:
  root@f1:~# ldapwhoami -Y GSS-SPNEGO
  SASL/GSS-SPNEGO authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1956833/+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 1956833] [NEW] No GSS-SPNEGO support in jammy

2022-01-08 Thread Andreas Hasenack
Public bug reported:

In jammy:
root@j1:~# saslpluginviewer | head | grep SPNEGO
root@j1:~# 

Confirming against a windows 2016 active directory server, fully patched:
root@j1:~# ldapwhoami -Y GSS-SPNEGO
ldap_sasl_interactive_bind: Unknown authentication method (-6)
additional info: SASL(-4): no mechanism available: No worthy mechs found


gssapi (kerberos) works:
root@j1:~# ldapwhoami -Y GSSAPI
SASL/GSSAPI authentication started
SASL username: administra...@internal.example.fake
SASL SSF: 256
SASL data security layer installed.
u:INTEXAMPLE\Administrator

root@j1:~# klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: administra...@internal.example.fake

Valid starting ExpiresService principal
01/08/22 22:31:48  01/09/22 08:31:48  
krbtgt/internal.example.f...@internal.example.fake
renew until 01/09/22 22:31:45
01/08/22 22:34:53  01/09/22 08:31:48  
ldap/win-kriet1e5elo.internal.example.fake@
renew until 01/09/22 22:31:45
Ticket server: 
ldap/win-kriet1e5elo.internal.example.f...@internal.example.fake


In focal, GSS-SPNEGO works:
root@f1:~# saslpluginviewer | head | grep SPNEGO
  GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
EXTERNAL NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS
  GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS

Confirming with ldapwhoami:
root@f1:~# ldapwhoami -Y GSS-SPNEGO
SASL/GSS-SPNEGO authentication started
SASL username: administra...@internal.example.fake
SASL SSF: 256
SASL data security layer installed.
u:INTEXAMPLE\Administrator

** Affects: cyrus-sasl2 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  No GSS-SPNEGO support in jammy

Status in cyrus-sasl2 package in Ubuntu:
  New

Bug description:
  In jammy:
  root@j1:~# saslpluginviewer | head | grep SPNEGO
  root@j1:~# 

  Confirming against a windows 2016 active directory server, fully patched:
  root@j1:~# ldapwhoami -Y GSS-SPNEGO
  ldap_sasl_interactive_bind: Unknown authentication method (-6)
  additional info: SASL(-4): no mechanism available: No worthy mechs 
found

  
  gssapi (kerberos) works:
  root@j1:~# ldapwhoami -Y GSSAPI
  SASL/GSSAPI authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

  root@j1:~# klist
  Ticket cache: FILE:/tmp/krb5cc_0
  Default principal: administra...@internal.example.fake

  Valid starting ExpiresService principal
  01/08/22 22:31:48  01/09/22 08:31:48  
krbtgt/internal.example.f...@internal.example.fake
  renew until 01/09/22 22:31:45
  01/08/22 22:34:53  01/09/22 08:31:48  
ldap/win-kriet1e5elo.internal.example.fake@
  renew until 01/09/22 22:31:45
  Ticket server: 
ldap/win-kriet1e5elo.internal.example.f...@internal.example.fake

  
  In focal, GSS-SPNEGO works:
  root@f1:~# saslpluginviewer | head | grep SPNEGO
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
EXTERNAL NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS
GS2-IAKERB GS2-KRB5 SCRAM-SHA-1 SCRAM-SHA-256 GSSAPI GSS-SPNEGO DIGEST-MD5 
NTLM CRAM-MD5 PLAIN LOGIN ANONYMOUS

  Confirming with ldapwhoami:
  root@f1:~# ldapwhoami -Y GSS-SPNEGO
  SASL/GSS-SPNEGO authentication started
  SASL username: administra...@internal.example.fake
  SASL SSF: 256
  SASL data security layer installed.
  u:INTEXAMPLE\Administrator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1956833/+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 1956831] [NEW] package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

2022-01-08 Thread Anders
Public bug reported:

Happened during do-release-upgrade.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.6
ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
Uname: Linux 4.15.0-166-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jan  8 18:54:36 2022
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2015-10-04 (2288 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2022-01-08 (0 days ago)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Happened during do-release-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 18:54:36 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-10-04 (2288 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2022-01-08 (0 days ago)

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

2022-01-08 Thread Bogus
Hi,
Here I found a better version of this script. It implements DHCPv6 and handles 
directory and file creation better f.ex when IF goes down.

https://roll.urown.net/desktop/network/time-sync.html

Unfortunately the variable $DHCP6_NTP_SERVERS is always empty in my
case. Even I have correct NTP and SNTP server addresses in my DHCPv6
options. I checked them with Wireshark.

-- 
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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

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

** Changed in: network-manager (Ubuntu Focal)
   Status: New => Confirmed

-- 
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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

-- 
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 1956823] Re: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

2022-01-08 Thread Paul White
*** This bug is a duplicate of bug 1956822 ***
https://bugs.launchpad.net/bugs/1956822

** This bug has been marked a duplicate of bug 1956822
   package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration

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

Title:
  package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Update issue

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 15:55:28 2022
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2021-05-29 (223 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: glib2.0
  Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1956823/+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 1956822] Re: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c

2022-01-08 Thread Paul White
Probably a bad download of the package.

Try the following in a terminal:

  sudo apt clean
  sudo apt update
  sudo apt upgrade

That should fix the update issue.


** Changed in: glib2.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in glib2.0 package in Ubuntu:
  Incomplete

Bug description:
  Update issue

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 15:55:28 2022
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2021-05-29 (223 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: glib2.0
  Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1956822/+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 1956822] [NEW] package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

2022-01-08 Thread Gulzar Khan
Public bug reported:

Update issue

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4
ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jan  8 15:55:28 2022
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2021-05-29 (223 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: i386
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: glib2.0
Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package focal i386 need-duplicate-check

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

Title:
  package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Update issue

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 15:55:28 2022
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2021-05-29 (223 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: glib2.0
  Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1956822/+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 1956823] [NEW] package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

2022-01-08 Thread Gulzar Khan
Public bug reported:

Update issue

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4
ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jan  8 15:55:28 2022
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2021-05-29 (223 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: i386
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: glib2.0
Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package focal i386 need-duplicate-check

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

Title:
  package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Update issue

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4
  ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 15:55:28 2022
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2021-05-29 (223 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: glib2.0
  Title: package libglib2.0-0:i386 2.64.6-1~ubuntu20.04.4 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1956823/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable

2022-01-08 Thread Mathew Hodson
** Changed in: exiv2 (Ubuntu)
   Importance: Undecided => High

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

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Fix Released
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

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