Bug 212340 - Segfault: /etc/init.d/cups restart
Summary: Segfault: /etc/init.d/cups restart
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 6
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-26 13:14 UTC by Rick Richardson
Modified: 2008-03-17 06:02 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2008-03-17 06:02:01 UTC

Attachments (Terms of Use)
/tmp/cups.tar.bz2 (47.68 KB, application/x-bzip)
2006-10-26 13:52 UTC, Rick Richardson 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Rick Richardson 2006-10-26 13:14:51 UTC 
$ lpstat
lpstat: Unable to connect to server

# /etc/init.d/cups restart
Segmentation fault

$ uname -a
Linux localhost.localdomain 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT
2006 i686 i686 i386 GNU/Linux
$ rpm -q cups
cups-1.2.4-9
Comment 1 Tim Waugh 2006-10-26 13:20:14 UTC 
I would like to preserve the configuration state in case it is possible to
replicate this on another machine.  Please do this as root:

tar jc /tmp/cups.tar.bz2 /etc/cups /var/cache/cups

..and attach /tmp/cups.tar.bz2 to this report.  Thanks.
Comment 2 Rick Richardson 2006-10-26 13:52:17 UTC 
Created attachment 139461 [details]
/tmp/cups.tar.bz2
Comment 3 Tim Waugh 2006-10-26 14:23:52 UTC 
I don't seem to be able to get it to happen here.

Please install cups-debuginfo with:

  yum --enablerepo=core-debuginfo install cups-debuginfo

and then run 'gdb --args /usr/sbin/cupsd -f'.  At the '(gdb)' prompt, enter 'run'.

Does it segfault under those circumstances as well?  If so, what does entering
'bt' show?
Comment 4 petrosyan 2008-03-17 06:02:01 UTC 
The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there have not been any
updates to the report since thirty (30) days or more since we
requested additional information, we're assuming the problem
is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.

Setting status to "INSUFFICIENT_DATA".  If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested, 
please feel free to reopen the bug report.

Thank you in advance.
Note You need to log in before you can comment on or make changes to this bug.