from:"Sergey Ivanov"

[Touch-packages] [Bug 1239756] Re: apport-bug linux hangs forever at "collecting problem information"

2022-12-14 Thread Sergey Ivanov

same issue as in https://bugs.launchpad.net/launchpad/+bug/1996471

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

Title:
  apport-bug linux hangs forever at "collecting problem information"

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  also apport-cli

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport 2.12.5-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportLog:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 14 12:13:38 2013
  InstallationDate: Installed on 2013-09-17 (26 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1239756/+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 1239756] Re: apport-bug linux hangs forever at "collecting problem information"

2022-12-14 Thread Sergey Ivanov

same for me. Bug report is

https://bugs.launchpad.net/ubuntu/+source/gdm3/+filebug/2954d34c-7bd9-11ed-8040-40a8f03099c8?

** Changed in: apport (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  apport-bug linux hangs forever at "collecting problem information"

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  also apport-cli

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport 2.12.5-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportLog:
   
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Mon Oct 14 12:13:38 2013
  InstallationDate: Installed on 2013-09-17 (26 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1239756/+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 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

2022-12-01 Thread Sergey Ivanov

still present in 22.10. Newest ubuntu still work against old version of
snap.

# probe for assertions, must run before udisks2
ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \
RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k"

in my rule file

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

Title:
  Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
  exit code 1." in Ubuntu 22.04

Status in snapd:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Configuration:
   OS:jammy-live-server20220320-amd64.iso
   CPU:AMD EPYC 7702 64-Core Processor
   UEFI Version:D8E119A
   BMC Version:D8BT19I
   SSD:Intel 1.60TB NVMe SSD
   Boot mode:legacy
  Reproduce Steps:
   1.Boot into BIOS and set boot mode to legacy
   2.install ubuntu 22.04 on NVMe SSD
   3.Check syslog log
  Current behaviors:
  syslog shows systemd-udevd errors in Ubuntu 22.04
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare 
-m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1.
  Feb  9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m 
/usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1966203/+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 1984067] Re: Xorg crash

2022-08-09 Thread Sergey Ivanov

** Attachment added: "xorg.1 file from crashed session"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1984067/+attachment/5607529/+files/Xorg.1.log.old

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  All logs should be added automatically but the central issue is:

  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace:
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0: 
/usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b7984596e9]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 1: 
/lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f3e6a242520]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 2: 
/usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x55b7982ee1e9]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 3: 
/usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x55b7982efc85]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 4: 
/usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x55b7982f0183]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 5: 
/usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x55b7982f1183]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 6: 
/usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x55b7983cfa7d]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 7: 
/usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x55b7983f9e4c]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 8: 
/usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x55b7983f2f21]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 9: 
/usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x55b7983f311e]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 10: 
/usr/lib/xorg/Xorg (TimerSet+0x170) [0x55b798452c60]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 11: 
/usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x55b798452ee8]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 12: 
/usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b7982e3257]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 13: 
/usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x55b7982e7524]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 14: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f3e6a229d90]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 15: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f3e6a229e40]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 16: 
/usr/lib/xorg/Xorg (_start+0x25) [0x55b7982d05f5]
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 
Segmentation fault at address 0x7ffc51d3
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Fatal server 
error:
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Caught 
signal 11 (Segmentation fault). Server aborting
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Please consult 
the The X.Org Foundation support
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: #011 at 
http://wiki.x.org
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]:  for help.
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Please also 
check the log file at "/var/log/Xorg.1.log" for additional information.
  Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
  Uname: Linux 5.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.73.05  Sat May  7 
05:30:26 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None

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

2022-08-09 Thread Sergey Ivanov

Public bug reported:

All logs should be added automatically but the central issue is:

Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace:
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0: 
/usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b7984596e9]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 1: 
/lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f3e6a242520]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 2: 
/usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x55b7982ee1e9]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 3: 
/usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x55b7982efc85]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 4: 
/usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x55b7982f0183]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 5: 
/usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x55b7982f1183]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 6: 
/usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x55b7983cfa7d]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 7: 
/usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x55b7983f9e4c]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 8: 
/usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x55b7983f2f21]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 9: 
/usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x55b7983f311e]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 10: 
/usr/lib/xorg/Xorg (TimerSet+0x170) [0x55b798452c60]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 11: 
/usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x55b798452ee8]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 12: 
/usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b7982e3257]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 13: 
/usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x55b7982e7524]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 14: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f3e6a229d90]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 15: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f3e6a229e40]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 16: 
/usr/lib/xorg/Xorg (_start+0x25) [0x55b7982d05f5]
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Segmentation 
fault at address 0x7ffc51d3
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Fatal server error:
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Caught signal 
11 (Segmentation fault). Server aborting
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Please consult the 
The X.Org Foundation support
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: #011 at 
http://wiki.x.org
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]:  for help.
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Please also 
check the log file at "/var/log/Xorg.1.log" for additional information.
Aug  9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.73.05  Sat May  7 05:30:26 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug  9 15:22:16 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 acpi-call/1.2.2, 5.15.0-41-generic, x86_64: installed
 acpi-call/1.2.2, 5.15.0-43-generic, x86_64: installed
 fwts-efi-runtime-dkms/22.03.00, 5.15.0-41-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
 fwts-efi-runtime-dkms/22.03.00, 5.15.0-43-generic, x86_64: installed (WARNING! 
Diff between built and installed module!)
DpkgLog:

