Difference between revisions of "Fedora Core - Troubleshooting"

From Scribus Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
{{TIP Index}}
 
{{TIP Index}}
  
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 up-to-date RPM (1.3.3.6) as part of the Extras repository -- just <tt>'yum install scribus'</tt>.
+
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>.
  
Fedora 7 has now been released, and it continues to have the direct printing problem. Follow the instructions below.
+
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===

Revision as of 02:17, 17 August 2007

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

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 'yum install scribus'.

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

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

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

lp -dlaser

Adobe Reader

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 /usr/bin/acroread 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:

echo $mfile| sed 's/libgtk-x11-\([0-9]*\).0.so.0.\([0-9]\)00.\([0-9]*\)\|\(.*\)/\1\2\3/g'

and change to:

echo $mfile| sed 's/libgtk-x11-\([0-9]*\).0.so.0.\([0-9]*\)00.\([0-9]*\)\|\(.*\)/\1\2\3/g'

Note: you are adding an asterix in about the middle

The other line is at about line number 643:

MIN_GTK_VERSION="240"

which needs to be changed to:

MIN_GTK_VERSION="2040"

Save the file, and you're done.

You might also try, instead of the last change, changing the line (number should be about 644)

check_gtk_ver_and_set_lib_path "$MIN_GTK_VERSION" 

to

#check_gtk_ver_and_set_lib_path "$MIN_GTK_VERSION" 

so that you don't even check the Gtk version.

If none of these work, try this -- in the CLI type:

export GTK_IM_MODULE=xim
acroread

If that helps, you can then modify the acroread script by adding

# "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

Just before these lines, which are at about line 648:

#
# Setup configuration specific environment variables
#