Catalyst and KDE Compositing Problem

Hi,
I'm new to Arch and just installed it using the chakra-livecd.
I've had some issues with fglrx, but after installing the newest version from kensais repo + the patched xorg-server from AUR it works.
Dmesg gets spammed with this error:
[fglrx:firegl_find_any_map] *ERROR* Invalid map handle!<3>[fglrx:drm_vm_close] *ERROR* map not found -> inconsistent kernel data!!! vma_start:0x7fa230d2b000,handle:0xe7532000
I've stopped getting them logged with the help of this post: http://bbs.archlinux.org/viewtopic.php? … 25#p571625
Is there any way to get those errors out of dmesg, or to completly fix them?
As for my KDE problem:
I only have the thumbnails in Cover Switch.
Present Windows, Taskbar, and the Desktop Grid don't show any thumbnails (black/grey boxes).
thanks for your time

Just checked the output of "kwin --replace"
Another Error-Spam \o/
kwin(2779) KWin::checkGLError: GL error ( PostPaint ): 0x "500"
/edit: Hooray, renaming ~/.kde4/share/config/kwinrc and restartin kwin fixed my KDE problem.
/edit2: Just downgraded to 2.6.28, modified catalyst from AUR (dependencies to 2.6.28 and removing .29 Patch), and my dmesg is clear \o/
So far I had to modify the PKGBUILD for my X-Fi (PCIe Versions need patching, i guess i should drop a comment at the ctxfi package) and catalyst. I expected this to be quite hard for me, but using yaourt and reading the PKGBUILDS was enough.
Last edited by stray (2009-06-22 07:54:49)

