[SOLVED] Awesome WM - Mouse Doesn't Work on Client Objects

I am new to Arch and awesome and I haven't tampered with the default rc.lua but my mouse doesn't do anything when used on windows(clients). It does in fact work everywhere else e.g. the root window, the menu-bar... Below is the relevant part of my rc.lua, even though its the default.
clientbuttons = aweful.util.table.join(
aweful.button({ }, 1, function(C) client.focus = c; c:raise() end),
aweful.button({modkey}, 1, aweful.mouse.client.move),
aweful.button({modkey}, 3, aweful.mouse.client.resize))
aweful.rules.rules = {
{rule = {},
properties = {keys = clientkeys,
buttons = clientbuttons}}
The client specific keyboard rules do in fact work so its just the mouse related client rules.
Has anyone had this issue or have any suggestions about how to go about debugging it?
Last edited by OneMintJulep (2014-01-05 17:07:04)

It turns out it was my mouse all along (R.A.T 7). I was able to fix the issue with the following post:
http://fcns.eu/2011/04/01/cyborg-rat-7- … der-linux/

Similar Messages

  • [SOLVED] External USB mouse doesn't work

    I've installed Arch on my laptop and today faced with a problem. When I boot with AC off my external USB mouse doesn't work. Also it looks like USB ports don't work. If I detached AC when working mouse works fine.
    I can suppose there is some problem with laptop mode. May be it turns off usb ports to save energy. Anyway quick search doesn't brings any results. If someone give me a hint how to solve this problem I'll be very grateful.
    Last edited by avli (2011-07-14 16:53:15)

    Well, after diving into configs solution has been founded. The point was to disable auto suspend feature in laptop-mode-tools config by setting BATT_SUSPEND_USB variable to 0 in /etc/laptop-mode/conf.d/usb-autosuspend.conf
    Hope this information will be helpful for users who probably faced with the same problem. Thank you!

  • RDP 6.0 Vista lefthand Mouse doesn't work

    When i connect to a Terminal client  with my Windows Vista my left hand lefthand Mouse doesn't work correctly (switch to right hand).
    With Windows XP and RDP 6.0 i haven't these problem.
    what goes wrong?
    Regards
    Walter

    First off, I can state with 99.9% certainty that this has *nothing* to do with USB vs. PS/2 mice, and since you don't have custom mouse software on the client, the driver on the client is irrelevant to the equation. The version of Remote Desktop you are using is the most up to date available, so upgrading won't help you.
    I suspect (this is just a theory as I lack a mouse to test it with presently), that the problem is not that Remote Desktop doesn't recognize the presenter mouse.  Rather, the Presenter mouse software that does the custom button swapping is only designed to work with the Presenter mouse.  It ignores the emulated mouse that Remote Desktop uses on the server to forward mouse clicks from the client, so Presenter settings don't get applied.
    Does the server's mouse software completely remove the check box to swap mouse buttons, or does it just offer an additional means of swapping mouse buttons?  If the check box still exists, you should be able to use it to fix the Remote Desktop problem.  If it doesn't exist, I'm afraid I can't offer much in the way of solutions. The only possibility I can suggest is that while the client mouse software is not causing your problem, you might be able to solve the problem using the same weird mouse software that is causing the problem on the server.  As a test, you might try turning off mouse button swapping on the client, installing the Presenter on the client, and using the mouse button assignment mechanism it provides.  If it is bypassing the usually mechanism for swapping mouse buttons, it is possible that the Remote Desktop client won't detect the swap, and will pass the clicks on to the server inverted.  It's not an ideal solution, since in order to make it work in the long term you'd need to get another Presenter mouse for the client, but try it out to see if it *can* solve your problem.
    I will look into providing a mechanism to solve this more easily in the future (even if it is just a checkbox to allow you to force a swap), but any solution would not be available for quite a while I'm sorry to say.

  • I m using apple mac pc, when we start windows 7 , apple mouse doesn't work properly it take to much time to gain signals from the pc and many times it not work but when we use mac it moves fastly and works properly. please suggest me. thanks ravi

    i m using apple mac pc, when we start windows 7 , apple mouse doesn't work properly it take to much time to gain signals from the pc and many times it not work but when we use mac it moves fastly and works properly. please suggest me.
    thanks
    ravi
    <Email removed by Host>                                                                                                                                                                                                                                       

    sounds more like Bluetooth rather than moue, but w/o knowing w/o posting mac model type/year we... will... not... know... what you have
    All computers are personal computers, a PC though is also "non-Apple" in common usage.
    Mac also is platform and OS.
    Very confused reading what you are trying to tell us.

  • Just upgraded to snow leopard and my intellipoint mouse doesn't work, does it not work with the later versions of the OS

    I just upgraded to snow leopard and now my intellipoint mouse doesn't work, I tried downloading a new driver and it installs successfully except an extension but it still doesn't work, is this typical of the OS higher than 10.4? Is there any way I can get around this problem?

    You need to check with the mouse's developer and see if it's supported or not. That information wouldn't be known by users on this forum.

  • Mouse doesn't work in Classic

    Although I've owned 10.3 for a while, I just started using it full time. However, I have some documents that require me to use OS 9. Here is the problem:
    When in Classic, the "click" of the mouse doesn't work on the Classic application or Classic menu. The mouse works fine in OS X or if I restart in OS 9.2.2 it also works. I got Classic to start using only the base extensions and that didn't fix the problem.
    Any ideas?

    Hi Lauren:
    Sorry, but I've got nothing to suggest. As long as you're not launching Classic from the Advanced tab of System Preferences (which by default would turn off the Extensions), I can't thing of any reason why the apple mouse wouldn't work properly in Classic. And as long as the software for the microsoft mouse was installed under OS 9, it should work properly as well.
    The only thing I can suggest is Disk Utility: select your hard drive, then from the File menu, select "Fix OS 9 Permissions".
    Hope you get things working again.
    Andrew Penner

  • My apple magic mouse doesn't work in windows 7 after installing maverick os x

    My apple magic mouse doesn't work in windows 7 after installing the maverick operating system on my mackbook pro.  How do I fix this problem?

    Hi bsruff,
    If you are having issues with your Magic Mouse in Windows 7 via Boot Camp after upgrading to Mavericks, you may find the following article helpful:
    Apple Support: Resolving issues with Windows when using Apple Magic Mouse or Apple Wireless Keyboard
    http://support.apple.com/kb/TS3092
    Regards,
    - Brenden

  • Magic Charger for the Magic Mouse doesn´t work

    Hi,
    I´ve recently did my first purchase on the apple store,
    I´ve bought the magic charger from mobee for the Magic Mouse,
    which has been working all good with the normal batteries,
    but since I´ve install the new magic charger batteries I just can´t make
    work the magic mouse, I´ve plug the magic charge into a usb from the iMac 24"
    I´ve wait almost a day so tha the Magic Mouse charge the batteries than
    when I switch on the Magic Mouse doesn´t work, the green light from Magic Mouse stands off,
    so obviously the bluetooth from iMac 24" doesn´t recognize Magic Mouse,
    ¿Any suggestion?
    Thank you very much in advance.

    Hi Allan Jones,
    I don´t know under with authority you´ve answered this thread,
    but and don´t get me wrong, your message was completely worthless.
    Since I did a purchase on the apple store, the apple store should answer
    for every inconvenient with the product than I did purchase, and as Apple
    is a big multinational who cares for his customers, they did so Apple store sended
    special transport to my home to get the malfunctional Magic Charger and than
    they send me a new one which seems would work fine.
    Thank you very much in advance.

  • Sometimes my screen starts to move on my iMac.    It's like it's trying to turn the page and it gets off center and the mouse doesn't work when it happens.  It usually lasts about 15 seconds or so and happens often.

    Sometimes the screen on my imac starts to shake like it it trying to "go to the next page".   When this happens it usually freezes up for 15 seconds or so and the mouse doesn't work.

    Have you tried a hard reset of the iPod to see if that helps?  To do this, press and hold both the Sleep/Wake and Home buttons together long enough for the Apple logo to appear. 
    Otherwise, work through each of the troubleshooting suggestions in this Apple support document as necessary.
    iOS: Troubleshooting Wi-Fi networks and connections
    B-rock

  • Autoreaction doesn't work from client 000 but works from other clients

    Autoreaction doesn't work from client 000.
    More details coming.   Having trouble getting the thread to post.

    We set up a new local auto-reaction.   This is not a central auto-reaction.  The auto-reaction writes a
    message to the UNIX system log /var/adm/messages when a "Security"
    alert i.e. - Logon, RFCLogon, TransactionStart, etc.  occurs.
    The RZ20 alerts are being properly generated and can be seen in both
    the CEN system and the local system. On the local system if I view
    all alerts for the MTE using transaction RZ20 and select one of the
    alerts and choose Edit -> Nodes ( MTE ) -> Start methods -> Start auto-
    reaction method. The auto-reaction writes the message to the UNIX
    system log. If I execute the same procedure in client 000 nothing is
    written to the UNIX system log.
    I've also tried triggering a new alert and running SAPMSSY8 from SE38
    while the alert is still in status ACTION_REQUIRED. If I do this from
    client 010, an entry is written to the unix system log. If I do this
    from client 000, nothing is written to the unix system log. In both
    cases, the status of the alert changes from ACTION_REQUIRED to ACTIVE.
    Since the System Cyclic program ( SAPMSSY6 ) that triggers SAPMSSY8
    always runs in client 000, the auto-reaction never writes the messages
    to the UNIX system log.
    I have been working on this issue for days.  There are several posts and notes relevant to a similar situation with e-mail alerts that are not working from client 000 because SAPCONNECT is not set up in client 000.   However, this auto-reaction does not send an e-mail, so SAPCONNECT set-up should not be necessary.   I've searched Service Marketplace and could not find any notes that resolved the problem either.  
    I've also checked CCMS Self-Monitoring and cannot find any alerts or errors relevant to this problem.
    Does anyone know why the auto-reaction only works from a client other than client 000?
    Best regards,
    Dave

  • KVM switch w/ usb i/o for keyboard mouse doesn't work [Solved]

    Edit:
    This problem appears to have magically disapeared.  I'm still not sure why it happened or why it has ceased.
    Hello Everybody,
    I'm not sure why this is happening, but I've got a KVM switch that used to get "automagically" detected as "a no-brand KVM switch" on boot-up that has ceased working.  I don't get this "no brand KVM switch" detected on boot-up anymore, but I can use the VGA part of the switch, at least, however the keyboard and mouse don't work unless plugged directly into the computer. 
    Below I've attached the result of
    dmesg | grep --context=3 usb
    dmesg | grep kvm
    returns no result.
    The most signifcant thing seems to be:
    usb 1-2: new full speed USB device using uhci_hcd and address 7
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: new full speed USB device using uhci_hcd and address 8
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: new full speed USB device using uhci_hcd and address 9
    usb 1-2: device not accepting address 9, error -71
    usb 1-2: new full speed USB device using uhci_hcd and address 10
    usb 1-2: device not accepting address 10, error -71
    hub 1-0:1.0: unable to enumerate USB device on port 2
    I've googled this, and somewhere it was suggested this mean the usb device is not drawing power.  The only thing that has happened that I can imagine as being the culprit between function/dysfunction here is that there was a power outage (circuit breaker tripped), and though my computers were on battery-backup, the monitor is not.  I don't suppose that this could have messed up the switch?
    Note this problem is uniform across 3 computers, 2 which have recently run a system update, but the 3rd has not recently run an update, this is not an Xorg problem, "K and M" don't work in either console or X.
    Any help would be appreciated.  Below as, mentioned previously, is the output of
    dmesg | grep --context=3 usb
    included on the off-chance that someone sees something significant there.
    ata1.00: configured for UDMA/100
    ata2.00: ATAPI: HL-DT-ST RW/DVD GCC-4480B, GW02, max UDMA/33
    ata2.00: configured for UDMA/33
    scsi 0:0:0:0: Direct-Access ATA WDC WD400EB-11CP 06.0 PQ: 0 ANSI: 5
    scsi 1:0:0:0: CD-ROM HL-DT-ST RW/DVD GCC-4480B GW02 PQ: 0 ANSI: 5
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    USB Universal Host Controller Interface driver v3.0
    huhci_hcd 0000:00:1d.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
    uhci_hcd 0000:00:1d.0: setting latency timer to 64
    uhci_hcd 0000:00:1d.0: UHCI Host Controller
    uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
    uhci_hcd 0000:00:1d.0: irq 16, io base 0x0000e800
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 2 ports detected
    uhci_hcd 0000:00:1d.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
    uhci_hcd 0000:00:1d.1: setting latency timer to 64
    uhci_hcd 0000:00:1d.1: UHCI Host Controller
    uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
    uhci_hcd 0000:00:1d.1: irq 19, io base 0x0000e880
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 2 ports detected
    Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
    Driver 'sd' needs updating - please use bus_type methods
    sd 0:0:0:0: [sda] 78165360 512-byte hardware sectors (40021 MB)
    uhci_hcd 0000:00:1d.2: PCI INT C -> GSI 18 (level, low) -> IRQ 18
    uhci_hcd 0000:00:1d.2: setting latency timer to 64
    uhci_hcd 0000:00:1d.2: UHCI Host Controller
    uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
    uhci_hcd 0000:00:1d.2: irq 18, io base 0x0000ec00
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 2 ports detected
    usb 1-2: new full speed USB device using uhci_hcd and address 2
    usb 1-2: device descriptor read/64, error -71
    ehci_hcd 0000:00:1d.7: PCI INT D -> GSI 23 (level, low) -> IRQ 23
    ehci_hcd 0000:00:1d.7: setting latency timer to 64
    ehci_hcd 0000:00:1d.7: EHCI Host Controller
    ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4
    ehci_hcd 0000:00:1d.7: debug port 1
    ehci_hcd 0000:00:1d.7: cache line size of 128 is not supported
    ehci_hcd 0000:00:1d.7: irq 23, io mem 0xffa7fc00
    ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 6 ports detected
    hub 1-0:1.0: unable to enumerate USB device on port 2
    kjournald starting. Commit interval 5 seconds
    EXT3-fs: mounted filesystem with ordered data mode.
    usb 1-2: new full speed USB device using uhci_hcd and address 3
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: new full speed USB device using uhci_hcd and address 4
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: new full speed USB device using uhci_hcd and address 5
    rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one month
    usb 1-2: device not accepting address 5, error -71
    usb 1-2: new full speed USB device using uhci_hcd and address 6
    usb 1-2: device not accepting address 6, error -71
    hub 1-0:1.0: unable to enumerate USB device on port 2
    usb 3-2: new low speed USB device using uhci_hcd and address 2
    e100: Intel(R) PRO/100 Network Driver, 3.5.23-k4-NAPI
    e100: Copyright(c) 1999-2006 Intel Corporation
    e100 0000:01:08.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
    e100 0000:01:08.0: PME# disabled
    e100: eth0: e100_probe: addr 0xff8fe000, irq 20, MAC addr 00:07:e9:50:88:58
    eepro100.c:v1.09j-t 9/29/99 Donald Becker
    eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <[email protected]> and others
    usb 3-2: configuration #1 chosen from 1 choice
    Intel ICH 0000:00:1f.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Intel ICH 0000:00:1f.5: setting latency timer to 64
    usbcore: registered new interface driver hiddev
    input: Logitech USB Optical Mouse as /class/input/input2
    input,hidraw0: USB HID v1.10 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1d.2-2
    usbcore: registered new interface driver usbhid
    usbhid: v2.6:USB HID core driver
    intel8x0_measure_ac97_clock: measured 50831 usecs
    intel8x0: clocking to 48000
    input: Power Button (FF) as /class/input/input3
    ACPI: Power Button (FF) [PWRF]
    input: Sleep Button (CM) as /class/input/input4
    reserve_memtype failed 0xf0000000-0xf8000000, track write-combining, req write-combining
    X:2394 freeing invalid memtype f0000000-f8000000
    X:2367 conflicting memory types f0000000-f8000000 write-combining<->uncached-minus
    reserve_memtype failed 0xf0000000-0xf8000000, track write-combining, req write-combining
    X:2395 freeing invalid memtype f0000000-f8000000
    usb 1-2: new full speed USB device using uhci_hcd and address 7
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: new full speed USB device using uhci_hcd and address 8
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: device descriptor read/64, error -71
    usb 1-2: new full speed USB device using uhci_hcd and address 9
    usb 1-2: device not accepting address 9, error -71
    usb 1-2: new full speed USB device using uhci_hcd and address 10
    usb 1-2: device not accepting address 10, error -71
    hub 1-0:1.0: unable to enumerate USB device on port 2
    Thanks again!
    Last edited by pseudonomous (2008-12-30 23:57:47)

    i'm sorry, but this is all software related then. if you haven't already, run disk utility a few times to try to correct the error. otherwise, you should back up your info immediately if you can. if you can access another mac you can do that with firewire target disk mode. http://docs.info.apple.com/article.html?artnum=58583. the other mac has to have built-in firewire. then you can try to repair the directory with a third party utility like diskwarrior or techtool pro. if it cannot solve the problem, or if you do not want to spend the money on the software, you have no choice but to erase and install your operating system. do you already have your info backed up?? it's always a good idea. keep us posted as to how it's going for you or if you have any further questions. [ 8 ) ]

  • Adesso wireless mouse doesn't work in Mountain Lion.

    My Bluetooth  Adesso iMouse S100 doesn't work in Mountain Lion. It barely moves and constantly halts as if its driver is continuously interrupted. It is unusable. It worked beautifully in Snow Leopard.
    I don't believe the problem is in the mouse, but just for completeness the batteries are full strength. The Bluetooth control panel signal  strength for the mouse ranges from -50 to -48, which may be low but I'm  pretty sure was the same in Snow Leopard.
    Has anyone experienced and have a fix for this problem?
    Thanks.

    A mouse pad solved the problem. The Ikea Lack table I'm using is the source of the problem. Its table top surface is apparently scattering the mouse's laser and not reflecting it back properly. I have not experienced this problem with any other table I've used, wood, Formica, et al.

  • When reinstalling OS X with install disk, wireless mouse doesn't work

    I have an unusual problem: My iMAC G5 hard drive died and I installed a replacement disk. Now, I am trying to reinstall OS X 10.3 with the help of my original install CDs that came with the iMAC.
    Unfortunately, my wireless mighty mouse doesn't react anymore and I cannot proceed with the installation through keyboard commands alone. I get stuck at the first install window where the system asks for the operating system language.
    I am clueless how to proceed since I don't have access to any utilities to test or connect the mouse because OS X is not installed yet. I tested the mouse on another Mac and it works. Any clues? Thanks for your help.

    I solved my problem by using the original mouse

  • [SOLVED]Xorg 1.8 doesn't work

    Hello, I've just upgraded to linux-firmware and the newest X.org, which doesn't work.
    Xorg.0.log tells me:
    [ 934.318]
    X.Org X Server 1.8.1
    Release Date: 2010-05-11
    [ 934.322] X Protocol Version 11, Revision 0
    [ 934.323] Build Operating System: Linux 2.6.33-ARCH x86_64
    [ 934.325] Current Operating System: Linux staerseus 2.6.34-ARCH #1 SMP PREEMPT Sat Jun 19 00:07:49 CEST 2010 x86_64
    [ 934.326] Kernel command line: root=/dev/disk/by-uuid/727c4683-ee4c-4b32-8a59-370264cb7d9f ro i915.modeset=1 init=/sbin/bootchartd
    [ 934.327] Build Date: 26 May 2010 07:50:07PM
    [ 934.329]
    [ 934.330] Current version of pixman: 0.18.2
    [ 934.331] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 934.334] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 934.338] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun 21 10:15:38 2010
    [ 934.340] (==) Using config file: "/etc/X11/xorg.conf"
    [ 934.341] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 934.343] (==) No Layout section. Using the first Screen section.
    [ 934.343] (==) No screen section available. Using defaults.
    [ 934.343] (**) |-->Screen "Default Screen Section" (0)
    [ 934.343] (**) | |-->Monitor "<default monitor>"
    [ 934.343] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 934.343] (==) Automatically adding devices
    [ 934.343] (==) Automatically enabling devices
    [ 934.343] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 934.343] Entry deleted from font path.
    [ 934.343] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 934.343] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 934.343] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 934.343] (II) Loader magic: 0x7ce880
    [ 934.343] (II) Module ABI versions:
    [ 934.343] X.Org ANSI C Emulation: 0.4
    [ 934.343] X.Org Video Driver: 7.0
    [ 934.343] X.Org XInput driver : 9.0
    [ 934.343] X.Org Server Extension : 3.0
    [ 934.352] (--) PCI:*(0:0:2:0) 8086:2a42:1734:113f Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller rev 7, Mem @ 0xf2400000/4194304, 0xd0000000/268435456, I/O @ 0x00001800/8
    [ 934.352] (--) PCI: (0:0:2:1) 8086:2a43:1734:113f Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller rev 7, Mem @ 0xf2100000/1048576
    [ 934.352] (II) Open ACPI successful (/var/run/acpid.socket)
    [ 934.352] (II) LoadModule: "extmod"
    [ 934.352] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 934.352] (II) Module extmod: vendor="X.Org Foundation"
    [ 934.352] compiled for 1.8.1, module version = 1.0.0
    [ 934.352] Module class: X.Org Server Extension
    [ 934.352] ABI class: X.Org Server Extension, version 3.0
    [ 934.352] (II) Loading extension MIT-SCREEN-SAVER
    [ 934.352] (II) Loading extension XFree86-VidModeExtension
    [ 934.352] (II) Loading extension XFree86-DGA
    [ 934.352] (II) Loading extension DPMS
    [ 934.352] (II) Loading extension XVideo
    [ 934.352] (II) Loading extension XVideo-MotionCompensation
    [ 934.352] (II) Loading extension X-Resource
    [ 934.352] (II) LoadModule: "dbe"
    [ 934.352] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 934.352] (II) Module dbe: vendor="X.Org Foundation"
    [ 934.353] compiled for 1.8.1, module version = 1.0.0
    [ 934.353] Module class: X.Org Server Extension
    [ 934.353] ABI class: X.Org Server Extension, version 3.0
    [ 934.353] (II) Loading extension DOUBLE-BUFFER
    [ 934.353] (II) LoadModule: "glx"
    [ 934.353] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 934.353] (II) Module glx: vendor="X.Org Foundation"
    [ 934.353] compiled for 1.8.1, module version = 1.0.0
    [ 934.353] ABI class: X.Org Server Extension, version 3.0
    [ 934.353] (==) AIGLX enabled
    [ 934.353] (II) Loading extension GLX
    [ 934.353] (II) LoadModule: "record"
    [ 934.353] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 934.353] (II) Module record: vendor="X.Org Foundation"
    [ 934.353] compiled for 1.8.1, module version = 1.13.0
    [ 934.353] Module class: X.Org Server Extension
    [ 934.353] ABI class: X.Org Server Extension, version 3.0
    [ 934.353] (II) Loading extension RECORD
    [ 934.353] (II) LoadModule: "dri"
    [ 934.353] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 934.353] (II) Module dri: vendor="X.Org Foundation"
    [ 934.353] compiled for 1.8.1, module version = 1.0.0
    [ 934.353] ABI class: X.Org Server Extension, version 3.0
    [ 934.353] (II) Loading extension XFree86-DRI
    [ 934.354] (II) LoadModule: "dri2"
    [ 934.354] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 934.354] (II) Module dri2: vendor="X.Org Foundation"
    [ 934.354] compiled for 1.8.1, module version = 1.2.0
    [ 934.354] ABI class: X.Org Server Extension, version 3.0
    [ 934.354] (II) Loading extension DRI2
    [ 934.354] (==) Matched intel as autoconfigured driver 0
    [ 934.354] (==) Matched vesa as autoconfigured driver 1
    [ 934.354] (==) Matched fbdev as autoconfigured driver 2
    [ 934.354] (==) Assigned the driver to the xf86ConfigLayout
    [ 934.354] (II) LoadModule: "intel"
    [ 934.354] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 934.354] (II) Module intel: vendor="X.Org Foundation"
    [ 934.354] compiled for 1.7.6, module version = 2.11.0
    [ 934.354] Module class: X.Org Video Driver
    [ 934.354] ABI class: X.Org Video Driver, version 6.0
    [ 934.354] (EE) module ABI major version (6) doesn't match the server's version (7)
    [ 934.356] (II) UnloadModule: "intel"
    [ 934.356] (II) Unloading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 934.356] (EE) Failed to load module "intel" (module requirement mismatch, 0)
    [ 934.357] (II) LoadModule: "vesa"
    [ 934.357] (WW) Warning, couldn't open module vesa
    [ 934.357] (II) UnloadModule: "vesa"
    [ 934.357] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 934.359] (II) LoadModule: "fbdev"
    [ 934.359] (WW) Warning, couldn't open module fbdev
    [ 934.359] (II) UnloadModule: "fbdev"
    [ 934.359] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 934.360] (EE) No drivers available.
    [ 934.362]
    Fatal server error:
    [ 934.364] no screens found
    [ 934.365]
    Please consult the The X.Org Foundation support
    at http://wiki.x.org
    for help.
    [ 934.370] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
    [ 934.372]
    What does the problem with modules mean? Archlinux was warning me, that "in future releases /etc/modprobe.d/framebuffer_blacklist.conf.save will be ignored, but it is the same file as /etc/modprobe.d/framebuffer_blacklist.conf.
    I don't understand, why it cannot find any screens (I use a laptop screen)
    I tried to start with and without xorg.conf, which is:
    Section "Device"
    Identifier "Intel X4500MHD"
    Driver "intel"
    VendorName "Intel Corporation"
    BoardName "Mobile 4 Series Chipset Integrated Graphics Controller"
    BusID "PCI:0:2:0"
    Option "DRI" "true"
    Option "AccelMethod" "uxa"
    Option "MigrationHeuristic" "greedy"
    EndSection
    The graphic driver I use is xf86-video-intel-newest from archstuff, but it is the same version as xf86-video-intel.
    I am not sure if I provided all needed info, but I hope so. Thank you for your help.SOLVED
    Last edited by Staerseus (2010-06-21 09:18:03)

    Use the arch version.   It is actually built against the xorg version that you are using...  here is the relevant section of your log:
    [ 934.354] (EE) module ABI major version (6) doesn't match the server's version (7)

  • Why does File send link not work? Even right clicking on my mouse doesn't work. Is there a fix for this?

    Why can I no longer send links to websites? Clicking File>Send Link doesn't work nor does right clicking on the mouse. Both worked prior to Firefox 6. I also can't send emails to websites that don't spell out their address but instead say "to send an email click here". Everything works fine in Chrome and Safari but not in Firefox.

    OK well after first reverting to an older version of firefox to get my right click menu options back I have since discovered one way that works but at a cost.
    By using the addon menu-editor it is possible to move the EMAIL LINK button from the file menu to the (Main Context Menu) ie the "right click menu" BUT you will loose the file menu button as there is no way to clone the button and only move a copy. Bunch of clowns that decided to do this I really don't know what they were thinking. Very VERY stupid move.
    Here is a link to the only option that works https://addons.mozilla.org/en-US/firefox/addon/menu-editor/
    Can you fellows/chaps <!--buggers--> at least provide a clone and move option in the menu-editor?

Maybe you are looking for