subject:"\[Desktop\-packages\] \[Bug 1086019\] Re\: cupsd crashes regularly \(daily\)"

Bad news : I had a cupsd crash this morning.
I will try to post the apport crash here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Here is the crash log found on /var/crash .

** Attachment added: New crash after having tested the proposed patch 
(05-17-2013)
   
https://bugs.launchpad.net/ubuntu/quantal/+source/cups/+bug/1086019/+attachment/3679380/+files/_usr_sbin_cupsd.0.crash.zip

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

I just checked the '/etc/logrotate.d/cups' file and it has the same
content as the improved script you provided.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-05-17 Thread Till Kamppeter

Cedric, can you run

ls -l /etc/apport/blacklist.d/cups*

post the output here, and attach all files which get listed by this
command.

Please attach the files one by one, do not compress or package them.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

 ls -l /etc/apport/blacklist.d/cups*
ls: impossible d'accéder à /etc/apport/blacklist.d/cups*: Aucun fichier ou 
dossier de ce type

== No such file or directory

 ls -l /etc/apport/blacklist.d/*
-rw-r--r-- 1 root root 216 oct.  10  2012 /etc/apport/blacklist.d/apport
-rw-r--r-- 1 root root  59 oct.  11  2012 /etc/apport/blacklist.d/firefox
-rw-r--r-- 1 root root 217 oct.   1  2012 
/etc/apport/blacklist.d/README.blacklist
-rw-r--r-- 1 root root  71 oct.  11  2012 /etc/apport/blacklist.d/thunderbird

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-05-17 Thread Till Kamppeter

Cedric, sorry, forget about the previous comment, I wanted to ask you
another thing.

You are sure that your file /etc/logrotate.d/cups is exactly the same as
the one I asked you for testing in comment #15.

Can you attach your /etc/logrotate.d/cups file here? Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Here is my '/etc/logrotate.d/cups' file.

** Attachment added: My /etc/logrotate.d/cups
   
https://bugs.launchpad.net/ubuntu/quantal/+source/cups/+bug/1086019/+attachment/3679435/+files/cups

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

My machine will be online the 3 following days and idle.
I will see Tuesday if other crashes occurred.
If you want I can also reboot the machine before leaving the office (in one 
hour).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-05-17 Thread Till Kamppeter

Cedric, the script is the correct one. Please do the reboot and then we
will see whether you get further crashes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-05-15 Thread Cedric M

I think I missed something, where do I find the 'proposed package' ?
Will automatic update propose it to me? Do I have to upgrade Ubuntu from 12.10 
to 13.04 ?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Cedric, you do not need to upgrade to 13.04.

The proposed package is not yet made available. It will be announced
here. I will try to make the SRU aware of the fact that they still did
not approve this package.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-05-15 Thread Adam Conrad

Hello Steve, or anyone else affected,

Accepted cups into quantal-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/cups/1.6.1-0ubuntu11.4
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: cups (Ubuntu Quantal)
   Status: In Progress = Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450]

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Cedric, please follow the instructions of  comment #25, comment #21, and
comment #22 and tell us your results here. First, do the steps of BOTH
comment #21 and comment #22 to clean up the configuration changes of
your first testing/workaround. ONLY AFTER THAT, follow the instructions
of comment #25.

Please report your results here. Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-05-15 Thread Launchpad Bug Tracker

** Branch linked: lp:ubuntu/quantal-proposed/cups

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-05-15 Thread Cedric M

Already did #21 two weeks ago and crashes came back.

#22 does not work:

cmarin@BAT:~/tmpdir$ sudo dpkg -i --force-confmiss cups-daemon_*.deb

dpkg: erreur de traitement de cups-daemon_*.deb (--install) :
 ne peut pas accéder à l'archive: Aucun fichier ou dossier de ce type
Des erreurs ont été rencontrées pendant l'exécution :
 cups-daemon_*.deb
-
in english:
 cannot access to archive: no such file or directory

I tried to add a apt-get download cups-daemon but it does not work
either.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Cedric, sorry, forget about comment #22. The cups-daem,on package was
only introduced with 13.04. So you need to follow only the instructions
of comment #21 and this you have done two weeks ago. Now you should
observe the daily crashes, which you already confirmed.

So now please install the proposed package as described in comment #25.
After that you should not observe the crashes any more. Please tell us
whether this is the case.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-05-15 Thread Cedric M

#25 done via automatic update: it worked but a dialog box asked me
whether to replace or not the content of a file like logrotate.d/cups
(I didn't note it, sorry). The file changes text field was empty.

I choose replace as recommended by the dialog but if this file is
related to the crash maybe the replace should be forced or at least it
should be told that 'replace' is needed to fix a crash.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Cedric, the pop-up about replacing the file does not appear for normal
users but only for you because you have manually put logrotate.d/cups
file in place for doing the first tests I asked you for. Having answered
Replace was correct. You are now using the file of the package. So now
you are all set for the test. If you have no crash report tomorrow, the
fix in the proposed package is verified.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  Fix Committed
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-05-11 Thread Till Kamppeter

When testing using the commands above, please replace

sudo dpkg -i --force-confmiss cups_*.deb

by

sudo dpkg -i --force-confmiss cups-daemon_*.deb
sudo dpkg -i --force-confmiss cups_*.deb

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-05-04 Thread Launchpad Bug Tracker

** Branch linked: lp:debian/experimental/cups

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day triggered by logrotate, popping up an Apport dialog to
  upload the crash info to Launchpad. Otherwise all is working
  correctly, there is only the annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package the logrotate script is improved to not take
  a way log files from CUPS while it is running. It stops CUPS, moves
  the log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.

  You can test whether crash reports still work with the proposed
  package by triggering an artificial crash running the command

  sudo killall -11 cupsd

  Check whether the crash report process of Apport gets triggered, but
  DO NOT post the generated bug report on Launchpad. Remove
  /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
  if this does not happen and try again.

  [Regression Potential]

  None. No change in any executable which could cause a regression.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-04-23 Thread Cedric M

Hi, 
It is now Tuesday and cupsd has not crashed since I replaced 
'/etc/logrotate.d/cups' , my machine was online all the week end.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day, popping up an Apport dialog to upload the crash info to
  Launchpad. Otherwise all is working correctly, there is only the
  annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package these crash reports are suppressed. CUPS is
  still crashing once a day, but Upstart restarts it and no crash report
  appears. So the system appears to behave normally. The crash is of no
  harm, it is probably triggered by cron job action during the night and
  due to Upstart restarting CUPS CUPS is always present. Printing does
  not trigger the crash, so print jobs are always executed correctly.

  [Regression Potential]

  None. No change in any executable which could cause a regression. Only
  disadvantage is that not yet discovered crashes for other reasons do
  not get visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8:
  dmi.product.name: MacBookPro3,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Cedric, thanks for the test. I will apply the new logrotate script for
CUPS soon, also for newer versions to avoid crashes and problems in the
future, simply by having a cleaner logrotate script.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
Fix Released
Status in “cups-filters” package in Ubuntu:
Fix Released
Status in “cups” source package in Quantal:
In Progress
Status in “cups-filters” source package in Quantal:
Invalid

Bug description:
Every day I get a 'System Problem Detected' dialog that says that
cupsd has crashed. The symptom is similar to the one described in bug
1034045.

I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
that version installed and the errors persist. The test case in bug
1034045 does not result in an immediate crash of cupsd. Specifically,
this does not produce a crash on my system:

1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
2. Run 'sudo service cupsd restart'
3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created
(and if on a desktop, that a new crash notification has been shown).

[IMPACT]

For CUPS users who activate the Show printers shared by other
systems in the server settings of system-config-printer or in the
CUPS web interface, so that they automatically get shared remote CUPS
printers listed in print dialogs CUPS crashes regularly, typically
once a day, popping up an Apport dialog to upload the crash info to
Launchpad. Otherwise all is working correctly, there is only the
annoying crash report.

[TESTCASE]

Activate Show printers shared by other systems in the server
settings of system-config-printer or run the command

cupsctl --remote-printers

I am not sure whether there must be actually a remote printer to
trigger the crash. So on another computer in the same local network
(or on a virtual machine if you do not have a second computer) create
a CUPS queue and share it. Activate Published shared printers
connected to this system in the server settings of system-config-
printer or run the command

cupsctl --share-printers

on that computer. Now observe for some days. Probably you will get a
crash report once a day.

With the proposed package these crash reports are suppressed. CUPS is
still crashing once a day, but Upstart restarts it and no crash report
appears. So the system appears to behave normally. The crash is of no
harm, it is probably triggered by cron job action during the night and
due to Upstart restarting CUPS CUPS is always present. Printing does
not trigger the crash, so print jobs are always executed correctly.

[Regression Potential]

None. No change in any executable which could cause a regression. Only
disadvantage is that not yet discovered crashes for other reasons do
not get visible.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: cups 1.6.1-0ubuntu11
ProcVersionSignature: Error: [Errno 2] No such file or directory:
'/proc/version_signature'
Uname: Linux 3.6.3-030603-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu6
Architecture: amd64
CupsErrorLog:

Date: Mon Dec 3 10:49:54 2012
InstallationDate: Installed on 2010-09-17 (808 days ago)
InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
KernLog:
Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
MachineType: Apple Inc. MacBookPro3,1
MarkForUpload: True
Papersize: letter
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
SourcePackage: cups
UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
dmi.bios.date: 03/05/08
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP31.88Z.0070.B07.0803051658
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F4238BC8
dmi.board.vendor: Apple Inc.
dmi.board.version: PVT
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 2
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F4238BC8
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8:
dmi.product.name: MacBookPro3,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

To manage

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Everyone testing my new logrotate script (comment #15), please do not
forget to remove the /etc/apport/blacklist.d/cups file from the
initially proposed package.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
cupsd crashes regularly (daily)

Bug description:
Every day I get a 'System Problem Detected' dialog that says that
cupsd has crashed. The symptom is similar to the one described in bug
1034045.

[IMPACT]

[TESTCASE]

Activate Show printers shared by other systems in the server
settings of system-config-printer or run the command

cupsctl --remote-printers

cupsctl --share-printers

on that computer. Now observe for some days. Probably you will get a
crash report once a day.

[Regression Potential]

None. No change in any executable which could cause a regression. Only
disadvantage is that not yet discovered crashes for other reasons do
not get visible.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Uploaded a new fixed package to quantal-proposed, this time using the
improved logrotate script. As soon as the package gets approved it will
be available for testing and a comment with instructions will be posted
here. Please test it and give us feedback as your feedback is required
to make the package an official update.

SRU Team: debdiff is attached.

** Patch added: cups_1.6.1-0ubuntu11.3_1.6.1-0ubuntu11.4.debdiff
   
https://bugs.launchpad.net/ubuntu/quantal/+source/cups/+bug/1086019/+attachment/3651525/+files/cups_1.6.1-0ubuntu11.3_1.6.1-0ubuntu11.4.debdiff

** Description changed:

  Every day I get a 'System Problem Detected' dialog that says that cupsd
  has crashed. The symptom is similar to the one described in bug 1034045.
  
  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that
  version installed and the errors persist. The test case in bug 1034045
  does not result in an immediate crash of cupsd. Specifically,  this does
  not produce a crash on my system:
  
  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).
  
  [IMPACT]
  
  For CUPS users who activate the Show printers shared by other systems
  in the server settings of system-config-printer or in the CUPS web
  interface, so that they automatically get shared remote CUPS printers
- listed in print dialogs CUPS crashes regularly, typically once a day,
- popping up an Apport dialog to upload the crash info to Launchpad.
- Otherwise all is working correctly, there is only the annoying crash
- report.
+ listed in print dialogs CUPS crashes regularly, typically once a day
+ triggered by logrotate, popping up an Apport dialog to upload the crash
+ info to Launchpad. Otherwise all is working correctly, there is only the
+ annoying crash report.
  
  [TESTCASE]
  
  Activate Show printers shared by other systems in the server settings
  of system-config-printer or run the command
  
  cupsctl --remote-printers
  
  I am not sure whether there must be actually a remote printer to trigger
  the crash. So on another computer in the same local network (or on a
  virtual machine if you do not have a second computer) create a CUPS
  queue and share it. Activate Published shared printers connected to
  this system in the server settings of system-config-printer or run the
  command
  
  cupsctl --share-printers
  
  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.
  
- With the proposed package these crash reports are suppressed. CUPS is
- still crashing once a day, but Upstart restarts it and no crash report
- appears. So the system appears to behave normally. The crash is of no
- harm, it is probably triggered by cron job action during the night and
- due to Upstart restarting CUPS CUPS is always present. Printing does not
- trigger the crash, so print jobs are always executed correctly.
+ With the proposed package the logrotate script is improved to not take a
+ way log files from CUPS while it is running. It stops CUPS, moves the
+ log files, and after that starts CUPS again. This way CUPS stops
+ crashing during the logrotate once a day, so the system will behave
+ normally now. Printing does not trigger the crash, so print jobs are
+ always executed correctly.
  
  [Regression Potential]
  
- None. No change in any executable which could cause a regression. Only
- disadvantage is that not yet discovered crashes for other reasons do not
- get visible.
+ None. No change in any executable which could cause a regression.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:
  
  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Cedric, and everyone else who tested my improved logrotate script, as
soon as the proposed package gets available please run the following
commands in a terminal window to remove my script before installing the
proposed package:

sudo rm  /etc/logrotate.d/cups /etc/apport/blacklist.d/cups
mkdir tmpdir
cd tmpdir
apt-get download cups 
sudo dpkg -i --force-confmiss cups_*.deb
cd ..
rm -rf tmpdir

Then install the package as described in the instructions which will get
posted here.

Note that testing the proposed package and giving feedback here is
required for the proposed package to get an official update.


** Description changed:

  Every day I get a 'System Problem Detected' dialog that says that cupsd
  has crashed. The symptom is similar to the one described in bug 1034045.
  
  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that
  version installed and the errors persist. The test case in bug 1034045
  does not result in an immediate crash of cupsd. Specifically,  this does
  not produce a crash on my system:
  
  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).
  
  [IMPACT]
  
  For CUPS users who activate the Show printers shared by other systems
  in the server settings of system-config-printer or in the CUPS web
  interface, so that they automatically get shared remote CUPS printers
  listed in print dialogs CUPS crashes regularly, typically once a day
  triggered by logrotate, popping up an Apport dialog to upload the crash
  info to Launchpad. Otherwise all is working correctly, there is only the
  annoying crash report.
  
  [TESTCASE]
  
  Activate Show printers shared by other systems in the server settings
  of system-config-printer or run the command
  
  cupsctl --remote-printers
  
  I am not sure whether there must be actually a remote printer to trigger
  the crash. So on another computer in the same local network (or on a
  virtual machine if you do not have a second computer) create a CUPS
  queue and share it. Activate Published shared printers connected to
  this system in the server settings of system-config-printer or run the
  command
  
  cupsctl --share-printers
  
  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.
  
  With the proposed package the logrotate script is improved to not take a
  way log files from CUPS while it is running. It stops CUPS, moves the
  log files, and after that starts CUPS again. This way CUPS stops
  crashing during the logrotate once a day, so the system will behave
  normally now. Printing does not trigger the crash, so print jobs are
  always executed correctly.
  
+ You can test whether crash reports still work with the proposed package
+ by triggering an artificial crash running the command
+ 
+ sudo killall -11 cupsd
+ 
+ Check whether the crash report process of Apport gets triggered, but DO
+ NOT post the generated bug report on Launchpad. Remove
+ /etc/apport/blacklist.d/cups (remainder from earlier proposed package)
+ if this does not happen and try again.
+ 
  [Regression Potential]
  
  None. No change in any executable which could cause a regression.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:
  
  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-04-19 Thread Cedric M

cupsd crashes nearly everyday on my machine.
I just replaced /etc/logrotate.d/cups by your file and I will tell you Monday
whether the crash still occurs.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
cupsd crashes regularly (daily)

Bug description:
Every day I get a 'System Problem Detected' dialog that says that
cupsd has crashed. The symptom is similar to the one described in bug
1034045.

[IMPACT]

[TESTCASE]

Activate Show printers shared by other systems in the server
settings of system-config-printer or run the command

cupsctl --remote-printers

cupsctl --share-printers

on that computer. Now observe for some days. Probably you will get a
crash report once a day.

[Regression Potential]

None. No change in any executable which could cause a regression. Only
disadvantage is that not yet discovered crashes for other reasons do
not get visible.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-01-18 Thread Till Kamppeter

Everyone who suffers this problem (probably only Quantal users), please
replace your file /etc/logrotate.d/cups by the attached file:

sudo cp cups.logrotate /etc/logrotate.d/cups

Now observe for some days. Do the daily crashes go away?

** Attachment added: cups.logrotate
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+attachment/3488179/+files/cups.logrotate

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day, popping up an Apport dialog to upload the crash info to
  Launchpad. Otherwise all is working correctly, there is only the
  annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package these crash reports are suppressed. CUPS is
  still crashing once a day, but Upstart restarts it and no crash report
  appears. So the system appears to behave normally. The crash is of no
  harm, it is probably triggered by cron job action during the night and
  due to Upstart restarting CUPS CUPS is always present. Printing does
  not trigger the crash, so print jobs are always executed correctly.

  [Regression Potential]

  None. No change in any executable which could cause a regression. Only
  disadvantage is that not yet discovered crashes for other reasons do
  not get visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-01-12 Thread Launchpad Bug Tracker

** Branch linked: lp:debian/experimental/cups-filters

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
cupsd crashes regularly (daily)

Bug description:
Every day I get a 'System Problem Detected' dialog that says that
cupsd has crashed. The symptom is similar to the one described in bug
1034045.

[IMPACT]

[TESTCASE]

Activate Show printers shared by other systems in the server
settings of system-config-printer or run the command

cupsctl --remote-printers

cupsctl --share-printers

on that computer. Now observe for some days. Probably you will get a
crash report once a day.

[Regression Potential]

None. No change in any executable which could cause a regression. Only
disadvantage is that not yet discovered crashes for other reasons do
not get visible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+subscriptions

--
Mailing list:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-01-02 Thread Launchpad Bug Tracker

This bug was fixed in the package cups-filters - 1.0.28-0ubuntu1

---
cups-filters (1.0.28-0ubuntu1) raring; urgency=low

  * New upstream release
 - cups-browsed: Added daemon to browse the Bonjour broadcasts of
   shared remote CUPS printers and automatically add local raw queues
   pointing to them, to resemble the behavior of the former CUPS
   broadcasting/browsing which was dropped in CUPS 1.6. Now remote
   printers appear as local print queues as before, but with the
   standardized Bonjour broadcasting (LP: #1086019, LP: #1061063,
   LP: #1061069).
  * debian/control: Added build dependencies on Avahi, needed for the new
cups-browsed and also a new binary package named cups-browsed.
  * debian/cups-browsed.install: New cups-browsed binary package.
  * debian/local/cups-browsed.upstart: Upstart configuration file for
cups-browsed.
  * debian/rules: Added everything needed so that the cups-browsed daemon gets
started automatically.
  * debian/cups-filters.install: Include files from /usr/bin.
 -- Till Kamppeter till.kamppe...@gmail.com   Sat, 29 Dec 2012 14:30:07 +0100

** Changed in: cups-filters (Ubuntu)
   Status: Triaged = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day, popping up an Apport dialog to upload the crash info to
  Launchpad. Otherwise all is working correctly, there is only the
  annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package these crash reports are suppressed. CUPS is
  still crashing once a day, but Upstart restarts it and no crash report
  appears. So the system appears to behave normally. The crash is of no
  harm, it is probably triggered by cron job action during the night and
  due to Upstart restarting CUPS CUPS is always present. Printing does
  not trigger the crash, so print jobs are always executed correctly.

  [Regression Potential]

  None. No change in any executable which could cause a regression. Only
  disadvantage is that not yet discovered crashes for other reasons do
  not get visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2013-01-02 Thread Launchpad Bug Tracker

** Branch linked: lp:ubuntu/cups-filters

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day, popping up an Apport dialog to upload the crash info to
  Launchpad. Otherwise all is working correctly, there is only the
  annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package these crash reports are suppressed. CUPS is
  still crashing once a day, but Upstart restarts it and no crash report
  appears. So the system appears to behave normally. The crash is of no
  harm, it is probably triggered by cron job action during the night and
  due to Upstart restarting CUPS CUPS is always present. Printing does
  not trigger the crash, so print jobs are always executed correctly.

  [Regression Potential]

  None. No change in any executable which could cause a regression. Only
  disadvantage is that not yet discovered crashes for other reasons do
  not get visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8:
  dmi.product.name: MacBookPro3,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+subscriptions

-- 
Mailing list:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2012-12-29 Thread Launchpad Bug Tracker

** Branch linked: lp:ubuntu/raring-proposed/cups

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Triaged
Status in “cups-filters” package in Ubuntu:
  Triaged
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day, popping up an Apport dialog to upload the crash info to
  Launchpad. Otherwise all is working correctly, there is only the
  annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package these crash reports are suppressed. CUPS is
  still crashing once a day, but Upstart restarts it and no crash report
  appears. So the system appears to behave normally. The crash is of no
  harm, it is probably triggered by cron job action during the night and
  due to Upstart restarting CUPS CUPS is always present. Printing does
  not trigger the crash, so print jobs are always executed correctly.

  [Regression Potential]

  None. No change in any executable which could cause a regression. Only
  disadvantage is that not yet discovered crashes for other reasons do
  not get visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8:
  dmi.product.name: MacBookPro3,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+subscriptions

-- 
Mailing list:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2012-12-29 Thread Launchpad Bug Tracker

This bug was fixed in the package cups - 1.6.1-0ubuntu13

---
cups (1.6.1-0ubuntu13) raring; urgency=low

  * debian/patches/forward-port-cups-1-5-x-cups-browsing.patch: Removed the
forward-port of CUPS broadcasting/browsing as from cups-filters 1.0.27
on we have cups-browsed which does Bonjour browsing for us making the
patch unneeded. This eliminates also a crash bug in cupsd (LP: #1086019,
LP: #1061063, LP: #1061069).
  * debian/rules: Removed --with-remote_protocols='CUPS dnssd' from the
./configure command line and removed the CUPS from
--with-local_protocols='CUPS dnssd'. These settings are not supported
any more in stock CUPS 1.6.x (without forward-port of CUPS broadcasting/
browsing).
  * debian/cups.postinst: Again clean /etc/cups/cupsd.conf from all keywords
and settings which got obsolete with the dropping CUPS Broadcasting/
Browsing in CUPS 1.6.x: BrowsePoll, BrowseAllow, BrowseDeny, BrowseOrder,
and BrowseRemoteProtocols lines get removed and the cups argument gets
removed from the BrowseLocalProtocols line.
  * debian/patches/airprint-support.patch,
debian/patches/cupsd-no-crash-on-avahi-threaded-poll-shutdown.patch:
Refreshed with quilt.
  * debian/patches/CVE-2012-5519.patch: Manually updated.
 -- Till Kamppeter till.kamppe...@gmail.com   Fri, 28 Dec 2012 22:27:30 +0100

** Changed in: cups (Ubuntu)
   Status: Triaged = Fix Released

** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2012-5519

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Triaged
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day, popping up an Apport dialog to upload the crash info to
  Launchpad. Otherwise all is working correctly, there is only the
  annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package these crash reports are suppressed. CUPS is
  still crashing once a day, but Upstart restarts it and no crash report
  appears. So the system appears to behave normally. The crash is of no
  harm, it is probably triggered by cron job action during the night and
  due to Upstart restarting CUPS CUPS is always present. Printing does
  not trigger the crash, so print jobs are always executed correctly.

  [Regression Potential]

  None. No change in any executable which could cause a regression. Only
  disadvantage is that not yet discovered crashes for other reasons do
  not get visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2012-12-29 Thread Launchpad Bug Tracker

** Branch linked: lp:ubuntu/raring-proposed/cups-filters

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
Fix Released
Status in “cups-filters” package in Ubuntu:
Triaged
Status in “cups” source package in Quantal:
In Progress
Status in “cups-filters” source package in Quantal:
Invalid

Bug description:
Every day I get a 'System Problem Detected' dialog that says that
cupsd has crashed. The symptom is similar to the one described in bug
1034045.

[IMPACT]

[TESTCASE]

Activate Show printers shared by other systems in the server
settings of system-config-printer or run the command

cupsctl --remote-printers

cupsctl --share-printers

on that computer. Now observe for some days. Probably you will get a
crash report once a day.

[Regression Potential]

None. No change in any executable which could cause a regression. Only
disadvantage is that not yet discovered crashes for other reasons do
not get visible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+subscriptions

--
Mailing list:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2012-12-27 Thread Till Kamppeter

** Also affects: cups-filters (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cups-filters (Ubuntu)
   Status: New = Triaged

** Changed in: cups-filters (Ubuntu Quantal)
   Status: New = Invalid

** Changed in: cups-filters (Ubuntu)
   Importance: Undecided = High

** Changed in: cups-filters (Ubuntu)
 Assignee: (unassigned) = Till Kamppeter (till-kamppeter)

** Changed in: cups-filters (Ubuntu)
Milestone: None = ubuntu-13.04-feature-freeze

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Triaged
Status in “cups-filters” package in Ubuntu:
  Triaged
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day, popping up an Apport dialog to upload the crash info to
  Launchpad. Otherwise all is working correctly, there is only the
  annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package these crash reports are suppressed. CUPS is
  still crashing once a day, but Upstart restarts it and no crash report
  appears. So the system appears to behave normally. The crash is of no
  harm, it is probably triggered by cron job action during the night and
  due to Upstart restarting CUPS CUPS is always present. Printing does
  not trigger the crash, so print jobs are always executed correctly.

  [Regression Potential]

  None. No change in any executable which could cause a regression. Only
  disadvantage is that not yet discovered crashes for other reasons do
  not get visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

2012-12-27 Thread Till Kamppeter

I have now released cups-filters 1.0.26 upstream, with the new cups-
browsed daemon added. cups-browsed browses the Bonjour broadcasts of
shared remote CUPS queues and makes the queues available locally,
eliminating the need of the forward-port patch for CUPS
broadcasting/browsing. As soon as this package is available in Raring I
will remove the patch from Raring's CUPS, eliminating the crashes.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Triaged
Status in “cups-filters” package in Ubuntu:
  Triaged
Status in “cups” source package in Quantal:
  In Progress
Status in “cups-filters” source package in Quantal:
  Invalid

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  [IMPACT]

  For CUPS users who activate the Show printers shared by other
  systems in the server settings of system-config-printer or in the
  CUPS web interface, so that they automatically get shared remote CUPS
  printers listed in print dialogs CUPS crashes regularly, typically
  once a day, popping up an Apport dialog to upload the crash info to
  Launchpad. Otherwise all is working correctly, there is only the
  annoying crash report.

  [TESTCASE]

  Activate Show printers shared by other systems in the server
  settings of system-config-printer or run the command

  cupsctl --remote-printers

  I am not sure whether there must be actually a remote printer to
  trigger the crash. So on another computer in the same local network
  (or on a virtual machine if you do not have a second computer) create
  a CUPS queue and share it. Activate Published shared printers
  connected to this system in the server settings of system-config-
  printer or run the command

  cupsctl --share-printers

  on that computer. Now observe for some days. Probably you will get a
  crash report once a day.

  With the proposed package these crash reports are suppressed. CUPS is
  still crashing once a day, but Upstart restarts it and no crash report
  appears. So the system appears to behave normally. The crash is of no
  harm, it is probably triggered by cron job action during the night and
  due to Upstart restarting CUPS CUPS is always present. Printing does
  not trigger the crash, so print jobs are always executed correctly.

  [Regression Potential]

  None. No change in any executable which could cause a regression. Only
  disadvantage is that not yet discovered crashes for other reasons do
  not get visible.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:

  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Uploaded a fixed package to quantal-proposed. As soon as the package
gets approved it will be available for testing and a comment with
instructions will be posted here. Please test it and give us fedback as
your feedback is required to make the package an official update.

SRU Team: debdiff is attached.

** Changed in: cups (Ubuntu Quantal)
   Status: Confirmed = In Progress

** Patch added: cups_1.6.1-0ubuntu11.3_1.6.1-0ubuntu11.4.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+attachment/3465196/+files/cups_1.6.1-0ubuntu11.3_1.6.1-0ubuntu11.4.debdiff

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
  cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
  Triaged
Status in “cups” source package in Quantal:
  In Progress

Bug description:
  Every day I get a 'System Problem Detected' dialog that says that
  cupsd has crashed. The symptom is similar to the one described in bug
  1034045.

  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have
  that version installed and the errors persist. The test case in bug
  1034045 does not result in an immediate crash of cupsd. Specifically,
  this does not produce a crash on my system:

  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:
   
  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
   Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
   Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F4238BC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8:
  dmi.product.name: MacBookPro3,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

Note thst the proposed package is applying a workaround which is
specific to Quantal. The fix in Raring will be removing the patch for
forward-porting CUPS broadcasting/browsing and replacing it by an extra
daemon for Avahi browsing, making use of CUPS' Avahi broadcasts. The
daemon will be part of the cups-filters package and I have nearly
completed its development. So please process this SRU without the Raring
task being Fix Released.


** Description changed:

  Every day I get a 'System Problem Detected' dialog that says that cupsd
  has crashed. The symptom is similar to the one described in bug 1034045.
  
  I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that
  version installed and the errors persist. The test case in bug 1034045
  does not result in an immediate crash of cupsd. Specifically,  this does
  not produce a crash on my system:
  
  1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash'
  2. Run 'sudo service cupsd restart'
  3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created 
(and if on a desktop, that a new crash notification has been shown).
  
+ [IMPACT]
+ 
+ For CUPS users who activate the Show printers shared by other systems
+ in the server settings of system-config-printer or in the CUPS web
+ interface, so that they automatically get shared remote CUPS printers
+ listed in print dialogs CUPS crashes regularly, typically once a day,
+ popping up an Apport dialog to upload the crash info to Launchpad.
+ Otherwise all is working correctly, there is only the annoying crash
+ report.
+ 
+ [TESTCASE]
+ 
+ Activate Show printers shared by other systems in the server settings
+ of system-config-printer or run the command
+ 
+ cupsctl --remote-printers
+ 
+ I am not sure whether there must be actually a remote printer to trigger
+ the crash. So on another computer in the same local network (or on a
+ virtual machine if you do not have a second computer) create a CUPS
+ queue and share it. Activate Published shared printers connected to
+ this system in the server settings of system-config-printer or run the
+ command
+ 
+ cupsctl --share-printers
+ 
+ on that computer. Now observe for some days. Probably you will get a
+ crash report once a day.
+ 
+ With the proposed package these crash reports are suppressed. CUPS is
+ still crashing once a day, but Upstart restarts it and no crash report
+ appears. So the system appears to behave normally. The crash is of no
+ harm, it is probably triggered by cron job action during the night and
+ due to Upstart restarting CUPS CUPS is always present. Printing does not
+ trigger the crash, so print jobs are always executed correctly.
+ 
+ [Regression Potential]
+ 
+ None. No change in any executable which could cause a regression. Only
+ disadvantage is that not yet discovered crashes for other reasons do not
+ get visible.
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 3.6.3-030603-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  CupsErrorLog:
-  
+ 
  Date: Mon Dec  3 10:49:54 2012
  InstallationDate: Installed on 2010-09-17 (808 days ago)
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1)
  KernLog:
-  Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
-  Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
+  Dec  3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 
audit(1354549274.550:29): apparmor=STATUS operation=profile_replace 
name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser
+  Dec  3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 
audit(1354549274.550:30): apparmor=STATUS operation=profile_replace 
name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser
  MachineType: Apple Inc. MacBookPro3,1
  MarkForUpload: True
  Papersize: letter
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic 
root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash
  SourcePackage: cups
  UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago)
  dmi.bios.date: 03/05/08
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP31.88Z.0070.B07.0803051658
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F4238BC8
  dmi.board.vendor: Apple Inc.
  dmi.board.version: PVT
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 2

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)

For me the crash always happens when the logrotate is done around 8am in
the morning (beginning of /ver/log/syslog), probably the logrotating of
the CUPS log files (perhaps the reload of the CUPS daemon) triggers the
crash.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1086019

Title:
cupsd crashes regularly (daily)

Status in “cups” package in Ubuntu:
Triaged
Status in “cups” source package in Quantal:
In Progress

Bug description:
Every day I get a 'System Problem Detected' dialog that says that
cupsd has crashed. The symptom is similar to the one described in bug
1034045.

[IMPACT]

[TESTCASE]

Activate Show printers shared by other systems in the server
settings of system-config-printer or run the command

cupsctl --remote-printers

cupsctl --share-printers

on that computer. Now observe for some days. Probably you will get a
crash report once a day.

[Regression Potential]

None. No change in any executable which could cause a regression. Only
disadvantage is that not yet discovered crashes for other reasons do
not get visible.

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)