[Touch-packages] [Bug 1908818] [NEW] pure packaging of libnss3

2020-12-20 Thread Sergey Ivanov

Public bug reported:

dpkg -L libnss3
/.
/usr
/usr/lib
/usr/lib/${DEB_HOST_MULTIARCH}
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libnss3.so
/usr/lib/x86_64-linux-gnu/libnssutil3.so
/usr/lib/x86_64-linux-gnu/libsmime3.so
/usr/lib/x86_64-linux-gnu/libssl3.so
/usr/lib/x86_64-linux-gnu/nss
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
/usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
/usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
/usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
/usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
/usr/share
/usr/share/doc
/usr/share/doc/libnss3
/usr/share/doc/libnss3/changelog.Debian.gz
/usr/share/doc/libnss3/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/libnss3
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk


as we can see soft links to libraries do nor resolve ${DEB_HOST_MULTIARCH} to 
x86_64-linux-gnu

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: libnss3 2:3.55-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Dec 20 14:36:10 2020
SourcePackage: nss
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  pure packaging of libnss3

Status in nss package in Ubuntu:
  New

Bug description:
  dpkg -L libnss3
  /.
  /usr
  /usr/lib
  /usr/lib/${DEB_HOST_MULTIARCH}
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libnss3.so
  /usr/lib/x86_64-linux-gnu/libnssutil3.so
  /usr/lib/x86_64-linux-gnu/libsmime3.so
  /usr/lib/x86_64-linux-gnu/libssl3.so
  /usr/lib/x86_64-linux-gnu/nss
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
  /usr/share
  /usr/share/doc
  /usr/share/doc/libnss3
  /usr/share/doc/libnss3/changelog.Debian.gz
  /usr/share/doc/libnss3/copyright
  /usr/share/lintian
  /usr/share/lintian/overrides
  /usr/share/lintian/overrides/libnss3
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk

  
  as we can see soft links to libraries do nor resolve ${DEB_HOST_MULTIARCH} to 
x86_64-linux-gnu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libnss3 2:3.55-1ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Dec 20 14:36:10 2020
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1908818/+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 1908814] [NEW] systemd : inconsistencies in man pages

2020-12-20 Thread Sergey Ivanov

Public bug reported:

>From "man systemd-system.conf":

