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
  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.

-- 
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).

  [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: 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

Reply via email to