Awesome desktop environment & terminator terminal-emulator problem.

awsome version v3.5
terminator version 0.97
When you want to change the size of the window, it usually goes volatile without control (the size of the window changes every now and then, bigger or smaller).
Is there anyone have the same problem like me ?
I emailed the author of terminator and be told that this kind of bug has been fix in version 0.97

zezhyrule3 wrote:
Don't use terminator
Is there really any reason to if you have a tiling window manager?
well, I've used to this terminal already ...
and other terminal emulators are neither too big nor support CJK fonts well ...

Similar Messages

  • Awesome desktop environment?

    Is there any desktop environment that encorporates the awesome window manager? Or a tiling window manager?

    Guff wrote:
    louis058 wrote:The problem is that by itself, Awesome misses a lot of features, most important for me is a shutdown/reboot utility. The Awesome documentation also doesn't seem to offer a way of integrating with PolicyKit. It would take a lot of work figuring it out by myself when I have zero knowledge of policykit, and little documentation from Awesome itself.
    There's actually an example on the awesome wiki.
    What I do is different, though:
    local lock = "slimlock"
    local ck = "dbus-send --system --print-reply --dest=\"org.freedesktop.ConsoleKit\" "
    .. "/org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager."
    local suspend = "dbus-send --system --print-reply --dest=\"org.freedesktop.UPower\" "
    .. "/org/freedesktop/UPower org.freedesktop.UPower.Suspend"
    local logoutmenu = {
    { "Shutdown", ck .. "Stop", freedesktop.utils.lookup_icon({ icon = 'system-shutdown' }) },
    { "Reboot", ck .. "Restart", freedesktop.utils.lookup_icon({ icon = 'gtk-refresh' }) },
    { "Suspend", suspend, freedesktop.utils.lookup_icon({ icon = 'media-playback-pause' }) },
    { "Lock screen", lock, freedesktop.utils.lookup_icon({ icon = 'system-lock-screen' }) },
    { "Log out", awesome.quit, freedesktop.utils.lookup_icon({ icon = 'system-log-out' }) },
    Then just add logoutmenu to your myawesomemenu table, and replace lock with whatever screenlocker you use. Or remove the "Lock screen" entry from the table if you don't use one.
    If you don't have awesome-freedesktop-git installed, just remove the freedesktop.utils.lookup_icon parts. I just like having icons on everything.
    Screenshot: http://ompldr.org/tOTJ0Ng
    This is the exact tutorial that I found on the wiki for implementing a shutdown menu. I may be wrong though, but I assumed that it needed a password to be used since it uses gksu.
    Sorry everyone, I just went and assumed doing it with policykit would be difficult, since there aren't any tutorials for it. I shall look into it by myself.

  • Vi editor and terminal emulation problem

    After installing Solaris 2.6 with the current recommended patches I am getting inconsistent results when attempting to use the vi editor. With the TERM=xterm or sun or the first 14 lines of a file are NOT displayed. If TERM=vt100 the system functions properly. I have other Solaris 2.6 systems where this is not an issue.
    In other words on a "good" system TERM=xterm and the vi editor functions properly.
    What am I missing?

    Looks like this is caused by kernel patch 105181-34. Check SunSolve for bug 4843340 and Sun Alert 53590. Current workarounds:
    when you open xterm run :
    #eval `/usr/openwin/bin/resize`
    This command works for sh. You have to rerun resize each time you resize your window, or open an new xterm.
    Take a /kernel/strmod/ptem binary from a system with an earlier patch revision.
    Wait for 105181-35 to be released.

  • Terminal Color emulation problems (emacs)

    I'm trying to use emacs for a C course I'm taking in college, and my goal is to configure it like a fully functional IDE. So far I'm at color problems.
    I've installed the color-themes package along with cc-mode, and some text/background combinations aren't being emulated correctly. For example, certain bold things have the same foreground and background colors, such as file names and other stuff. I've been having more problems with other color emulation too, like servers that use color emulation for ls to show different types of files.
    Also, I can't seem to use control+meta at the same time, it just uses meta.
    My terminal is set to xterm-color
    Here are some images demonstrating the problem:
    http://users.wpi.edu/~zm/emacs-colors1.jpg
    http://users.wpi.edu/~zm/emacs-colors2.jpg
    Here is my .emacs file :
    (custom-set-variables
    ;; custom-set-variables was added by Custom -- don't edit or cut/paste it!
    ;; Your init file should contain only one such instance.
    '(case-fold-search t)
    '(current-language-environment "English"))
    (custom-set-faces
    ;; custom-set-faces was added by Custom -- don't edit or cut/paste it!
    ;; Your init file should contain only one such instance.
    ;; add ~/emacs-libs to load path
    (setq load-path (cons "~/emacs-libs" load-path))
    (progn (cd "~/emacs-libs") (normal-top-level-add-subdirs-to-load-path))
    (progn (cd "~/"))
    ;; load color-theme library and start color-theme-andreas
    (global-font-lock-mode t 1)
    (font-lock-mode)
    (load-library "color-theme")
    (color-theme-initialize)
    (color-theme-andreas)
    ;; load line number mode
    (require 'linum)
    ;; Create my personal style.
    (defconst my-c-style
    '((c-cleanup-list . (brace-else-brace
    brace-elsif-brace
    brace-catch-brace
    empty-defun-braces
    defun-close-semi
    list-close-comma))
    "My C Programming Style")
    (c-add-style "PERSONAL" my-c-style)
    ;; Customizations for all modes in CC Mode.
    (defun my-c-mode-common-hook ()
    ;; set my personal style for the current buffer
    (c-set-style "PERSONAL"))
    ;; Customizations for all modes in CC Mode.
    (add-hook 'c-mode-common-hook 'my-c-mode-common-hook)

    Are you using the emacs that Apple provides in Terminal? The one in /usr/bin?
    If so, perhaps you would be happier with an emacs that understands the idea of having its own windows?
    Two ways to do that...
    1) Use X windows, and install an emacs that understands X windows
    2) Find one of the versions of emacs that has been taught to understand Aqua, i.e., that works within the Finder/Desktop environment.
    Of the latter, I think there are couple out there on the web, Aquamacs Emacs and Carbon Emacs (but I don't keep carefull track, so I'm not sure).
    For the former, it's a bit more work to find and install such an emacs. One possibility is the "fink" package management system.

  • My awesome WM(desktop environment) with sound problem!

    I'm a newer to awesome .there's only one window manager awesome in my linux without any desktop environment(KDE GNOME...) or  display manager(gdm kdm...etc) ,but I encountered a problem :  there's no sound when playing music  in the awesome environment ,but it sounds  when switch to  anoter tty  on which the user of awesome DE has logined.
    It's really strange.... beg for help .
    Here's my rc.lua  about  volume:
    vicious = require("vicious")
    volumewidget = widget({ type = "textbox"})
    volumewidget:buttons(awful.util.table.join(
    --    awful.button({ }, 1, function () awful.util.spawn("amixer -q set Master toggle", false) end),
        awful.button({ }, 2, function () awful.util.spawn("xterm -e alsamixer", true)      end)
    --    awful.button({ }, 4, function () awful.util.spawn("amixer -q set Master 2dB+", false) end),
    --    awful.button({ }, 5, function () awful.util.spawn("amixer -q set Master 2dB-", false) end)
    vicious.register(volumewidget, vicious.widgets.volume," $1% ", 2, "Capture")
    supplement :   I entered awesoem DE by   typing in : /bin/su will -l -c "/bin/bash --login -c xinit" (issue "startx" makes no difference) in tty1,  then  awesome startup  on another tty (tty2 ,tty7 e.g.).   
    Here's the  processes after login in awesome:
    [will@will-laptop ~]$ pstree
    systemd─┬─NetworkManager─┬─dhclient
            │                └─3*[{NetworkManager}]
            ├─4*[agetty]
            ├─atd
            ├─auditd─┬─audispd─┬─sedispatch
            │        │         └─{audispd}
            │        └─{auditd}
            ├─chrome─┬─chrome
            │        ├─chrome-sandbox───chrome─┬─chrome─┬─10*[chrome───3*[{chrome}]]
            │        │                         │        └─chrome───12*[{chrome}]
            │        │                         └─nacl_helper_boo
            │        └─25*[{chrome}]
            ├─chronyd
            ├─crond
            ├─2*[dbus-daemon]
            ├─dbus-launch
            ├─login───bash───su───xinit─┬─X
            │                           └─awesome
            ├─login───bash
            ├─mcelog
            ├─modem-manager
            ├─polkitd───{polkitd}
            ├─pulseaudio───2*[{pulseaudio}]
            ├─roxterm─┬─bash───sudo───vi
            │         ├─bash───pstree
            │         ├─gnome-pty-helpe
            │         └─{roxterm}
            ├─rsyslogd───3*[{rsyslogd}]
            ├─rtkit-daemon───2*[{rtkit-daemon}]
            ├─system-setup-ke
            ├─systemd-journal
            ├─systemd-logind
            ├─udevd───2*[udevd]
            └─wpa_supplicant

    Well, if you don't necessarily need pulseaudio, I'd just uninstall it. I've never had any problems with alsa and awesome wm. However, if you need pulseaudio, like I did, then some applications are going to throw errors. Is the sound muted for any sound or just when you use a specific application? If its all applications, try just using alsa and see if the problem persists. If its a specific application, you might not be able to do anything about it depending on the application. Either way, install pavucontrol, which is a great gui for pulseaudio. You might notice that the channel is muted or something else through pavucontrol. Check that dbus is started in the daemons in /etc/rc.conf. Check the troubleshooting section here: https://wiki.archlinux.org/index.php/Pu … figuration.

  • [SOLVED] Tmux in terminal emulator having strange effect on X session

    Hello. I've searched about and googled for this problem for a while, but to no avail. The problem is this:
    When in an X session, in the Awesome WM, when I fire up a terminal emulator (so far I tried lxterminal, xterm, urxvt and lilyterm), the console (from before the X session) appears with the X startup messages and it's stuck that way. I'm still in the WM however and the mouse shows. I just can't see anything past that console screen. I can't see any error messages thereon either.
    When not in Awesome (and X), tmux starts up fine, and also when in Awesome and I run
    sudo tmux
    in the terminal emulators.
    I first encountered this some time ago, using just lilyterm, but then I tried running tmux in lxterminal instead and it worked fine. Now this always happens, no matter the terminal. Right before this incident, I was doing some experiments with running a detached tmux session on login. I tried executing in .bash_profile, .bashrc, .xinitrc and .config/awesome/rc.lua. Since this started happening at some point, I'm not sure when, I tried some different files. Now I have removed what I put in them but this behavior keeps occurring. I've tried to make sure the $TERM variable is set right inside and outside tmux for some of them and
    set -g default-terminal "screen/screen-color256"
    in the .tmux.conf.
    I sync my config files between my laptop and desktop so they have the same behavior, except on the desktop the console screen flashes momentarily and then all GUI programs have disappeared from the screen, leaving just bare Awesome. I can then start some more GUI programs again. If I try to start tmux again in another terminal emulator. I get the "nested tmux sessions" message.
    I don't know if it matters, but using screen instead works as intended. Anyway, any help is appreciated. My tmux.conf is really just
    set -g default-terminal "screen"
    at the moment.
    Last edited by m73 (2013-07-22 12:06:03)

    Tried the same in Openbox instead of Awesome and I get the same behavior. I also made a tmux session before starting X and attached it in the terminal emulator afterwards. That worked, but when I try to make a new window in that session with Ctrl-b C, the same thing happens. So this happens if I try to make new sessions or windows as the current user in an X session. Listing and killing sessions works as intended.

  • Cannot access desktop environment, neither gnome nor awesome

    Hi All,
    My Archlinux has been installed for a while when suddenly, maybe after one `yaourt -Syu` and reboot, cannot reach my desktop environment(gnome).
    At first, it seems like gdm doesn't run. So I manually run it, but the gnome reports an error in the GUI (the error is very general, so I have no idea what happened at all). Then I tried to install awesome, but I can't access to it as well.
    I've tried to switch my graphical driver from nouveau to nvidia, but I still can't get into Gnome. Surprisingly, I get into awesome successfully. However, I failed to open any terminal or application but quit awesome.
    I've tried to replace sysvinit with systemd-sysvcompat after switching my graphical driver back to nouveau. By doing that, gdm seems to run at boot up, but I still can access Gnome, because the computer just halt and the graphical interface never come up. Neither can I access awesome.
    I can't figure out where the problem is. My desktop environment used to function normal for a long time. What could possibly be wrong after any upgrade?

    1)  What was updated.
    2)  What are the errors.
    3)  What can you find in the various logs and/or journal.

  • [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.

  • Free Linux Terminal emulator

    Hi friends,
    As you know, some oracle DB components  need be installed under GUI interface.
    Please advise which is a free best linux client Terminal emulator that can be easy configured a linux  GUI interface  for DBA?
    I do not think  putty is a good linux GUI interface tool.
    Thanks
    newdba

    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.

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

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

  • Intall X3270 Terminal emulator on Solaris 10 x86

    Hi! I'm trying to install IBM 3270 Terminal Emulator from source code on solaris 10 x86. I had some problems when I run ./configure but was PATH's configuration. Now I'm trying to run make but at certain moment the folowing erro return:
    makeconv -d . -p icudt3l ibm-837_P100-2000.ucm
    sh: makeconv: not found
    *** Error code 1
    make: Fatal error: Command failed for target `icudt3l_ibm-837_P100-2000.cnv'
    I tried to find this 'makeconv' but I haven't found. Does anybody have some esperience with the instalation of X3270? Thank's a lot.

    problem 1 is that it's looking for ../../s0.. Which I
    managed to
    fake out by creating the dir in the same mount
    point.
    Problem 2 is that it can't find .tmp_proto, which I
    must
    concur with. I can't find that on any of the b72 cd
    images.
    So, the setup_install_server fails.This seems to be the problem when you try to setup an install
    server on a Solaris SPARC system for Solaris x86 clients, using
    the Solaris 9 or Solaris 10/Express CD media.
    There's a Solaris x86 UFS filesystem on slice 0 on the CD media,
    and it's supposed to be mounted on the "s0" mount point,
    otherwise setup_install_server won't work. On a Solaris x86 box,
    vold mounts it automatically for you: /cdrom/cdrom0/s2 is the
    mount point for the platform independant ISO9660 part of the CD
    media, /cdrom/cdrom0/s0 is the UFS root filesystem.
    Problem is that Solaris SPARC:
    - does not understand Solaris x86 disk labels
    - does not allow mounting x86 UFS filesystems
    (and vice versa).
    AFAIK, Solaris 9 DVD media does not have this problem. I
    guess the same will be true when Solaris 10 DVD media is
    available in a few months. On the DVD media there's enough
    free space to include an extra copy of the files in the ISO9660
    filesystem.

  • 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

  • Carbon - yet another terminal emulator

    What is carbon?
    Carbon is yet another terminal emulator aiming at minimalism, speed, functionality, and aesthetics. As an added bonus, the code is very modular.
    Carbon is built on xcb instead of Xlib. There has yet, to my knowledge, a terminal emulator built like this. This should prove to provide a faster and more responsive terminal.
    Features
      * Support for managing different colour themes.
      * Ability to install custom escape sequence handlers.
      * Daemon mode much like urxvt, possibly with some degree of detaching/reattaching support.
    While I haven't figured out how I'm going to handle configuration, I will utilize custom escape sequences to control certain settings. For example, unless I find it unsatisfactory, carbon will provide a shell script for theme changing/previewing, relying on escape sequences to tell the terminal what color theme to use.
    The code it somewhat suckless inspired, it will utilize a config.h file by the time its done. However, I have a somewhat bigger aim on making carbon modular than most suckless projects. The terminal emulator back-end should be easily reusable other projects.
    Current status:
      * I can create a tty and read and write from it.
      * I can parse CSI escape sequences (but I ignore them for now)
      * I can read keypresses from a windows and send the appropriate character to to the tty (at time of posting, this is not committed to repo).
    Not really worth running as it doesn't draw to the screen yet, but its getting there.
    Thanks to:
       * st, madtty: This project was largely written looking at how they did things; my code ranges from very similar to blatant rip-off.
       * Awesome: I gutted their keycode->keysym->string code to get input working. Kudos for adopting xcb.
    Heres a link to the project on github: github.com/simongmzlj/carbon
    Thanks for your time. Any comments, ideas, or criticisms would be appreciated.

    Sorry, I really wasn't very clear, and I'm not positive how to say it.  I'm perfectly happy with being able to scroll through history.  That's a useful feature.  But consider this situation: You're checking out the git man files.  This gives you a page far longer than your terminal is, and you work your way down to the command you wanted to check out.  Then, when you quit, I prefer if the info stays on your screen instead of removing the git man page and going back to what you had before calling man.  Hopefully that makes sense.  If not, think the default behaviour of screen (prefered) vs. xterm.

  • Graphical Terminal Emulator for Solaris

    hi all,
    can anyone recommend a graphical terminal emulator for solaris? i'd like to see the solaris graphical desktop from a windows PC.
    thanks!

    Quite good is commercial XWin by Starnet. Demo version enables 30 minutes of uninterrupted work. I assume that You know all about minor slip in Xsetup file in Solaris distribution.

Maybe you are looking for

  • Lenovo 3000 H series computer boots up to a small blinking blue square on a black screen

    The computer powers on but after the Lenovo screen, the screen goes blank with a small blinking blue square on the left hand side and that's it? Anyone experienced this and know what could be the problem?  Message Edited by Bloome on 07-15-2009 12:39

  • BI: time Stamp format

    Hi Experts , I have mapped the source Timestamp to 0RSTT_TIME. it is actually giving the value in the wrong format as shown below. It should be year,month and day respectively. KIndly advise where can we set the format change to laod it in the right

  • Insufficient Data for an Image Acrobat Pro 11.0.6 - Windows 8.1

    We have recently upgraded several users in our office to Windows 8.1.  They are running Acrobat Pro 11.0.6, which they had previously been running Windows 7 without issue. Now, in Windows 8, they will have a PDF file open and pages in it start to go

  • Common class resource for loaded and loading swf

    hi, i have built a video player, and now i'm working on (sort-of) video editor.  both of them use a singleton class 'DataRepository', which - as it name implies - serves as a repository for all the data needed to play the video and/or edit it. now i

  • Howto call a Javabean function from javascript

    Hi, I want to fill some properties from an object which can be chosen from a selection box. When an object is chosen, I want to fill the propertie fields of the chosen object. How can I do this? Can I call from a 'onChange' a javabean function? or do