[Touch-packages] [Bug 2059862] Re: Getting dependency error when trying to install vim on noble chroot

[Ro$k0]

Same behaviour happens when using image from Docker Hub
https://hub.docker.com/layers/library/ubuntu/24.04/images/sha256-69ce9399fe60c5710baee8416b7991183653c3d577afc2b0e3bfe508d7c76142?context=explore

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

Title:
  Getting dependency error when trying to install vim on noble chroot

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  I'm getting dependency conflict when trying to install vim in Ubuntu
  noble chroot. The dependency version it wants is older then what is
  available in repositories. Running apt-get install vim fails with
  error as shown below:

  (chroot) $ sudo apt-get install vim
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   vim : Depends: vim-common (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 is 
to be installed
     Depends: vim-runtime (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  Apt-cache policy shows older version of vim available while in
  launchpad the newer version is shown, also the amd64 package version
  2:9.1.0016-1ubuntu6 is missing from repositories, no amd64 deb within
  repository pool directory of repository files

  (chroot) $ apt-cache policy vim
  vim:
    Installed: (none)
    Candidate: 2:9.1.0016-1ubuntu3
    Version table:
   2:9.1.0016-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages

  If vim was installed before, it would be uninstalled by upgrading vim-
  common and vim-runtime

  My sources list file:

  (chroot) $ cat /etc/apt/sources.list
  deb http://archive.ubuntu.com/ubuntu noble main restricted universe multiverse
  deb http://archive.ubuntu.com/ubuntu noble-security main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-updates main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-backports main restricted universe 
multiverse

  Contents of /etc/lsb-release

  (chroot) $ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=24.04
  DISTRIB_CODENAME=noble
  DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)"

  Host is Ubuntu 22.04 LTS, using schroot 1.6.10 to access Ubuntu Noble
  chroot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2059862/+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 2021956] Re: crash cups-proxyd

[Ro]

Upon further investigation, I noticed that the cups snap was installed
alongside the apt package from the Ubuntu repositories, which is
installed by default on ubuntu-desktop and ubuntu-desktop-minimal:

# dpkg -l | grep cups
ii  bluez-cups 5.64-0ubuntu1
   amd64Bluetooth printer driver for CUPS
ii  cups   2.4.1op1-1ubuntu4.4  
   amd64Common UNIX Printing System(tm) - PPD/driver support, web 
interface
ii  cups-browsed   1.28.15-0ubuntu1.2   
   amd64OpenPrinting CUPS Filters - cups-browsed
ii  cups-bsd   2.4.1op1-1ubuntu4.4  
   amd64Common UNIX Printing System(tm) - BSD commands
ii  cups-client2.4.1op1-1ubuntu4.4  
   amd64Common UNIX Printing System(tm) - client programs (SysV)
ii  cups-common2.4.1op1-1ubuntu4.4  
   all  Common UNIX Printing System(tm) - common files
ii  cups-core-drivers  2.4.1op1-1ubuntu4.4  
   amd64Common UNIX Printing System(tm) - driverless printing
ii  cups-daemon2.4.1op1-1ubuntu4.4  
   amd64Common UNIX Printing System(tm) - daemon
ii  cups-filters   1.28.15-0ubuntu1.2   
   amd64OpenPrinting CUPS Filters - Main Package
ii  cups-filters-core-drivers  1.28.15-0ubuntu1.2   
   amd64OpenPrinting CUPS Filters - Driverless printing
ii  cups-ipp-utils 2.4.1op1-1ubuntu4.4  
   amd64Common UNIX Printing System(tm) - IPP developer/admin 
utilities
ii  cups-pk-helper 0.2.6-1ubuntu5   
   amd64PolicyKit helper to configure cups with fine-grained 
privileges
ii  cups-ppdc  2.4.1op1-1ubuntu4.4  
   amd64Common UNIX Printing System(tm) - PPD manipulation utilities
ii  cups-server-common 2.4.1op1-1ubuntu4.4  
   all  Common UNIX Printing System(tm) - server common files
ii  libcups2:amd64 2.4.1op1-1ubuntu4.4  
   amd64Common UNIX Printing System(tm) - Core library
ii  libcupsfilters1:amd64  1.28.15-0ubuntu1.2   
   amd64OpenPrinting CUPS Filters - Shared library
ii  libcupsimage2:amd642.4.1op1-1ubuntu4.4  
   amd64Common UNIX Printing System(tm) - Raster image library
