Can't run fusion-icon

File "/usr/bin/fusion-icon", line 31
print ' * Configuration file (%s) being reset' %config_file
^
SyntaxError: invalid syntax
this is the error i get. nothing on google

thx , worked

Similar Messages

  • Fusion-Icon doesn't show fluxbox?

    I have been using LXDE for a while now, and have decided to mess around with different window managers.  So I installed compiz and fluxbox to mess with them.  When I run fusion-icon I can see both OpenBox and Compiz, but not fluxbox as an option under "Select Window Manager".  Anyone know how to get Fluxbox to show up?

    Hiya!
    Failing that, you can try plugging the phone into the charger, with it ON and still plugged in... remove the battery. leave it out for a minute and then reinsert it.
    1). Please thank those who help you by clicking the beside the 'Reply' button.
    2). If your issue has been solved, please resolve it by marking "Accept as Solution" on the correct post!
    3). Remember to have fun! We are all in this together!
    4). Follow me on

  • Fusion-Icon

    I reinstalled everything recently. When I try to run Fusion-Icon as anything other than root I get this:
    [grod@ficulnean ~]$ fusion-icon
    * Detected Session: unknown
    * Searching for installed applications...
    Traceback (most recent call last):
    File "/usr/bin/fusion-icon", line 57, in <module>
       from FusionIcon.interface import choose_interface
    File "/usr/lib/python2.5/site-packages/FusionIcon/interface.py", line 23, <module>
       import start
    File "/usr/lib/python2.5/site-packages/FusionIcon/start.py", line 36, in <module>
       config.check()
    File "/usr/lib/python2.5/site-packages/FusionIcon/util.py", line 363, in checkos.makedirs (self.config_folder)
    File "/usr/lib/python2.6/os.py", line 150, in makedirs
       makedirs(head, mode)
    File "/usr/lib/python2.6/os.py", line 157, in makedirs
       mkdir (name, mode)
    OSError: [Errno 13] Permission denied: '/root/.config'
    [grod@ficulnean ~]$ _
    Why does it need to write to /root ? How can I change it to write to /home/grod ? I installed as root because Pacman won't let me install as anything else. I tried yaourt -R fusion-icon and then yaourt -S fusion-icon as grod, but that didn't make a difference.
    I'm about ready to give up and just run as root all the time.

    My point to you is that your error message has everything to do with your python-path and your fusion-icon. Notice the python2.5 and python2.6 errors in the error message. The upgrade that borked everything was the upgrade of python2.5 to python2.6.....
    I had a lot of breakages from that upgrade..... most all of it was because the python-path was wrong.
    You need to have the correct python paths in your new "python 2.6".
    I fixed my python-path problems with the fusion-icon by un-installing the "compiz-fusion-gtk" group, then re-installing the whole "compiz-fusion-gtk" group.
    (I use the gtk packages from this page: http://wiki.archlinux.org/index.php/Com … _Community ..... you might be using the kde group or just the regular compiz-fusion group)
    If you open up the "/usr/lib/python2.6/site-packages" directory, you will see the FusionIcon folder is now in it.
    I also had to make sure the "/usr/lib/python2.6/site-packages/gtk-2.0" directory was also added. Do this by re-installing pygtk and all of it's dependencies that I listed in my post above.
    See, all of this is relating to FusionIcon and python being screwed up:
    Traceback (most recent call last):
    File "/usr/bin/fusion-icon", line 57, in <module>
    from FusionIcon.interface import choose_interface
    File "/usr/lib/python2.5/site-packages/FusionIcon/interface.py", line 23, <module>
    import start
    File "/usr/lib/python2.5/site-packages/FusionIcon/start.py", line 36, in <module>
    config.check()
    File "/usr/lib/python2.5/site-packages/FusionIcon/util.py", line 363, in checkos.makedirs (self.config_folder)
    File "/usr/lib/python2.6/os.py", line 150, in makedirs
    makedirs(head, mode)
    File "/usr/lib/python2.6/os.py", line 157, in makedirs
    mkdir (name, mode)
    OSError: [Errno 13] Permission denied: '/root/.config'
    I'm no expert, but this is what I just went through and it was fixed by reinstalling the missing paths in python2.6.... since they were still pointed at python2.5 and hadn't been upgrade to python2.6.
    Last edited by methuselah (2008-11-20 18:49:36)

  • Fusion-icon and xfce

    how can I get fusion-icon to start with xfce? 
    First I tried to edit the xfce config file and make it load fusion-icon instead of xfwn4 but that just make xfce load with a screwed up version of xfwm4.
    When I add it to autostarted applications it says error writing autostart/compiz.de  but when I use the terminal and do su then afce4-autostart-editor I can edit it?  But it still wont work.

    chrisn2323 wrote:how would I fix permissions issue?
    The easiest way to check that this is the problem in Xfce would be through Thunar: open ~/.config and right-click the autostart folder to open the "Properties" window, and see what it says in the "Permissions" tab. The owner should be your usual user, and permissions should be "Read & Write".
    If the owner is something different, you won't be able to change the permissions. I don't think Thunar can change the owner, so open a terminal and, as root,
    chown [your user]:users /home/[your home directory]/.config/autostart
    You should then be able to change the permissions with Thunar if you need to (it's possible they're set to "Read & Write" already, but for the wrong user).
    Last edited by dunc (2009-01-19 19:47:37)

  • Fusion-icon problem

    When i try to run fusion-icon i get this:
    * Using the Qt4 Interface
    Backend     : ini
    Integration : true
    Profile     : default
    Traceback (most recent call last):
      File "/usr/bin/fusion-icon", line 129, in <module>
        choose_interface()
      File "/usr/bin/fusion-icon", line 101, in choose_interface
        import_interface(interface)
      File "/usr/bin/fusion-icon", line 66, in import_interface
        exec('import ' + module)
      File "<string>", line 1, in <module>
      File "/usr/share/fusion-icon/interface_qt4.py", line 6, in <module>
        from libfusionicon import *
      File "/usr/share/fusion-icon/libfusionicon.py", line 229, in <module>
        decoplugin = context.Plugins['decoration']
    KeyError: 'decoration'
    I'm running XGL whith an ATI X300 and Kde.

    I removed archlinuxfr and reinstalled compiz and fusion-icon bu tnow getting the following error instead:
    * Detected Session: gnome
    * Searching for installed applications...
    Backend     : ini
    Integration : true
    Profile     : default
    Initializing decoration options...done
    Traceback (most recent call last):
      File "/usr/bin/fusion-icon", line 57, in <module>
        from FusionIcon.interface import choose_interface
      File "/usr/lib/python2.7/site-packages/FusionIcon/interface.py", line 22, in <module>
        from util import env
      File "/usr/lib/python2.7/site-packages/FusionIcon/util.py", line 421, in <module>
        decorators = CompizDecorators(_installed)
      File "/usr/lib/python2.7/site-packages/FusionIcon/util.py", line 228, in __init__
        self.command = context.Plugins['decoration'].Display['command']
    KeyError: 'command'
    Any ideas?

  • KDE4 question - Built-in effects compared to compiz/fusion icon/emeral

    Hello i am new to the forums and i've been using Arch for a few months now, but i have a couple of questions.
    I was a hardcore KDE user in the 3.X days, but when 4.0 first launched i was confused and shocked, so i decided to give Gnome a try and its pretty darn nice, and i have been using it for awhile now.  I just did a fresh install with KDEmod 4.2.1 to see if things have changed and i'm a bit confused.
    1. What is the relationship between the effects in kde4 and the old-school method still used in Gnome (fusion-icon, emerald, compiz-config settings manager)?  In gnome i managed to get 99% of everthing working with my Nvidia card on this same pc, but KDE4 i am confused about how to set these options from the CCSM.  These options were essential on Gnome to get the effects tear-free and to get video output tear-free.
    2. Can I use the old method on KDE4?  The old method has 20X more effects to choose from.  Any drawbacks to that method?
    I won't hesitate to go back to Gnome if i can't get everything working, but it would be nice to use KDE again, as this release seems to be less buggy.
    Thanks!

    DrTankMC wrote:
    Hello i am new to the forums and i've been using Arch for a few months now, but i have a couple of questions.
    I was a hardcore KDE user in the 3.X days, but when 4.0 first launched i was confused and shocked, so i decided to give Gnome a try and its pretty darn nice, and i have been using it for awhile now.  I just did a fresh install with KDEmod 4.2.1 to see if things have changed and i'm a bit confused.
    1. What is the relationship between the effects in kde4 and the old-school method still used in Gnome (fusion-icon, emerald, compiz-config settings manager)?  In gnome i managed to get 99% of everthing working with my Nvidia card on this same pc, but KDE4 i am confused about how to set these options from the CCSM.  These options were essential on Gnome to get the effects tear-free and to get video output tear-free.
    They are not the same. Although many of the effects are similar, the native effects are provided by kwin and do not require compiz at all. Hence you can't use ccsm to set these.
    2. Can I use the old method on KDE4?  The old method has 20X more effects to choose from.  Any drawbacks to that method?
    Yes you can. In systemsettings under standard applications there is also an option for you to set whether kde should use kwin or another installed window manager (such as compiz) as the standard window manager. You can also use fusion-icon.
    The drawbacks are that the integretation is not as smooth. You won't be able to get the same integrated miniature preview of launchers and open apps in the panel and the pager plasmoid doesn't recognise compiz workspaces. If your taskbar as sorted by desktops, that might also be problematic.
    Last edited by b9anders (2009-03-18 10:55:27)

  • I have a mac osx version 10.6.8 no windows and i am trying to install a program but keep getting can not run in dos mode  ( the disk says on back works on intel mac with parallels or vm fusion) is this program not compatible with my mac?

    i have a mac osx version 10.6.8 no windows installed and i am trying to install a program but keep getting can not run in dos mode  ( the disk says on back works on intel mac with parallels or vm fusion) is this program not compatible with my mac?

    You run Windows in Parallels or Fusion. Then in Windows you install the program.

  • After upgrading to Lion, Preview (5.2.2) appears to have lost the facility to run a slide show by using my mouse to click an icon in the visible menu bar, as I could in the previous version.  Can I retrieve that icon and thus that facility?

    After upgrading to Lion, Preview (5.2.2) appears to have lost the facility to run a slide show by using my mouse to click an icon in the visible menu bar, as I could in the previous version.  Can I retrieve that icon and thus that facility?

    Unfortunately not. Lion has made many adjustments to the previous system. Try opening your pdfs in keynote.

  • Can you run Boot Camp and Fusion at the same time?

    Hi,
    I had boot camp installed on my mac pro and loved it. I decided to get greedy and install Fusion using the boot camp partition. The Fusion install went ok but then Microsoft started to get fussy. Every time I would do something on Fusion it would ask me to "Re-activate Windows" when I logged into boot camp. Maybe if I saw Fusion fully working I wouldn't want to run boot camp any more but I think I want to have the option to run either. Right now I only have 1 gig real memory on my mac pro and Fusion seems a little slow compared to native boot camp. Can I run both boot camp and fusion without having to buy two native copies of Windows XP pro? I don't want a "sensible" answer, I want an answer that takes into account how Microsoft treats this re-activation situation.
    I guess Leopard might make this all obsolete, but until then .....
    ... Flash Gordon

    You need to make sure to install VMware Tools into your virtual machine (while booted into Windows via Fusion). Once you do this you shouldn't have to continually activate Windows when going back and forth from Boot Camp to Fusion. I've seen this discussed over on the VMware Fusion discussion boards, so you may want to look there for more details.
    Also, if Windows starts telling you it's been activated too many times, you can call Microsoft and they'll give you an alternate activation key. The phone number is listed on the Windows error screen. I had to do it and they were very accommodating. I just told them I was running Windows in a virtual machine, and there were almost no questions asked.
    You don't need to buy 2 copies of Windows to run both Boot Camp and VMFusion.

  • How can I run Mac OS 10.6 on VMware fusion 5 on my macbook pro late 2011?

    How can I run Mac OS 10.6 on VMWare fusion 5 on my late 2011 MacBook Pro?

    Someone has 10.6 running in Parallels, not Fusion under 10.7/10.8
    http://forums.macrumors.com/showthread.php?t=1365439

  • [SOLVED] Compiz fusion-icon won't run

    Hello,
    I'm new to Arch Linux and I've just installed it on my laptop. I want to run Compiz on XFCE: I tried the methods on the Arch Wiki (https://wiki.archlinux.org/index.php/Co … icon.22.29) on replacing XFWM with Compiz. The second method doesn't work, only the first one works, but I don't want to use that one.
    I've tried the third method, but when I followed the instructions and I rebooted my computer, I've got no window manager at all: I have to manually load Compiz.
    The only thing that works right now is following the third method and also do the first one at together.
    But I just want to do either the second or the third method. Does anyone know how to solve this problem?
    Thank you in advance.
    (Sorry for bad English).
    Last edited by jonasty123dm (2013-02-27 18:46:56)

    ewaller wrote:It is your system, so do as you will.   I really do not recommend running compiz as root.  Enough said.
    Hi, I didn't mean running Compiz as root: I just edited this file: "/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-session.xml" to make Compiz start for all users. I followed the method without the fusion icon this time (https://wiki.archlinux.org/index.php/Co … icon.22.29) and everything works now.
    Thank you very much for the help.
    (P.S.: I don't know how to mark this thread as SOLVED).
    Last edited by jonasty123dm (2013-02-27 13:06:12)

  • I can see the Safari icon on my iPhone screen, but the program doesn't run. I have checked the settings and it is on and not restricted. Can I delete the application and reinstall it?

    I can see the Safari icon on my iPhone screen, but the program doesn't run. I have checked the settings and it is on and not restricted. It seems that the application has simply stopped running. The little "searching" icon just spins and spins. Can I delete the application and reinstall it?

    You can't delete it. you will need to do a restore.
    Restore: http://support.apple.com/kb/HT1414

  • Fusion-icon loading problem

    Hi everyone.
    Recently I installed compiz fusion and I get this error when I load fusion-icon on the terminal.
    * Setting window manager to Compiz
    ... executing: compiz --replace --sm-disable --ignore-desktop-hints ccp
    compiz (core) - Fatal: No GLXFBConfig for default depth, this isn't going to work.
    compiz (core) - Error: Failed to manage screen: 0
    compiz (core) - Fatal: No manageable screens found on display :0.0
    I really don't know how to solve it. I've tried adding the extra needed options in xorg.conf to make it work but it still does not.
    Here it is if it would be of any help to solve this problem.
    # File generated by xorgconfig.
    # Copyright 2004 The X.Org Foundation
    # Permission is hereby granted, free of charge, to any person obtaining a
    # copy of this software and associated documentation files (the "Software"),
    # to deal in the Software without restriction, including without limitation
    # the rights to use, copy, modify, merge, publish, distribute, sublicense,
    # and/or sell copies of the Software, and to permit persons to whom the
    # Software is furnished to do so, subject to the following conditions:
    # The above copyright notice and this permission notice shall be included in
    # all copies or substantial portions of the Software.
    # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
    # The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
    # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
    # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
    # SOFTWARE.
    # Except as contained in this notice, the name of The X.Org Foundation shall
    # not be used in advertising or otherwise to promote the sale, use or other
    # dealings in this Software without prior written authorization from
    # The X.Org Foundation.
    # Refer to the xorg.conf(5) man page for details about the format of
    # this file.
    # Module section -- this section is used to specify
    # which dynamically loadable modules to load.
    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"
    # Load "drm"
    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" "pc105"
    Option "XkbLayout" "us"
    # Option "XkbVariant" "us"
    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 30-81
    # 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 "My Video Card"
    Driver "radeon"
    Option "XAANoOffscreenPixmaps" "on"
    # unsupported card
    #VideoRam 512000
    # 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 "My Video Card"
    Monitor "My Monitor"
    DefaultDepth 24
    Subsection "Display"
    Depth 8
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Subsection "Display"
    Depth 16
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Subsection "Display"
    Depth 24
    Modes "1280x1024" "1024x768" "800x600" "640x480"
    ViewPort 0 0
    EndSubsection
    Option "AddARGBGLXVisuals" "True"
    Option "DisableGLXRootClipping" "True"
    Option "RenderAccel" "True"
    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"
    Option "AIGLX" "on"
    EndSection
    Section "DRI"
    Group "video"
    Mode 0666
    EndSection
    Section "Extensions"
    Option "Composite" "Enable"
    EndSection
    Thanks in advance!

    Do you have those images in the right path?
    I tried it and it gave the same exception when the image did not exist.
    now that it exists it works well.

  • I can't run compiz

    i followed th e wiki
    i installed all
    but the fusion-icon load nothing
    typing
    compiz
    the windows borders disapear
    if anyone can't guide for at leat know what is wrong
    by the way, i have a Nvidia card fx5200 and only a few hours ago i was running beryl on my PC in a good way
    thanks

    compiz --replace
    load compiz, but no effects is applied
    emerald never loads
    after i make a compiz --replace i run
    emerald --replace
    but never it appears emerald
    the most weird thing is when i run
    ccsm
    no change is possible
    i don't know what is wrong
    in my xorg.conf i have all ok
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/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"
    Load "glx"
    Load "record"
    #Load "dri"
    Load "dbe"
    Load "xtrap"
    Load "extmod"
    Load "type1"
    Load "freetype"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbLayout" "es"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    #DisplaySize 270 200 # mm
    Identifier "Monitor0"
    VendorName "EPI"
    ModelName "4V"
    ### Comment all HorizSync and VertRefresh values to use DDC:
    HorizSync 30.0 - 54.0
    VertRefresh 50.0 - 120.0
    Option "DPMS"
    EndSection
    Section "Device"
    ### Available Driver options are:-
    ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
    ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
    ### [arg]: arg optional
    #Option "SWcursor" # [<bool>]
    #Option "HWcursor" # [<bool>]
    #Option "NoAccel" # [<bool>]
    #Option "ShadowFB" # [<bool>]
    #Option "UseFBDev" # [<bool>]
    #Option "Rotate" # [<str>]
    #Option "VideoKey" # <i>
    #Option "FlatPanel" # [<bool>]
    #Option "FPDither" # [<bool>]
    #Option "CrtcNumber" # <i>
    #Option "FPScale" # [<bool>]
    #Option "FPTweak" # <i>
    Identifier "Card0"
    Driver "nvidia"
    VendorName "nVidia Corporation"
    BoardName "NV34 [GeForce FX 5200]"
    BusID "PCI:1:0:0"
    Option "TripleBuffer" "True"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 1
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 4
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 8
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 15
    Modes "1024x768"
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 16
    Modes "1024x768"
    EndSubSection
    SubSection "Display"
    Viewport 0 0
    Depth 24
    Modes "1024x768"
    EndSubSection
    Option "AddARGBGLXVisuals" "True"
    EndSection
    Section "Extensions"
    Option "Composite" "Enable"
    EndSection
    help me please

  • Can't run JRE 1.2.2 applets once 1.4.1 installed

    I have an applet developed with JDK 1.2.2 (uses 3rd-party jars) which was working perfectly with the 1.2.2 plug-in
    that comes with the JDK.
    The OBJECT tag specifies the dynamic versioning clsid clsid:8AD9C840-044E-11D1-B3E9-00805F499D93 (which is the
    only possibility for 1.2.2?).
    However, when users who have downloaded the 1.4.1 plug-in run the applet (quite apart from the fact that I have had
    to solve a problem where plug-in 1.2.2 accepts PARAMs with initail _ but plug-in 1.4.1 does not!) they are
    getting an ExceptionInInitializerError inside one of the 3rd-party libraries. I have reproduced this
    error on my Windows XP PC (IE 6). The stack trace is as follows :
    (this has been reproduced outside of the browser using JRE 1.4.1 because the 1.4.1 plug-in console won't display,
    even after manually running the Console and setting the Show Console checkbox,
    and the icon doesn't appear on the System menu, presumably all because I have JDK 1.2.2 + plug-in installed)
    java.lang.ExceptionInInitializerError
    at javax.crypto.Mac.getInstance(DashoA6275)
    at com.baltimore.jpkiplus.pkcs12.PFX.fromASN1Object([DashoPro-V1.3-01300
    0])
    at com.baltimore.jpkiplus.pkcs12.PFX.fromBER([DashoPro-V1.3-013000])
    at com.baltimore.jpkiplus.pkcs12.PFX.<init>([DashoPro-V1.3-013000])
    at com.baltimore.jpkiplus.pkidevice.PKCS12Provider.openFile([DashoPro-V1
    .3-013000])
    at com.baltimore.jpkiplus.pkidevice.PKCS12Provider.openFile([DashoPro-V1
    .3-013000])
    at com.baltimore.jpkiplus.pkidevice.PKCS12Device.initInstance([DashoPro-
    V1.3-013000])
    at com.baltimore.jpkiplus.pkidevice.PKIDeviceManager.getPKIDevice([Dasho
    Pro-V1.3-013000])
    at com.baltimore.jpkiplus.vaults.Vault.a([DashoPro-V1.3-013000])
    at com.baltimore.jpkiplus.vaults.Vault.openVault([DashoPro-V1.3-013000])
    at mailsign.signer.signAndSend(signer.java:262)
    at mailsign.AppletSigner.signAndSend(AppletSigner.java:329)
    at mailsign.AppletSigner.action(AppletSigner.java:521)
    at java.awt.Component.handleEvent(Unknown Source)
    at java.awt.Component.postEvent(Unknown Source)
    at java.awt.Component.postEvent(Unknown Source)
    at java.awt.Component.dispatchEventImpl(Unknown Source)
    at java.awt.Component.dispatchEvent(Unknown Source)
    at java.awt.EventQueue.dispatchEvent(Unknown Source)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
    at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
    at java.awt.EventDispatchThread.run(Unknown Source)
    Caused by: java.lang.SecurityException: Cannot set up certs for trusted CAs
    at javax.crypto.SunJCE_b.<clinit>(DashoA6275)
    ... 24 more
    Caused by: java.lang.UnsupportedOperationException
    at java.security.cert.CertificateFactorySpi.engineGenerateCertPath(Unkno
    wn Source)
    at java.security.cert.CertificateFactory.generateCertPath(Unknown Source
    at javax.crypto.SunJCE_d.a(DashoA6275)
    at javax.crypto.SunJCE_d.a(DashoA6275)
    at javax.crypto.SunJCE_b.i(DashoA6275)
    at javax.crypto.SunJCE_b.h(DashoA6275)
    at javax.crypto.SunJCE_v.run(DashoA6275)
    at java.security.AccessController.doPrivileged(Native Method)
    ... 25 more
    In my opinion, this has something to do with the way service providers are handled. The 3rd party jar requires
    a Security.insertProviderAt () call. My suspicion is that there is some kind of conflict with the JCE stuff
    that comes bundled with JRE 1.4.1 to handle RSA signed applets. I found a similar conflict with the 1.2.2 JRE
    when I tried to jarsign the 3rd-party libraries - I was getting, at runtime, either some kind of infinite loop hanging or
    a stack overflow due to recursive function calls.
    The fact that I can run the applet as a main and that I get the exact same error running the app from the DOS
    prompt would indicate that this is a JRE 1.4.1 problem (surely the JREs are supposed to be downwardly-
    compatible??!!! - i.e. the JRE 1.4 should run apps compiled with JDK 1.2.2 without any problem). Yes, I have
    run the app as a main with JRE 1.2.2 and all works fine.
    However, I could get around this if I could force the 1.2.2 plug-in to run instead of the 1.4.1 plug-in (quite
    how the users are going to be able to get the 1.2.2 plug-in if they have plug-in 1.4.1 installed
    without being Java experts is a problem I will leave
    till later when I try to figure out how to make my applet an RSA signed applet (which if the documentation is
    correct are only available from 1.3 onwards, hence solving this 1.4.1 problem would be VERY nice)).
    But the problem is that once the 1.4.1 plug-in is installed, it always takes precedence over lower versions.
    It's not obvious from the documentation whether older plug-in versions get executed when static versioning
    is used for the clsid in the OBJECT tag. I can't be bothered to download a 1.3 plug-in and try.
    However, unless I am mistaken, there is not a static versioning clsid for plug-in 1.2.2 ?????
    In summary, once users download a plug-in version greater than 1.2.2 (presumably by running another applet from some
    other site that requires eg 1.4.1 - I guess Sun's aim is to make the Plug-In as prevalent as possible, hence
    this is not a far-fetched scenario), it is no longer possible for my applet to be run by a 1.2.2 JRE !!!!!!!
    Because the 1.4.1 JRE is not downwardly-compatible, it can't run my 1.2.2-developed applet and my deployed
    application is broke.
    Unless I am missing something somewhere (which is possible because I am getting fed up of solving problem after
    problem with the Plug-In - eg the mess of setting the right codebase to get different plug-ins to be downloaded
    automatically - the HTML converter doesn't always set up the codebase correctly), this seems like a nightmare
    for applet developers - from one day to the next your applications will break because of Sun's plug-in upgrading.
    Please tell me there is a way to force the 1.2.2 JRE/plug-in to execute instead of 1.4.1 and that there is a
    way for the 1.2.2 plug-in to be downloaded automatically by users even when they have 1.4.1 already installed.

    Are you using signtool? I had a problem where applets stopped working when I went from JRE 1.3.1_01a to 1.3.1_07. I updated the signtool from 1.1 to 1.3 and now my applets run.
    Mark

Maybe you are looking for