[Touch-packages] [Bug 1565982] Re: MakeModel gets erased from printers.conf from time to time
Hi there! I could not reproduce this issue on a fresh bionic install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1565982 Title: MakeModel gets erased from printers.conf from time to time Status in cups package in Ubuntu: Incomplete Bug description: Using printers.conf from an ansible module for fact collection, I noticed that a printer's MakeModel randomly disappears from printers.conf. The bug has already been fixed upstream and it's easy to backport: https://www.cups.org/pipermail/cups/2014-December/026601.html Attached is the same patch from the link, applied to the current sources in trusty (1.7.2-0ubuntu1.7). $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy cups cups: Installed: 1.7.2-0ubuntu1.7 Candidate: 1.7.2-0ubuntu1.7 Version table: *** 1.7.2-0ubuntu1.7 0 500 http://ar.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1.7.2-0ubuntu1 0 500 http://ar.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.7 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Mon Apr 4 16:52:50 2016 Lpstat: device for q_other: socket://q_other device for q_other2: socket://q_other2 device for q_other3: socket://q_other3 Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Papersize: a4 PpdFiles: q_other2: Generic PCL 3 Printer Foomatic/pcl3 (recommended) q_other: Generic PCL 3 Printer Foomatic/pcl3 (recommended) q_other3: Generic PCL 3 Printer Foomatic/pcl3 (recommended) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/xvda2 ro elevator=noop root=/dev/xvda1 ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1565982/+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 1301015] Re: Networking does not restart
Seriously people, get over yourself. Here's what the init script did on
restart:
ifdown -a --exclude=lo $verbose
ifup -a --exclude=lo $exclusions $verbose && ifup_hotplug $exclusions $verbose
All the rest is message output, checking for /etc/network/options and
other boilerplate stuff. That's exactly the same suggestion feliperechia
made in #8 about 2 years ago.
"Oh, but he didn't mention ifup_hotplug or $exclusions yadda yadda"
Well, ifup_hotplug actually extracts a list of interfaces from the
output of `ifquery --list --allow=hotplug`, checks they're physical
interfaces and have physical link, and runs ifup for all of them.
I sincerely doubt any of the "oh I screwed up and now have to take a 4
hour flight to the datacenter" are hotplugging their network interfaces.
If your NIC is available on boot it should be set to 'auto' and will be
picked up by `ifup -a`. No need for ifup_hotplug on headless servers.
$exclusions is the EXCLUDE_INTERFACES parameter from /etc/default/networking.
$verbose is either '-v' or empty. You probably don't use either.
So yeah, `( ifdown -a --exclude=lo; ifup -a --exclude=lo) &` should work
for everyone because that's exactly what `/etc/init.d/networking
restart` did.
Can we move along now? Thanks!
--
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 1565982] [NEW] MakeModel gets erased from printers.conf from time to time
Public bug reported: Using printers.conf from an ansible module for fact collection, I noticed that a printer's MakeModel randomly disappears from printers.conf. The bug has already been fixed upstream and it's easy to backport: https://www.cups.org/pipermail/cups/2014-December/026601.html Attached is the same patch from the link, applied to the current sources in trusty (1.7.2-0ubuntu1.7). $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ apt-cache policy cups cups: Installed: 1.7.2-0ubuntu1.7 Candidate: 1.7.2-0ubuntu1.7 Version table: *** 1.7.2-0ubuntu1.7 0 500 http://ar.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1.7.2-0ubuntu1 0 500 http://ar.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.7 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Mon Apr 4 16:52:50 2016 Lpstat: device for q_other: socket://q_other device for q_other2: socket://q_other2 device for q_other3: socket://q_other3 Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Papersize: a4 PpdFiles: q_other2: Generic PCL 3 Printer Foomatic/pcl3 (recommended) q_other: Generic PCL 3 Printer Foomatic/pcl3 (recommended) q_other3: Generic PCL 3 Printer Foomatic/pcl3 (recommended) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/xvda2 ro elevator=noop root=/dev/xvda1 ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cups trusty ** Patch added: "Upstream patch backported to 1.7.2-0ubuntu1.7" https://bugs.launchpad.net/bugs/1565982/+attachment/4623492/+files/makemodel.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1565982 Title: MakeModel gets erased from printers.conf from time to time Status in cups package in Ubuntu: New Bug description: Using printers.conf from an ansible module for fact collection, I noticed that a printer's MakeModel randomly disappears from printers.conf. The bug has already been fixed upstream and it's easy to backport: https://www.cups.org/pipermail/cups/2014-December/026601.html Attached is the same patch from the link, applied to the current sources in trusty (1.7.2-0ubuntu1.7). $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy cups cups: Installed: 1.7.2-0ubuntu1.7 Candidate: 1.7.2-0ubuntu1.7 Version table: *** 1.7.2-0ubuntu1.7 0 500 http://ar.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1.7.2-0ubuntu1 0 500 http://ar.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.7 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Mon Apr 4 16:52:50 2016 Lpstat: device for q_other: socket://q_other device for q_other2: socket://q_other2 device for q_other3: socket://q_other3 Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 Papersize: a4 PpdFiles: q_other2: Generic PCL 3 Printer Foomatic/pcl3 (recommended) q_other: Generic PCL 3 Printer Foomatic/pcl3 (recommended) q_other3: Generic PCL 3 Printer Foomatic/pcl3 (recommended) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=es_AR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: root=/dev/xvda2 ro elevator=noop root=/dev/xvda1 ro SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1565982/+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 1299727] Re: init --user 100% one core, 2, 5 GB memory taken
I'm on Lubuntu 14.04 64 bit and it happens consistently when logging out from lxde session. I have a multi-user LTSP setup, and it doesn't happen when a thin client user logs out, only when the local (tty7) user logs out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1299727 Title: init --user 100% one core, 2,5 GB memory taken Status in upstart package in Ubuntu: Confirmed Bug description: As in summary. I didn't track the exact steps to reproduce, it seems to happen when idle. Also Nicotine and Apport have similar issues, so maybe python is to blame? Started to happen only recently, so probably one of the latest updates introduced this regression. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: upstart 1.10-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 Date: Sun Mar 30 11:00:50 2014 InstallationDate: Installed on 2012-05-12 (686 days ago) InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True SourcePackage: upstart UpgradeStatus: Upgraded to saucy on 2013-10-17 (163 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1299727/+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