ii  printer-driver-hpcups  3.21.12+dfsg0-1  
   amd64HP Linux Printing and Imaging - CUPS Raster driver (hpcups)
ii  python3-cups:amd64 2.0.1-5build1
   amd64Python3 bindings for CUPS
ii  python3-cupshelpers1.5.16-0ubuntu3  
   all  Python utility modules around the CUPS printing system


# snap list
Name   Version Revision  Tracking   
Herausgeber  Hinweise
bare   1.0 5 latest/stable  
canonical✓   base
chromium   114.0.5735.198  2529  latest/stable  
canonical✓   -
core18 202305302785  latest/stable  
canonical✓   base
core20 202306221974  latest/stable  
canonical✓   base
core22 20230703817   latest/stable  
canonical✓   base
cups   2.4.6-4 980   latest/stable  
openprinting✓-
firefox115.0.2-1   2908  latest/stable  
mozilla✓ -
gnome-3-28-18043.28.0-19-g98f9e67.98f9e67  198   latest/stable  
canonical✓   -
gnome-3-38-20040+git.efb213a   143   latest/stable  
canonical✓   -
gnome-42-2204  0+git.ff35a85   120   latest/stable  
canonical✓   -
gtk-common-themes  0.1-81-g442e511 1535  latest/stable  
canonical✓   -
mqtt-explorer  0.3.5   29latest/stable  
thomasnordquist  -
snap-store 41.3-71-g709398e959   latest/stable  
canonical✓   -
snapd  2.59.5  19457 latest/stable  
canonical✓   snapd
snapd-desktop-integration  0.9 83latest/stable  
canonical✓   -


After removing the snap package the segfault did not occur again:

# snap remove cups

I have yet to 

[Touch-packages] [Bug 2021956] Re: crash cups-proxyd

[Ro]

I also experience this issue on a freshly installed Ubuntu 22.04 Desktop
with no printers atteched.

First I give an overview of my system and then I'll try to add the
missing information.


*** Kernel version: ***
# uname -a
Linux hostname 5.15.0-76-generic #83-Ubuntu SMP Thu Jun 15 19:16:32 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux


*** OS information: ***
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.2 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.2 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
UBUNTU_CODENAME=jammy


*** List of installed Snaps: ***
root@hostname:~# snap list
Name   Version Revision  Tracking   
Herausgeber  Hinweise
bare   1.0 5 latest/stable  
canonical✓   base
chromium   114.0.5735.198  2529  latest/stable  
canonical✓   -
core18 202305302785  latest/stable  
canonical✓   base
core20 202306221974  latest/stable  
canonical✓   base
core22 20230703817   latest/stable  
canonical✓   base
cups   2.4.6-4 980   latest/stable  
openprinting✓-
firefox115.0.2-1   2908  latest/stable  
mozilla✓ -
gnome-3-28-18043.28.0-19-g98f9e67.98f9e67  198   latest/stable  
canonical✓   -
gnome-3-38-20040+git.efb213a   143   latest/stable  
canonical✓   -
gnome-42-2204  0+git.ff35a85   120   latest/stable  
canonical✓   -
gtk-common-themes  0.1-81-g442e511 1535  latest/stable  
canonical✓   -
mqtt-explorer  0.3.5   29latest/stable  
thomasnordquist  -
snapd  2.59.5  19457 latest/stable  
canonical✓   snapd


*** Segfault in the syslog: ***
# less /var/log/syslog:
Jul 20 09:48:29 hostname kernel: [   86.133013] audit: type=1326 
audit(1689839309.216:87): auid=4294967295 uid=0 gid=0 ses=4294967295 
subj=snap.cups.cupsd pid=8278 comm="cupsd" exe="/snap/cups/980/sbin/cupsd" 
sig=0 arch=c03e syscall=93 compat=0 ip=0x7fd3108a8c4b code=0x5
Jul 20 09:48:30 hostname kernel: [   87.194090] audit: type=1326 
audit(1689839310.280:88): auid=4294967295 uid=0 gid=0 ses=4294967295 
subj=snap.cups.cupsd pid=8280 comm="cups-proxyd" 
exe="/snap/cups/980/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 
ip=0x7f652264ca3d code=0x5
Jul 20 09:48:30 hostname kernel: [   87.861485] cups-proxyd[8280]: segfault at 
18 ip 56043483ad75 sp 7f58ad80 error 4 in 
cups-proxyd[560434837000+7000]
Jul 20 09:48:30 hostname kernel: [   87.861534] Code: 83 3d ee b2 00 00 00 41 
54 55 48 89 fd 53 0f 85 f4 00 00 00 48 8d 1d 69 3d 00 00 48 63 45 1c 48 89 df 
48 c1 e0 05 48 03 45 08 <48> 8b 50 18 8b 70 14 e8 0f d0 ff ff 44 8b 65 18 48 89 
c7 45 85 e4


