Fedora Core - Troubleshooting: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{TIP Index}}
{{TIP Index}}[[Category:Installation]] [[Category:Printing]] [[Category:Troubleshooting]] [[Category:EN]] [[Category:Linux]]


FC6 has been released, and some Scribus-related issues are present. The first thing you must do, of course, is to recompile Scribus under FC6. Alternatively, there is an RPM (1.3.3.6) as part of the Extras repository -- just <tt>'yum install scribus'</tt>.
With the release of FC6, some Scribus-related issues developed. Unfortunately, subsequent Fedora releases, up to the current F14, continue to have this direct printing problem. Follow the instructions below. Occasionally, we have heard of similar problems with other Linux distros.
 
Fedora 7 has now been released, with Scribus version 1.3.3.9, and it continues to have the direct printing problem. Follow the instructions below.


===Printing===
===Printing===
Printing directly from Scribus may be broken, if you use the same method and settings from FC5. It seems to generate an error message and no output.
Printing directly from Scribus may be broken, i.e., simply not work.


The fix for this is to check the box for '''Alternative Printing Command''' then in the '''Command''' text box enter  
The fix for this is to check the box for '''Alternative Printing Command''' then in the '''Command''' text box enter  


<tt>lp -d''name-of-your-printer''</tt>
<pre>lp -dname-of-your-printer</pre>


For example, for my printer named "laser", I entered
or


<tt>lp -dlaser</tt>
<pre>lpr -Pnameofprinter</pre>


===Adobe Reader===
''There can, but doesn't have to be, a space between'' <tt>-d</tt> ''and'' <tt>laser</tt>.
If you use either the tar.gz or .rpm files for Adobe Reader 7.08, it will not work. The fix for this is to open '''<tt>/usr/bin/acroread</tt>''' as root (or with sudo) into a text editor (this will be a link to the "real" file, but nonetheless you will be editing the real one). There are two lines that need to be edited.


Look for this line, at about line number 418:
If you have KDE installed, you might try entering <tt>kprinter</tt> as an alternative, in which case kprinter will take care of the connection to CUPS.
<pre>
echo $mfile| sed 's/libgtk-x11-\([0-9]*\).0.so.0.\([0-9]\)00.\([0-9]*\)\|\(.*\)/\1\2\3/g'
</pre>
and change to:
<pre>
echo $mfile| sed 's/libgtk-x11-\([0-9]*\).0.so.0.\([0-9]*\)00.\([0-9]*\)\|\(.*\)/\1\2\3/g'
</pre>
''Note: you are adding an asterix in about the middle''


The other line is at about line number 643:
===Adobe Reader===
<pre>
''Current versions of Adobe Reader do not have this issue, so printing from a PDF is not affected.''
MIN_GTK_VERSION="240"
</pre>
which needs to be changed to:
<pre>
MIN_GTK_VERSION="2040"
</pre>
 
Save the file, and you're done.
 
You might also try, instead of the last change, changing the line (number should be about 644)
<pre>
check_gtk_ver_and_set_lib_path "$MIN_GTK_VERSION"
</pre>
to
<pre>
#check_gtk_ver_and_set_lib_path "$MIN_GTK_VERSION"
</pre>
so that you don't even check the Gtk version.
 
If none of these work, try this -- in the CLI type:
<pre>
export GTK_IM_MODULE=xim
acroread
</pre>
 
If that helps, you can then modify the acroread script by adding
<pre>
# "SCIM hack"
# check if we have a scim GTK module load, and overwrite it to avoid crash
 
if [ $GTK_IM_MODULE = "scim" ]; then
 
export GTK_IM_MODULE=xim
fi
</pre>
Just before these lines, which are at about line 648:
<pre>
#
# Setup configuration specific environment variables
#
</pre>

Latest revision as of 05:32, 14 January 2011

This article is part of the Tips & Tricks series.
Installation • Usage • PDF issues • Other

With the release of FC6, some Scribus-related issues developed. Unfortunately, subsequent Fedora releases, up to the current F14, continue to have this direct printing problem. Follow the instructions below. Occasionally, we have heard of similar problems with other Linux distros.

Printing

Printing directly from Scribus may be broken, i.e., simply not work.

The fix for this is to check the box for Alternative Printing Command then in the Command text box enter 

lp -dname-of-your-printer

or 

lpr -Pnameofprinter

There can, but doesn't have to be, a space between -d and laser.

If you have KDE installed, you might try entering kprinter as an alternative, in which case kprinter will take care of the connection to CUPS.

Adobe Reader

Current versions of Adobe Reader do not have this issue, so printing from a PDF is not affected.

Retrieved from "https://wiki.scribus.net/wiki/index.php?title=Fedora_Core_-_Troubleshooting&oldid=24555"