Bug 873 - Boot failure, subsequent restarts possible
Summary: Boot failure, subsequent restarts possible
Alias: None
Product: xprint
Classification: Unclassified
Component: Server: Other (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Roland Mainz
QA Contact:
Depends on:
Reported: 2004-07-15 20:34 UTC by Mark Roberts
Modified: 2011-09-13 13:34 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Description Mark Roberts 2004-07-15 20:34:55 UTC
Upon system startup, xprint appears to fail. The following boot.log message is

Jul 15 20:14:23 markhost xprint: /etc/rc5.d/S61xprint[1256]: internal error:
alloc: freeing memory outside of block (corrupted?)

However, once started, one can login, either as root, or user and then su, and
start the server manually. Logging out and back in against produces normal
xplsprinters output and the server will produce output.

Workaround: manual start, logout, re-login, check xplsprinters for output.

Build: 009.001, from SRPM on a Red Hat 7.2 system, kernel 2.4.20-28.7, gcc
2.96.3, glibc 2.2.4. The binary from mozdev.org did not work because of a call
to a glibc 2.3 library.

Note that the symlinks had to be created manually. I will be entering a separate
bug for this problem.
Comment 1 Roland Mainz 2004-07-15 21:10:52 UTC
Mark Roberts  wrote:
> Jul 15 20:14:23 markhost xprint: /etc/rc5.d/S61xprint[1256]: internal error:
> alloc: freeing memory outside of block (corrupted?)

Which process (bash, ksh, Xprt etc.) prints this message ? A quick "grep" over
the old Xprint CVS doesn't show any trace of the message so I assume it comes
from an other application (bash ?!) ... ;-(
Comment 2 Mark Roberts 2004-07-16 19:22:13 UTC
It's done init at that point, and has switched into a run level, so it's bash
that's running the script. But I'm not able to run ps -ef at that spot in the
sequence, so I can't tell you which processes are running (and as whose
children, if any) when xprint is starting.

Additional information:
Even when the error is logged, the screen prompt reports that xprint started OK.

"Interactive" startup was the same (for run level 5).

The logged error does not occur when starting at run level 3. (no NFS on this
system, so didn't try 2)

I tried changing the symlink target paths from an absolute /etc/init.d/xprint to
../init.d/xprint, on the wild chance that the init script might be parsing
something strangely, but that also fails for a run level 5 startup.

Here's what /var/run/Xprint_servers looks like after the failed start (i.e. it's
[root@markhost root]# less /var/run/Xprint_servers 
# Xprint server list
# File is for private use for /etc/rc5.d/S61xprint.
# Do not edit, rely on the content or file format.
# EOF.
Comment 3 Corbin Simpson 2011-09-13 13:34:22 UTC
Closing WONTFIX because nobody cares about Xprint. Reopen if you plan to address this bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.