Activity log for bug #1747765

Date Who What changed Old value New value Message
2018-02-06 21:45:40 Bo Kersey bug added bug
2019-05-30 07:29:46 Launchpad Janitor cups (Ubuntu): status New Confirmed
2019-05-30 07:32:53 Dariusz Gadomski cups (Ubuntu): status Confirmed Fix Released
2019-05-30 07:40:48 Dariusz Gadomski description 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading...
2019-05-30 07:40:55 Dariusz Gadomski cups (Ubuntu): importance Undecided Medium
2019-05-30 07:41:04 Dariusz Gadomski nominated for series Ubuntu Disco
2019-05-30 07:41:04 Dariusz Gadomski bug task added cups (Ubuntu Disco)
2019-05-30 07:41:04 Dariusz Gadomski nominated for series Ubuntu Xenial
2019-05-30 07:41:04 Dariusz Gadomski bug task added cups (Ubuntu Xenial)
2019-05-30 07:41:04 Dariusz Gadomski nominated for series Ubuntu Bionic
2019-05-30 07:41:04 Dariusz Gadomski bug task added cups (Ubuntu Bionic)
2019-05-30 08:19:29 Dariusz Gadomski attachment added disco_cups_2.2.10-4ubuntu2.debdiff https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267599/+files/disco_cups_2.2.10-4ubuntu2.debdiff
2019-05-30 08:19:59 Dariusz Gadomski attachment added bionic_cups_2.2.7-1ubuntu2.6.debdiff https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267600/+files/bionic_cups_2.2.7-1ubuntu2.6.debdiff
2019-05-30 08:22:16 Dariusz Gadomski bug added subscriber STS Sponsors
2019-05-30 08:23:28 Dariusz Gadomski cups (Ubuntu Xenial): assignee Dariusz Gadomski (dgadomski)
2019-05-30 08:23:31 Dariusz Gadomski cups (Ubuntu Xenial): importance Undecided Medium
2019-05-30 08:23:33 Dariusz Gadomski cups (Ubuntu Bionic): importance Undecided Medium
2019-05-30 08:23:35 Dariusz Gadomski cups (Ubuntu Disco): importance Undecided Medium
2019-05-30 11:13:48 Dariusz Gadomski attachment added xenial_cups_2.1.3-4ubuntu0.9.debdiff https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267662/+files/xenial_cups_2.1.3-4ubuntu0.9.debdiff
2019-05-30 12:10:49 Dariusz Gadomski nominated for series Ubuntu Cosmic
2019-05-30 12:10:49 Dariusz Gadomski bug task added cups (Ubuntu Cosmic)
2019-05-30 12:21:23 Dariusz Gadomski attachment added cosmic_cups_2.2.8-5ubuntu1.4.debdiff https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267676/+files/cosmic_cups_2.2.8-5ubuntu1.4.debdiff
2019-05-30 14:03:03 Dariusz Gadomski attachment removed cosmic_cups_2.2.8-5ubuntu1.4.debdiff https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267676/+files/cosmic_cups_2.2.8-5ubuntu1.4.debdiff
2019-05-30 14:03:45 Dariusz Gadomski attachment added cosmic_cups_2.2.8-5ubuntu1.4.debdiff https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+attachment/5267712/+files/cosmic_cups_2.2.8-5ubuntu1.4.debdiff
2019-05-30 14:05:09 Dariusz Gadomski cups (Ubuntu Xenial): assignee Dariusz Gadomski (dgadomski)
2019-05-30 14:05:13 Dariusz Gadomski cups (Ubuntu Cosmic): importance Undecided Medium
2019-05-30 18:22:30 Till Kamppeter cups (Ubuntu Xenial): status New In Progress
2019-05-30 18:22:33 Till Kamppeter cups (Ubuntu Bionic): status New In Progress
2019-05-30 18:22:35 Till Kamppeter cups (Ubuntu Cosmic): status New In Progress
2019-05-30 18:22:38 Till Kamppeter cups (Ubuntu Disco): status New In Progress
2019-05-30 18:23:02 Till Kamppeter bug added subscriber Ubuntu SRU developers
2019-05-30 18:23:15 Till Kamppeter bug added subscriber Ubuntu Stable Release Updates Team
2019-05-30 18:23:18 Till Kamppeter removed subscriber Ubuntu SRU developers
2019-05-31 13:21:54 Dariusz Gadomski removed subscriber STS Sponsors
2019-05-31 18:33:55 Dan Streetman tags sts
2019-05-31 18:34:11 Dan Streetman cups (Ubuntu Disco): assignee Dariusz Gadomski (dgadomski)
2019-06-03 15:55:25 Łukasz Zemczak cups (Ubuntu Disco): status In Progress Fix Committed
2019-06-03 15:55:27 Łukasz Zemczak bug added subscriber SRU Verification
2019-06-03 15:55:30 Łukasz Zemczak tags sts sts verification-needed verification-needed-disco
2019-06-03 16:04:56 Łukasz Zemczak cups (Ubuntu Cosmic): status In Progress Fix Committed
2019-06-03 16:05:02 Łukasz Zemczak tags sts verification-needed verification-needed-disco sts verification-needed verification-needed-cosmic verification-needed-disco
2019-06-03 16:11:07 Łukasz Zemczak cups (Ubuntu Bionic): status In Progress Fix Committed
2019-06-03 16:11:13 Łukasz Zemczak tags sts verification-needed verification-needed-cosmic verification-needed-disco sts verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco
2019-06-03 16:12:18 Łukasz Zemczak cups (Ubuntu Xenial): status In Progress Fix Committed
2019-06-03 16:12:22 Łukasz Zemczak tags sts verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco sts verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco verification-needed-xenial
2019-06-04 08:49:14 Dariusz Gadomski description [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case] * Set PreserveJobHistory to 300. * Schedule a job for printing. * Check the error_log. Expected result: Job is save for at least 300 seconds. Actual results: Job is immediately removed from history. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... [Impact]  The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case]  1. Set PreserveJobHistory to 300.  2. Schedule a job for printing.  3. Check the error_log. 4. Set PreserveJobHistory to Yes. Repeat 2-3. 5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): 300: Job is save for at least 300 seconds. Yes: Job is never removed. No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 300: Job is immediately removed from history. Yes: Job is never removed. No: Job is removed right after processing. [Regression Potential]  * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info]  * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading...
2019-06-04 08:50:58 Dariusz Gadomski description [Impact]  The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case]  1. Set PreserveJobHistory to 300.  2. Schedule a job for printing.  3. Check the error_log. 4. Set PreserveJobHistory to Yes. Repeat 2-3. 5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): 300: Job is save for at least 300 seconds. Yes: Job is never removed. No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 300: Job is immediately removed from history. Yes: Job is never removed. No: Job is removed right after processing. [Regression Potential]  * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info]  * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... [Impact]  The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case]  1. Set PreserveJobHistory to 30.  2. Schedule a job for printing.  3. Check the error_log.  4. Set PreserveJobHistory to Yes. Repeat 2-3.  5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): 300: Job is save for at least 30 seconds. Yes: Job is never removed. No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 300: Job is immediately removed from history. Yes: Job is never removed. No: Job is removed right after processing. [Regression Potential]  * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info]  * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading...
2019-06-04 08:51:12 Dariusz Gadomski description [Impact]  The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case]  1. Set PreserveJobHistory to 30.  2. Schedule a job for printing.  3. Check the error_log.  4. Set PreserveJobHistory to Yes. Repeat 2-3.  5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): 300: Job is save for at least 30 seconds. Yes: Job is never removed. No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 300: Job is immediately removed from history. Yes: Job is never removed. No: Job is removed right after processing. [Regression Potential]  * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info]  * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... [Impact]  The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case]  1. Set PreserveJobHistory to 30.  2. Schedule a job for printing.  3. Check the error_log.  4. Set PreserveJobHistory to Yes. Repeat 2-3.  5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. Yes: Job is never removed. No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. Yes: Job is never removed. No: Job is removed right after processing. [Regression Potential]  * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info]  * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading...
2019-06-04 08:53:34 Dariusz Gadomski description [Impact]  The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case]  1. Set PreserveJobHistory to 30.  2. Schedule a job for printing.  3. Check the error_log.  4. Set PreserveJobHistory to Yes. Repeat 2-3.  5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. Yes: Job is never removed. No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. Yes: Job is never removed. No: Job is removed right after processing. [Regression Potential]  * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info]  * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... [Impact]  The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case]  1. Set PreserveJobHistory to 30. Set LogLevel to debug.  2. Schedule a job for printing.  3. Check the error_log.  4. Set PreserveJobHistory to Yes. Repeat 2-3.  5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. Yes: Job is never removed. No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. Yes: Job is never removed. No: Job is removed right after processing. [Regression Potential]  * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info]  * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading...
2019-06-04 08:56:10 Dariusz Gadomski tags sts verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco verification-needed-xenial sts verification-done-bionic verification-needed verification-needed-cosmic verification-needed-disco verification-needed-xenial
2019-06-04 09:05:39 Dariusz Gadomski tags sts verification-done-bionic verification-needed verification-needed-cosmic verification-needed-disco verification-needed-xenial sts verification-done-bionic verification-done-disco verification-needed verification-needed-cosmic verification-needed-xenial
2019-06-04 09:14:02 Dariusz Gadomski tags sts verification-done-bionic verification-done-disco verification-needed verification-needed-cosmic verification-needed-xenial sts verification-done-bionic verification-done-cosmic verification-done-disco verification-needed verification-needed-xenial
2019-06-04 14:55:42 Dariusz Gadomski cups (Ubuntu Disco): assignee Dariusz Gadomski (dgadomski)
2019-06-04 14:56:38 Dariusz Gadomski description [Impact]  The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case]  1. Set PreserveJobHistory to 30. Set LogLevel to debug.  2. Schedule a job for printing.  3. Check the error_log.  4. Set PreserveJobHistory to Yes. Repeat 2-3.  5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. Yes: Job is never removed. No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. Yes: Job is never removed. No: Job is removed right after processing. [Regression Potential]  * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info]  * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... [Impact]  The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for <seconds>. [Test Case]  1. Set PreserveJobHistory to 30. Set LogLevel to debug.  2. Schedule a job for printing.  3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3.  5. Set PreserveJobHistory to Yes. Repeat 2-3.   Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential]  * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info]  * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups:   Installed: 2.1.3-4ubuntu0.3   Candidate: 2.1.3-4ubuntu0.3   Version table:  *** 2.1.3-4ubuntu0.3 500         500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf       PreserveJobFiles Yes        PreserveJobFiles No        PreserveJobFiles seconds             Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved             for the indicated number of seconds after printing. The default is "86400" (preserve 1 day).        PreserveJobHistory Yes        PreserveJobHistory No        PreserveJobHistory seconds             Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for             the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default             is "Yes". 4) What happens instead.... If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading...
2019-06-04 17:52:08 Dariusz Gadomski tags sts verification-done-bionic verification-done-cosmic verification-done-disco verification-needed verification-needed-xenial sts verification-done verification-done-bionic verification-done-cosmic verification-done-disco verification-done-xenial
2019-06-10 13:25:01 Łukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team
2019-06-10 13:35:04 Launchpad Janitor cups (Ubuntu Disco): status Fix Committed Fix Released
2019-06-10 14:42:59 Launchpad Janitor cups (Ubuntu Cosmic): status Fix Committed Fix Released
2019-06-10 14:45:01 Launchpad Janitor cups (Ubuntu Bionic): status Fix Committed Fix Released
2019-06-10 14:57:14 Launchpad Janitor cups (Ubuntu Xenial): status Fix Committed Fix Released