*** cups-proxyd_log from the time of the system startup: ***
# cat /var/snap/cups/current/var/log/cups-proxyd_log
Thu Jul 20 09:48:29 2023 main() in THREAD 140072331107008
Thu Jul 20 09:48:29 2023 System CUPS: /run/cups/cups.sock
Thu Jul 20 09:48:29 2023 Proxy CUPS: /var/snap/cups/common/run/cups.sock
Thu Jul 20 09:48:29 2023 cups-proxyd version 1.0 starting.
Thu Jul 20 09:48:29 2023 Check whether both CUPS daemons are running.
Thu Jul 20 09:48:29 2023 cups-proxyd: Creating http connection to CUPS daemon 
via domain socket: /var/snap/cups/common/run/cups.sock
Thu Jul 20 09:48:29 2023 cups-proxyd: Failed creating http connection to CUPS 
daemon via domain socket: /var/snap/cups/common/run/cups.sock
Thu Jul 20 09:48:30 2023 cups-proxyd: Creating http connection to CUPS daemon 
via domain socket: /var/snap/cups/common/run/cups.sock
Thu Jul 20 09:48:30 2023 cups-proxyd: Creating http connection to CUPS daemon 
via domain socket: /run/cups/cups.sock
Thu Jul 20 09:48:30 2023 cups-proxyd: Closing connection to proxy CUPS daemon.
Thu Jul 20 09:48:30 2023 cups-proxyd: Closing connection to system's CUPS 
daemon.
Thu Jul 20 09:48:30 2023 cups-proxyd (/var/snap/cups/common/run/cups.sock): 
cupsEnumDests
Thu Jul 20 09:48:30 2023 Using signal handler SIGNAL
Thu Jul 20 09:48:30 2023 [Avahi Browser] Avahi server connection got available, 
setting up service browsers.
Thu Jul 20 09:48:30 2023 Creating subscription to D-Bus notifications on the 
system's CUPS daemon.
Thu Jul 20 09:48:30 2023 cups-proxyd: Creating http connection to CUPS daemon 
via domain socket: /run/cups/cups.sock
Thu Jul 20 09:48:30 2023 cups-proxyd: Closing connection to system's CUPS 
daemon.
Thu Jul 20 09:48:30 2023 Updating queues on proxy CUPS in 500 msecs
Thu Jul 20 09:48:30 2023 browse_callback() in THREAD 

[Touch-packages] [Bug 1301015] Re: Networking does not restart

[Ro]

#74: Good point!

Stéphane Graber (stgraber) is not subscribed to this bug anymore and
this bug is unassigned. I fear that #64 point a) has happened for real.
Hmm...

At the same time an officially supported way to restart the interfaces
reliably, even over SSH, is missing. My only hope is that this will be
implicitly resolved in 16.04 when migrating to systemd.

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

Title:
  Networking does not restart

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu Server 14.04 it appears it is not possible to restart
  networking. This is fresh install from ISO.

  wirehive@ubuntu:~$ sudo /etc/init.d/networking restart
  wirehive@ubuntu:~$ echo $?
  1
  wirehive@ubuntu:~$ sudo service networking restart
  stop: Job failed while stopping
  start: Job is already running: networking
  wirehive@ubuntu:~$ sudo bash -x /etc/init.d/networking restart
  + PATH=/sbin:/bin
  + RUN_DIR=/run/network
  + IFSTATE=/run/network/ifstate
  + STATEDIR=/run/network/state
  + '[' -x /sbin/ifup ']'
  + '[' -x /sbin/ifdown ']'
  + . /lib/lsb/init-functions
  +++ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/20-left-info-blocks ']'
  ++ . /lib/lsb/init-functions.d/20-left-info-blocks
  ++ for hook in '$(run-parts --lsbsysinit --list /lib/lsb/init-functions.d 