When packages need to customize the configuration, they can install
configuration snippets in /usr/lib/systemd/*.conf.d/ or
/usr/local/lib/systemd/*.conf.d/. The main configuration file is read
before any of the configuration directories, and has the lowest
precedence; entries in a file in any configuration directory override
entries in the single configuration file. Files in the *.conf.d/
configuration subdirectories are sorted by their filename in
lexicographic order, regardless of in which of the subdirectories they
reside. When multiple files specify the same option, for options which
accept just a single value, the entry in the file with the
lexicographically latest name takes precedence. For options which accept
a list of values, entries are collected as they occur in files sorted
lexicographically.


However from "man SYSTEMD":

DIRECTORIES
   System unit directories
   The systemd system manager reads unit configuration from various 
directories. Packages that want to install unit files shall place them in the 
directory returned by pkg-config systemd
   --variable=systemdsystemunitdir. Other directories checked are 
/usr/local/lib/systemd/system and /lib/systemd/system. User configuration 
always takes precedence.  pkg-config systemd
   --variable=systemdsystemconfdir returns the path of the system 
configuration directory. Packages should alter the content of these directories 
only with the enable and disable commands of
   the systemctl(1) tool. Full list of directories is provided in 
systemd.unit(5).

   User unit directories
   Similar rules apply for the user unit directories. However, here the 
XDG Base Directory specification[6] is followed to find units. Applications 
should place their unit files in the
   directory returned by pkg-config systemd 
--variable=systemduserunitdir. Global configuration is done in the directory 
reported by pkg-config systemd --variable=systemduserconfdir. The
   enable and disable commands of the systemctl(1) tool can handle both 
global (i.e. for all users) and private (for one user) enabling/disabling of 
units. Full list of directories is provided
   in systemd.unit(5).


Obviously, the 2nd one is more precise about directories for
configuration files and therefore should be used in all cases. 1st
paragraph of doc should link there

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: 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/1908814

Title:
  systemd : inconsistencies in man pages

Status in openssh package in Ubuntu:
  New

Bug description:
  From "man systemd-system.conf":

  When packages need to customize the configuration, they can install
  configuration snippets in /usr/lib/systemd/*.conf.d/ or
  /usr/local/lib/systemd/*.conf.d/. The main configuration file is read
  before any of the configuration directories, and has the lowest
  precedence; entries in a file in any configuration directory override
  entries in the single configuration file. Files in the *.conf.d/
  configuration subdirectories are sorted by their filename in
  lexicographic order, regardless of in which of the subdirectories they
  reside. When multiple files specify the same option, for options which
  accept just a single value, the entry in the file with the
  lexicographically latest name takes precedence. For options which
  accept a list of values, entries are collected as they occur in files
  sorted lexicographically.

  
  However from "man SYSTEMD":

  DIRECTORIES
 System unit directories
 The systemd system manager reads unit configuration from various 
directories. Packages that want to install unit files shall place them in the 
directory returned by pkg-config systemd
 --variable=systemdsystemunitdir. Other directories checked are 
/usr/local/lib/systemd/system and /lib/systemd/system. User configuration 
always takes precedence.  pkg-config systemd
 --variable=systemdsystemconfdir returns the path of the system 
configuration directory. Packages should alter the content of these directories 
only with the enable and disable commands of
 the systemctl(1) tool. Full list of directories is provided in 
systemd.unit(5).

 User unit directories
 Similar rules apply for the user unit directories. However, here 
the XDG Base Directory specification[6] is followed to find units. Applications 
should place their unit files in the
 directory returned by pkg-config systemd 
--variable=systemduserunitdir. Global configuration is done in the directory 
reported by pkg-config systemd --variable=systemduserconfdir. The
 enable and disable commands of the systemctl(1) tool can handle 
both global (i.e.

[Touch-packages] [Bug 1753946] Re: verbosity for logrotate

2018-03-07 Thread Sergey Ivanov

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

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

Title:
  verbosity for logrotate

Status in logrotate package in Ubuntu:
  Invalid

Bug description:
  User has modified /etc/logrotate.conf file such that it includes another file 
/path/to/own/other_logrotate.conf:
  ...
  include /path/to/own/other_logrotate.conf
  ...

  Now run under root:

  logrotate -v /etc/logrotate.conf

  Expected result:
  verbosity related to other logrotate file should be very same as if we run 
other logrotate directly
  i.e:
  logrotate -v /etc/logrotate.conf should have same output related to 
/path/to/own/other_logrotate.conf
  as if we run directly
  logrotate -v /path/to/own/other_logrotate.conf

  Actual result:
  logrotate -v /etc/logrotate.conf has empty output regarding to 
/path/to/own/other_logrotate.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: logrotate 3.8.7-2ubuntu2.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 10:33:11 2018
  InstallationDate: Installed on 2018-01-23 (42 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: logrotate
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.conf: 2018-03-07T10:33:03.883000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1753946/+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 1753946] [NEW] verbosity for logrotate

2018-03-07 Thread Sergey Ivanov

Public bug reported:

User has modified /etc/logrotate.conf file such that it includes another file 
/path/to/own/other_logrotate.conf:
...
include /path/to/own/other_logrotate.conf
...

Now run under root:

logrotate -v /etc/logrotate.conf

Expected result:
verbosity related to other logrotate file should be very same as if we run 
other logrotate directly
i.e:
logrotate -v /etc/logrotate.conf should have same output related to 
/path/to/own/other_logrotate.conf
as if we run directly
logrotate -v /path/to/own/other_logrotate.conf

Actual result:
logrotate -v /etc/logrotate.conf has empty output regarding to 
/path/to/own/other_logrotate.conf

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: logrotate 3.8.7-2ubuntu2.16.04.2
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Mar  7 10:33:11 2018
InstallationDate: Installed on 2018-01-23 (42 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.logrotate.conf: 2018-03-07T10:33:03.883000

** Affects: logrotate (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-bug xenial

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

Title:
  verbosity for logrotate

Status in logrotate package in Ubuntu:
  Invalid

Bug description:
  User has modified /etc/logrotate.conf file such that it includes another file 
/path/to/own/other_logrotate.conf:
  ...
  include /path/to/own/other_logrotate.conf
  ...

  Now run under root:

  logrotate -v /etc/logrotate.conf

  Expected result:
  verbosity related to other logrotate file should be very same as if we run 
other logrotate directly
  i.e:
  logrotate -v /etc/logrotate.conf should have same output related to 
/path/to/own/other_logrotate.conf
  as if we run directly
  logrotate -v /path/to/own/other_logrotate.conf

  Actual result:
  logrotate -v /etc/logrotate.conf has empty output regarding to 
/path/to/own/other_logrotate.conf

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: logrotate 3.8.7-2ubuntu2.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Mar  7 10:33:11 2018
  InstallationDate: Installed on 2018-01-23 (42 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: logrotate
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.logrotate.conf: 2018-03-07T10:33:03.883000

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1753946/+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 1239756] Re: apport-bug linux hangs forever at "collecting problem information"

[Touch-packages] [Bug 1239756] Re: apport-bug linux hangs forever at "collecting problem information"

[Touch-packages] [Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04

[Touch-packages] [Bug 1984067] Re: Xorg crash

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

[Touch-packages] [Bug 1908818] [NEW] pure packaging of libnss3

[Touch-packages] [Bug 1908814] [NEW] systemd : inconsistencies in man pages

[Touch-packages] [Bug 1753946] Re: verbosity for logrotate

[Touch-packages] [Bug 1753946] [NEW] verbosity for logrotate

9 matches

Site Navigation

Mail list logo

Footer information