Multimedia key issue in a terminal emulator

My keyboard has a few multimedia keys(XF86AudioRaiseVolume, etc.) and
they have been correctly recognized by X and have keycodes/keysyms. I
can get them work on most programs, but they are not recognized by
programs run inside a terminal emulator(urxvt or xterm, for example).
Specifically, I want to control my emms playlist via
XF86AudioPrev/XF86AudioNext. I have the key bindings in emacs start up
file and it actually works when emacs appears as a standalone X
window. But it fails when emacs is inside a terminal. it appears to
me that the terminal/shell never delivers these key strokes to any
processes spawned by them.
I searched for the keysym/keymap resources in urxvt/xterm but can't
quite catch the idea and don't even know if this helps.
Last edited by eirika (2009-09-15 02:50:23)

Response marked with
line 1 16
modem InOut
it says that, "line 2 does not support modem control"
- can you please try only one line at a time, that is:
line 1
modem inout
then try line 2 and so on and see if we see errors for specific lines only (which we can investigate further)
Then I typed:
(config)#line 0 17
(config-line)#modem InOut
it says, "line 0 does not support modem control. Now it doesn't talk about line 2, instead it says that line 0 does not support modem control.
This error is ok since line 0 is console and does not support modem control, mind you IOS spills out errors one after another so probably would have given error for line 2 next.
In here, the main problem is that, when I type:
(config)#line 1 16
(config-line)#no exec
and when I telnet, the router doesn't even prompt for anything. But when I again say, "exec" in line mode, then the router prompts me for the username.
Do you mean reverse telnet out of these lines? Not sure I understand what you are trying to do here.
A few things to check:
1. Is the router completely up, means its not in boot mode etc.
2. Are the IOS images different or same on the working vs non working 2511?
Thanks, Mak