2>/dev/null)'
  ++ '[' -r /lib/lsb/init-functions.d/50-ubuntu-logging ']'
  ++ . /lib/lsb/init-functions.d/50-ubuntu-logging
  +++ LOG_DAEMON_MSG=
  ++ FANCYTTY=
  ++ '[' -e /etc/lsb-base-logging.sh ']'
  ++ true
  + CONFIGURE_INTERFACES=yes
  + EXCLUDE_INTERFACES=
  + VERBOSE=no
  + '[' -f /etc/default/networking ']'
  + verbose=
  + '[' no = yes ']'
  + case "$1" in
  + init_is_upstart
  + '[' -x /sbin/initctl ']'
  + /bin/grep -q upstart
  + /sbin/initctl version
  + return 0
  + exit 1
  wirehive@ubuntu:~$ sudo bash -x service networking restart
  ++ basename service
  + VERSION='service ver. 0.91-ubuntu1'
  ++ basename service
  + USAGE='Usage: service < option > | --status-all | [ service_name [ command 
| --full-restart ] ]'
  + SERVICE=
  + ACTION=
  + SERVICEDIR=/etc/init.d
  + OPTIONS=
  + '[' 2 -eq 0 ']'
  + cd /
  + '[' 2 -gt 0 ']'
  + case "${1}" in
  + '[' -z '' -a 2 -eq 1 -a networking = --status-all ']'
  + '[' 2 -eq 2 -a restart = --full-restart ']'
  + '[' -z '' ']'
  + SERVICE=networking
  + shift
  + '[' 1 -gt 0 ']'
  + case "${1}" in
  + '[' -z networking -a 1 -eq 1 -a restart = --status-all ']'
  + '[' 1 -eq 2 -a '' = --full-restart ']'
  + '[' -z networking ']'
  + '[' -z '' ']'
  + ACTION=restart
  + shift
  + '[' 0 -gt 0 ']'
  + '[' -r /etc/init/networking.conf ']'
  + which initctl
  + grep -q upstart
  + initctl version
  + case "${ACTION}" in
  + stop networking
  stop: Job failed while stopping
  + :
  + exec start networking
  start: Job is already running: networking
  wirehive@ubuntu:~$

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1301015/+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 1186662] Re: isc-dhcp-server fails to renew lease file

[Ro]

Following up on comment #14, this bug (ISC-Bugs #36978) seems to have
been fixed in ISC DHCP upstream version 4.3.2 [1]:

"   - Enhance the PARANOIA patch to include fchown() the lease file to
  allow it to be manipulated after the server does a chown().
  Thanks to Jiri Popelka at Red Hat for the patch.
  [ISC-Bugs #36978]
"

[1] https://fossies.org/diffs/dhcp/4.3.2_vs_4.3.3/RELNOTES-diff.html

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

Title:
  isc-dhcp-server fails to renew lease file

Status in isc-dhcp package in Ubuntu:
  Triaged
Status in isc-dhcp source package in Trusty:
  Confirmed

Bug description:
  After raring upgrade, the dhcp server fails to renew lease file when
  it tries to (about every hour).

  The syslog says:
  dhcpd: Can't create new lease file: Permission denied

  It looks like a permission problem, because

  # chown -R dhcpd:dhcpd /var/lib/dhcp

  the above command temporarily solves the issue, until dhcpd is
  restarted: at that time, the ownership of the directory and the lease
  file is set back to root:root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1352504] Re: Regression in 2.11.1-0ubuntu7.14; segfault in getservbyname

[Ro]

@Marc: Yes, running nscd with ldap.

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

Title:
  Regression in 2.11.1-0ubuntu7.14; segfault in getservbyname

Status in “eglibc” package in Ubuntu:
  Invalid
Status in “eglibc” source package in Lucid:
  Confirmed
Status in “eglibc” source package in Precise:
  Invalid
Status in “eglibc” source package in Trusty:
  Invalid
Status in “eglibc” source package in Utopic:
  Invalid

Bug description:
  After taking security updates to 2.11.1-0ubuntu7.14 on Lucid, calls to
  getservbyname() are causing segfaults; backtrace attached.  I suspect
  a failure in debian/patches/any/CVE-2013-4357.diff

  nscd is installed and in use as a caching layer for openldap, which
  use used for passwd, group, and shadow but not services.

  Needless to say, a security update that causes a regression which
  makes 'apt-get' segfault is quite unfortunate.

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