[Touch-packages] [Bug 1020048] Re: after certain time printing to cups stops working

2016-08-18 Thread Marc Kolly
How is it possible I see the exact same issue with LO (1:5.1.4-0ubuntu1) and 
cups (2.1.3-4) on Ubuntu 16.04 with a central Debian cups server 
(1.7.5-11+deb8u1)?
I'm not using the /etc/cups/client.conf, but instead a normal full Ubuntu 16.04 
installation + all released updates.

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

Title:
  after certain time printing to cups stops working

Status in LibreOffice:
  Invalid
Status in cups package in Ubuntu:
  Fix Released
Status in libreoffice package in Ubuntu:
  Invalid
Status in cups source package in Precise:
  Fix Released
Status in libreoffice source package in Precise:
  Invalid

Bug description:
  SRU justification:

  [Impact]

  * When the CUPS client connects to a remote cupsd over TCP, the server 
closes an idle connection after 5 minutes and the client does not reconnect.

  * LibreOffice is affected because it keeps a CUPS connection open. The 
effect is that printing to a remote cupsd is no longer possible after 
LibreOffice has been open for 5 minutes.

  [Test Case]

  * This can be reproduced on a desktop system. You don't need a separate 
CUPS server.

  * You need at least one print queue in CUPS. If you don't have a 
printer, install "cups-pdf".

  * Optional, configure CUPS with a shorter timeout for testing:

sudo cupsctl Timeout=30 # seconds
sudo restart cups

  * Configure the CUPS client to use a TCP socket:

mkdir ~/.cups
echo ServerName 127.0.0.1 > ~/.cups/client.conf

  * Open LibreOffice. Press Ctrl-P to open the Print dialog. Press Esc to 
dismiss the dialog. Wait long enough for the timout to elapse (5 
minutes by default, or as per the Timeout setting).

  * Try to print. With cups in precise, the job simply vanishes and is 
never seen by the server. With the proposed patch, printing works 
normally.

  [Regression Potential]

  * The patch changes a library linked by many programs. An incorrect 
change might result in those programs misbehaving or crashing.

  * The patch is minimal, only adding a branch to handle a case that was 
previously not handled. The behaviour in other cases should be 
unchanged.

  [Other Info]

  * A workaround is to set the cupsd Timeout to a high value such as 8 
hours. This works on a server with few users, but on a busy server 
more and more connections are opened and eventually cupsd isn't able 
to accept new clients.

  Original description:

  == Problem ==
  In our institution we are running only printers through a cups server. while 
freshly opened document prints well, after some time (few minutes) clicking 
"print file directly" and menu item "print" do not work any more. after close 
and open again, thing prints correctly. i have checked what exactly is going on 
in such cases and logs on the cups server don't show any submissions and/or 
errors so that the thing is obviously stopped at the level of libreoffice.

  == Analysis ==
  LibreOffice loses it's TCP connection to CUPS after exactly 5 minutes of 
inactivity and does not manage to reconnect. To reproduce: print something (to 
a real printer or cups-pdf), wait 6 minutes not printing anything, and print 
again. Then, nothing is printed. You can watch the TCP connection using
  netstat -tpn | grep soffice
  While it's working, it looks like this:
  tcp0  0 127.0.0.1:48810 127.0.0.1:631   
ESTABLISHED 13976/soffice.bin
  After 5 minutes, that connection is gone permanently.

  WORKAROUND: To set the timeout to 24 hours add this line to the top of 
/etc/cups/cupsd.conf :
  Timeout 62400

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1020048/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"

2016-07-03 Thread Marc Kolly
@pitti: your fix still doesn't work all the time. It still happens once
in ~10 times.

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

Title:
  No wifi connection after suspend with systemd due to missing "wpa_cli
  suspend"

Status in One Hundred Papercuts:
  Fix Released
Status in NetworkManager:
  Unknown
Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Wily:
  Fix Committed
Status in wpa source package in Xenial:
  Fix Released

Bug description:
  Using systemd as my default init system if I resume from suspend my
  laptop, it doesn't automatically reconnect to the wireless network and
  it doesn't list the available network connections.

  The only way to get a wireless connection is to restart the network-
  manager daemon or going to the gnome-control-center, disable wireless
  and enable it again.

  SRU INFORMATION
  ===
  In some of these cases this bug can be worked around by calling "wpa_cli 
suspend/resume" before/after suspend, like we used to do with the old pm-utils 
quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects 
particular hardware, and thus this needs to be tested by affected reporters, 
there is no general reproducer for arbitrary systems.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  Uname: Linux 3.19.0-031900-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  Date: Sun Feb 15 18:27:39 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-10-22 (116 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  IpRoute:
   default via 10.0.0.1 dev wlan0  proto static  metric 1024
   10.0.0.0/24 dev wlan0  proto kernel  scope link  src 10.0.0.36
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlan0wifi  connected/org/freedesktop/NetworkManager/Devices/2  
openhost_caldas  09d1f69d-d3da-4978-a69c-d94455db7ecf  
/org/freedesktop/NetworkManager/ActiveConnection/0
   docker0  bridgeunavailable  /org/freedesktop/NetworkManager/Devices/3  
--   ----
   eth0 ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  
--   ----
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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