openoffice won't start due to xorg.conf

Cyrusm · 2008-02-20 17:10:24

So first of all, Open Office used to work. I recently purchased a new monitor and a new graphics card (so I can run dual monitors, which is sweet btw ) anyway. since upgrading my system, open office doesn't work, and I believe the problem is rooted to my xorg.conf file or possibly the graphics card/driver.

I've got a ATI radeon x1550 card and I'm using the Catalyst driver. when I set it up I cheated (was lazy) and used the aticonfig command to generate xorg.conf (because I'm not very knowledgeable at getting this set up on my own) and now I need some help. goal: get open office working. I think this has something to do with DRI (according to the OpenOffice wiki) any ideas?

my xorg.conf:

Section "ServerLayout"

# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
    Identifier     "Simple Layout"
    Screen      0  "aticonfig-Screen[0]" 0 0
    Screen         "aticonfig-Screen[1]" RightOf "aticonfig-Screen[0]"
    InputDevice    "Mouse1" "CorePointer"
    InputDevice    "Keyboard1" "CoreKeyboard"
EndSection

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.
#    RgbPath    "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# 
#    FontPath   "/usr/lib/X11/fonts/local/"
#    FontPath   "/usr/lib/X11/fonts/misc/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/lib/X11/fonts/Type1/"
#    FontPath   "/usr/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/lib/X11/fonts/freefont/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/"
#    FontPath   "/usr/lib/X11/fonts/100dpi/"
# The module search path.  The default path is shown here.
#    ModulePath "/usr/lib/modules"
    FontPath     "/usr/share/fonts/misc"
    FontPath     "/usr/share/fonts/100dpi:unscaled"
    FontPath     "/usr/share/fonts/75dpi:unscaled"
    FontPath     "/usr/share/fonts/TTF"
    FontPath     "/usr/share/fonts/Type1"
EndSection

Section "Module"

# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
#    Load        "type1"
# This loads the GLX module
#    Load       "glx"
# This loads the DRI module
#    Load       "dri"
    Load  "dbe"      # Double buffer extension
    SubSection "extmod"
        Option        "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection
    Load  "freetype"
#    Load        "xtt"
EndSection

Section "InputDevice"

#    Option    "Xleds"      "1 2 3"
#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"
# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""
#    Option "XkbDisable"
    Identifier  "Keyboard1"
    Driver      "kbd"
    Option        "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
    Option        "XkbRules" "xorg"
    Option        "XkbModel" "pc105"
    Option        "XkbLayout" "us"
EndSection

Section "InputDevice"

# Identifier and driver
#    Option "Resolution"    "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
#    Option "BaudRate"    "9600"
#    Option "SampleRate"    "150"
# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
    Identifier  "Mouse1"
    Driver      "mouse"
    Option        "Protocol" "Auto"    # Auto detect
    Option        "Device" "/dev/input/mice"
# Mouse-speed setting for PS/2 mouse.
    Option        "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
    Option        "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"
# ChordMiddle is an option for some 3-button Logitech mice
#    Option "ChordMiddle"
EndSection

Section "Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
#    HorizSync    30-64         # multisync
#    HorizSync    31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync    15-25, 30-50  # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
    Identifier   "monitor0"
    HorizSync    31.5 - 31.5
    VertRefresh  56.0 - 75.0
EndSection

Section "Monitor"
    Identifier   "aticonfig-Monitor[0]"
    Option        "VendorName" "ATI Proprietary Driver"
    Option        "ModelName" "Generic Autodetecting Monitor"
    Option        "DPMS" "true"
EndSection

Section "Monitor"
    Identifier   "aticonfig-Monitor[1]"
    Option        "VendorName" "ATI Proprietary Driver"
    Option        "ModelName" "Generic Autodetecting Monitor"
    Option        "DPMS" "true"
EndSection

Section "Device"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.
#    Chipset    "generic"
# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.
#    BusID      "PCI:0:10:0"
#    VideoRam    256
#    Clocks    25.2 28.3
    Identifier  "Standard VGA"
    Driver      "vga"
    VendorName  "Unknown"
    BoardName   "Unknown"
EndSection

Section "Device"

    #VideoRam    262144
    # Insert Clocks lines here if appropriate
    Identifier  "** ATI Radeon (generic)               [radeon]"
    Driver      "radeon"
EndSection

Section "Device"
    Identifier  "aticonfig-Device[0]"
    Driver      "fglrx"
    BusID       "PCI:2:0:0"
EndSection

Section "Device"
    Identifier  "aticonfig-Device[1]"
    Driver      "fglrx"
    BusID       "PCI:2:0:0"
    Screen      1
EndSection

Section "Screen"
    Identifier "Screen 1"
    Device     "** ATI Radeon (generic)               [radeon]"
    Monitor    "monitor0"
    DefaultDepth     24
    SubSection "Display"
        Viewport   0 0
        Depth     8
        Modes    "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     16
        Modes    "1280x1024" "1024x768" "800x600" "640x480"
    EndSubSection
    SubSection "Display"
        Viewport   0 0
        Depth     24
        Modes    "1024x768" "800x600" "640x480"
    EndSubSection
EndSection

Section "Screen"
    Identifier "aticonfig-Screen[0]"
    Device     "aticonfig-Device[0]"
    Monitor    "aticonfig-Monitor[0]"
    DefaultDepth     24
    SubSection "Display"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

Section "Screen"
    Identifier "aticonfig-Screen[1]"
    Device     "aticonfig-Device[1]"
    Monitor    "aticonfig-Monitor[1]"
    DefaultDepth     24
    SubSection "Display"
        Viewport   0 0
        Depth     24
    EndSubSection
EndSection

signor_rossi · 2008-02-20 18:04:52

First of all, wth did you get an ATI card? Don't you read the forums?
Just joking a little...
To your problem; You are lucky that your system doesn't freeze completely like mine does in dual head mode. I have to use BigDesktop mode which probably is better suited to your needs anyway (if you don't need AIGLX) working atm). You can create a working BigDesktop setup with aticonfig, and probably uncomment the dri and glx lines in your Module section. Maybe worth a try. Before I forget, what was the error with OpenOffice exactly?

Bye, signor_Rossi.

Cyrusm · 2008-02-20 18:17:33

The error is, when I use the soffice command (also when I use /opt/openoffice/programs/soffice) nothing opens. and the prompt just sits there blinking. when I try to start it from the menu it shows up in ps aux as follows:

cyrus 20462 0.0 0.0 4508 1436 ? Ss 11:15 0:00 /bin/sh /usr/bin/soffice
cyrus 20482 0.1 1.3 65468 21188 ? Sl 11:15 0:00 /opt/openoffice/program/soffice.bin

and I have to kill the process. once again, no office opening up.
therefore, ultra-lame :\

Cyrusm · 2008-02-28 16:00:44

fdn, I actually solved this problem by changing to a different driver, so the problem is probably a bug in catalyst. try switching to the radeonhd driver.
http://bbs.archlinux.org/viewtopic.php?id=44542
here's the thread I went through for setting it up. hope it's some use to you!

Cheers
Cyrus

Arch Linux

#1 2008-02-20 17:10:24

openoffice won't start due to xorg.conf

#2 2008-02-20 18:04:52

Re: openoffice won't start due to xorg.conf

#3 2008-02-20 18:17:33

Re: openoffice won't start due to xorg.conf

#4 2008-02-28 16:00:44

Re: openoffice won't start due to xorg.conf

Board footer