[Touch-packages] [Bug 559331] Re: Permanent "Printer-out-of-paper" message.

2019-07-26 Thread volker mischo
Same Problem with Ubuntu 18-04 and xerox printer . Always out-of-paper
but this is wrong. Can not clear that or suppress that message.

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

Title:
  Permanent "Printer-out-of-paper" message.

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: cups

  This probably has to do with CUPS. Version: 1.4.1- 4ubuntu2.4 (latest
  on Karmic).

  I was printing a document when the printer was out of paper and got a
  message that "The printer is out of paper". I went to reload it and
  clicked resume on the printer and printing carried on normally.

  From this point on, the message "The printer is out of paper" is permanently 
stuck on the printer. 
  - Every time i print, i get the message "The printer is out of paper", but 
the printing occurs without errors. 
  - The configuration tool (system-config-printer 1.1.12) shows the printer 
with the red error sign. When viewing the properties of said printer, in the 
"Ink/Toner Levels" section, i have the "Status Message":  "Printer 
HP-Officejet-Pro-k550 is out of paper". If i click refresh then i get a "CUPS 
server error": "There was an error during the CUPS operation: 
'client-error-document-format-not-supported'." (Not sure this is relevant). 

  
  Removing and reinstalling the printer fixes this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/559331/+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 1610499] Re: hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process group

2017-12-12 Thread Volker Mischo
*** This bug is a duplicate of bug 1637026 ***
https://bugs.launchpad.net/bugs/1637026

Hello, I 've got the same problem with DB2. When I'm leaving the system
as the DB instance owner, all procs are killed. I guess, it depends on
the new systemd in 1604. ( see /var/log/syslog "received SIGRTMIN+24
from PID  (kill) "  ) maybe some sysctl param like kernel.shmall ..
are involved too. It would be nice if a maintainer finally fixed that
problem.

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

Title:
  hadoop crash: /bin/kill in ubuntu16.04 has bug in killing process
  group

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  when i run hadoop in ubuntu 16.04, ssh will exit, all process which
  belong to hadoop user will be killed ,through debug ,i found the
  /bin/kill in ubuntu16.04 has a bug , it has bug in killing process
  group   .

  Ubuntu version is:

  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  (1)The way to repeat this bug
  It is easy to repeat this bug , run “/bin/kill -15 -12345”  or any like 
“/bin/kill -15 -1”  in ubuntu16.04  , it will kill all the process .

  (2)Cause analysis
  The code of /bin/kill in ubuntu16.04 come from procps-3.3.10 ,  when I run 
“/bin/kill -15 -1” , it actually send signal 15 to -1 ,

  -1 mean it will kill all the process .

  (3)The bug in procps-3.3.10/skill.c ,I think the code "pid =
  (long)('0' - optopt) " is not right .

  static void __attribute__ ((__noreturn__)) kill_main(int argc, char 
**argv)
  {
    case '?':
  if (!isdigit(optopt)) {
  xwarnx(_("invalid argument %c"), optopt);
  kill_usage(stderr);
  } else {
  /* Special case for signal digit negative
   * PIDs */
  pid = (long)('0' - optopt);

  if (kill((pid_t)pid, signo) != 0)
   exitvalue = EXIT_FAILURE;
  exit(exitvalue);
  }
  loop=0;
  }

  (4) the cause
   sometimes when the resource is tight or a hadoop container lost connection 
in sometime, the nodemanager will kill this container , it send a signal to 
kill this jvm process ,it is a normal behavior for hadoop to kill a task and 
then reexecute this task. but with this kill bug ,it kill all the process 
belong to a hadoop user .

  (5) The way to workaround
   I  copy /bin/kill in ubuntu14.04 to override /bin/kill in ubuntu16.04, it is 
ok in this way . I also think it is better to ask procps-3.3.10 maintainer to 
solve their bug,but i don't know how to contact them .

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