Similar Messages

  • Gaming and window compositing problems [SOLVED]

    Greetings,
    I suffer from frame rate problems when compositing is enabled while playing games.
    On this computer, they worked side by side without too many problems when I used KDE (the desktop effects were not automatically disabled by KDE either).
    Now I use Xfce and have enjoyed it so far except for the problem mentioned earlier.
    I have a NVIDIA graphics card and tried some ideas out at this article but with no luck so far.
    I remember changing KDE's texture filter to "nearest" and I think that helped but I am not completely sure.
    Are there some settings in Xfce or NVIDIA I should change? Or should I do something else all together?
    Last edited by feet4337 (2011-02-04 00:33:02)

    I have an idea that I will be researching around for more information on.
    In KDE, I remember that Opengl was used in a setting instead of NVIDIA's X Rendering (or was it direct rendering...).
    With my minor knowledge of graphics cards and rendering, I came up with this:
    Opengl's memory management was used in KDE, so it explains how my computer was able to handle both compositing and graphic intensive games. And that X Rendering is not good  at(or has any ability)  managing memory. So I must find a way for NVIDIA to only use Opengl.
    Please correct me if I am making the wrong conclusion!
    EDIT: Looking at the NVIDIA server settings again, it looks like it already uses Opengl.
    Reading more from many forums, it looks like Xfce's compositing uses EXA for rendering confusing the situation just a little more.
    Last edited by feet4337 (2011-02-03 23:45:18)

  • Troubles after installing Catalyst and re-installing KDE

    Hi everybody, when I was installing arch I was following the wiki and installed the open source driver xf86-video-ati and KDE (the last version in the repository). After that everything worked fine, until I heard about some nice games that run on Linux. This is the place where the troubles began. I read that I should switch video drivers with the catalyst ones for better 3D performance. After a couple painful days I had the Catalyst working... or had I. In this painful period I uninstalled the xf86-video-ati driver, installed the Catalyst (several times), after that I had many crashes from the KDE so I decided to re-install it too :] So the result from all this is: I can play the games that I wanted, but many of the nice KDE effects disappear (ex. the window switching - whatever type of window switch I select I get the basic one) plus the synaptics drivers don't work. I also found some errors in the /var/log/kdm.log file:
    X.Org X Server 1.11.4
    Release Date: 2012-01-27
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.2.2-1-ARCH x86_64
    Current Operating System: Linux sphex 3.3.6-1-ARCH #1 SMP PREEMPT Sun May 13 10:52:32 CEST 2012 x86_64
    Kernel command line: root=/dev/sda2 ro nomodeset
    Build Date: 29 January 2012 03:38:00PM
    Current version of pixman: 0.24.4
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 31 21:56:50 2012
    (==) Using config file: "/etc/X11/xorg.conf"
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    (EE) module ABI major version (16) doesn't match the server's version (13)
    (EE) Failed to load module "synaptics" (module requirement mismatch, 0)
    (EE) No input driver matching `synaptics'
    (EE) fglrx(0): Can not enable interrupt sourceID 0xff000066!
    klauncher(586) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(580)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(580)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (EE) fglrx(0): Can not enable interrupt sourceID 0xff000066!
    (EE) fglrx(0): Can not enable interrupt sourceID 0xff000066!
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    (EE) fglrx(0): Can not enable interrupt sourceID 0xff000066!
    (EE) fglrx(0): Can not enable interrupt sourceID 0xff000066!
    (EE) fglrx(0): Can not enable interrupt sourceID 0xff000066!
    Same errors are seen in /var/log/Xorg.0.log. What causes them? Could this be the root problem for all others?
    Here is also my /etc/X11/xorg.conf
    Section "ServerLayout"
    Identifier "aticonfig Layout"
    Screen 0 "aticonfig-Screen[0]-0" 0 0
    EndSection
    Section "Module"
    EndSection
    Section "Monitor"
    Identifier "aticonfig-Monitor[0]-0"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    BusID "PCI:1:0:0"
    EndSection
    Section "Screen"
    Identifier "aticonfig-Screen[0]-0"
    Device "aticonfig-Device[0]-0"
    Monitor "aticonfig-Monitor[0]-0"
    DefaultDepth 24
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    EDIT:
    Here is some more info on my graphics card:
    01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] (prog-if 00 [VGA controller])
    Subsystem: ASUSTeK Computer Inc. Device 19e2
    Flags: bus master, fast devsel, latency 0, IRQ 40
    Memory at c0000000 (32-bit, prefetchable) [size=512M]
    I/O ports at d800 [size=256]
    Memory at fdef0000 (32-bit, non-prefetchable) [size=64K]
    Expansion ROM at fdec0000 [disabled] [size=128K]
    Capabilities: <access denied>
    Kernel driver in use: fglrx_pci
    Any help would be highly appreciated.
    Last edited by maistora (2012-05-31 21:34:25)

    (EE) module ABI major version (16) doesn't match the server's version (13)
    There's your problem. Are you using the xorg111 repo? If not, enable that and then pacman -Syuu.
    As a warning, xorg-server 1.11 is now broken with the new udev package (at least until someone rebuilds it and updates the repo). You'll need to rebuild it manually to avoid this.
    Last edited by Pres (2012-06-01 21:54:17)

  • Catalyst and opengl problems

    So I've been using catalyst for a while on my HD5750 and overall enjoyed it but got fed up with how it wouldn't keep up with xserver and the kernel, so in April I decided to go for the open source drivers.  Those drivers performed fine for what I wanted but they lacked features I use, so yesterday I decided to go back to the catalyst drivers.
    I'm using KDE 4.8 and the catalyst-test package from AUR.  The problem is anything opengl related will show 1 frame and completely freeze, whether that be kwin, glxgears, a web browser, or a game.
    amdcccle and glxinfo seem to give accurate info stating that everything is working (such as direct rendering, opengl 4.2, and so on).
    I have noticed that if I disable vsync and tear-free, opengl programs will still only draw 1 frame, but they won't freeze.  So for example I can run GLX gears and it might show a frame or 2 but I'm still getting reports of framerate in the terminal.  If I disable "Catalyst AI" as well, then the programs will ONLY update their display if something else (aside from the mouse) is visually changing the screen.  So if I drag a window around, glxgears will have a smooth consistent framerate but if I stop dragging it, the gears stop moving (but I'm still getting outputs).
    Any idea why this is happening and what I can do about it?
    Last edited by schmidtbag (2012-07-02 19:56:46)

    So I've narrowed down the problem to being either fglrx's fault or KDE 4.8.  I had both update at the same time so I can't really tell.  The reasoning why I'm blaming fglrx should be fairly obvious.
    I think KDE might be the problem because if I create a brand new user account and log into it, it works just fine with anything opengl related.  However, if I reboot there seems to be something that gets triggered and screws up opengl again.  I can't figure out what this is - I don't change a single option in this other user account.  The weird thing is it isn't easily reproducible, so for example I might clean the slate of that new user account and reboot several times with success each time, but then one time it doesn't work anymore and when that happens, opengl never works again.
    I tried deleting nearly everything KDE related on my account and I was able to get opengl working for 1 session.  After re-applying all my settings (which, BTW, were all working just fine and were active in front of me) and rebooting, opengl failed again.  I don't feel like deleting my account every time I log in, so unless someone can help me out or the next catalyst and/or kde release arrives, I'm going back to the open source drivers.

  • Problems whit catalyst and 3d application

    Hi to all!
    I'm new of the forum and I don't know if this is the right place to show my issue
    Howewer I have a lot of problems with my ATI HD3450 video card...
    before I used the xf86-video-ati, but wiht the 6.14 version it showed me a 'segmentation fault' and X refused to start...
    So I decided to try the catalyst...I have added the catalyst repo as suggested by the wiki, I have installed catalyst, catalyst-utils and lib32-catalyst-utils and X and KDE came back!
    But i have a lot of problem with 3d application...
    my glxinfo | grep rendering says that:
    direct rendering: Yes
    and if I start a game such as 'Foobillard' it works properly...
    but if I start a full-screen game as OpenArena or an emulated game as WoW i've got only a  black screen and I have to restart KDM...
    I premise that the games were ok with the xf86-video-ati and I have generated the xorg.conf with aticonfig --initial...
    can someone help me?

    You need to look at the Exe4j site, this is a Java forum. If you would like to know how to do executable Jars, then this is an appropriate site and supported by Java natively.

  • Problem upgrading due to catalyst and libgl

    Hi all,
    I am trying to do an upgrade and am having issues ... I get the following when trying the upgrade ..
    :: Starting full system upgrade...
    warning: ethtool: local (6-2) is newer than extra (2.6.36-1)
    :: Replace go-openoffice with extra/libreoffice? [Y/n] y
    :: Replace libusb1 with core/libusb? [Y/n] y
    :: Replace pycairo with extra/python2-cairo? [Y/n] y
    :: Replace pyqt with extra/python2-qt? [Y/n] y
    :: Replace sip with extra/python2-sip? [Y/n] y
    resolving dependencies...
    looking for inter-conflicts...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: catalyst-test: requires kernel26<2.6.37
    [root@Laptop2 bmentink]# pacman -R catalyst-test
    checking dependencies...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: catalyst-2.6.35-ARCH: requires catalyst-test
    :: compiz-core: requires libgl
    :: gnome-screensaver: requires libgl
    :: go-openoffice: requires libgl
    :: google-talkplugin: requires libgl
    :: libva: requires libgl
    :: mesa: requires libgl
    :: miniracer: requires libgl
    :: mplayer-vaapi: requires libgl
    :: qt: requires libgl
    :: tuxkart: requires libgl
    :: wxgtk: requires libgl
    :: xbmc: requires libgl
    :: xine-lib: requires libgl
    :: xorg-utils: requires libgl
    :: xvba-video: requires catalyst-utils
    Any suggestions on how to handle this, do I have to force the un-install .... seems like not a good way to proceed ..
    As this is a laptop I use evey day, I don't want to break it .. :-0
    Cheers,
    Bernie

    catalyst-test is kinda old now, it's only updated when AMD is releasing ubuntu beta driver with fresh xserver support ;P
    please:
    # pacman -Rd catalyst-test
    and install newest catalyst and catalyst-utils packages
    And yes, wiki is a good place to find extra infos and candies
    Last edited by Vi0L0 (2011-02-17 12:42:30)

  • Catalyst+awesome35 panel refresh problem

    Hello,
    met anyone problems with this combination and panel update problem?
    I tried catalyst stable and beta from arch wiki, and awesome 3.5.1 and 3.5.2 ... And I have problem that, when I switch to any nonempty tag, then my upper panel(tasklist,taglist) will not be refreshed(re-render,update ....). There are still old applications visible. I must take some action, for example focus window, or when CPU widget refresh, then it will be fine and right tag/task list appears.
    I tried:
    catalyst 13.4   13.11
    awesome 3.5.1   3.5.2
    X 1.13   1.14
    In all combinations I have this problem.
    I tried
    awesome 3.4, with this version all is OK, but I dont want learn deprecated configuration.
    I tried
    open source vga drivers, with this driver all is OK. But it consumes much more power.
    Thanks for help.
    Last edited by kubco2 (2013-10-14 09:19:51)

    Not sure if it could help but I had a problem in awesome 3.5.1 (and wasn't present in 3.4). And I think the problem you describe is the same I had.
    In /etc/X11/xorg.conf put this
    Section "Extensions"
    Option "Composite" "Disable"
    EndSection

  • Weird line on the right edge of the screen with fglrx and KDE Plasma

    Hey there,
    I am using an AMD Radeon R9 280X with the fglrx driver for my 2-monitor setup: One 1366x768 monitor on the left side, one 1920x1080 monitor on the right side. My current DE is Plasma with KDE 5, but the bug also existed (though not as bad) with Cinnamon.
    Now to the problem: On the right edge of the screen is the 2-pixel-width vertical line currently in grey, which even exist in full-screen applications.
    On Cinnamon the situation is a little bit different: Here it only appears sometimes, but then it flashes frequently, though full-screen applications cover it.
    Interestingly I can hover my mouse pointer over it.
    Here are two screenshots: One with the whole line and one showing the above described.
    I configured my screens with amdccle and/or the KDE 5 display manager. Here's the generated xorg.conf:
    Section "ServerLayout"
    Identifier "amdcccle Layout"
    EndSection
    Section "Files"
    FontPath "/usr/share/fonts/adobe-source-sans-pro/"
    FontPath "/usr/share/fonts/cyrillic/"
    EndSection
    Section "Module"
    EndSection
    Section "ServerFlags"
    Option "Xinerama" "off"
    Option "RandR" "on"
    EndSection
    Section "Monitor"
    Identifier "DFP6"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    Option "Primary" "true"
    EndSection
    Section "Monitor"
    Identifier "DFP7"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    Option "LeftOf" "DFP6"
    EndSection
    Section "Monitor"
    Identifier "0-DFP6"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    Option "PreferredMode" "1920x1080"
    Option "TargetRefresh" "60"
    Option "Position" "1366 0"
    Option "Rotate" "normal"
    Option "Disable" "false"
    Option "Primary" "true"
    EndSection
    Section "Monitor"
    Identifier "0-DFP7"
    Option "VendorName" "ATI Proprietary Driver"
    Option "ModelName" "Generic Autodetecting Monitor"
    Option "DPMS" "true"
    Option "PreferredMode" "1366x768"
    Option "TargetRefresh" "60"
    Option "Position" "0 312"
    Option "Rotate" "normal"
    Option "Disable" "false"
    EndSection
    Section "Device"
    Identifier "aticonfig-Device[0]-0"
    Driver "fglrx"
    Option "Monitor-DFP6" "0-DFP6"
    Option "Monitor-DFP7" "0-DFP7"
    BusID "PCI:1:0:0"
    EndSection
    Thanks for any help in advance
    Last edited by Quanttek (2015-05-03 12:57:23)

    ewaller wrote:Now that it interesting    This only happens on the big screen?
    Yes, this only happens on the big screen
    ewaller wrote:Not that it matters (as the full screen display overwrites it), but what type of interface is it?  HDMI, VGA?
    DVI
    ewaller wrote:What does the display report as its current resolution in the on screen menu?
    It reports 1920x1080 as it's current resolution
    As a test I changed the resolution to 1400x1050 in the KDE menu, but the monitor reports it as 1680x1050. Though the bug still persists.
    ewaller wrote:What effects to you use in KDE?  Although this is mitigated by your having had the problem with Cinnamon
    I use the standard configuration of effects in KDE. But the bug persists even when I turn off compositing.
    There is a small difference in the bug between Cinnamon and KDE: First off the line has a smaller width in Cinnamon and full-screen applications covered it.
    Also it isn't an offset per se off the whole X screen, but instead only of the KDE/Cinnamon "workspace".  E.g. windows snap with the line, but behind the flickering you can still see the current window, e.g. when moved to the right.
    (Sorry for not answering for so long)
    EDIT: Also the flickering gets more extreme the smaller the reosultion was I changed to inbetween http://i.imgur.com/WQ4fkmf.jpg
    Last edited by Quanttek (2015-05-02 18:21:23)

  • Gnome and KDE 4.1 without mixing?

    I'm running Gnome and love it, but wanted to give KDE 4.1 a chance so I installed it too. When logging in (GDM) I choose whether I want to run Gnome or KDE 4.1,  but when I boot KDE the kde menus are full Gnome stuff, and when I boot Gnome, the menus are full of KDE stuff. It's a mix I don't like. Either I run Gnome or KDE.
    Is there a way to stop the Gnome menus scanning the KDE apps and the KDE menus to stop scanning the Gnome apps?
    Besides that, when I'm in Gnome and open a nautilus bookmark from the "Places" menu, Konquerer starts up happily and makes me think, "What a mess. Is this the way it's supposed to work?"
    If I want to run Gnome only and KDE only, do I need to make a dual boot with two separate Arch installations?
    Last edited by thunderogg (2008-08-01 08:54:02)

    The menu "problem" is due to both desktops using the standard menu item location (Freedesktop.org, I believe defines this).  If you want completely separate, you don't have to dual boot with two separate Arch installs, just create a new user and make a shared data location that your KDE and Gnome user can access.  For example:
    /home/thunderogg could be thunderogg, your Gnome user
    /home/kthunderogg could be kthunderogg, your KDE user
    Create a new /home/shared folder with permissions for both users and save your documents there.  That's the only way that I know of to have both installed and not have a menu mess.

  • Wine and KDE shortcuts

    Using the Window-Specific workarounds I'm able to disable KDE global shortcuts.  For example, in Diablo 2, ALT-F2 does not bring up the run dialog.  GREAT!
    My problem is that there are occasions that I want my full-screen wine application to loose focus or minimize; for example to make a Skype call.  When someone calls me the Skype dialog and KDE taskbar pop to the front allowing me to minimize my wine application.  However, I have no way of making a call without exiting the application.
    I'm kind of at a loss here.  I don't want to disable the KDE global shortcuts but I'd like some way of minimizing the full-screen wine application.  Does anyone have a creative suggestion?

    simongmzlj wrote:You could start wine games in another xserver...
    Very cool idea!  Google found me this: http://ubuntuforums.org/showthread.php? … b&t=634067
    This is way simpler than I thought it'd be.  Thanks.

  • Gkrellm and KDE

    I have recently been having problems with Gkrellm and KDE.  I have gkrellm set to be dockable.  However, when I move gkrellm to the right of the screen and it docks there, the KDE panel shrinks in width a little bit, and shifts to the right.  Any ideas why this is happening?

    When you open up Konsole (or whatever terminal program you are using) it logs you in automatically for the terminal session. So you are logged in to KDE and also Konsole. As a test, open up more Konsoles and see how many users you have.
    Last edited by michy99 (2010-03-20 01:47:23)

  • [SOLVED] xserver 1.5 and KDE 4 keymaps - strange behavior

    I apologize if this has already been addressed, but I have read every thread about this I can find, and the wiki page, and I can't find a solution.
    I use a standard US keyboard (it's a laptop), but with the Dvorak keymap.  Most things work fine, except for any Ctrl-Alt combinations.  For example, ctrl-alt-left is detected as D.   ctrl-alt-right is C,  ctrl-alt-up is A, and ctrl-alt-down is B.  These are my shortcuts for switching desktops, so I use them constantly.  The Windows key works perfectly, as do ctrl-shift sequences.
    There's no problem in the VTs, and in xev, all the keys are detected normally.  I've also discovered that I can temporarily fix the problem by going into system settings, unsetting a shortcut, than resetting it, but this only lasts for that one session.  The next time I start KDE, the problem returns.   
    I have removed my input devices from xorg.conf after upgrading to xserver 1.5, and in KDE system settings I've set it to Evdev-managed keyboard, with the us map and dvorak variant.  My /etc/hal/fdi/policy/10-keymap.fdi is as follows:
    <?xml version="1.0" encoding="ISO-8859-1"?> <!-- -*- SGML -*- -->
    <deviceinfo version="0.2">
    <device>
    <match key="info.capabilities" contains="input.keymap">
    <append key="info.callouts.add" type="strlist">hal-setup-keymap</append>
    </match>
    <match key="info.capabilities" contains="input.keys">
    <merge key="input.xkb.rules" type="string">base</merge>
    <!-- If we're using Linux, we use evdev by default (falling back to
    keyboard otherwise). -->
    <merge key="input.xkb.model" type="string">keyboard</merge>
    <match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
    string="Linux">
    <merge key="input.xkb.model" type="string">evdev</merge>
    </match>
    <merge key="input.xkb.layout" type="string">dvorak</merge>
    <!-- <merge key="input.xkb.model" type="string">pc105</merge> -->
    <!-- <merge key="input.xkb.options" type="string">altwin:super_win</merge> -->
    <!-- <merge key="input.xkb.variant" type="string">dvorak</merge> -->
    </match>
    </device>
    </deviceinfo>
    The 3 lines that I've commented out at the end have been on and off at various times - makes no difference.  I've also noticed that in Xorg.0.log, there are 4 keyboards detected and enabled by HAL, as you can see here:
    (II) config/hal: Adding input device Video Bus
    (II) LoadModule: "evdev"
    (II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
    (II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.5.2, module version = 2.0.7
    Module class: X.Org XInput Driver
    ABI class: X.Org XInput driver, version 2.1
    (**) Video Bus: always reports core events
    (**) Video Bus: Device: "/dev/input/event7"
    (II) Video Bus: Found keys
    (II) Video Bus: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
    (**) Option "xkb_rules" "base"
    (**) Video Bus: xkb_rules: "base"
    (**) Option "xkb_model" "evdev"
    (**) Video Bus: xkb_model: "evdev"
    (**) Option "xkb_layout" "dvorak"
    (**) Video Bus: xkb_layout: "dvorak"
    (II) config/hal: Adding input device Video Bus
    (**) Video Bus: always reports core events
    (**) Video Bus: Device: "/dev/input/event6"
    (II) Video Bus: Found keys
    (II) Video Bus: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
    (**) Option "xkb_rules" "base"
    (**) Video Bus: xkb_rules: "base"
    (**) Option "xkb_model" "evdev"
    (**) Video Bus: xkb_model: "evdev"
    (**) Option "xkb_layout" "dvorak"
    (**) Video Bus: xkb_layout: "dvorak"
    (II) config/hal: Adding input device Video Bus
    (**) Video Bus: always reports core events
    (**) Video Bus: Device: "/dev/input/event5"
    (II) Video Bus: Found keys
    (II) Video Bus: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD)
    (**) Option "xkb_rules" "base"
    (**) Video Bus: xkb_rules: "base"
    (**) Option "xkb_model" "evdev"
    (**) Video Bus: xkb_model: "evdev"
    (**) Option "xkb_layout" "dvorak"
    (**) Video Bus: xkb_layout: "dvorak"
    (II) config/hal: Adding input device AT Translated Set 2 keyboard
    (**) AT Translated Set 2 keyboard: always reports core events
    (**) AT Translated Set 2 keyboard: Device: "/dev/input/event1"
    (II) AT Translated Set 2 keyboard: Found keys
    (II) AT Translated Set 2 keyboard: Configuring as keyboard
    (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
    (**) Option "xkb_rules" "base"
    (**) AT Translated Set 2 keyboard: xkb_rules: "base"
    (**) Option "xkb_model" "evdev"
    (**) AT Translated Set 2 keyboard: xkb_model: "evdev"
    (**) Option "xkb_layout" "dvorak"
    (**) AT Translated Set 2 keyboard: xkb_layout: "dvorak"
    Any ideas are welcome...I'm totally stumped!!
    Last edited by noahsark1126 (2008-12-03 05:32:59)

    cameel wrote:
    Executing   
    setxkbmap -model evdev
    brings things back to normality.
    I don't know, however, whether it is a bug in KDE (I am using KDEmod 3.5.10) or in xkeyboard-config package which provides setxkbmap and its config files - in particular /usr/share/X11/xkb/symbols/inet which contains definitions for keyboard models.
    I don't think this is a bug in KDE, as this fixed a problem I was having with xmodmap on Openbox.
    If I used xmodmap to remap my Caps Lock key to Ctrl in my openbox startup scripts, odd things happen to my keymap (Super key stops working, left arrow key stops repeating, etc).  Running setxkbmap before xmodmap seems to fix everything.
    Thanks!
    Last edited by tom5760 (2008-12-06 02:22:16)

  • Is X-windows and GUI desktops supported on the ODA "engineered system" running a RAC database?  If it is, what is the yum command needed to install the X-windows, Gnome, and KDE package groups?

    Is X-windows and GUI desktops supported on the ODA "engineered system" running a RAC database?  If it is, what is the yum command needed to install the X-windows, Gnome, and KDE package groups?

    While I agree with the direction of the suggestions with installing packages for X-windows, we do not have a blanket 'apply any package' recommendation.
    In particular we do not support altering the kernel (although we do have exceptions which we review on a case by case basis).
    Basically, if the you want to alter functionality that would not impact core functionality you are usually fine.
    A good guideling is : The more dependencies that there are between the package / rpm you are considering using the higher the potential impact on functionality - meaning higher chance for problems
    Note: We do use VNC including Real and Tiger regularly , but we have no hard recommendation on how you may want to use X-windows. I have never seen a limitation other than comments on bugs
    or incompatibility within the X-window product itself with certain kernel levels.
    Patching may overwrite some packages that you may install, however,  _depending on packages/rpms added_ there is also the possibility that you will break existing functionality to the point
    that patching itself will fail ( we have already seen a few cases of this in which case the proper mitigation is to remove / roll-back any alterations to the ODA before patching, and then adding the packages/rpms
    back after the patching is completed.
    From what you are discussing the impact should be low without conflicts, but please consider the above, and if you have specific packages which you consider potential problems
    please create an SR so that we can review packages / rpms on an individual basis.
    Once again: the main criteria for not supporting rpms is regarding the kernel itself
    Chuck

  • After Effects CS6: Cache and Reload Footage Problem

    After Effects CS6: Cache and Reload Footage Problem
    I am having trouble getting my footage to update in an AE project. 
    In an existing project, there is an image sequence in a composition.  I have saved and closed AE, modified the footage (same dimensions and qty. of frames, only the pixel data changes), and then re-launched AE and opened the project.  Though I have changed the footage, the old content still appears.
    To resolve this, I have done the following:
    Edit>Purge>All Memory
    Edit>Purge>Image Cache Memory
    Edit>Preferences>Media & Disk Cache>Empty Disk Cache
    Edit>Preferences>Media & Disk Cache>Clean Database & Cache
    From the Project window I've selected all footage and selected Reload
    None of these got the footage to update.  I could double-click on the footage in the project bin and scrub the play head and the old footage was still displayed.
    Finally I had to replace the footage with itself and that resolved the issue.
    If this is operator error, lack of understanding the cache functions, or something else, I'd appreciate some assistance. I don't recall this behavior in CS 5.5, so I am guessing this is a change in CS 6.
    Win 7 Pro 64bit Service Pack 1
    Intel Xeon CPU X5450 @ 3.00 GHz 2.99 GHz
    RAM 20 GB

    about Illustrator and Photoshop files in CS6 especially - you should work with Ctrl/Cmd+E (Edit Original).
    when in Ae and you want to change a source file, use this command on one of the layers
    from the source file you wish to change (doesn't matter if its in the timeline or project window) and
    your original software linked to that file will open.
    when you work this way you make AE reload that file and any change after that will be seen back in AE immediately.
    it is also very convenient way to work because there can be no confusion on which file you are on
    if you work with multiple source files for example.
    even if you made the change with your Photoshop/Illustrator opened file and got back to Ae
    and didn't see any change - press on one of the layers Ctrl/Cmd+E and this will refresh it immediately.
    This is the case in CS6.
    in CC I have noticed that any change I make is refreshed immediately in Ae as if it rechecks the changes all the time,
    and didn't even need to use Ctrl/Cmd+E but it's a good habit all the same.
    didn't come across a case where that didn't work for be but
    if all fails you could always change the folder location of the file, let Ae lose it, then replace footage of the file,
    and thus let Ae re-link it back.

  • SOLVED! --- compositing problem after update

    well, I've made this week's update too, just as always
    since this update I do not have compositing on my gnome desktop ( I've used fusion-icon)
    ps ax | grep fusion    showed no process, so I've tried to start fusion-icon from a terminal, here's the result:
    ------------- code -----------------
    fusion-icon
    * Detected Session: gnome
    * Searching for installed applications...
    * NVIDIA on Xorg detected, exporting: __GL_YIELD=NOTHING
    * Using the GTK Interface
    * No module named cairo
    ... Trying another interface
    * Using the Qt4 Interface
    * No module named PyQt4
    ... Trying another interface
    * Using the Qt3 Interface
    * Interface not installed
    *** Error: All interfaces failed, aborting!
    Hmm, so, as far as i know I've cairo and qt installed.
    Any ideas? Anyone has the same problem?
    Had a good night's sleep and corrected the problem,
    I've installed the [pycairo] package.
    Everything's fine now.
    Last edited by scar (2010-12-18 11:21:45)

    jasonwryan wrote:
    I thought I was.
    The first clause in the sentence tells you that you can search the boards for the answer; the second provides the high-level solution.
    https://bbs.archlinux.org/viewtopic.php?id=140439
    Thank you for the link!

Maybe you are looking for

  • IPhone and Windows 7 64 Bit - syncing issues

    Hi, Just wondering if anyone is able to help. I have updated to Windows 7 and am having problems syning my iPhone. It comes up with a multitude of errors but the most common is: 'The iPhone "Michael's iPhone" can not be syned. The required file can n

  • I can't download any app from cc

    I can't download any app from cc, because it say to me "download error, reload or conctat the assistance". What i have to do?

  • Not able to back up my moutain lion on 10.5.8..

    Hi,      I Jst formatted my mac for the first time with mac os x dvd as it was really slow. I backed up in a external drive. When installation finished it didnt allowed me to copy my back up from time machine giving an error your back up is using a n

  • Digital camera to Extreme for wireless picture downloads.

    I have an AirPort Extreme to which I have successfully added a printer and external hard drive using a powered hub. I can access both wirelessly. I am also trying to add a digital camera to the hub so that I can download my new pictures to iPhoto wir

  • Histogram PtByPt is very slow

    I don't know why the General Histogram PtByPt.vi is so slow.  Using an uninitialized shift register and the General Histogram.vi I can implement the same functionality that runs at least 50 times faster processing the same number of points.  See my a