Tri Monitor Setup

Any way to hook up 3 external monitors from my black Macbook?
Thanks,
-Ian B.

The MacBook is not designed to run more than one external. The hardware and the firmware aren't designed for it. Hence the link I gave. With a splitter assuming it would be able to handle 4 externals you would have four identical screens as extended desktop or 5 total mirrored displays counting the MacBooks.

Similar Messages

  • I have 12 core with Quatro 4000 and 5770, I want to use dual monitor setup, monitors are NEC with Spectraview-II.  How do I connect?  4000 only has 1 Display Port and 1 DVI.  5770 has 2 of each, if I use both 5770 Display Ports, does the 4000 contribute?

    I just bought a 12 core with Quatro 4000 and 5770, I want to use dual monitor setup, monitors are NEC with Spectraview-II.  How do I connect?  4000 only has 1 Display Port and 1 DVI.  5770 has 2 of each, if I use both 5770 Display Ports, does the 4000 contribute any work at all?  I read where on a PC they would work together, but on a MAC they do not.
    I read that Display Port has higher band width than DVI, NEC monitors for best performance they recommend using DIsplay Port.
    When I was setting this up I looked at a Nvidia Quadro 4000, unfortunately it was for PC, it had 2 Display Ports, in the Mac version they reduce it to one.  I did not think there could be a difference.
    Mainly want to use it for CS6 and LR4.
    How to proceed??? 
    I do not want to use the Quadro 4000 for both, that would not optimize both monitors, one DP and 1 DVI.  Using just the 5770 would work but I do not think the 4000 would be doing anything, and the 5770 has been replaced by the 5870.more bandwidth.
    Any ideas, I am a Mac newbie, have not ever tried a Mac Pro, just bought off ebay and now I have these problems.
    As a last resort I could sell both and get a 5870.  That would work, I'm sure of that, it's just that I wanted the better graphics card.
    Thanks,
    Bill

    The Hatter,
    I am a novice at Mac so I read all I can.  From what I understand the NEC monitors I bought require Display Port for their maximum performance.  The GTX 680 only has DVI outputs.  Difference from what I understand is larger bandwidth with the DP.
    You said I have the 4000 for CUDA.  I am not all that familiar with CUDA and when I do read about it I do not understand it. 
    A concern I have is, that if I connect the 2 high end NEC monitors via the 5770, using it's 2 Display Ports I would have nothing connected to the 4000.  Is the 4000 doing anything with nothing connected?  I read where in a PC system the 2 cards would interact but in a Mac system they do not.
    Bottom line, as I see it, the 4000 will not be useful at all to me, since I want a dual monitor set-up.
    So far the 5870 seems the best choice, higher band width than the 5770, and it has 2 Display Ports to optimize the NEC monitors.
    I'm not sure how fine I am splitting hairs, nor do I know how important those hairs are.  I am just trying to set up a really fast reliable system that will mainly be used for CS6 and LR4.  Those NEC monitors are supposed to be top notch.

  • Trying to setup systemd user instance

    Hi guys!
    For the past few days I have been trying to setup systemd to run a user instance (user is 'hans'). Sadly, I have been unable to find a lot of detail in doing this, so much of my work has been trial and error. Just recently I learned about the [email protected] and also about loginctl enable-linger. However to what degree they are related to setting up a user instance, I do not know. I set the user 'hans' to 'linger' using the loginctl enable-linger hans command, however I think I might have misunderstood the significance of the command in relation to what I am trying to do.
    What I want to for user 'hans' to have his own service file, i.e. irssi.service, and start/stop/enable/disable/etc that service independently of the system. I realize that I could use sudo and configure it to only allow certain commands, and more than that have individual 'system' services for each user, i.e. hansirssi.service, janeirssi.service, joeirssi.service, etc., but I don't want to have to do that unless there is no other option.
    So Question 1:
    Is it possible to setup up systemd user instances as I envision it? Or have I misunderstood something?
    My system:
    [root@ru ~]# uname -a
    Linux ru 3.5.4-1-ARCH #1 SMP PREEMPT Sat Sep 15 08:12:04 CEST 2012 x86_64 GNU/Linux
    The system is installed in a Proxmox virtual machine with a virtio virtual HDD and standard setup. It is a headless system. I have a complete systemd conversion as per the wiki plus polkit 0.107-2 for use with 'loginctl'.
    I tried:
    [root@ru ~]$ systemctl enable [email protected]
    The unit files have no [Install] section. They are not meant to be enabled using systemctl.
    [root@ru ~]$ systemctl start [email protected]
    [root@ru ~]# systemctl status [email protected]
    [email protected] - User Manager for hans
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
    Active: active (running) since Fri, 21 Sep 2012 18:33:07 +0100; 42min ago
    Main PID: 23189 (systemd)
    Status: "Startup finished in 822us."
    CGroup: name=systemd:/user/hans/shared
    â 23190 (sd-pam)
    â systemd-23189
    â 23189 /usr/lib/systemd/systemd --user
    And on the user account hans I confirm that the service is running:
    [hans@ru ~]$ systemctl status [email protected]
    [email protected] - User Manager for hans
    Loaded: loaded (/usr/lib/systemd/system/[email protected]; static)
    Active: active (running) since Fri, 21 Sep 2012 18:33:07 +0100; 13s ago
    Main PID: 23189 (systemd)
    Status: "Startup finished in 822us."
    CGroup: name=systemd:/user/hans/shared
    â 23190 (sd-pam)
    â systemd-23189
    â 23189 /usr/lib/systemd/systemd --user
    But in regard to actually starting/stopping/enabling a user specific service, I keep getting this error:
    [hans@ru ~]$ systemctl start dummyservice.service
    Failed to issue method call: Access denied
    and when I try by accessing the 'user' instance, I get the following error:
    [hans@ru ~]$ systemctl --user
    Failed to get D-Bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    The thing is that dbus is running:
    [root@ru ~]# systemctl status dbus
    dbus.service - D-Bus System Message Bus
    Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
    Active: active (running) since Thu, 20 Sep 2012 18:19:18 +0100; 24h ago
    Main PID: 248 (dbus-daemon)
    CGroup: name=systemd:/system/dbus.service
    â 248 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    Sep 21 18:12:40 ru dbus-daemon[248]: dbus[248]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Sep 21 18:12:40 ru dbus[248]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
    Sep 21 18:17:50 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid.../init ")
    Sep 21 18:17:50 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid=1000 pid=23167 c...n/init ")
    Sep 21 18:32:46 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.31" (uid.../init ")
    Sep 21 18:32:46 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.31" (uid=1000 pid=23185 c...n/init ")
    Sep 21 18:35:45 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid.../init ")
    Sep 21 18:35:45 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=23195 c...n/init ")
    Sep 21 18:36:06 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.35" (uid.../init ")
    Sep 21 18:36:06 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.35" (uid=1000 pid=23197 c...n/init ")
    Here is the full output from 'journalctl':
    Sep 21 18:17:50 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid=1000 pid=23167 comm="systemctl enable [email protected] ") interface="org.freedesktop.systemd1.Manager" member="EnableUnitFiles" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Sep 21 18:17:50 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.26" (uid=1000 pid=23167 comm="systemctl enable [email protected] ") interface="org.freedesktop.systemd1.Manager" member="EnableUnitFiles" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Sep 21 18:32:46 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.31" (uid=1000 pid=23185 comm="systemctl start [email protected] ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Sep 21 18:32:46 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.31" (uid=1000 pid=23185 comm="systemctl start [email protected] ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Sep 21 18:33:07 ru systemd[23189]: Failed to open private bus connection: Failed to connect to socket /run/user/hans/dbus/user_bus_socket: No such file or directory
    Sep 21 18:35:45 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=23195 comm="systemctl start userservice ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Sep 21 18:35:45 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=23195 comm="systemctl start userservice ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Sep 21 18:36:06 ru dbus-daemon[248]: dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.35" (uid=1000 pid=23197 comm="systemctl start userservice.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Sep 21 18:36:06 ru dbus[248]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.35" (uid=1000 pid=23197 comm="systemctl start userservice.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply="0" destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init ")
    Question 2:
    Why would dbus reject the 'messages', is there something I need to configure (permissions,...?) in order to get this to work?
    I suspect that it is my lacking knowledge to blame for this problem, which is why I have sought help here.
    EDIT#1:
    I forgot to show you what 'loginctl' was doing:
    [root@ru ~]# loginctl user-status hans
    hans (1000)
    Since: Thu, 20 Sep 2012 18:19:18 +0100; 24h ago
    State: lingering
    CGroup: name=systemd:/user/hans
    â shared
    â 23190 (sd-pam)
    â systemd-23189
    â 23189 /usr/lib/systemd/systemd --user
    Last edited by sunite (2012-09-21 18:17:35)

    I just went through the install process, read through the user-session-units doc, I was finally able to get the user instance working, no Dbus errors . However I decided to make sure and run 'dbus-monitor' within the user 'hans' and I got the following error message:
    Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
    I checked and there is no such file, however I checked the dbus.socket:
    [root@ru user]# cat /usr/lib/systemd/user/dbus.socket
    [Unit]
    Description=D-Bus System Message Bus Socket
    [Socket]
    ListenStream=%t/dbus/user_bus_socket
    And dbus.service:
    [root@ru user]# dbus-monitor
    Failed to open connection to session bus: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
    [root@ru user]# cat /usr/lib/systemd/user/dbus.service
    [Unit]
    Description=D-Bus System Message Bus
    Requires=dbus.socket
    [Service]
    ExecStart=/usr/bin/dbus-daemon --session --address=systemd: --nofork --systemd-activation
    ExecReload=/usr/bin/dbus-send --print-reply --session --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
    and as far as I can tell everything see alright there.
    EDIT#1:
    I just restarted the system to see if my symlink worked for the user-session service. It did, sort of, however the following error occured during boot:
    Sep 21 22:15:14 ru systemd[307]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory
    Last edited by sunite (2012-09-21 21:22:11)

  • Dual monitor setup - need laptop on the left

    Hi All
    I'm running a dual monitor setup - specifically a HP G72 laptop and a widescreen monitor. I use the monitor as the default and sometimes I want to use the Laptop as a secondary screen for watching TV etc. My desktop is Enlightenment, I just changed to it from Gnome. My issue is that I want the laptop to be on the left of the monitor - that's how it is physically positioned - but when I switch the Laptop screen on all my applications shift over to the laptop screen. I've written 2 scripts, attached to hotkeys, one to turn the laptop off and the other to turn the laptop on. The script to turn the laptop on is as follows:
    xrandr --output LVDS1 --mode 1600x900 --pos 1600x0 --rotate normal
    --output VGA1 --primary --mode 1920x1080 --pos 0x0 --rotate normal --left-of LVDS1
    This works fine, applications stay where they should be, except that the physical position is incorrect; VGA1 should be to the right of LVDS1 like this:
    xrandr --output LVDS1 --mode 1600x900 --pos 1600x0 --rotate normal
    --output VGA1 --primary --mode 1920x1080 --pos 0x0 --rotate normal --right-of LVDS1
    However, when I use the second script all of the applications shift to the laptop but at least the physical position is correct. The issue appears to be something to do with laptops, almost as though when it's a laptop the default monitor is forced to be on the left. Has anybody got any suggestions how to get around this issue?
    Thanks
    Richard

    This is due to your window manager treating the two monitors as a larger 'desktop' area - that combined with your specification of the pos=0x0 you are telling it to do this.
    If you have only the VGA output on, the top left corner of the VGA monitor is 0x0.  If you open a window, and it is placed 10 pixels in and down from the top left, it is at coordinates 10x10 in the x session.  Then you turn on the laptop monitor and specify that the top left corner of the laptop monitor should now bo considered 0x0 - but nothing is done to move the windows, so the window with coordinates 10x10 is now near the top left of the laptop monitor.
    I see 3 possible ways of acheiving what you want:
    1) swap the "pos" parameters in your xrandr commands so that the monitor on the left is always at 0x0 and the one on the right is always at 1920x0 (or whatever).  This will leave a large area of available X desktop that is not visible - I don't know how your window manager will treat this.  It might try to map windows on the laptop screen space even though that screen is not on.  I know openbox is easy to configure where it tries to place windows.
    2) Keep the VGA monitor always at 0x0, but place the laptop monitor at a negative offset when you want it on.  I don't actually know if X allows negative coordinates like that, but it's worth a shot.
    3) Configure your window manager, or use a different window manager, so that it is aware of the two screens and treats them reasonably (e.g. moves windows when the desktop area is changed).
    Last edited by Trilby (2014-07-12 12:15:42)

  • Dual monitor setup flashes constantly

    I am trying to set up a dual monitor setup with a Lenovo Thinkcentre Edge computer.  I reset the BIOS to enable multimonitor support and IGD Active Video.  One monitor is plugged into the VGA port.  But when I plug the second monitor into the DVI-D port, both monitors flash constantly and the speakers make the sound of a device being disconnected.  Unplugging the DVI-D monitor stops the problem on the VGA monitor.  I checked the drivers and they are all up to date.  Any ideas?

    Bad cable?
    Disclaimer: While I do work for Lenovo Partner, all my contributions are my personal, non-official and not that of Lenovo or my employer.

  • Dual monitor setup broken in Leopard

    There are numerous problems running an external Cinema Display from a MacBook Pro using Leopard. I've tried with 2 MacBook Pros (one 15", one 17") and 2 different Cinema Displays (24" and 30"). Not to mention everything was fine under Tiger. Both Leopard installations were "clean installs".
    1. Closing the lid of the MBP doesn’t remove the screen from Leopard (Or Spaces).
    2. When the MBP sleeps with a Display attached it never comes back onto the Display, only the MBP’s LCD.
    3. Periodically the MBP refuses to wake when it’s connected to the display.
    4. I can no longer use the power button on the Display to sleep/shutdown the MBP.
    5. Simply plugging the Display sometimes causes it to wake (while the MBP is closed). In Tiger, I had to have the Power Adapter connected to wake my Sleeping MBP with the lid closed (as stated in the documentation).
    Wonder if all this will be fixed in 10.5.1 (hoping)?

    Firefox doesn't always play well with a multiple monitor setup and hardware acceleration.
    Try to disable hardware acceleration.
    *Tools > Options > Advanced > General > Browsing: "Use hardware acceleration when available"
    *https://support.mozilla.org/kb/how-do-i-upgrade-my-graphics-drivers

  • Video Resolution and monitor setup

    OK, I need a little help here because I can not get what I want.  I am running a gaming system with MSI Plat. K9A2, with 8G gskil ram @1066, timings 5-5-5-15, 2.1v, two saphire 4870 1g cards, crossfireX via dual HDMI. CCC 9.7 for 64 bit on 64 bit Vista Prem.  The monitors are ACER H233H with a max resolution of 1920x1080.  I am basically only using widows video config. and CCC. I am set to extend my desk top.  If i try to run 1920x1080 it crops around the image by abour 3/4 of an inch.  The same for both monitors.  I can run both at 1650x1080, full screen without a problem. color is 32bit. 59-60 hz is the refresh rate.  I have tried to force the config. for full screen 1920x1080, but still get the cropping or the 1920x1080 monitor pushes the windows tool bar off the screen along with any icons that are left side of the primary monitor.  All drivers are up to date at this time.  I have tried ccc with full enable gpu scaling, no change.  I have tried the setup with maintaining aspect ratio, scaling image to full (where it is set now) and using centered timings, no change.  I can not change the scaling options slide bar or check the box, the slider is all the way up to over  scan (which may be the problem), but i can not change it. The OSD H-position and V-position for each on monitor control is 83 and 3 respectively.  The screens are set at full, If i set them at aspect I get cropping of about 1 inch on the right and left side of each monitor. DDC is on, and ACM is off.  Under the regular settings for color management I can no change the V.position and H.position, they are set to 0.  Any thoughts?  I am well powered and well cooled, so that is not a problem.  Thanks in advanced.

    Thanks guys. There's no issue with playing the video when launching it direct in Windows Media Player. Its just when launched from the DirectShow API. We've now got a 3rd party looking at that API and have a temporary fix.
    So for future reference there are no specific problems with the rendering, codecs or resolutions, but there may be an issue with applications that launch high res media on to a 2nd monitor with the DirectShow API.
    thanks

  • I have a dual monitor setup.  When I paste develop settings from one image to another, Lightroom switches the active window.

    Strange problem.  Lightroom 5.5.  Windows 8.1. Dual monitor setup.
    I'm processing a large batch of photos.  I have Monitor #1 set as my main develop window, with Monitor #2 set only to display a larger version of the image I'm working with. If I copy the develop settings off of one image and try to paste them onto another image, Lightroom will switch from Monitor #1 to Monitor #2 as the main develop window, and will not display anything on Monitor #1.
    If I then try to paste develop settings onto another image on Monitor #2, LR will then display a larger version of the image I'm working with on Monitor #1.
    To work the way I want to, I have to continually drag my develop window back to Monitor #1 every time I try to paste develop settings onto a new image. How can I make this stop?

    I just tried what I think you’re saying you’re doing and I don’t have the problem with LR 5.5 on Windows 7 SP 2.
    Does the same thing happen whether you use the key shortcuts vs the Settings / Copy/Paste options on the menu?
    I ask this because if you’re using the keyboard shortcuts, maybe you have some display-manager program that has bound itself to the Ctrl-Shift-V (paste settings) to the function of move-to-other-monitor which would do at least part of what you describe.
    You can also test this theory by doing a Ctrl-Shift-V with an application other than LR as the active window and see if it moves.  I suppose Ctrl-Shift-C might also play into it so try both of these hot-key combinations with a program that isn’t LR.
    If none of this sheds any light on the situation, then give a more detailed description of the low-level functions you’re doing to accomplish the copy-paste of settings, so someone else could replicate the steps exactly.
    Specific detailed steps, like:
    left-click on source photo’s thumbnail in the filmstrip
    press Ctrl-Shift-C to copy the settings
    click Check-None
    enable the white-balance and calibration checkboxes
    click Ok
    left-click on destination photo's thumbnail in the filmstrip
    click on Settings / Paste Settings in LR’s menus to paste the settings to the selected photo

  • Monitor setup for Premier CS5?

    I will be building a stand alone system for Premiere CS5 to edit HDV tape. I'm a graphic designer by trade and video editing is completely new to me. In addition to building a monster system I'm not sure what to do for monitors. Is it pretty standard to run a dual monitor setup in Premiere as it is with most adobe programs since you can put all your pallets on the 2nd monitor? What size monitors are a standard for premiere? Our IT department tried to get us to use 16x9 format monitors (only 11" tall) on our CS4 systems and they were worthless since only the highest setting kept things in proper perspective and then you couldn't read anything on the screen. So, I'm still using CRT monitors. Also, would it be a wise decision to get a HDTV to hook up to the computer for viewing purposes. I work for a large commercial development company and we will be brodcasting this video to about 12 large HDTVs through out our headquarters. Any advice on monitors would be greatly appreciated.

    Take a look at these:
    http://usa.asus.com/product.aspx?P_ID=zMRyN4KB5o5rSqKr
    http://usa.asus.com/product.aspx?P_ID=VtCFrzY48DGVjc6r
    http://usa.asus.com/product.aspx?P_ID=QC3Ie0INJMD9PlEP
    Those are all 1080P (1920x1080 res) monitors 22 to 24 inch range. For the price, you can't beat them.

  • Monitor setup has changed - KDE Daemon after sleep

    After the monitor goes into powersave mode and is restored I keep gettung the Monitor setup has changed - KDE Daemon  box, anyone know how to get rid of this? everything seams to work but the box is getting annoying.  Logs dont show anything wrong and I have tried lots of things to fix it with no solution.

    Ok still cant work this out. manually set monitor settings etc the box still pops up when waking monotor from sleep. logs still show nothing.  Can anyone help?
    Log below
    [ 11.918]
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    [ 11.918]
    X.Org X Server 1.13.2.901 (1.13.3 RC 1)
    Release Date: 2013-02-15
    [ 11.918] X Protocol Version 11, Revision 0
    [ 11.918] Build Operating System: Linux 3.7.5-1-ARCH x86_64
    [ 11.918] Current Operating System: Linux ThunderBolt.LoadBalancer.Org 3.7.9-2-ARCH #1 SMP PREEMPT Mon Feb 25 12:04:25 CET 2013 x86_64
    [ 11.918] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=bc60faad-b008-4f1f-8682-88d4c6f235cc ro quiet
    [ 11.918] Build Date: 18 February 2013 03:52:56PM
    [ 11.918]
    [ 11.918] Current version of pixman: 0.28.2
    [ 11.918] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 11.918] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 11.918] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 17:45:33 2013
    [ 12.161] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 12.326] (==) ServerLayout "ServerLayout0"
    [ 12.326] (==) No screen section available. Using defaults.
    [ 12.326] (**) |-->Screen "Default Screen Section" (0)
    [ 12.326] (**) | |-->Monitor "<default monitor>"
    [ 12.326] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 12.326] (**) | |-->Device "Intel Graphics"
    [ 12.326] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 12.326] (**) Option "BlankTime" "0"
    [ 12.326] (**) Option "StandbyTime" "0"
    [ 12.326] (**) Option "SuspendTime" "0"
    [ 12.326] (**) Option "OffTime" "0"
    [ 12.326] (==) Automatically adding devices
    [ 12.326] (==) Automatically enabling devices
    [ 12.326] (==) Automatically adding GPU devices
    [ 12.513] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 12.513] Entry deleted from font path.
    [ 12.561] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 12.561] Entry deleted from font path.
    [ 12.561] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 12.561] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 12.561] Entry deleted from font path.
    [ 12.561] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 12.561] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 12.561] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 12.561] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 12.562] (II) Loader magic: 0x7fcc20
    [ 12.562] (II) Module ABI versions:
    [ 12.562] X.Org ANSI C Emulation: 0.4
    [ 12.562] X.Org Video Driver: 13.1
    [ 12.562] X.Org XInput driver : 18.0
    [ 12.562] X.Org Server Extension : 7.0
    [ 12.562] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 12.563] (--) PCI:*(0:0:2:0) 8086:2e22:1025:0251 rev 3, Mem @ 0xfe400000/4194304, 0xd0000000/268435456, I/O @ 0x0000dc00/8
    [ 12.563] (--) PCI: (0:0:2:1) 8086:2e23:1025:0251 rev 3, Mem @ 0xfe900000/1048576
    [ 12.762] Initializing built-in extension Generic Event Extension
    [ 12.763] Initializing built-in extension SHAPE
    [ 12.763] Initializing built-in extension MIT-SHM
    [ 12.763] Initializing built-in extension XInputExtension
    [ 12.763] Initializing built-in extension XTEST
    [ 12.763] Initializing built-in extension BIG-REQUESTS
    [ 12.763] Initializing built-in extension SYNC
    [ 12.763] Initializing built-in extension XKEYBOARD
    [ 12.763] Initializing built-in extension XC-MISC
    [ 12.763] Initializing built-in extension SECURITY
    [ 12.763] Initializing built-in extension XINERAMA
    [ 12.763] Initializing built-in extension XFIXES
    [ 12.763] Initializing built-in extension RENDER
    [ 12.763] Initializing built-in extension RANDR
    [ 12.763] Initializing built-in extension COMPOSITE
    [ 12.763] Initializing built-in extension DAMAGE
    [ 12.763] Initializing built-in extension MIT-SCREEN-SAVER
    [ 12.763] Initializing built-in extension DOUBLE-BUFFER
    [ 12.763] Initializing built-in extension RECORD
    [ 12.763] Initializing built-in extension DPMS
    [ 12.763] Initializing built-in extension X-Resource
    [ 12.763] Initializing built-in extension XVideo
    [ 12.763] Initializing built-in extension XVideo-MotionCompensation
    [ 12.763] Initializing built-in extension XFree86-VidModeExtension
    [ 12.763] Initializing built-in extension XFree86-DGA
    [ 12.763] Initializing built-in extension XFree86-DRI
    [ 12.763] Initializing built-in extension DRI2
    [ 12.763] (II) LoadModule: "glx"
    [ 12.816] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 12.828] (II) Module glx: vendor="X.Org Foundation"
    [ 12.829] compiled for 1.13.2.901, module version = 1.0.0
    [ 12.829] ABI class: X.Org Server Extension, version 7.0
    [ 12.829] (==) AIGLX enabled
    [ 12.829] Loading extension GLX
    [ 12.829] (II) LoadModule: "intel"
    [ 12.853] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 13.078] (II) Module intel: vendor="X.Org Foundation"
    [ 13.078] compiled for 1.13.2.901, module version = 2.21.3
    [ 13.079] Module class: X.Org Video Driver
    [ 13.079] ABI class: X.Org Video Driver, version 13.1
    [ 13.079] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
    Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
    Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
    Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
    Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
    Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
    Ivybridge Server (GT2), Haswell Desktop (GT1), Haswell Desktop (GT2),
    Haswell Desktop (GT2+), Haswell Mobile (GT1), Haswell Mobile (GT2),
    Haswell Mobile (GT2+), Haswell Server (GT1), Haswell Server (GT2),
    Haswell Server (GT2+), Haswell SDV Desktop (GT1),
    Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT2+),
    Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
    Haswell SDV Mobile (GT2+), Haswell SDV Server (GT1),
    Haswell SDV Server (GT2), Haswell SDV Server (GT2+),
    Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
    Haswell ULT Desktop (GT2+), Haswell ULT Mobile (GT1),
    Haswell ULT Mobile (GT2), Haswell ULT Mobile (GT2+),
    Haswell ULT Server (GT1), Haswell ULT Server (GT2),
    Haswell ULT Server (GT2+), Haswell CRW Desktop (GT1),
    Haswell CRW Desktop (GT2), Haswell CRW Desktop (GT2+),
    Haswell CRW Mobile (GT1), Haswell CRW Mobile (GT2),
    Haswell CRW Mobile (GT2+), Haswell CRW Server (GT1),
    Haswell CRW Server (GT2), Haswell CRW Server (GT2+),
    ValleyView PO board
    [ 13.079] (++) using VT number 7
    [ 13.213] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 13.213] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 13.213] (==) intel(0): RGB weight 888
    [ 13.213] (==) intel(0): Default visual is TrueColor
    [ 13.213] (**) intel(0): Option "AccelMethod" "sna"
    [ 13.213] (--) intel(0): Integrated Graphics Chipset: Intel(R) G45/G43
    [ 13.213] (**) intel(0): Framebuffer tiled
    [ 13.213] (**) intel(0): Pixmaps tiled
    [ 13.213] (**) intel(0): "Tear free" disabled
    [ 13.213] (**) intel(0): Forcing per-crtc-pixmaps? no
    [ 13.253] (II) intel(0): Output VGA1 has no monitor section
    [ 13.362] (II) intel(0): Output HDMI1 using monitor section HDMI1
    [ 13.403] (II) intel(0): Output DP1 has no monitor section
    [ 13.443] (II) intel(0): EDID for output VGA1
    [ 13.552] (II) intel(0): EDID for output HDMI1
    [ 13.552] (II) intel(0): Manufacturer: GSM Model: 56cc Serial#: 258443
    [ 13.552] (II) intel(0): Year: 2011 Week: 4
    [ 13.552] (II) intel(0): EDID Version: 1.3
    [ 13.552] (II) intel(0): Digital Display Input
    [ 13.552] (II) intel(0): Max Image Size [cm]: horiz.: 53 vert.: 30
    [ 13.552] (II) intel(0): Gamma: 2.20
    [ 13.552] (II) intel(0): No DPMS capabilities specified
    [ 13.552] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [ 13.552] (II) intel(0): First detailed timing is preferred mode
    [ 13.552] (II) intel(0): redX: 0.635 redY: 0.342 greenX: 0.292 greenY: 0.611
    [ 13.552] (II) intel(0): blueX: 0.147 blueY: 0.070 whiteX: 0.313 whiteY: 0.329
    [ 13.552] (II) intel(0): Supported established timings:
    [ 13.552] (II) intel(0): 640x480@60Hz
    [ 13.552] (II) intel(0): 800x600@60Hz
    [ 13.552] (II) intel(0): 1024x768@60Hz
    [ 13.552] (II) intel(0): Manufacturer's mask: 0
    [ 13.552] (II) intel(0): Supported standard timings:
    [ 13.552] (II) intel(0): #0: hsize: 1680 vsize 1050 refresh: 60 vid: 179
    [ 13.552] (II) intel(0): #1: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [ 13.552] (II) intel(0): #2: hsize: 1280 vsize 960 refresh: 60 vid: 16513
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 138.5 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 1968 h_sync_end 2000 h_blank_end 2080 h_border: 0
    [ 13.552] (II) intel(0): v_active: 1080 v_sync: 1083 v_sync_end 1088 v_blanking: 1111 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 148.5 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 13.552] (II) intel(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 13.552] (II) intel(0): Ranges: V min: 56 V max: 61 Hz, H min: 30 H max: 83 kHz, PixClock max 155 MHz
    [ 13.552] (II) intel(0): Monitor name: W2442
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 148.5 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 13.552] (II) intel(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 74.2 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [ 13.552] (II) intel(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 74.2 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
    [ 13.552] (II) intel(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [ 13.552] (II) intel(0): Supported detailed timing:
    [ 13.552] (II) intel(0): clock: 27.0 MHz Image Size: 531 x 299 mm
    [ 13.552] (II) intel(0): h_active: 720 h_sync: 736 h_sync_end 798 h_blank_end 858 h_border: 0
    [ 13.552] (II) intel(0): v_active: 480 v_sync: 489 v_sync_end 495 v_blanking: 525 v_border: 0
    [ 13.552] (II) intel(0): Number of EDID sections to follow: 1
    [ 13.552] (II) intel(0): EDID (in hex):
    [ 13.552] (II) intel(0): 00ffffffffffff001e6dcc568bf10300
    [ 13.552] (II) intel(0): 0415010380351e780aaec5a2574a9c25
    [ 13.552] (II) intel(0): 125054210800b3008180814001010101
    [ 13.552] (II) intel(0): 0101010101011a3680a070381f403020
    [ 13.552] (II) intel(0): 3500132b2100001a023a801871382d40
    [ 13.552] (II) intel(0): 582c4500132b2100001e000000fd0038
    [ 13.552] (II) intel(0): 3d1e530f000a202020202020000000fc
    [ 13.552] (II) intel(0): 0057323434320a202020202020200128
    [ 13.552] (II) intel(0): 020321f14e900403011412051f101300
    [ 13.552] (II) intel(0): 000000230907078301000065030c0010
    [ 13.552] (II) intel(0): 00023a801871382d40582c4500132b21
    [ 13.552] (II) intel(0): 00001e011d8018711c1620582c250013
    [ 13.552] (II) intel(0): 2b2100009e011d007251d01e206e2855
    [ 13.552] (II) intel(0): 00132b2100001e8c0ad08a20e02d1010
    [ 13.552] (II) intel(0): 3e9600132b2100001800000000000000
    [ 13.552] (II) intel(0): 00000000000000000000000000000026
    [ 13.552] (II) intel(0): Printing probed modes for output HDMI1
    [ 13.552] (II) intel(0): Modeline "1920x1080"x59.9 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 13.552] (II) intel(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e)
    [ 13.552] (II) intel(0): Modeline "1920x1080i"x60.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 13.552] (II) intel(0): Modeline "1920x1080i"x50.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 13.552] (II) intel(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 13.552] (II) intel(0): Modeline "1680x945"x60.0 131.48 1680 1784 1960 2240 945 946 949 978 -hsync +vsync (58.7 kHz)
    [ 13.552] (II) intel(0): Modeline "1400x1050"x59.9 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e)
    [ 13.552] (II) intel(0): Modeline "1600x900"x60.0 118.96 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz)
    [ 13.552] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "1440x900"x59.9 88.75 1440 1488 1520 1600 900 903 909 926 +hsync -vsync (55.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x960"x60.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "1366x768"x60.0 85.89 1366 1439 1583 1800 768 769 772 795 -hsync +vsync (47.7 kHz)
    [ 13.552] (II) intel(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x800"x59.9 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x768"x60.0 68.25 1280 1328 1360 1440 768 771 778 790 +hsync -vsync (47.4 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 13.552] (II) intel(0): Modeline "1024x576"x60.0 46.97 1024 1064 1168 1312 576 577 580 597 -hsync +vsync (35.8 kHz)
    [ 13.552] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 13.552] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [ 13.552] (II) intel(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 13.552] (II) intel(0): Modeline "848x480"x60.0 33.75 848 864 976 1088 480 486 494 517 +hsync +vsync (31.0 kHz e)
    [ 13.552] (II) intel(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 13.552] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 13.593] (II) intel(0): EDID for output DP1
    [ 13.593] (II) intel(0): Output VGA1 disconnected
    [ 13.593] (II) intel(0): Output HDMI1 connected
    [ 13.593] (II) intel(0): Output DP1 disconnected
    [ 13.593] (II) intel(0): Using exact sizes for initial modes
    [ 13.593] (II) intel(0): Output HDMI1 using initial mode 1920x1080
    [ 13.593] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 13.593] (==) intel(0): DPI set to (96, 96)
    [ 13.593] (II) Loading sub module "dri2"
    [ 13.593] (II) LoadModule: "dri2"
    [ 13.593] (II) Module "dri2" already built-in
    [ 13.593] (==) Depth 24 pixmap format is 32 bpp
    [ 13.793] (II) intel(0): SNA initialized with Broadwater/Crestline backend
    [ 13.793] (==) intel(0): Backing store disabled
    [ 13.793] (==) intel(0): Silken mouse enabled
    [ 13.793] (II) intel(0): HW Cursor enabled
    [ 13.793] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 13.794] (==) intel(0): DPMS enabled
    [ 13.794] (II) intel(0): Overlay video not supported on this hardware
    [ 13.794] (II) intel(0): [XvMC] xvmc_vld driver initialized.
    [ 13.794] (II) intel(0): [DRI2] Setup complete
    [ 13.794] (II) intel(0): [DRI2] DRI driver: i965
    [ 13.794] (II) intel(0): direct rendering: DRI2 Enabled
    [ 13.794] (==) intel(0): hotplug detection: "enabled"
    [ 13.794] (--) RandR disabled
    [ 14.124] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 14.124] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 14.124] (II) AIGLX: enabled GLX_ARB_create_context
    [ 14.124] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 14.124] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 14.124] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 14.124] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 14.124] (II) AIGLX: Loaded and initialized i965
    [ 14.124] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 14.125] (II) intel(0): switch to mode 1920x1080 on crtc 3 (pipe 0)
    [ 14.210] (II) intel(0): Setting screen physical size to 508 x 285
    [ 14.922] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 14.922] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 14.922] (II) LoadModule: "evdev"
    [ 14.922] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 14.957] (II) Module evdev: vendor="X.Org Foundation"
    [ 14.957] compiled for 1.13.0, module version = 2.7.3
    [ 14.957] Module class: X.Org XInput Driver
    [ 14.957] ABI class: X.Org XInput driver, version 18.0
    [ 14.957] (II) Using input driver 'evdev' for 'Power Button'
    [ 14.957] (**) Power Button: always reports core events
    [ 14.957] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 14.957] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 14.957] (--) evdev: Power Button: Found keys
    [ 14.957] (II) evdev: Power Button: Configuring as keyboard
    [ 14.957] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
    [ 14.957] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 14.957] (**) Option "xkb_rules" "evdev"
    [ 14.957] (**) Option "xkb_model" "evdev"
    [ 14.957] (**) Option "xkb_layout" "us"
    [ 14.988] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 14.988] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 14.988] (II) Using input driver 'evdev' for 'Power Button'
    [ 14.988] (**) Power Button: always reports core events
    [ 14.988] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 14.988] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 14.988] (--) evdev: Power Button: Found keys
    [ 14.989] (II) evdev: Power Button: Configuring as keyboard
    [ 14.989] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
    [ 14.989] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 14.989] (**) Option "xkb_rules" "evdev"
    [ 14.989] (**) Option "xkb_model" "evdev"
    [ 14.989] (**) Option "xkb_layout" "us"
    [ 14.989] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 14.989] (II) config/udev: Adding input device UVC Camera (046d:0825) (/dev/input/event14)
    [ 14.989] (**) UVC Camera (046d:0825): Applying InputClass "evdev keyboard catchall"
    [ 14.989] (II) Using input driver 'evdev' for 'UVC Camera (046d:0825)'
    [ 14.989] (**) UVC Camera (046d:0825): always reports core events
    [ 14.989] (**) evdev: UVC Camera (046d:0825): Device: "/dev/input/event14"
    [ 14.989] (--) evdev: UVC Camera (046d:0825): Vendor 0x46d Product 0x825
    [ 14.989] (--) evdev: UVC Camera (046d:0825): Found keys
    [ 14.989] (II) evdev: UVC Camera (046d:0825): Configuring as keyboard
    [ 14.989] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.7/usb1/1-6/1-6:1.0/input/input14/event14"
    [ 14.989] (II) XINPUT: Adding extended input device "UVC Camera (046d:0825)" (type: KEYBOARD, id 8)
    [ 14.989] (**) Option "xkb_rules" "evdev"
    [ 14.989] (**) Option "xkb_model" "evdev"
    [ 14.989] (**) Option "xkb_layout" "us"
    [ 14.990] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event4)
    [ 14.990] (II) No input driver specified, ignoring this device.
    [ 14.990] (II) This device may have been added with another device file.
    [ 14.990] (II) config/udev: Adding input device HDA Intel Front Headphone (/dev/input/event10)
    [ 14.990] (II) No input driver specified, ignoring this device.
    [ 14.990] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel Line Out CLFE (/dev/input/event11)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel Line Out Surround (/dev/input/event12)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel Line Out Front (/dev/input/event13)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.991] (II) config/udev: Adding input device HDA Intel HDMI/DP,pcm=3 (/dev/input/event6)
    [ 14.991] (II) No input driver specified, ignoring this device.
    [ 14.991] (II) This device may have been added with another device file.
    [ 14.992] (II) config/udev: Adding input device HDA Intel Line (/dev/input/event7)
    [ 14.992] (II) No input driver specified, ignoring this device.
    [ 14.992] (II) This device may have been added with another device file.
    [ 14.992] (II) config/udev: Adding input device HDA Intel Front Mic (/dev/input/event8)
    [ 14.992] (II) No input driver specified, ignoring this device.
    [ 14.992] (II) This device may have been added with another device file.
    [ 14.992] (II) config/udev: Adding input device HDA Intel Rear Mic (/dev/input/event9)
    [ 14.992] (II) No input driver specified, ignoring this device.
    [ 14.992] (II) This device may have been added with another device file.
    [ 14.993] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 14.993] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 14.993] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 14.993] (**) AT Translated Set 2 keyboard: always reports core events
    [ 14.993] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 14.993] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 14.993] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 14.993] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 14.993] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 14.993] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
    [ 14.993] (**) Option "xkb_rules" "evdev"
    [ 14.993] (**) Option "xkb_model" "evdev"
    [ 14.993] (**) Option "xkb_layout" "us"
    [ 14.993] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/event5)
    [ 14.993] (**) ImPS/2 Generic Wheel Mouse: Applying InputClass "evdev pointer catchall"
    [ 14.993] (II) Using input driver 'evdev' for 'ImPS/2 Generic Wheel Mouse'
    [ 14.993] (**) ImPS/2 Generic Wheel Mouse: always reports core events
    [ 14.993] (**) evdev: ImPS/2 Generic Wheel Mouse: Device: "/dev/input/event5"
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Vendor 0x2 Product 0x5
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found 3 mouse buttons
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found scroll wheel(s)
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found relative axes
    [ 14.993] (--) evdev: ImPS/2 Generic Wheel Mouse: Found x and y relative axes
    [ 14.993] (II) evdev: ImPS/2 Generic Wheel Mouse: Configuring as mouse
    [ 14.993] (II) evdev: ImPS/2 Generic Wheel Mouse: Adding scrollwheel support
    [ 14.994] (**) evdev: ImPS/2 Generic Wheel Mouse: YAxisMapping: buttons 4 and 5
    [ 14.994] (**) evdev: ImPS/2 Generic Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 14.994] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input5/event5"
    [ 14.994] (II) XINPUT: Adding extended input device "ImPS/2 Generic Wheel Mouse" (type: MOUSE, id 10)
    [ 14.994] (II) evdev: ImPS/2 Generic Wheel Mouse: initialized for relative axes.
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) keeping acceleration scheme 1
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration profile 0
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration factor: 2.000
    [ 14.994] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration threshold: 4
    [ 14.994] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/mouse0)
    [ 14.994] (II) No input driver specified, ignoring this device.
    [ 14.994] (II) This device may have been added with another device file.
    [ 14.994] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    [ 14.994] (II) No input driver specified, ignoring this device.
    [ 14.994] (II) This device may have been added with another device file.
    [ 23.841] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 23.841] (II) intel(0): Using EDID range info for horizontal sync
    [ 23.841] (II) intel(0): Using EDID range info for vertical refresh
    [ 23.841] (II) intel(0): Printing DDC gathered Modelines:
    [ 23.841] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 23.841] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 23.842] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 23.842] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 23.842] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 23.842] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 23.842] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 23.842] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 23.842] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 23.884] (II) intel(0): switch to mode 1920x1080 on crtc 3 (pipe 0)
    [ 24.108] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 24.108] (II) intel(0): Using hsync ranges from config file
    [ 24.108] (II) intel(0): Using vrefresh ranges from config file
    [ 24.108] (II) intel(0): Printing DDC gathered Modelines:
    [ 24.108] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 24.108] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 24.108] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 24.108] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 24.108] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 24.108] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 24.108] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 24.108] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 24.108] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 33.191] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 33.191] (II) intel(0): Using hsync ranges from config file
    [ 33.191] (II) intel(0): Using vrefresh ranges from config file
    [ 33.191] (II) intel(0): Printing DDC gathered Modelines:
    [ 33.191] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 33.191] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 33.191] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 33.191] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 33.191] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 33.191] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 33.191] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 33.191] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 33.191] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 33.191] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 33.192] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 33.192] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 33.192] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 33.192] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 33.192] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 33.192] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 33.192] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 40.998] (II) intel(0): EDID vendor "GSM", prod id 22220
    [ 40.998] (II) intel(0): Using hsync ranges from config file
    [ 40.998] (II) intel(0): Using vrefresh ranges from config file
    [ 40.998] (II) intel(0): Printing DDC gathered Modelines:
    [ 40.998] (II) intel(0): Modeline "1920x1080"x0.0 138.50 1920 1968 2000 2080 1080 1083 1088 1111 +hsync -vsync (66.6 kHz eP)
    [ 40.998] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 40.998] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 40.998] (II) intel(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x960"x0.0 108.00 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync (60.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [ 40.998] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [ 40.998] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [ 40.998] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [ 40.998] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [ 40.998] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [ 936.094] (II) evdev: ImPS/2 Generic Wheel Mouse: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: AT Translated Set 2 keyboard: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: UVC Camera (046d:0825): Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: Power Button: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.094] (II) evdev: Power Button: Close
    [ 936.094] (II) UnloadModule: "evdev"
    [ 936.194] Server terminated successfully (0). Closing log file.
    kde log
    Note that your system uses syslog. All of kdm's internally generated messages
    (i.e., not from libraries and external programs/scripts it uses) go to the
    daemon.* syslog facility; check your syslog configuration to find out to which
    file(s) it is logged. PAM logs messages related to authentication to authpriv.*.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(7126) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(7120)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(7120)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    klauncher(7543) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(7537)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(7537)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    kdmgreet: Fatal IO error: client killed
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(326) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(285)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(285)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(341) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(294)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(294)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(273) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(264)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(264)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    klauncher(857) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(847)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(847)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    klauncher(1223) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(1215)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(1215)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Error: Can't find file "uk" for symbols include
    > Exiting
    > Abandoning symbols file "default"
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(269) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(263)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(263)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(706) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(700)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(700)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(2630) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(2624)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(2624)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(3118) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(3112)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(3112)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(4638) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(4632)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(4632)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    klauncher(5014) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(5008)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(5008)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    Server terminated successfully (0). Closing log file.
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extensio

  • Dual monitor setup and intel help

    Hello
    I am trying to set up and dual monitor setup here, with a monitor and a tv, the monitors resolution is 1680x1050, the tv's resolution is 1360x720, which results in that the desktop will have an resolution on 3040x1050.
    When I try to do this with GNOME's xrandr gui, I get this:
    required virtual size does not fit available size: requested=(3040, 1050), minimum=(320, 200), maximum=(1920, 1920)
    When looking in the motherboards manual, it states that each out of my graphics card can do a resolution of 1980x1080. Is the intel driver missunderstanding something? Since both the dvi and hdmi output only delivers 1360x720 and 1680x1050, 3040x1050 is only an virtual resolution.
    Any suggestions?

    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    EndSection
    Section "Files"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "record"
    Load "dbe"
    Load "extmod"
    Load "glx"
    Load "dri"
    Load "dri2"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbLayout" "no"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Monitor Vendor"
    ModelName "Monitor Model"
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "intel"
    VendorName "Intel Corporation"
    BoardName "4 Series Chipset Integrated Graphics Controller"
    BusID "PCI:0:2:0"
    Option "AccelMethod" "exa"
    Option "MigrationHeuristic" "greedy"
    EndSection
    Section "Device"
    Identifier "Card1"
    Driver "intel"
    VendorName "Intel Corporation"
    BoardName "4 Series Chipset Integrated Graphics Controller"
    BusID "PCI:0:2:1"
    Option "AccelMethod" "exa"
    Option "MigrationHeuristic" "greedy"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Card1"
    Monitor "Monitor1"
    Option "LeftOf" "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 24
    EndSubSection
    EndSection
    Section "ServerFlags"
    Option "AutoAddDevices" "False"
    EndSection
    Uhm do I only need one Screen section?

  • Separate workspaces on dual monitor setup?

    Sorry if I leave out any details -- just ask if you need anymore.
    A little background information before I begin: I am using 3.12-ck x86_64 kernel, using Cinnamon, and have a dual monitor setup via one graphics card, which is an NVIDIA 560 Ti, and I'm using nvidia-ck-bulldozer
    I'm trying to have each monitor have its own Workspace instead of just being one large desktop, but I'm not exactly sure how. The only solution I've found so far is:
    1) Right click the panels on Monitor #1 and choose "New Panel" -- (This is where my problem lies; there is no "New Panel" option)
    2) Then hold Alt and click and drag the new panel to Monitor #2 -- (I also cannot even move my current panel from monitor via clicking + key combos; I have to change the primary monitor in Cinnamon System Settings)
    But, as I said, this solution doesn't work for me. What exactly should I do?
    Edit:
    Forgot to mention, I'm using Cinnamon version 2.0.14
    Last edited by DealerNextDoor (2013-12-25 06:39:25)

    I am using the same version as you right now, but I couldn't find out what you are searching for. I think this is because this feature doesn't exist yet. See https://github.com/linuxmint/Cinnamon/issues/130

  • Quicktime screen record on multiple monitor setup error

    Hello, I am trying to record a webinar using Quicktime 10.2 on my three monitor setup (usb video cards). The program loads fine and I can drag the record area on the main monitor that I want to record and then I get an error saying "The operation cannot be completed". I'd appreciate any assitance, I've also had a similar problem trying to record with iShowU HD. I find it difficult that in 2014 I cannot not record on a 3 screen set up.

    Apple Menu / System Preferences / Displays / Arrangement
    Drag the Menu bar - the white strip that is on one of the rectangles -  to the cinema display rectangle.

  • HP Pavilion dv7-2250ed and dual monitor setup

    Good evening,
    Currently I own a HP Pavilion dv7-2250ed notebook using a dual monitor setup (notebook display + extra monitor)
    I wondered if it would be possible to hook 2 monitors to this laptop? (notebook display + extra monitor + extra monitor)
    If this causes the problem, the notebook display isn't requered.
    Also, if not, is there a dockingstation for this brand which supports the above?
    Kind Regards,
    Cor van Noorloos
    Edit: a note to the devs of these forums, using multiple tags is done by comma's, not by spaces. You might wish to rephrase this phrase.

    wgarn wrote:
    I have attempted to connect one monitor via HDMI and the other one via the VGA interface.
    Using Windows 7 OS and "default configurations" (Control Panel\Appearance and Personalization\Display\Screen Resolution) it is possible to use both external monitors as desktop. However the laptop screen will go blank. So at any time it appears to be possible to have an extended desktop with only two screens.
    - Does HP have any drivers/solutions that make it possible to extend the desktop from "Mobile PC" display to two additional desktops?
    - Has anyone tried third party software  (e.g.. UltraMon)?
    - Is there a technical restriction (e.g.. Videocard capability)?
    - How about using a Linux OS (e.g.. Ubuntu)?
    - What external Hardware exists that would enable me to extend my desktop to three or more monitors simultaneously?
    Many thanks in advance.
    It's the graphics card and the number of physical connections available.  You might have 3 connections (notebook display being one) but the graphics card likely does not support more than 2 monitors.  Intel graphics only support 2, however you may be able to find some AMD chips that will support more however that would be a major upgrade.
    ________________________________________________________________________________________________________ I Love Kudos! If you feel my post has helped you please click the White Kudos! Star just below my name
    If you feel my answer has fixed your problem please click 'Mark As Solution' and make it easier for others to find help quickly

  • Preview app opens "split screen" on dual monitor setup

    This is a minor issue, I rarely use the utilility "Preview" app. but I'd still like to understand this issue....I use a two monitor setup (MBP & StudioDisplay)..
    The following happens if the window was last closed in "expanded" mode (you can see options for Drawer, rotate, etc)
    When "Preview" launches and opens a window, it places the top portion of the window on the secondary display and bottom part of the window on the primary display.
    This Does Not happen if the window was last closed in "non-exanded" (collasped) mode (sorry, I don't know the proper term).
    In other words, in respect to it's position on the screen, when the window opens it always assumes it's in "collasped" mode.
    Weird... any comments?

    There's something wrong with the way Preview handles dual monitors. In my case if I open a smallish item, for instance a small png, instead of opening in the upper left corner of my main monitor it opens so that about half an inch of the Preview window is sticking over onto the second monitor (which is to the left of my main monitor). I had never "collapsed" the tool bar before, so I just now tried that on a small png, then closed it and re-opened. Sure enough, without the toolbar it opens properly. Display the toolbar, close, reopen, and it sticks onto the second monitor. Weird indeed. Larger size files open normally.
    This started with the Tiger version of Preview. If you wish you can send feedback:
    http://www.apple.com/macosx/feedback/
    Maybe it will help get this odd bug squashed in a future version of Preview.
    Francine
    Francine
    Schwieder

Maybe you are looking for

  • Email attachments in PDF

    I am using Windows XP and have Adobe Reader 9. The message attachment comes in to us with winmail.dat but the attachment was sent to us using PDF producer Acrobat Distiller 6.0 (windows) PDF version 1.4 (Acrobat 5.x) why does it do this? we need to b

  • Migrate data from B&W G3

    My old B&W G3 has some problems - it won't boot into OS9.2.2 unless the Mac install disc is in the machine (already tried new battery). It's a workaround, but that's not my main concern. I want to move all the important data onto my G5. Tried to conn

  • Running Sproxy from ECC 6.0/ SAP NW 7.0 - BI service pack 16

    We have ECC 6.0 / SAP Netweave BI 7.0 sps 16 I want run Sproxy, after this new service pack I could not figure out how to run SPROXY by giving oue own data. Earlier I have use dSPROXY, when I run it ask for Generate XML template, i could paste the da

  • I cant open my id iTunes

    How to open my itnunes id

  • H.264 export without audio creates files that are not recognized in Quicktime or VLC

    Dear all, I need to generate h.264 files with video only. (short clips for use with a "clickable" catalog on an iPad) Used the "H.264" category and chose a preset. Unchecked "Audio" so I only get the video exported. The resulting .m4v file is not pla