Arch Linux

ArchNewbie

Member

Registered: 2008-06-18

Posts: 7

compiz-fusion fails

Hi dears!
I've just successfully installed compiz-fusion with the following command:

pacman -S compiz-fusion

I wasn't given any errors.

But unfortunately, i can't launch it. When I write fusion-icon, i am given this:

* Detected Session: kde
* Searching for installed applications...
* No GLX_EXT_texture_from_pixmap with direct rendering context
... nor with indirect rendering, this isn't going to work!
* Using the GTK Interface
No protocol specified
/usr/lib/python2.5/site-packages/gtk-2.0/gtk/__init__.py:72: GtkWarning: could not open display
  warnings.warn(str(e), _gtk.Warning)
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: Warning: invalid (NULL) pointer instance
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: Warning: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: Screen for GtkWindow not set; you must always set
a screen for a GtkWindow before using the window
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: gdk_screen_get_default_colormap: assertion `GDK_IS_SCREEN (screen)' failed
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: gdk_colormap_get_visual: assertion `GDK_IS_COLORMAP (colormap)' failed
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: gdk_screen_get_root_window: assertion `GDK_IS_SCREEN (screen)' failed
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: gdk_window_new: assertion `GDK_IS_WINDOW (parent)' failed
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: gdk_screen_get_display: assertion `GDK_IS_SCREEN (screen)' failed
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: gdk_display_sync: assertion `GDK_IS_DISPLAY (display)' failed
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: gdk_drawable_get_display: assertion `GDK_IS_DRAWABLE (drawable)' failed
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: gdk_x11_get_xatom_by_name_for_display: assertion `GDK_IS_DISPLAY (display)' failed
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: gdkdrawable-x11.c:878 drawable is not a pixmap or window
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
/usr/lib/python2.5/site-packages/FusionIcon/interface_gtk/main.py:207: GtkWarning: gdk_x11_display_get_xdisplay: assertion `GDK_IS_DISPLAY (display)' failed
  icon = gtk.status_icon_new_from_icon_name('fusion-icon')
Segmentation fault

Any advices? I guess there are some problems with NVidia drivers or X configuration

Thanks in advance for your help

pheon

Member

From: Berlin, Germany

Registered: 2008-05-14

Posts: 91

Re: compiz-fusion fails

Hello,
as far as I can see, you don't have Direct Rendering activated.

* No GLX_EXT_texture_from_pixmap with direct rendering context
... nor with indirect rendering, this isn't going to work!

Can you please give us the result of the following command?

glxinfo | grep Direct

If this command states Direct Rendering: No we first have to set up 3D-Acceleration.

In addition, please provide us your /etc/X11/xorg.conf

Best regards

---

watching someone else use your computer is like watching a drunk orangutan solve a rubix cube

ArchNewbie

Member

Registered: 2008-06-18

Posts: 7

Re: compiz-fusion fails

glxinfo | grep Direct:

Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".

em... xorg.conf file is quite big but ok, here it is:

Section "Module"

# This loads the DBE extension module.

    Load        "dbe"      # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
#    Load        "type1"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
#    Load       "glx"
# This loads the DRI module
#    Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

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

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier    "Keyboard1"
    Driver    "kbd"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    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"

    Option "XkbRules"    "xorg"
    Option "XkbModel"    "pc101"
    Option "XkbLayout"    "lt,us"
    Option "XkbOptions"    "grp:alt_shift_toggle,keypad:legacy,kpdl:dot"

EndSection

# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier    "Mouse1"
    Driver    "mouse"
    Option "Protocol"    "Auto"    # Auto detect
    Option "Device"      "/dev/input/mice"

# Mouse-speed setting for PS/2 mouse.

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

    Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection

# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "My 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   31.5 - 57.0

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

    VertRefresh 50-70

EndSection

# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier    "Standard VGA"
    VendorName    "Unknown"
    BoardName    "Unknown"

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

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

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "* Generic VESA compatible"
    Driver      "vesa"
    #VideoRam    512
    # Insert Clocks lines here if appropriate
EndSection

# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "* Generic VESA compatible"
    Monitor     "My Monitor"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "800x600" "640x480"
        ViewPort    0 0
        Virtual     800 600
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "640x400"
        ViewPort    0 0
        Virtual     0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1024x768"
        ViewPort    0 0
        Virtual     0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

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

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

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection

INCSlayer

Member

From: Sweden

Registered: 2007-09-06

Posts: 296

Website

Re: compiz-fusion fails

first of all you are running vesa as a graphics driver which means you cant have flashy graphics what graphics card do you have?

---

dovie andi se tovya sagain

shazeal

Member

From: New Zealand

Registered: 2007-06-05

Posts: 341

Re: compiz-fusion fails

http://wiki.archlinux.org/index.php/Composite

ArchNewbie

Member

Registered: 2008-06-18

Posts: 7

Re: compiz-fusion fails

first of all you are running vesa as a graphics driver which means you cant have flashy graphics what graphics card do you have?

lspci | grep VGA   command gives me this text:

01:00.0 VGA compatible controller: nVidia Corporation NV34 [GeForce FX 5200] (rev a1)

INCSlayer

Member

From: Sweden

Registered: 2007-09-06

Posts: 296

Website

Re: compiz-fusion fails

then you have to install the nvidia drivers on your computer:
pacman -S nvidia nvidia-utils should do it i belive
then you might want to look at this page:
http://wiki.archlinux.org/index.php/NVIDIA

---

dovie andi se tovya sagain

ArchNewbie

Member

Registered: 2008-06-18

Posts: 7

Re: compiz-fusion fails

I've just installed NVIDIA drivers using command you gave me but fusion-icon still doesn't work. Maybe there are more steps which are haven't done by me?

Last edited by ArchNewbie (2008-06-19 10:13:00)

pheon

Member

From: Berlin, Germany

Registered: 2008-05-14

Posts: 91

Re: compiz-fusion fails

Can you please tell us, what exactly you have done, what errors occur when you run fusion-icon and what changes you've made in your xorg.conf?

Last edited by pheon (2008-06-19 10:17:49)

---

watching someone else use your computer is like watching a drunk orangutan solve a rubix cube

INCSlayer

Member

From: Sweden

Registered: 2007-09-06

Posts: 296

Website

Re: compiz-fusion fails

did you read:
http://wiki.archlinux.org/index.php/NVIDIA
because if you do and follow the instructions then everything should work fine
im not going to hold your hand every step of the way
pheon im fairly certain that the same error that happened last time for him happened this time because he is running xorg with vesa driver and just installing nvidia drivers will not magically change everything

Last edited by INCSlayer (2008-06-19 10:20:44)

---

dovie andi se tovya sagain

ArchNewbie

Member

Registered: 2008-06-18

Posts: 7

Re: compiz-fusion fails

Well, sorry guys but i'm afraid, i haven't read it yet Just wrote pacman -S nvidia nvidia-utils
I thought that it wasn't necessary
So I will follow all instructions given in the link this evening and write was it successful or not.

pheon

Member

From: Berlin, Germany

Registered: 2008-05-14

Posts: 91

Re: compiz-fusion fails

It seems to me that you need some kind of list, what to do:

1.) install nvidia-drivers
2.) configure your X-Server to use those new drivers
3.) get 3D-Acceleration to work
Instructions how to do this: http://wiki.archlinux.org/index.php/NVIDIA

4.) Enable Composite in your X-Config
Instructions how to do this: http://wiki.archlinux.org/index.php/Composite

5.) install and configure compiz-fusion
Instructions how to do this: http://wiki.archlinux.org/index.php/Compiz

It is essential that you read the entire articles (besides the ati-related stuff )
If you need help with one of the steps, feel free to ask, but include as many (relevant) information in your post, as you can.

Best regards

---

watching someone else use your computer is like watching a drunk orangutan solve a rubix cube

ArchNewbie

Member

Registered: 2008-06-18

Posts: 7

Re: compiz-fusion fails

An enormous thanks to  pheon for a list, it will be useful for me