Similar Messages

  • Cinnamon Multimedia Keys Issue

    My multimedia keys only work in the sound applet in Cinnamon.
    Output of uname -a:
    Linux WITHHELD 4.0.4-1-ARCH #1 SMP PREEMPT Mon May 18 06:43:19 CEST 2015 x86_64 GNU/Linux
    Output of pacman -Q | grep cinnamon:
    cinnamon 2.4.8-1
    cinnamon-control-center 2.4.2-3
    cinnamon-desktop 2.4.2-1
    cinnamon-menus 2.4.1-1
    cinnamon-screensaver 2.4.2-1
    cinnamon-session 2.4.3-2
    cinnamon-settings-daemon 2.4.3-1
    cinnamon-translations 2.4.4-1
    Any ideas? Please and thank you.

    Same here. does anyone know how to fix this?

  • Font rendering issue & multimedia keys not working

    Hi, yesterday i switched to KDEmod 4.1 and I have two major problems...
    One is font rendering issue... I did not change anything in my font-related packages (cairo, freetype, fontconfig, libxft) and i have to add that this setup worked perfectly in KDEmod 3.5.9, but now it looks like this:
    This bug occurs only in qt apps and mostly in kmenu... i.e firefox renders my fonts flawlessly...
    Second problem are multimedia keys on my keyboard...
    They worked in KDE 3.5.9, but now I cannot set them up properly... Sometimes they work, sometimes they don't...
    KDE recognizes the pressed key, but when I assign specific action and press the key, just nothing happens...

    You might be able to solve your font issue by going to System Settings -> Appearance -> Fonts.  I enable ant-aliasing.  I also clicked on configure and select "Use sub-pixel rendering" to RGB and the hinting style to Full.  I also use the Force fonts DPI to 96 DPI.  This makes the fonts pleasing to my eyes.
    This is how I got my multimedia keys to work in KDE4.1:
    Go to System Settings -> Regional and Language and make sure to set the County or region to your location.
    khotkeys needs to be running.  I added it to the autostarted progam list. System Settings -> Advanced tab -> Autostart
    When I got the multimedia keys working, I was really tring to get the keyboard shortcuts to work.  In addition to the above steps, I also deleted
    ~/.kde4/share/config/kglobalshortcutsrc.  I do not know if deleting this file is needed to get the multimedia keys working, but it was to get the keyboard shortcuts woring.
    Restart X
    Go to  System Settings -> Keyboard and Mouse -> Keyboard Shortcuts
    I set the volume control in the KMix component section.
    To get the keyboard shortcuts to work, go to the menu editor and select the program you want to create a shortcuts for.  Click on the advanced tab and create the shortcut in the shortcut field.  Save.
    Then go to  System Settings -> Keyboard and Mouse -> Keyboard Shortcuts. Change the component to KHotkeys.  Select the Program and then select the default shortcut that you just created.  (This works for the multimedia keys aswell).
    Hope this helps,
    pudge

  • Xmodmap: problems emulating multimedia keys

    Using xmodmap I have remapped my Menu key to Mode_switch and used the modifier to emulate some multimedia keys, like this:
    keycode 75 = F9 F9 XF86AudioPlay F9 F9 F9 XF86Switch_VT_9 F9 F9 XF86Switch_VT_9 F9 F9 F9 F9 XF86Switch_VT_9 F9 F9 F9 F9 XF86Switch_VT_9
    keycode 76 = F10 F10 XF86AudioStop F10 F10 F10 XF86Switch_VT_10 F10 F10 XF86Switch_VT_10 F10 F10 F10 F10 XF86Switch_VT_10 F10 F10 F10 F10 XF86Switch_VT_10
    keycode 95 = F11 F11 XF86AudioPrev F11 F11 F11 XF86Switch_VT_11 F11 F11 XF86Switch_VT_11 F11 F11 F11 F11 XF86Switch_VT_11 F11 F11 F11 F11 XF86Switch_VT_11
    keycode 96 = F12 F12 XF86AudioNext F12 F12 F12 XF86Switch_VT_12 F12 F12 XF86Switch_VT_12 F12 F12 F12 F12 XF86Switch_VT_12 F12 F12 F12 F12 XF86Switch_VT_12
    keycode 78 = Scroll_Lock NoSymbol XF86AudioLowerVolume NoSymbol Scroll_Lock Scroll_Lock
    keycode 107 = Print Sys_Req XF86AudioMute Sys_Req Print Sys_Req Print Sys_Req
    keycode 127 = Pause Break XF86AudioRaiseVolume Break Pause Break Pause Break
    keycode 135 = Mode_switch
    clear mod3
    clear mod4
    clear mod5
    !add shift = Shift_L Shift_R
    !add lock = Caps_Lock
    !add control = Control_L Control_R
    !add mod1 = Alt_L Meta_L Alt_R
    !add mod2 = Num_Lock
    add mod3 = Mode_switch
    add mod4 = Super_L Hyper_L
    add mod5 = ISO_Level3_Shift
    Testing with xev, I see that the codes are sent correctly.
    But in kde, only mute button works.
    The other controls, like volume up/down, etc, are ignored.
    My intention was to emulate the behavior of Fn + various keys from laptops and keyboards with similar functionality.
    Any thoughts what is wrong? I searched a lot of info and didn't find any clues.

    Yeah, I forgot to mention, when I try to set a new custom shortcut, and I press first Menu, it doesn't wait for the next key and I the label changes to unprintable characters.

  • Terminal Emulation/TN5250 on a Blackberry

    All -
    I am looking for some software to do terminal emulation on the Blackberry.  I used to use MobileSSH from Rove, but now that they have incorporated it into Mobile Admin, I can no longer purchase just MobileSSH and the cost has also rised about 3x-4x to $595 and I can't get justification for that amount of money.
    I am wanting to connect to an AS/400 through MDS via TN5250 emulation.  I will need function key access, special character input ability, and field exit key capability.  Any suggestions anyone?  Please let me know!!
    Thanks,
    Charlie
    Blackberry Administrator
    BES 4.1.6 MR1 with Lotus Domino 8.0.1
    58 Users

    HI and welcome to the forums!
    http://www.my-install.com/prog/Network-Internet-Terminal-Telnet-Clients/36377/Mobile-SSH-for-BlackBe...
    Idokorro Mobile. Shareware.
    Thanks,
    Please remember to resolve your thread. Put the check mark in the green box that contained your answer! Thanks
    Message Edited by Bifocals on 11-11-2008 11:47 PM
    Click Accept as Solution for posts that have solved your issue(s)!
    Be sure to click Like! for those who have helped you.
    Install BlackBerry Protect it's a free application designed to help find your lost BlackBerry smartphone, and keep the information on it secure.

  • [SOLVED] Terminal emulator that allows free resizing?

    EDIT: Answered my own question; terminator allows per-pixel resizing if you disable window hinting in the preferences.
    I have an annoyance with resizing terminal emulators. I use stacking WMs (xfwm4 on one setup, compiz standalone on another) but I usually like to tile my windows manually. I've enabled edge snapping in both of these WMs. However, whenever I'm resizing a terminal window, the snapping doesn't work because the terminal window can't be freely resized - I can only change the size of the window by one character's height/width. For example, if a terminal is open at 80x36, and I want to make it just a little bit wider to snap against the edge of another window, I can't because it won't let me resize the window between 80 and 81 characters.
    I've tried xfce's terminal, gnome-terminal, lxterminal, xterm, urxvt, and st. Can someone direct me to a terminal emulator that will let me resize windows to whatever size I want, regardless of whether it is a discrete character size, or am I out of luck?
    P.S. I've noticed that if I resize a window with wmctrl and issue the resize command twice, then xfce's terminal behaves the way it should. Can I replicate this behavior for resizing with the mouse?
    Last edited by thorion (2012-10-19 05:14:41)

    A terminal emulator and X Window GUI are different things. You can have a terminal emulator in a graphical desktop environment, but you cannot display GUI in a terminal.
    Putty is just a SSH client and terminal emulator (VT) and can be used with X-forwarding to display remote GUI applications (Linux), provided you are have a X Window server installed and running on your local computer, e.g. Xming Server for Windows.
    Perhaps you will find the free version of http://mobaxterm.mobatek.net/ useful. It is a single application based on Cygwin that allows you run GUI applications from your remote Linux system.
    By far the best terminal emulator in terms of user interface and configuration options that I’m aware of is the Terminal App of MacOSX, which also automatically opens Xorg if you open a GUI application. And it provides the full set of terminal escape sequences. But if you are on Windows….
    Alternatively, use VNC. You can run VNC in several modes, either to open an existing remote desktop connection, start a new desktop connection, or run a minimal X windows server, such as TWM that does not require you to install or run a graphical user desktop on your remote Linux server. If you are interested in VNC, perhaps check the following: https://community.oracle.com/thread/2456580. You can also tunnel VNC through SSH if your network firewall prevents communication.

  • Multimedia Keys in Awesome Window Manager [SOLVED]

    Hey,
    I've googled, searched, grepped and scanned about this for weeks, and I think I can't get it working on my own, although I'm sure the right answer is just out there waiting to be found, and one of you brighter minds might just know it already. Right, here's what happens.
    I was using openbox, and the keybindings were working just fine. This should probably discard missing symbols or scancodes for the keys, IMHO. Then I switch over to Awesome, and fall in love. The awesome (pun intended) config files by anrxc made it even better, and these days I can't live without my awesome. But I also wanted my volume keys to work. Not like I mind opening a terminal and popping alsamixer... I got 15 of them open all the time anyway. But I still wanted to use the fancy buttons.
    The strange thing is, the keys seem to "disappear" as soon as I map them somewhere. I've tried binding them in rc.lua:
    awful.key({}, "#121", function () exec("pvol.py -m", false) end),
    awful.key({}, "#122", function () exec("pvol.py -c -2", false) end),
    awful.key({}, "#123", function () exec("pvol.py -c 2", false) end),
    pvol.py is a script (made by anrxc too) that does stuff to the volume and displays a cute gtk progress bar to indicate current volume level. Invoking it from the terminal works fine.
    I also tried using xbindkeys:
    "pvol.py -m"
    XF86AudioMute
    "pvol.py -c -2"
    XF86AudioLowerVolume
    "pvol.py -c 2"
    XF86AudioRaiseVolume
    But the result was the same. Here's the output of xev with the keys unbound:
    KeyPress event, serial 25, synthetic NO, window 0x1600001,
    root 0x15a, subw 0x0, time 4706773, (74,267), root:(796,288),
    state 0x10, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False
    KeyRelease event, serial 28, synthetic NO, window 0x1600001,
    root 0x15a, subw 0x0, time 4706853, (74,267), root:(796,288),
    state 0x10, keycode 123 (keysym 0x1008ff13, XF86AudioRaiseVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
    KeyPress event, serial 28, synthetic NO, window 0x1600001,
    root 0x15a, subw 0x0, time 4712422, (74,267), root:(796,288),
    state 0x10, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False
    KeyRelease event, serial 28, synthetic NO, window 0x1600001,
    root 0x15a, subw 0x0, time 4712534, (74,267), root:(796,288),
    state 0x10, keycode 122 (keysym 0x1008ff11, XF86AudioLowerVolume), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
    KeyPress event, serial 28, synthetic NO, window 0x1600001,
    root 0x15a, subw 0x0, time 4713862, (74,267), root:(796,288),
    state 0x10, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False
    KeyRelease event, serial 28, synthetic NO, window 0x1600001,
    root 0x15a, subw 0x0, time 4713878, (74,267), root:(796,288),
    state 0x10, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
    As you can see, they respond to the key codes 121. 122, and 123. Going to a console and running showkey, however, gives me the key codes 113, 114, and 115. I've tried mapping both, and the X11 symbols, with the same result. Below, a sample of xev's output when I bind the keys somewhere (out put for a single key, all result in the same output):
    FocusOut event, serial 29, synthetic NO, window 0x1600001,
    mode NotifyGrab, detail NotifyAncestor
    FocusIn event, serial 29, synthetic NO, window 0x1600001,
    mode NotifyUngrab, detail NotifyAncestor
    KeymapNotify event, serial 29, synthetic NO, window 0x0,
    keys: 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
    And of course, nothing happens. The same happens whether I bind the keys in awesome or through xbindkeys. I have to admit, I'm pretty much out of ideas. Anyone seen this before?
    Last edited by mkaito (2010-06-16 15:06:06)

    d2ogch3n wrote:
    Here's what I have
        -- Multimedia keys
        awful.key({ }, "XF86AudioRaiseVolume",    function () awful.util.spawn("amixer set Master 2+") end),
        awful.key({ }, "XF86AudioLowerVolume",    function () awful.util.spawn("amixer set Master 2-") end)
    Just to clarify for anyone who comes across this, "%" is needed after the number. It should be:
    awful.key({ }, "XF86AudioRaiseVolume", function () awful.util.spawn("amixer set Master 2%+") end),
    awful.key({ }, "XF86AudioLowerVolume", function () awful.util.spawn("amixer set Master 2%-") end)
    You should also be able to add Mute functionality:
    awful.key({ }, "XF86AudioMute", function () awful.util.spawn("amixer set Master toggle") end)
    Also, to get rid of the loading cursor, pass false as a second argument to all three of these:
    awful.key({ }, "XF86AudioRaiseVolume", function () awful.util.spawn("amixer set Master 2%+", false) end),
    awful.key({ }, "XF86AudioLowerVolume", function () awful.util.spawn("amixer set Master 2%-", false) end)
    awful.key({ }, "XF86AudioMute", function () awful.util.spawn("amixer set Master toggle", false) end)
    The AWM wiki is the source for this:
    http://awesome.naquadah.org/wiki/Volume … nd_display

  • ITunes 7.1.1 only partially fixes multimedia keys

    Well... after all the hassle we had before; http://discussions.apple.com/thread.jspa?threadID=881133
    It appears that iTunes developers have adressed part of the problem with the multimedia keys in 7.1.1. Now the play/pause, stop, forward, and reverse buttons work well, even when iTunes is minimized to the systray.
    However, the volume buttons are still hosed. Whenever iTunes isn't the "top window", or window in focus and I press mute it still mutes the system, then quickly unmutes it again. The same for pressing the up and down volume. When iTunes is in focus it will only increase the volume by 1 notch. When iTunes isn't in focus it increases or decreases the volume by two notches.
    What would really be nice is if there were a checkbox in the preferences section to completely disable iTunes multimedia key support.
    Still a bad day for me, so I'm going back to 7.02 again.
    Dell inspiron 8500   Windows XP  

    WOOOOHOOOO!!!!! I Finally found a way to fix this issue! After playing around with the iTunesKeyboardCompatibility.dll a while I think I got it working again for me.
    Here's the situation. Most of you know that if you remove the iTunesKeyboardCompatibility.dll the program will just recreate it when you try to launch iTunes again.
    Some of you know that if you delete the iTunesKeyboardCompatibility.dll and recreate an empty file with the same name iTunes will complain that it's not a valid windoze file... ya ya ya... whatever.
    SO this gets me to thinking.... the mmkeys.dll is a valid windoze dll file. What would happen if we took the mmkeys.dll and renamed it to iTunesKeyboardCompatibility.dll?
    Alas.... SUCCESS!!!! At least for me on my machine. I can't speak for anyone else. Hope this helps guys.
    Dell inspiron 8500 Windows XP

  • Xmonad - Can't start any terminal emulator (xterm,urxvt,etc)

    Hi,
    I've recently installed Arch Linux in Virtualbox-OSE and also installed xmonad. It took me a while to get it running. It is all working fine and I can start all kinds of applications with MOD+Shift+P, but the only thing I can't do is start a terminal emulator such as xterm or urxvt. Neither with MOD+Shift+P and MOD+Shift+Return. When I do this I see a window flashing and I think it is the program I am trying to start but it is closing right after the startup.
    Does anybody recognize this problem or know how to fix it?
    Thanks,
    Webfp

    lifeafter2am wrote:Please post your xmoand.hs file and your xorg log.
    my xmonad.hs
    import XMonad
    import XMonad.Util.Replace
    import XMonad.Hooks.EwmhDesktops
    main = xmonad $ ewmh defaultConfig
    { terminal = "urxvt"
    , modMask = mod4Mask
    , borderWidth = 0
    xorg log
    [ 174.789]
    X.Org X Server 1.11.3
    Release Date: 2011-12-16
    [ 174.790] X Protocol Version 11, Revision 0
    [ 174.791] Build Operating System: Linux 3.1.5-1-ARCH i686
    [ 174.791] Current Operating System: Linux Laptop-Frank 3.1.8-1-ARCH #1 SMP PREEMPT Sat Jan 7 08:03:08 UTC 2012 i686
    [ 174.792] Kernel command line: root=/dev/disk/by-uuid/1b11e5e6-5760-4dbb-9d54-0c982c0a37a4 ro
    [ 174.794] Build Date: 17 December 2011 09:38:27AM
    [ 174.794]
    [ 174.795] Current version of pixman: 0.24.0
    [ 174.795] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 174.796] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 174.801] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jan 11 16:17:09 2012
    [ 174.883] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 174.928] (==) No Layout section. Using the first Screen section.
    [ 174.928] (==) No screen section available. Using defaults.
    [ 174.928] (**) |-->Screen "Default Screen Section" (0)
    [ 174.928] (**) | |-->Monitor "<default monitor>"
    [ 174.954] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 174.955] (==) Automatically adding devices
    [ 174.955] (==) Automatically enabling devices
    [ 175.021] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 175.021] Entry deleted from font path.
    [ 175.057] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 175.057] Entry deleted from font path.
    [ 175.057] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 175.059] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 175.059] Entry deleted from font path.
    [ 175.059] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 175.059] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 175.059] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 175.060] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 175.072] (II) Loader magic: 0x8228580
    [ 175.073] (II) Module ABI versions:
    [ 175.073] X.Org ANSI C Emulation: 0.4
    [ 175.073] X.Org Video Driver: 11.0
    [ 175.073] X.Org XInput driver : 13.0
    [ 175.073] X.Org Server Extension : 6.0
    [ 175.078] (--) PCI:*(0:0:2:0) 80ee:beef:0000:0000 rev 0, Mem @ 0xe0000000/16777216
    [ 175.079] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 175.079] (II) LoadModule: "extmod"
    [ 175.104] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 175.136] (II) Module extmod: vendor="X.Org Foundation"
    [ 175.136] compiled for 1.11.3, module version = 1.0.0
    [ 175.136] Module class: X.Org Server Extension
    [ 175.137] ABI class: X.Org Server Extension, version 6.0
    [ 175.137] (II) Loading extension MIT-SCREEN-SAVER
    [ 175.137] (II) Loading extension XFree86-VidModeExtension
    [ 175.137] (II) Loading extension XFree86-DGA
    [ 175.138] (II) Loading extension DPMS
    [ 175.138] (II) Loading extension XVideo
    [ 175.138] (II) Loading extension XVideo-MotionCompensation
    [ 175.138] (II) Loading extension X-Resource
    [ 175.139] (II) LoadModule: "dbe"
    [ 175.142] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 175.146] (II) Module dbe: vendor="X.Org Foundation"
    [ 175.146] compiled for 1.11.3, module version = 1.0.0
    [ 175.146] Module class: X.Org Server Extension
    [ 175.146] ABI class: X.Org Server Extension, version 6.0
    [ 175.146] (II) Loading extension DOUBLE-BUFFER
    [ 175.146] (II) LoadModule: "glx"
    [ 175.147] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 175.166] (II) Module glx: vendor="X.Org Foundation"
    [ 175.166] compiled for 1.11.3, module version = 1.0.0
    [ 175.166] ABI class: X.Org Server Extension, version 6.0
    [ 175.166] (==) AIGLX enabled
    [ 175.166] (II) Loading extension GLX
    [ 175.167] (II) LoadModule: "record"
    [ 175.169] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 175.172] (II) Module record: vendor="X.Org Foundation"
    [ 175.173] compiled for 1.11.3, module version = 1.13.0
    [ 175.173] Module class: X.Org Server Extension
    [ 175.173] ABI class: X.Org Server Extension, version 6.0
    [ 175.173] (II) Loading extension RECORD
    [ 175.173] (II) LoadModule: "dri"
    [ 175.174] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 175.205] (II) Module dri: vendor="X.Org Foundation"
    [ 175.205] compiled for 1.11.3, module version = 1.0.0
    [ 175.205] ABI class: X.Org Server Extension, version 6.0
    [ 175.205] (II) Loading extension XFree86-DRI
    [ 175.205] (II) LoadModule: "dri2"
    [ 175.207] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 175.210] (II) Module dri2: vendor="X.Org Foundation"
    [ 175.210] compiled for 1.11.3, module version = 1.2.0
    [ 175.210] ABI class: X.Org Server Extension, version 6.0
    [ 175.210] (II) Loading extension DRI2
    [ 175.211] (==) Matched vboxvideo as autoconfigured driver 0
    [ 175.211] (==) Matched vesa as autoconfigured driver 1
    [ 175.211] (==) Matched fbdev as autoconfigured driver 2
    [ 175.211] (==) Assigned the driver to the xf86ConfigLayout
    [ 175.211] (II) LoadModule: "vboxvideo"
    [ 175.247] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo.so
    [ 175.265] (II) Module vboxvideo: vendor="Oracle Corporation"
    [ 175.266] compiled for 1.5.99.901, module version = 1.0.1
    [ 175.266] Module class: X.Org Video Driver
    [ 175.266] ABI class: X.Org Video Driver, version 11.0
    [ 175.266] (**) Load address of symbol "VBOXVIDEO" is 0xb7396420
    [ 175.266] (II) LoadModule: "vesa"
    [ 175.268] (WW) Warning, couldn't open module vesa
    [ 175.268] (II) UnloadModule: "vesa"
    [ 175.269] (II) Unloading vesa
    [ 175.269] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 175.269] (II) LoadModule: "fbdev"
    [ 175.271] (WW) Warning, couldn't open module fbdev
    [ 175.271] (II) UnloadModule: "fbdev"
    [ 175.271] (II) Unloading fbdev
    [ 175.272] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 175.272] (II) VBoxVideo: guest driver for VirtualBox: vbox
    [ 175.273] (--) using VT number 7
    [ 175.301] (II) Loading /usr/lib/xorg/modules/drivers/vboxvideo.so
    [ 175.311] (II) VBoxVideo(0): VirtualBox guest additions video driver version 4.1.8_OSE
    [ 175.341] (II) Loading sub module "ramdac"
    [ 175.341] (II) LoadModule: "ramdac"
    [ 175.342] (II) Module "ramdac" already built-in
    [ 175.342] (II) Loading sub module "fb"
    [ 175.342] (II) LoadModule: "fb"
    [ 175.344] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 175.361] (II) Module fb: vendor="X.Org Foundation"
    [ 175.361] compiled for 1.11.3, module version = 1.0.0
    [ 175.362] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 175.362] (II) Loading sub module "shadowfb"
    [ 175.362] (II) LoadModule: "shadowfb"
    [ 175.370] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
    [ 175.378] (II) Module shadowfb: vendor="X.Org Foundation"
    [ 175.378] compiled for 1.11.3, module version = 1.0.0
    [ 175.379] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 175.379] (II) Loading sub module "vgahw"
    [ 175.379] (II) LoadModule: "vgahw"
    [ 175.379] (II) Loading /usr/lib/xorg/modules/libvgahw.so
    [ 175.383] (II) Module vgahw: vendor="X.Org Foundation"
    [ 175.383] compiled for 1.11.3, module version = 0.1.0
    [ 175.383] ABI class: X.Org Video Driver, version 11.0
    [ 175.383] (II) Loading sub module "dri"
    [ 175.383] (II) LoadModule: "dri"
    [ 175.384] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 175.384] (II) Module dri: vendor="X.Org Foundation"
    [ 175.384] compiled for 1.11.3, module version = 1.0.0
    [ 175.384] ABI class: X.Org Server Extension, version 6.0
    [ 175.384] (II) VBoxVideo(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 175.385] (==) VBoxVideo(0): Depth 24, (--) framebuffer bpp 32
    [ 175.385] (--) VBoxVideo(0): Virtual size is 32000x32000 (pitch 32000)
    [ 175.385] (**) VBoxVideo(0): Built-in mode "VBoxInitialMode": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
    [ 175.385] (II) VBoxVideo(0): Modeline "VBoxInitialMode"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
    [ 175.385] (**) VBoxVideo(0): Built-in mode "VBoxDynamicMode": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
    [ 175.385] (II) VBoxVideo(0): Modeline "VBoxDynamicMode"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
    [ 175.385] (**) VBoxVideo(0): Built-in mode "VBoxDynamicMode": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
    [ 175.386] (II) VBoxVideo(0): Modeline "VBoxDynamicMode"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
    [ 175.386] (**) VBoxVideo(0): Built-in mode "VBox-1024x768": 47.8 MHz (scaled from 0.0 MHz), 46.4 kHz, 60.0 Hz
    [ 175.386] (II) VBoxVideo(0): Modeline "VBox-1024x768"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
    [ 175.386] (**) VBoxVideo(0): Built-in mode "VBox-800x600": 29.3 MHz (scaled from 0.0 MHz), 36.4 kHz, 60.0 Hz
    [ 175.386] (II) VBoxVideo(0): Modeline "VBox-800x600"x0.0 29.31 800 802 804 806 600 602 604 606 (36.4 kHz)
    [ 175.386] (**) VBoxVideo(0): Built-in mode "VBox-640x480": 18.8 MHz (scaled from 0.0 MHz), 29.2 kHz, 60.0 Hz
    [ 175.386] (II) VBoxVideo(0): Modeline "VBox-640x480"x0.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz)
    [ 175.389] (II) VBoxVideo(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
    [ 175.389] (==) VBoxVideo(0): RGB weight 888
    [ 175.389] (==) VBoxVideo(0): Default visual is TrueColor
    [ 175.389] (==) VBoxVideo(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 175.390] (==) VBoxVideo(0): DPI set to (96, 96)
    [ 175.390] (--) Depth 24 pixmap format is 32 bpp
    [ 175.820] drmOpenDevice: node name is /dev/dri/card0
    [ 175.821] drmOpenDevice: open result is 13, (OK)
    [ 175.828] drmOpenDevice: node name is /dev/dri/card0
    [ 175.829] drmOpenDevice: open result is 13, (OK)
    [ 175.829] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 175.829] drmOpenDevice: node name is /dev/dri/card0
    [ 175.829] drmOpenDevice: open result is 13, (OK)
    [ 175.829] drmOpenByBusid: drmOpenMinor returns 13
    [ 175.829] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 175.830] (II) [drm] DRM interface version 1.4
    [ 175.830] (II) [drm] DRM open master succeeded.
    [ 175.830] (II) VBoxVideo(0): [drm] Using the DRM lock SAREA also for drawables.
    [ 175.830] (II) VBoxVideo(0): [drm] framebuffer handle = 0xe0000000
    [ 175.831] (II) VBoxVideo(0): [drm] added 1 reserved context for kernel
    [ 175.831] (II) VBoxVideo(0): X context handle = 0x1
    [ 175.835] (II) VBoxVideo(0): [drm] installed DRM signal handler
    [ 175.836] (II) VBoxVideo(0): visual configurations initialized
    [ 175.845] (II) VBoxVideo(0): Requested monitor count: 1
    [ 175.845] (II) VBoxVideo(0): Output VBOX0 has no monitor section
    [ 175.845] (II) VBoxVideo(0): Output VBOX0 has no monitor section
    [ 175.846] (II) VBoxVideo(0): EDID for output VBOX0
    [ 175.846] (II) VBoxVideo(0): Manufacturer: VBX Model: 0 Serial#: 50332672
    [ 175.846] (II) VBoxVideo(0): Year: 1990 Week: 1
    [ 175.846] (II) VBoxVideo(0): EDID Version: 1.3
    [ 175.846] (II) VBoxVideo(0): Digital Display Input
    [ 175.846] (II) VBoxVideo(0): Indeterminate output size
    [ 175.846] (II) VBoxVideo(0): Gamma: 2.20
    [ 175.846] (II) VBoxVideo(0): DPMS capabilities: StandBy Suspend Off
    [ 175.847] (II) VBoxVideo(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 175.847] (II) VBoxVideo(0): Default color space is primary color space
    [ 175.847] (II) VBoxVideo(0): First detailed timing is preferred mode
    [ 175.847] (II) VBoxVideo(0): redX: 0.640 redY: 0.330 greenX: 0.300 greenY: 0.600
    [ 175.847] (II) VBoxVideo(0): blueX: 0.150 blueY: 0.060 whiteX: 0.312 whiteY: 0.329
    [ 175.847] (II) VBoxVideo(0): Manufacturer's mask: 0
    [ 175.847] (II) VBoxVideo(0): Supported detailed timing:
    [ 175.847] (II) VBoxVideo(0): clock: 47.8 MHz Image Size: 0 x 0 mm
    [ 175.847] (II) VBoxVideo(0): h_active: 1024 h_sync: 1026 h_sync_end 1028 h_blank_end 1030 h_border: 0
    [ 175.848] (II) VBoxVideo(0): v_active: 768 v_sync: 770 v_sync_end 772 v_blanking: 774 v_border: 0
    [ 175.848] (II) VBoxVideo(0): Ranges: V min: 0 V max: 200 Hz, H min: 0 H max: 200 kHz, PixClock max 1005 MHz
    [ 175.848] (II) VBoxVideo(0): Monitor name: VBOX monitor
    [ 175.848] (II) VBoxVideo(0): EDID (in hex):
    [ 175.848] (II) VBoxVideo(0): 00ffffffffffff005858000000040003
    [ 175.848] (II) VBoxVideo(0): 0100010380000078eeee91a3544c9926
    [ 175.848] (II) VBoxVideo(0): 0f505400000001010101010101010101
    [ 175.848] (II) VBoxVideo(0): 010101010101af120006400006300202
    [ 175.848] (II) VBoxVideo(0): 2200000000000000000000fd0000c800
    [ 175.848] (II) VBoxVideo(0): c864000a202020202020000000fc0056
    [ 175.849] (II) VBoxVideo(0): 424f58206d6f6e69746f720a00000010
    [ 175.849] (II) VBoxVideo(0): 000a20202020202020202020202000fb
    [ 175.849] (II) VBoxVideo(0): EDID vendor "VBX", prod id 0
    [ 175.849] (II) VBoxVideo(0): DDCModeFromDetailedTiming: 1024x768 Warning: We only handle separate sync.
    [ 175.849] (II) VBoxVideo(0): Using hsync ranges from config file
    [ 175.849] (II) VBoxVideo(0): Using vrefresh ranges from config file
    [ 175.849] (II) VBoxVideo(0): Printing DDC gathered Modelines:
    [ 175.850] (II) VBoxVideo(0): Modeline "1024x768"x0.0 47.83 1024 1026 1028 1030 768 770 772 774 -hsync -vsync (46.4 kHz)
    [ 175.851] (II) VBoxVideo(0): Printing probed modes for output VBOX0
    [ 175.851] (II) VBoxVideo(0): Modeline "1024x768"x60.0 47.83 1024 1026 1028 1030 768 770 772 774 (46.4 kHz)
    [ 175.851] (II) VBoxVideo(0): Modeline "800x600"x60.0 29.31 800 802 804 806 600 602 604 606 (36.4 kHz)
    [ 175.851] (II) VBoxVideo(0): Modeline "640x480"x60.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz)
    [ 175.851] (II) VBoxVideo(0): Output VBOX0 connected
    [ 175.852] (II) VBoxVideo(0): Using exact sizes for initial modes
    [ 175.852] (II) VBoxVideo(0): Output VBOX0 using initial mode 1024x768
    [ 175.852] (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 175.852] (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 175.856] (==) VBoxVideo(0): DPMS enabled
    [ 175.857] (II) VBoxVideo(0): [DRI] installation complete
    [ 175.857] (--) RandR disabled
    [ 175.857] (II) Initializing built-in extension Generic Event Extension
    [ 175.857] (II) Initializing built-in extension SHAPE
    [ 175.857] (II) Initializing built-in extension MIT-SHM
    [ 175.857] (II) Initializing built-in extension XInputExtension
    [ 175.857] (II) Initializing built-in extension XTEST
    [ 175.857] (II) Initializing built-in extension BIG-REQUESTS
    [ 175.857] (II) Initializing built-in extension SYNC
    [ 175.857] (II) Initializing built-in extension XKEYBOARD
    [ 175.857] (II) Initializing built-in extension XC-MISC
    [ 175.858] (II) Initializing built-in extension SECURITY
    [ 175.858] (II) Initializing built-in extension XINERAMA
    [ 175.858] (II) Initializing built-in extension XFIXES
    [ 175.858] (II) Initializing built-in extension RENDER
    [ 175.858] (II) Initializing built-in extension RANDR
    [ 175.858] (II) Initializing built-in extension COMPOSITE
    [ 175.858] (II) Initializing built-in extension DAMAGE
    [ 175.887] (II) AIGLX: Screen 0 is not DRI2 capable
    [ 175.887] drmOpenDevice: node name is /dev/dri/card0
    [ 175.887] drmOpenDevice: open result is 14, (OK)
    [ 175.888] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [ 175.888] drmOpenDevice: node name is /dev/dri/card0
    [ 175.888] drmOpenDevice: open result is 14, (OK)
    [ 175.888] drmOpenByBusid: drmOpenMinor returns 14
    [ 175.888] drmOpenByBusid: Interface 1.4 failed, trying 1.1
    [ 175.888] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [ 176.017] (II) Next line is added to allow vboxvideo_drv.so to appear as whitelisted driver
    [ 176.017] (II) The file referenced, is *NOT* loaded
    [ 176.017] (II) Loading /usr/lib/xorg/modules/drivers//ati_drv.so
    [ 176.017] (EE) AIGLX error: vboxvideo does not export required DRI extension
    [ 176.019] (EE) AIGLX: reverting to software rendering
    [ 176.437] (II) AIGLX: Loaded and initialized swrast
    [ 176.437] (II) GLX: Initialized DRISWRAST GL provider for screen 0
    [ 176.442] (II) VBoxVideo(0): Setting screen physical size to 270 x 203
    [ 176.899] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 176.899] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 176.899] (II) LoadModule: "evdev"
    [ 176.901] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 176.935] (II) Module evdev: vendor="X.Org Foundation"
    [ 176.935] compiled for 1.10.99.902, module version = 2.6.0
    [ 176.935] Module class: X.Org XInput Driver
    [ 176.935] ABI class: X.Org XInput driver, version 13.0
    [ 176.935] (II) Using input driver 'evdev' for 'Power Button'
    [ 176.935] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 176.935] (**) Power Button: always reports core events
    [ 176.935] (**) Power Button: Device: "/dev/input/event3"
    [ 176.936] (--) Power Button: Found keys
    [ 176.936] (II) Power Button: Configuring as keyboard
    [ 176.936] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 176.936] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 176.936] (**) Option "xkb_rules" "evdev"
    [ 176.936] (**) Option "xkb_model" "evdev"
    [ 176.936] (**) Option "xkb_layout" "us"
    [ 177.050] (II) config/udev: Adding input device Sleep Button (/dev/input/event4)
    [ 177.050] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 177.050] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 177.050] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 177.050] (**) Sleep Button: always reports core events
    [ 177.051] (**) Sleep Button: Device: "/dev/input/event4"
    [ 177.051] (--) Sleep Button: Found keys
    [ 177.051] (II) Sleep Button: Configuring as keyboard
    [ 177.051] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSLPBN:00/input/input4/event4"
    [ 177.051] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 7)
    [ 177.051] (**) Option "xkb_rules" "evdev"
    [ 177.051] (**) Option "xkb_model" "evdev"
    [ 177.051] (**) Option "xkb_layout" "us"
    [ 177.055] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/event1)
    [ 177.055] (**) VirtualBox USB Tablet: Applying InputClass "evdev pointer catchall"
    [ 177.055] (II) Using input driver 'evdev' for 'VirtualBox USB Tablet'
    [ 177.055] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 177.055] (**) VirtualBox USB Tablet: always reports core events
    [ 177.055] (**) VirtualBox USB Tablet: Device: "/dev/input/event1"
    [ 177.056] (--) VirtualBox USB Tablet: Found 9 mouse buttons
    [ 177.056] (--) VirtualBox USB Tablet: Found scroll wheel(s)
    [ 177.056] (--) VirtualBox USB Tablet: Found relative axes
    [ 177.056] (--) VirtualBox USB Tablet: Found absolute axes
    [ 177.057] (--) VirtualBox USB Tablet: Found x and y absolute axes
    [ 177.057] (II) VirtualBox USB Tablet: Configuring as mouse
    [ 177.057] (II) VirtualBox USB Tablet: Adding scrollwheel support
    [ 177.057] (**) VirtualBox USB Tablet: YAxisMapping: buttons 4 and 5
    [ 177.057] (**) VirtualBox USB Tablet: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 177.057] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:06.0/usb1/1-1/1-1:1.0/input/input1/event1"
    [ 177.057] (II) XINPUT: Adding extended input device "VirtualBox USB Tablet" (type: MOUSE, id 8)
    [ 177.057] (EE) VirtualBox USB Tablet: failed to initialize for relative axes.
    [ 177.058] (II) VirtualBox USB Tablet: initialized for absolute axes.
    [ 177.058] (**) VirtualBox USB Tablet: (accel) keeping acceleration scheme 1
    [ 177.058] (**) VirtualBox USB Tablet: (accel) acceleration profile 0
    [ 177.058] (**) VirtualBox USB Tablet: (accel) acceleration factor: 2.000
    [ 177.058] (**) VirtualBox USB Tablet: (accel) acceleration threshold: 4
    [ 177.060] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/js0)
    [ 177.060] (II) No input driver/identifier specified (ignoring)
    [ 177.062] (II) config/udev: Adding input device VirtualBox USB Tablet (/dev/input/mouse0)
    [ 177.063] (II) No input driver/identifier specified (ignoring)
    [ 177.065] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 177.065] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 177.065] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 177.066] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 177.066] (**) AT Translated Set 2 keyboard: always reports core events
    [ 177.066] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 177.066] (--) AT Translated Set 2 keyboard: Found keys
    [ 177.066] (II) AT Translated Set 2 keyboard: Configuring as keyboard
    [ 177.066] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 177.066] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
    [ 177.066] (**) Option "xkb_rules" "evdev"
    [ 177.067] (**) Option "xkb_model" "evdev"
    [ 177.067] (**) Option "xkb_layout" "us"
    [ 177.070] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/event5)
    [ 177.070] (**) ImExPS/2 Generic Explorer Mouse: Applying InputClass "evdev pointer catchall"
    [ 177.070] (II) Using input driver 'evdev' for 'ImExPS/2 Generic Explorer Mouse'
    [ 177.070] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 177.070] (**) ImExPS/2 Generic Explorer Mouse: always reports core events
    [ 177.070] (**) ImExPS/2 Generic Explorer Mouse: Device: "/dev/input/event5"
    [ 177.070] (--) ImExPS/2 Generic Explorer Mouse: Found 9 mouse buttons
    [ 177.071] (--) ImExPS/2 Generic Explorer Mouse: Found scroll wheel(s)
    [ 177.071] (--) ImExPS/2 Generic Explorer Mouse: Found relative axes
    [ 177.071] (--) ImExPS/2 Generic Explorer Mouse: Found x and y relative axes
    [ 177.071] (II) ImExPS/2 Generic Explorer Mouse: Configuring as mouse
    [ 177.071] (II) ImExPS/2 Generic Explorer Mouse: Adding scrollwheel support
    [ 177.071] (**) ImExPS/2 Generic Explorer Mouse: YAxisMapping: buttons 4 and 5
    [ 177.071] (**) ImExPS/2 Generic Explorer Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 177.071] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input5/event5"
    [ 177.071] (II) XINPUT: Adding extended input device "ImExPS/2 Generic Explorer Mouse" (type: MOUSE, id 10)
    [ 177.072] (II) ImExPS/2 Generic Explorer Mouse: initialized for relative axes.
    [ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) keeping acceleration scheme 1
    [ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration profile 0
    [ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration factor: 2.000
    [ 177.072] (**) ImExPS/2 Generic Explorer Mouse: (accel) acceleration threshold: 4
    [ 177.074] (II) config/udev: Adding input device ImExPS/2 Generic Explorer Mouse (/dev/input/mouse1)
    [ 177.074] (II) No input driver/identifier specified (ignoring)
    [ 177.077] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
    [ 177.078] (II) No input driver/identifier specified (ignoring)
    [ 177.082] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/event2)
    [ 177.082] (**) VirtualBox mouse integration: Applying InputClass "evdev pointer catchall"
    [ 177.082] (II) Using input driver 'evdev' for 'VirtualBox mouse integration'
    [ 177.082] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 177.082] (**) VirtualBox mouse integration: always reports core events
    [ 177.082] (**) VirtualBox mouse integration: Device: "/dev/input/event2"
    [ 177.083] (--) VirtualBox mouse integration: Found 1 mouse buttons
    [ 177.083] (--) VirtualBox mouse integration: Found absolute axes
    [ 177.083] (--) VirtualBox mouse integration: Found x and y absolute axes
    [ 177.083] (II) VirtualBox mouse integration: Configuring as mouse
    [ 177.083] (**) VirtualBox mouse integration: YAxisMapping: buttons 4 and 5
    [ 177.083] (**) VirtualBox mouse integration: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 177.084] (**) Option "config_info" "udev:/sys/devices/virtual/input/input2/event2"
    [ 177.084] (II) XINPUT: Adding extended input device "VirtualBox mouse integration" (type: MOUSE, id 11)
    [ 177.084] (II) VirtualBox mouse integration: initialized for absolute axes.
    [ 177.084] (**) VirtualBox mouse integration: (accel) keeping acceleration scheme 1
    [ 177.084] (**) VirtualBox mouse integration: (accel) acceleration profile 0
    [ 177.084] (**) VirtualBox mouse integration: (accel) acceleration factor: 2.000
    [ 177.084] (**) VirtualBox mouse integration: (accel) acceleration threshold: 4
    [ 177.086] (II) config/udev: Adding input device VirtualBox mouse integration (/dev/input/js1)
    [ 177.086] (II) No input driver/identifier specified (ignoring)
    BTW it was a real hassle to find the content of those files when you do not have a terminal emulator to use.

  • Sonata and Multimedia Keys (Gnome)

    I've just started using sonata again (was using amarok) and I can't make my multimedia keys work properly with it It was supposed to be fixed a few versions ago but with 1.5.1, 1.5.2 and SVN I can't make it work. However If I go into keyboard shortcuts and set the keys again it all works perfectly but I have to do it again every time I restart my computer. Anyone else got this problem?

    @tacticalbread: thanks for the config, but that didn't solve the issue.
    @invalidArgument597: no, I've tried both, still nothing.
    EDIT: Ok, it's solved now.  I commented out the lines right before the XF86 bindings and it automagically started working.  I guess the lines before XF86 bindings were somehow problematic!
    These are the lines that I commented out/removed:
    rodentbane.bind({ modkey, "Control" }, "m", function() rodentbane.stop() end),
    -- move mouse to bottom-right corner because it's just annoying!
    awful.key({ modkey, "Control", "Shift" }, "m", function() move_mouse_out() end),
    mod+ctrl+m was already assigned to rodentbane previously, so maybe reassigning it was the problem.
    Thanks for the help!
    Last edited by amoradi (2011-07-09 06:43:54)

  • N95 multimedia key stuck?

    Hello, I recently purchased a 2nd hand N95 8GB. At first it seemed to work quite finely however after a day or two the multimedia key (that useless key located to the left of directional keys) started playing up by just randomly pressing itself. Most of the time it works normally and then completely at random it will start playing up, entering my music folder and playing songs. I've tried updating to the latest firmware, restoring it to factory setting and erasing everything off of it but to no avail. The key itself isn't physically stuck in any way. I think the phone was originally locked to a network, but it was then unlocked and had Nokia's firmware installed on it. If someone could help get this fixed I would really appreciate it. Thanks.

    It's a hardware issue, most likely a failed or damaged (drop/shock/moisture) component.
    Take it to a nokia care point for inspection.
    Care points/service centres and repair info:
    UK • Europe • Asia-Pacific • USA •
    Canada • Middle East and Africa
    Elsewhere: Click here, select your country, go to the support section, then select repair. 

  • G500 - switch functionality of Multimedia keys with F1-F12?

    Hi all.
    I have just bought the G500 and I'm getting really annoyed by the keyboard. 
    It has "great" multimedia keys as the main keys instead of usual F1-F12 keys. To access their functionality you must press Fn+appropriate key. The problem has been described here many times. But no solution works for G500.
    I have tried: 
    enter BIOS (no such option for keyboard)
    install Lenovo Slim USB Keyboard application (runs, but the option selected have no effect)
    install Lenovo Ultraslim Plus Wireless Keyboard & Mouse Driver application (do not run at all - just brings me to the desktop and do nothing)
    I'm wondering if someone experience such problems too, and if there is some solution. I'm not able to use the computer since I use a lot of application depending on the functional keys and if there is no solution I will have to buy another computer, and it would not be Lenovo anymore as this really disappointed me:-(.
    Btw: does anyone at all really like new keyboard?
    Thanks,
    Michal Linhart
    Solved!
    Go to Solution.

    hi Zoka17,
    You concern might be similar to this thread
        http://forums.lenovo.com/t5/IdeaPad-Y-U-V-Z-and-P-series/How-do-I-invert-the-F-keys-and-the-Fn-keys-...
    If you don't have the setting in the BIOS under Configuration TAB named "Hotkey"
    then I'm afraid on that thread they had to use a Software to remap few of the FN keys and reverse it.
     I'm not sure how or if this will help, but give it a try,
    Best regards
    Solid Cruver
    Did someone help you today? Press the star on the left to thank them with a Kudo!
    If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
    Follow @LenovoForums on Twitter!

  • Is there a terminal emulator with up- down output?

    The idea just hit me but it's very hard to find something in search or on google (up and down are popular keywords...).
    Here's my idea: the terminal I use (urxvt) and every other I heard of always outputs text sort of 'upwards'. Meaning: the prompt line is mostly on the bottom (and if you use a tiling wm like me it's mostly on the bottom of the screen), well except for new terminal windows of course.
    I thought it would be cool if it could be on the top of the screen and the lines would be output towards the bottom of the window. Get it? If you would take a normal terminal window and reverse the lines order, this would be exactly what I need.
    Quick example:
    A normal terminal
    [user@desktop]: ls -l
    drwxr-xr-x 5 user user 4096 Jan 17 12:53 dir1
    lrwxrwxrwx 1 user user 30 Dec 23 17:14 a-link
    drwxr-xr-x 2 user user 4096 Feb 10 13:26 dir2
    [user@desktop]: _
    What I would like
    [user@desktop]: _
    drwxr-xr-x 5 user user 4096 Jan 17 12:53 dir1
    lrwxrwxrwx 1 user user 30 Dec 23 17:14 a-link
    drwxr-xr-x 2 user user 4096 Feb 10 13:26 dir2
    [user@desktop]: ls -l
    Get it? Top -> down! So the prompt always gravitates toward the top of the window (provided enough output of course)
    So anyway, back to the question: is there a terminal emulator that can do it?
    Last edited by kosmiciatakuja (2011-03-14 10:47:55)

    lives2evil wrote:Interesting idea!
    But no, as far as I know there's no such things.
    Any if you think it a little further, it's a trouble some idea. You may not notice with a simple "ls" command but with something more complex trouble will pop up every where.
    How about you try and think how exactly will you implemented this idea.
    Could be fun (Tried it).
    Heh yea, i just did the same and came to the same conclusions.

  • How can I stop iTunes from using my multimedia keys on my keyboard?

    I use the multimedia keys on my keyboard for WinAmp, which is my primary music player.  When iTunes is open it hijacks every one of them.  WinAmp has options to enable and disable the use of global hotkeys and multimedia keys.  iTunes does not seem to.  Is there really no way to get iTunes to stop taking control of my keys?  I am using Windows 7 Home Premium 64 bit, for the record.

    Yep.  Don't manually manage.

  • SAP GUI Memory issues on Windows Terminal Server 2003!!

    Hi All
    We are currently experiencing serious issues with our terminal servers and SAP GUI. It appears that SAP GUI is consuming a large amount of memory inorder to run, which in term is causing our terminal servers to page more.
    I am not sure where to start with this issue so any help would be great!
    Thanks
    Phil
    Loads of points if someone helps me solve this!!!

    Citrix won´t help much, it´s "just" a different protocol between the client and the server, Citrix itself will use even more memory.
    Why are you sure, that the reason for this is the SAPGUI and not any other Office program?
    Let´s calculate:
    I´m writing this message on a TS too. My Outlook (2003) consumes ~ 32 MB memory (incl. virtual), I have 4 SAPGUI windows open which consume 64 MB and some telnet sessions (no Word, Excel etc.)
    Let say roughly 128 MB all in all.
    If you have 2000 users with 20 servers, means, 100 users on one server, that would be 12,8 GB memory - not caclulated other services running on that box (printserver etc.) including the operating system itself.
    If your users have Internet Explorer (or other browsers) open too, you will need to add that amount too. 128 MB per user is the minimum.
    If users use BEx (or other .NET based BI developer tools), that amount will doubled (at least).
    SAP recommends a PC with at least 256 MB memory to run a SAPGUI with acceptable performance, do you have that much per users? How big are your single servers?
    Markus

Maybe you are looking for