Much of my text looks fuzzy until I roll over it with my mouse

much of the text looks out of focus until i roll over it with my mouse, then it is clearly readable

This usually occurs because you're printing a photo in an Aspect Ratio different from the actual shot. The Aspect Ratio is the shape of the photo, expressed as the length x breadth.
So, if you have - for instance - a 4:3 shot and try print that at  4:6 you will have issues.

Similar Messages

  • When I copy and paste text in facebook, the text looks fine until I hit 'share' or 'comment' to submit it. Firefox then adds indiscriminate line-feeds within the text and it looks nothing like the original text. This does not happen in Safari. (Mac OSX 10

    When I copy and paste text in facebook, the text looks fine until I hit 'share' or 'comment' to submit it. Firefox then adds indiscriminate line-feeds within the text and it looks nothing like the original text. It makes it very difficult to read and awful to look at.
    This does not happen in Safari.
    (Mac OSX 10.6.4 with Firefox 3.6.6).
    == URL of affected sites ==
    http://

    Same problem, 3.6.8 and previous recent versions. I never thought to try another browser but I just pasted into IE and it worked fine. I copied from Firefox to IE and it worked as well. It's just when you paste into Firefox that you get the weird line breaks.

  • How come my text looks fuzzy on CS6 ?

    how come my text looks fuzzy on CS6 ?
    Is it the ADOBE problem or the MAC BOOK PRO 2013 problem?

    What text? You need to provide more info and possibly screenshots. Could be one of those Retina things, so make sure to apply all the latest updates for your Adobe products.
    Mylenium

  • How can i change the color of the text on a button in Roll Over or Click state (Cs5.5)

    Hello,
    Here is the problematic:
    1° How can i change the color of the text on a button in Roll Over or Click state (Cs5.5)
    - I've many button in a doc im creating
    - the color of the buttons is white with black stoke & black text
    - in roll over state i want them to inverse the color coding (the text white & bottom black)
    - currently the text becomes invisible as black on black cant be seen (ive stroked it white but that looks ugly)
    - i would just like to know if there is a function made for this?
    My other questions:
    2° Ive a presentation on which Ive created buttons which tigger pop-up animations
    - i have 5 buttons which trigger animations
    - the viewer can chose to Click on any of the buttons randomly
    - the problem is once the animation is open how can it be close... either:
    a) by it self after "40" seconds
    b) when ther viewer clicks another button
    3° Ive created buttons linking pages..
    - "go to page xxx"
    - when i do a preview and click on the buttons the links dont take me to the right pages
    - is that normal? (maybe in preview its suppose to be like that)
    4° I would like to intergrate YouTube videos in the presentation so they play inside the docment.. when i tried.. it said the 'link isnt a flash video'
    - what should i do?
    5° Once i export it into Swf. how how can i visualize it? or put it online?
    Thank you for your time.

    stlbbl4u wrote:
    Hello,
    Here is the problematic:
    1° How can i change the color of the text on a button in Roll Over or Click state (Cs5.5)
    - I've many button in a doc im creating
    - the color of the buttons is white with black stoke & black text
    - in roll over state i want them to inverse the color coding (the text white & bottom black)
    - currently the text becomes invisible as black on black cant be seen (ive stroked it white but that looks ugly)
    - i would just like to know if there is a function made for this?
    You should setup Object Styles - these can also include Paragarph Styles that can be triggered when the Style is selected.
    http://help.adobe.com/en_US/indesign/cs/using/WS5CEDB81A-0011-4dc9-9DE8-AC7AD4C80076a.html
    My other questions:
    2° Ive a presentation on which Ive created buttons which tigger pop-up animations
    - i have 5 buttons which trigger animations
    - the viewer can chose to Click on any of the buttons randomly
    - the problem is once the animation is open how can it be close... either:
    a) by it self after "40" seconds
    b) when ther viewer clicks another button
    I'm not sure what you mean - I don't do files with Animations
    3° Ive created buttons linking pages..- "go to page xxx"
    - when i do a preview and click on the buttons the links dont take me to the right pages
    - is that normal? (maybe in preview its suppose to be like that)
    Does it work properly when you export it to the finished file?
    4° I would like to intergrate YouTube videos in the presentation so they play inside the docment.. when i tried.. it said the 'link isnt a flash video'- what should i do?
    InDesign won't link directly to youtube videos. I think your best bet would be to use Downloader to download the video and embed them directly in Indesign.
    5° Once i export it into Swf. how how can i visualize it? or put it online? 
    Thank you for your time.
    You can look up how to embed a SWF file into your HTML - but it depends what you mean by "online" there's a dozen ways to get a file "online".

  • The type seems fuzzy, and when rolling over a link the underline is sharp on both ends like a javelin. Can the type be sharpened up?

    I thought it was my computer that was out of wack, but it turns out it started happening when I upgraded to Firefox 5.

    If you have an advanced graphics card, Firefox tries to use hardware acceleration for your fonts as well as for other graphics tasks. This isn't always pretty. You might want to turn it off for now, and keep an eye on other threads here for future developments.
    orange Firefox button ''or'' Tools menu > Options > Advanced
    On the Advanced tab > General sub-tab > ''uncheck'' "Use hardware acceleration when available"
    Then restart Firefox. Does text look normal again?

  • Button roll-over animation with dynamic text

    So I have a button I want to be able to use over and over. When you roll over the button, it does an animation and has a dynamic text box in it. Ovbiously im trying to make each text different for each button. What would be the smartest way to go about this? Thanks,
    Dan

    create a movieclip, put a stop() in frame one and add your "up" graphics, textfield etc put everything in its own layer.  create another keyframe on that timeline and label the frame "over" and add new keyframes only on the layers that will change.  ie, if the textfield doesn't change, don't put a keyframe on its layer.  likewise, for a "down" frame, if you want one.
    use instance names for everything in the movieclip that you want to control with actionscript.  ie, your textfield(s) will need instance name(s).  i usually use one textfield named tf.
    then use:
    btn1.tf.text = "test"
    btn1.addEventListener(MouseEvent.ROLL_OVER,overF);
    btn1.addEventListener(MouseEvent.ROLL_OUT,outF);
    btn1.addEventListener(MouseEvent.MOUSE_DOWN,downF);
    function overF(e:Event){
    // if you have another textfield here assign its text
    // likewise for other objects you want to change
    e.currentTarget.gotoAndStop("over");
    function outF(e:Event){
    // if you changed textfields in the other frames, reassign tf.text here
    e.currentTarget.gotoAndStop(1);
    function downF(e:Event){
    // if you have another textfield here assign its text
    e.currentTarget.gotoAndStop("down");

  • Rendered text looks low res

    I've read every post I could find about this and gleaned some insight, but still need a more definitive answer than I've come across. I created title cards using the 2D FCE program, as the boris Calligraphy program seemed too complcated for what I need to do and I'm running out of time.
    Problem is, the text looks fine until I render it. Render User Settings are 100% for Frame Rate and Resolution. Filters, Frame blending and Motion Blur are all checkmarked. I've tried various combinations of those uncheckmarked. No improvement.
    The fonts are Gill Sans plain 27 pt. and Geneva bold italic 24 pt., but it doesn't matter what the fonts are, or the point size, or whether it's the graphic bar I created from a rectangular shape... They all look degraded after render, like a low res approximation for playback. The type, however big or bold gets suddenly darker, and less cleanly defined and the graphic bar actually shortens slightly. Is that in fact what it is, just a low res way of playing back, so I shouldn't worry about how it looks here? However, a fairly knowledgable friend says the image shouldn't look degraded after render. Ultimately going to DVD. Please straighten me out here. Much thanks.

    The material is being rendered into an interlaced
    digital format for display on an interlaced analog
    monitor. It's not intended for display on a computer
    screen. The Canvas is for monitoring purposes only.
    If you really want to see how it looks set the Canvas
    to 100% view. That's the true interlaced image as it
    will appear. Of course you can't see this properly on
    a computer screen especially if the material has
    motion or is animated.
    Thanks, Tom, for the explanation and your patience. All is clear except that you suggest that if I really want to see what it looks like, to set the canvas to 100%... that that's the true interlaced image as it will appear. I must be misunderstanding, but when I set the view to 100%, I get an enlarged, TV Safe sort of view, but the resolution looks the same (de-interlaced) as always after the render. Basically what I'm asking is whether the eventual video will look like (with, of course, the normal degradation of NTSC) what I created on 2D text or graphics BEFORE I rendered it.
    I tried to check it on a monitor, but when I plugged Video Out from my G4 to the monitor, I got a nice image of the FCE interface on TV, rather than a screenfilling view of the selected sequence. What am I doing wrong here?
    Thank you again. I don't know how you put up with these kind of questions, but I deeply appreciate it. Restores my faith in mankind.
    - Frazzled in SF

  • Why are my programs glitching and everything become hidden until you hover over it

    Over the past few days my adobe programs have been failing on me.
    layers and their details have become invisible and various menu buttons and text will disappear until you hover over it.
    I am not sure why this is happening and it is stressful when I am trying to get projects done...

    I have Mavericks, now when I am in dreamweaver certain buttons are glitches out and rainbow colours?? super confused...

  • PDF alt text displays as a roll over

    When I generate PDFs, the alt text is displayed when I roll over the figure to which the alt text is assigned. Is there any way to keep the alt text but turn off the roll over effect?
    I have a customer who finds the roll over effect bothersome.
    thanks for any assistance.
    Steve

    No - if there's some ALT text, the Acrobat Family will always show it.

  • Text buttons and roll over

    Hi
    I have text buttons and want to make the text bold when the user rolls over. (this is a menu)
    Are there any other ways besides having the text as a master slide and then click boxes and roll overs, I realise I can do text buttons but there is a small icon that I need at the front of the text which will also need to be clickable.
    thanks

    Bold only when rolling over? That means that you will not be able to use it for HTML5 output? Only SWF is OK?
    My first idea is to use the EventHandler widget of InfoSemantics (not free but you can download a trial version), because it can create a rollover event for your text button. Anyway you'll have to create a transparent text container (shape or caption) that has the Bold Text and appears when rolling over. If you don't want to go with that widget, you can simulate the same by using the Rollover slidelet (you'll need only the Area, can drag the Slidelet itself outside of the sldie), that has a rollover event that can trigger an action to show that previously hidden transparent text.
    Welcome to the forum, just one tip: mention the version number (exact number, which you find under Help, About Captivate) when you post a question.
    Lilybiri

  • In Preview, when I add text annotations to my PDF (lecture note slides), they look fine until I close it and reopen it, and then they are rotated 90 degrees. How do I fix this and keep it from happening again?

    In Preview, when I add text annotations to my PDF (lecture note slides), they look fine until I close it and reopen it, and then they are rotated 90 degrees. How do I fix this and keep it from happening again?

    I have the same problem with lectures slides.
    Furthermore, sometimes the text box, when doube-clicking, turns  the text into a one-liner. Causing the text box to sometimes get 3. times wider than the pdf itself.
    tcrother wrote:
    ... then when it rotates the text isn't visible and I'm stuck clicking on random parts of my lecture slides hoping the text box will come back. ...
    By pressing [cmd + I] the Inspector opens up and clicking on the rightmost tab 'Annotations' you should be able find those Annotations again. I do this regularly to find the empty annotations I accidentally create while clicking through slides.

  • Rotated Text/Images look fuzzy when Published

    I've a menu on my site which uses angled text. As soon as I publish this however, the text gets fuzzy edges. I thought I could get over this issue by creating the links in my meny as graphics in PS and importing them as buttons but as soon as I roate them in Muse they get fuzzy edges again.
    I havn't made the site live yet as it's in very early design stages.
    Does anyone have an answer to fix this issue? Thanks

    Thanks for coming back to me! I tried that actually as well. I rotated the images which are the links in PS and then imported them and it works fine from a quality point of view but it introduced another issue. My menu is basically composed of links at an angle as I was saying but I save this as a rectangle from PS and import. Only the centre part of this rectangle has text, the rest is transparent. When I align them all up in Muse, some of the links overlap which causes issues with my buttons. If I roll over one, it activates the one beside it. I couldn't see any other way around this other than to create them flat and then rotate them in muse. Do you see how I can fix this?

  • Text looks blurred on Samsung display

    Hi,
    So, I have just gotten a Samsung SyncMaster TA550 for Christmas. I have it connected to my MBP13 mid-2012 (2,5GHz i5, 8GB of RAM, Intel HD Graphics 4000) with a HDMI cable and a Dr. Bott HDMI & DVI to Mini Displayport adapter.
    The display looks absolutely fabulous as long as watch videos, but text looks like crap, all blurry, and gives me headaches, not matter if it's text I'm currently writing (in pages or online) or the song list in iTunes for example. The problem is: I mainly wanted to use this display for writing. Also the bars in pretty much every programme I've used so far have this strange grey blur to them.
    I'll attach screencaps of both text and video on the screen. You'll see the grey blur in the safari window.
    I toyed around with resolutions and practically all the display settings in OS X and the display itself - nothing worked. It looks slightly better when I change to 720p instead of 1080p or 1080i using underscan to fill the display, but that's not what we want, right?
    Currently it's set back to "Best for display" and a 60 hertz refresh rate.
    I thought that maybe the adapter (which wasn't a particularly expensive one) might be the problem, so I have now ordered a HDMI to Mini Displayport cable that had good reviews online. It might take a few days for that one to arrive though, and I was hoping that maybe I could solve the problem without having to use that one.
    I hope you'll be able to help me, cause honestly, this is getting annoying.
    Thanks in advance,
    Sabrina
    Strangely the screencap looks good on my MBP's LCD...

    I have been switching from PC to MAC for the last couple years. One of the last bones was my desktop computer which had a SAMSUNG 29'' HD monitor.
    Last friday I bought a MAC MINI and connected it to the Samsung thru HDMI. I had almost a breakdown when I realized the blurry text from the OS X against the crisp and bright text from the Windows machine. I started to investigate without any luck until I came across this post. Thank you MissKillALot, you save my day! Finally now I have a monitor working like it should, and no more PCs at home!!!
    P.S. No wonder people keep ditching Samsung equipment: For the HDMI - DVI PC port to work properly you have to "RENAME" the port from HDMI to DVI PC. Rename? Who thinks that by "renaming" some port it will actually change its properties? Is this on purpose to annoy the user?

  • Photoshop file looks fuzzy after render

    I have an RGB Photoshop file over a white color matte over video. It's text I created in PSCS2, nothing rasterized, with transparency. When I bring the PS file into the timeline it looks crisp and legible, but when I render to preview the timeline, the text gets fuzzy and it starts to look pixelated on the monitor like when you start scaling up too much. I have my RT set to high as well. Any ideas?

    what color is the render bar in this portion of the timeline? if its bright green then what you're seeing during playback is the realtime "preview" quality, not the fully rendered quality as you see when the playhead is parked
    another issue you should consider is the placement of the graphic. in the motion properties make sure its placed on a whole even numbered y cordinate, otherwise you may see a slight softening of the image due to interlace issues (unless i'm confusing this with a diferent issue)

  • Screen display looks fuzzy using xf86-video-intel on a HP Pavilion 23

    Hello,
    First off I want to say, thank you for Arch! Been using some distros on and off and I think I found my /home! I made a full plunge into Linux a bit ago after some Windows 8.1 issues, switched to Arch and not looking back. Anyways, So far all my computers are either Arch or Manjaro which I am moving more towards straight arch as Manjaro does have some issues when updating your system (dependency loops). All and all not bad, just liking the full control of a pure system then building from scratch.
    Ok, the issue at hand. I have removed Windows 8.1 from my HP All in One Pavilion 23 machine....what a nightmare that was.... Everything was good after turning off secure boot. I installed Arch Linux (3.14.4-1) x86_64, and I am having issues getting the xf86-video-intel driver to play nice with X.
    I have taken a screenshot:
    Screenshot
    I notice this starts right after the choosing the Arch Linux from the boot option menu. It starts the load nice and crisp but after a second the screen flickers with some lines at the top of the screen, random colors, only about the top 3rd of the screen. This modules begin to load but the terminal text looks blocky and horrible.
    I am using Openbox 3.5.2-6 with slim 1.3.6-4. Running xorg-server 1.15.1-1 and xorg-server-utils 7.6-3 with all the dependencies of course.
    Output from pacman queries for video drivers
    xf86-video-intel 2.99.911-2
    xf86-video-vesa 2.3.2-4
    lspci output
    00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
    00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
    00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
    00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
    00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05)
    00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
    00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
    00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
    00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
    00:1c.5 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 (rev d5)
    00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05)
    00:1f.0 ISA bridge: Intel Corporation H87 Express LPC Controller (rev 05)
    00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05)
    00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
    02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
    03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
    04:00.0 Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01)
    my /etc/mkinitcpio.conf
    # vim:set ft=sh
    # MODULES
    # The following modules are loaded before any boot hooks are
    # run. Advanced users may wish to specify all system modules
    # in this array. For instance:
    # MODULES="piix ide_disk reiserfs"
    MODULES="i915"
    # BINARIES
    # This setting includes any additional binaries a given user may
    # wish into the CPIO image. This is run last, so it may be used to
    # override the actual binaries included by a given hook
    # BINARIES are dependency parsed, so you may safely ignore libraries
    BINARIES=""
    # FILES
    # This setting is similar to BINARIES above, however, files are added
    # as-is and are not parsed in any way. This is useful for config files.
    FILES=""
    # HOOKS
    # This is the most important setting in this file. The HOOKS control the
    # modules and scripts added to the image, and what happens at boot time.
    # Order is important, and it is recommended that you do not change the
    # order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
    # help on a given hook.
    # 'base' is _required_ unless you know precisely what you are doing.
    # 'udev' is _required_ in order to automatically load modules
    # 'filesystems' is _required_ unless you specify your fs modules in MODULES
    # Examples:
    ## This setup specifies all modules in the MODULES setting above.
    ## No raid, lvm2, or encrypted root is needed.
    # HOOKS="base"
    ## This setup will autodetect all modules for your system and should
    ## work as a sane default
    # HOOKS="base udev autodetect block filesystems"
    ## This setup will generate a 'full' image which supports most systems.
    ## No autodetection is done.
    # HOOKS="base udev block filesystems"
    ## This setup assembles a pata mdadm array with an encrypted root FS.
    ## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
    # HOOKS="base udev block mdadm encrypt filesystems"
    ## This setup loads an lvm2 volume group on a usb device.
    # HOOKS="base udev block lvm2 filesystems"
    ## NOTE: If you have /usr on a separate partition, you MUST include the
    # usr, fsck and shutdown hooks.
    HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
    # COMPRESSION
    # Use this to compress the initramfs image. By default, gzip compression
    # is used. Use 'cat' to create an uncompressed image.
    #COMPRESSION="gzip"
    #COMPRESSION="bzip2"
    #COMPRESSION="lzma"
    #COMPRESSION="xz"
    #COMPRESSION="lzop"
    #COMPRESSION="lz4"
    # COMPRESSION_OPTIONS
    # Additional options for the compressor
    #COMPRESSION_OPTIONS=""
    ,my /etc/default/grub.conf
    GRUB_DEFAULT=0
    GRUB_TIMEOUT=5
    GRUB_DISTRIBUTOR="Arch"
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    GRUB_CMDLINE_LINUX=""
    # Preload both GPT and MBR modules so that they are not missed
    GRUB_PRELOAD_MODULES="part_gpt part_msdos"
    # Uncomment to enable Hidden Menu, and optionally hide the timeout count
    #GRUB_HIDDEN_TIMEOUT=5
    #GRUB_HIDDEN_TIMEOUT_QUIET=true
    # Uncomment to use basic console
    GRUB_TERMINAL_INPUT=console
    # Uncomment to disable graphical terminal
    #GRUB_TERMINAL_OUTPUT=console
    # The resolution used on graphical terminal
    # note that you can use only modes which your graphic card supports via VBE
    # you can see them in real GRUB with the command `vbeinfo'
    GRUB_GFXMODE=auto
    # Uncomment to allow the kernel use the same resolution used by grub
    GRUB_GFXPAYLOAD_LINUX=keep
    # Uncomment if you want GRUB to pass to the Linux kernel the old parameter
    # format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
    #GRUB_DISABLE_LINUX_UUID=true
    # Uncomment to disable generation of recovery mode menu entries
    GRUB_DISABLE_RECOVERY=true
    # Uncomment and set to the desired menu colors. Used by normal and wallpaper
    # modes only. Entries specified as foreground/background.
    #GRUB_COLOR_NORMAL="light-blue/black"
    #GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
    # Uncomment one of them for the gfx desired, a image background or a gfxtheme
    #GRUB_BACKGROUND="/path/to/wallpaper"
    #GRUB_THEME="/path/to/gfxtheme"
    # Uncomment to get a beep at GRUB start
    #GRUB_INIT_TUNE="480 440 1"
    #GRUB_SAVEDEFAULT="true"
    And last my /var/log/Xorg.0.log
    [ 15.641]
    X.Org X Server 1.15.1
    Release Date: 2014-04-13
    [ 15.641] X Protocol Version 11, Revision 0
    [ 15.641] Build Operating System: Linux 3.14.0-4-ARCH x86_64
    [ 15.641] Current Operating System: Linux localhost 3.14.4-1-ARCH #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014 x86_64
    [ 15.641] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=0c1916a0-b631-478f-ac6b-aa5d123f75cd rw quiet splash
    [ 15.641] Build Date: 14 April 2014 08:39:09AM
    [ 15.641]
    [ 15.641] Current version of pixman: 0.32.4
    [ 15.641] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 15.641] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 15.641] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Jun 1 17:05:15 2014
    [ 15.687] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 15.687] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 15.739] (==) No Layout section. Using the first Screen section.
    [ 15.739] (==) No screen section available. Using defaults.
    [ 15.739] (**) |-->Screen "Default Screen Section" (0)
    [ 15.739] (**) | |-->Monitor "<default monitor>"
    [ 15.764] (==) No device specified for screen "Default Screen Section".
    Using the first device section listed.
    [ 15.764] (**) | |-->Device "Intel Graphics"
    [ 15.764] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 15.764] (==) Automatically adding devices
    [ 15.764] (==) Automatically enabling devices
    [ 15.764] (==) Automatically adding GPU devices
    [ 15.793] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 15.793] Entry deleted from font path.
    [ 15.795] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 15.795] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 15.795] (**) Extension "Composite" is enabled
    [ 15.795] (**) Extension "RENDER" is enabled
    [ 15.795] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 15.795] (II) Loader magic: 0x804c80
    [ 15.795] (II) Module ABI versions:
    [ 15.795] X.Org ANSI C Emulation: 0.4
    [ 15.795] X.Org Video Driver: 15.0
    [ 15.795] X.Org XInput driver : 20.0
    [ 15.796] X.Org Server Extension : 8.0
    [ 15.796] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 15.798] (--) PCI:*(0:0:2:0) 8086:0412:103c:2b0f rev 6, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64
    [ 15.798] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 15.798] Initializing built-in extension Generic Event Extension
    [ 15.798] Initializing built-in extension SHAPE
    [ 15.798] Initializing built-in extension MIT-SHM
    [ 15.798] Initializing built-in extension XInputExtension
    [ 15.798] Initializing built-in extension XTEST
    [ 15.798] Initializing built-in extension BIG-REQUESTS
    [ 15.798] Initializing built-in extension SYNC
    [ 15.798] Initializing built-in extension XKEYBOARD
    [ 15.798] Initializing built-in extension XC-MISC
    [ 15.798] Initializing built-in extension SECURITY
    [ 15.798] Initializing built-in extension XINERAMA
    [ 15.798] Initializing built-in extension XFIXES
    [ 15.798] Initializing built-in extension RENDER
    [ 15.799] Initializing built-in extension RANDR
    [ 15.799] Initializing built-in extension COMPOSITE
    [ 15.799] Initializing built-in extension DAMAGE
    [ 15.799] Initializing built-in extension MIT-SCREEN-SAVER
    [ 15.799] Initializing built-in extension DOUBLE-BUFFER
    [ 15.799] Initializing built-in extension RECORD
    [ 15.799] Initializing built-in extension DPMS
    [ 15.799] Initializing built-in extension Present
    [ 15.799] Initializing built-in extension DRI3
    [ 15.799] Initializing built-in extension X-Resource
    [ 15.799] Initializing built-in extension XVideo
    [ 15.799] Initializing built-in extension XVideo-MotionCompensation
    [ 15.799] Initializing built-in extension XFree86-VidModeExtension
    [ 15.799] Initializing built-in extension XFree86-DGA
    [ 15.799] Initializing built-in extension XFree86-DRI
    [ 15.799] Initializing built-in extension DRI2
    [ 15.799] (II) "glx" will be loaded by default.
    [ 15.799] (II) LoadModule: "dri2"
    [ 15.799] (II) Module "dri2" already built-in
    [ 15.799] (II) LoadModule: "glamoregl"
    [ 15.808] (II) Loading /usr/lib/xorg/modules/libglamoregl.so
    [ 15.917] (II) Module glamoregl: vendor="X.Org Foundation"
    [ 15.917] compiled for 1.15.0, module version = 0.6.0
    [ 15.917] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 15.917] (II) LoadModule: "glx"
    [ 15.917] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 15.928] (II) Module glx: vendor="X.Org Foundation"
    [ 15.929] compiled for 1.15.1, module version = 1.0.0
    [ 15.929] ABI class: X.Org Server Extension, version 8.0
    [ 15.929] (==) AIGLX enabled
    [ 15.929] Loading extension GLX
    [ 15.929] (II) LoadModule: "intel"
    [ 15.929] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 15.955] (II) Module intel: vendor="X.Org Foundation"
    [ 15.955] compiled for 1.15.0, module version = 2.99.911
    [ 15.955] Module class: X.Org Video Driver
    [ 15.955] ABI class: X.Org Video Driver, version 15.0
    [ 15.955] (II) intel: Driver for Intel(R) 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
    [ 15.956] (II) intel: Driver for Intel(R) HD Graphics: 2000-5000
    [ 15.956] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100
    [ 15.956] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200
    [ 15.956] (++) using VT number 7
    [ 15.971] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4600
    [ 15.971] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx, avx2
    [ 15.971] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 15.971] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 15.971] (==) intel(0): RGB weight 888
    [ 15.971] (==) intel(0): Default visual is TrueColor
    [ 15.971] (**) intel(0): Option "AccelMethod" "sna"
    [ 15.971] (**) intel(0): Option "DRI" "true"
    [ 15.971] (**) intel(0): Option "TearFree" "true"
    [ 15.972] (**) intel(0): Framebuffer tiled
    [ 15.972] (**) intel(0): Pixmaps tiled
    [ 15.972] (**) intel(0): "Tear free" enabled
    [ 15.972] (**) intel(0): Forcing per-crtc-pixmaps? no
    [ 15.972] (II) intel(0): Output eDP1 has no monitor section
    [ 15.972] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output eDP1
    [ 15.972] (II) intel(0): Output VGA1 has no monitor section
    [ 15.972] (II) intel(0): Output DP1 has no monitor section
    [ 15.972] (II) intel(0): Output HDMI1 has no monitor section
    [ 15.972] (II) intel(0): Output DP2 has no monitor section
    [ 15.972] (II) intel(0): Output HDMI2 has no monitor section
    [ 15.972] (II) intel(0): Output VIRTUAL1 has no monitor section
    [ 15.972] (--) intel(0): Output eDP1 using initial mode 1920x1080 on pipe 0
    [ 15.972] (==) intel(0): DPI set to (96, 96)
    [ 15.972] (II) Loading sub module "dri2"
    [ 15.972] (II) LoadModule: "dri2"
    [ 15.972] (II) Module "dri2" already built-in
    [ 15.972] (==) Depth 24 pixmap format is 32 bpp
    [ 15.986] (II) intel(0): SNA initialized with Haswell (gen7.5, gt2) backend
    [ 15.986] (==) intel(0): Backing store enabled
    [ 15.986] (==) intel(0): Silken mouse enabled
    [ 15.986] (II) intel(0): HW Cursor enabled
    [ 15.986] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 15.987] (==) intel(0): DPMS enabled
    [ 15.987] (II) intel(0): [DRI2] Setup complete
    [ 15.987] (II) intel(0): [DRI2] DRI driver: i965
    [ 15.987] (II) intel(0): [DRI2] VDPAU driver: i965
    [ 15.987] (II) intel(0): direct rendering: DRI2 Enabled
    [ 15.987] (==) intel(0): hotplug detection: "enabled"
    [ 15.987] (--) RandR disabled
    [ 16.067] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 16.067] (II) AIGLX: enabled GLX_ARB_create_context
    [ 16.067] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 16.067] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 16.067] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 16.067] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 16.067] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 16.067] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 16.067] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 16.067] (II) AIGLX: enabled GLX_ARB_create_context_robustness
    [ 16.067] (II) AIGLX: Loaded and initialized i965
    [ 16.067] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 16.085] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 16.107] (II) intel(0): Setting screen physical size to 508 x 285
    [ 16.375] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [ 16.375] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 16.375] (II) LoadModule: "evdev"
    [ 16.383] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 16.402] (II) Module evdev: vendor="X.Org Foundation"
    [ 16.402] compiled for 1.15.1, module version = 2.9.0
    [ 16.402] Module class: X.Org XInput Driver
    [ 16.402] ABI class: X.Org XInput driver, version 20.0
    [ 16.402] (II) Using input driver 'evdev' for 'Power Button'
    [ 16.402] (**) Power Button: always reports core events
    [ 16.402] (**) evdev: Power Button: Device: "/dev/input/event1"
    [ 16.402] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 16.402] (--) evdev: Power Button: Found keys
    [ 16.402] (II) evdev: Power Button: Configuring as keyboard
    [ 16.402] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
    [ 16.402] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 16.402] (**) Option "xkb_rules" "evdev"
    [ 16.402] (**) Option "xkb_model" "pc104"
    [ 16.402] (**) Option "xkb_layout" "us"
    [ 16.442] (II) config/udev: Adding input device Video Bus (/dev/input/event2)
    [ 16.442] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 16.442] (II) Using input driver 'evdev' for 'Video Bus'
    [ 16.442] (**) Video Bus: always reports core events
    [ 16.442] (**) evdev: Video Bus: Device: "/dev/input/event2"
    [ 16.442] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 16.442] (--) evdev: Video Bus: Found keys
    [ 16.442] (II) evdev: Video Bus: Configuring as keyboard
    [ 16.442] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/input/input2/event2"
    [ 16.442] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 16.442] (**) Option "xkb_rules" "evdev"
    [ 16.442] (**) Option "xkb_model" "pc104"
    [ 16.442] (**) Option "xkb_layout" "us"
    [ 16.443] (II) config/udev: Adding input device Power Button (/dev/input/event0)
    [ 16.443] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 16.443] (II) Using input driver 'evdev' for 'Power Button'
    [ 16.443] (**) Power Button: always reports core events
    [ 16.443] (**) evdev: Power Button: Device: "/dev/input/event0"
    [ 16.443] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 16.443] (--) evdev: Power Button: Found keys
    [ 16.443] (II) evdev: Power Button: Configuring as keyboard
    [ 16.443] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
    [ 16.443] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
    [ 16.443] (**) Option "xkb_rules" "evdev"
    [ 16.443] (**) Option "xkb_model" "pc104"
    [ 16.443] (**) Option "xkb_layout" "us"
    [ 16.444] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 16.444] (II) config/udev: Adding input device HP High Definition 1MP Webcam (/dev/input/event8)
    [ 16.444] (**) HP High Definition 1MP Webcam: Applying InputClass "evdev keyboard catchall"
    [ 16.444] (II) Using input driver 'evdev' for 'HP High Definition 1MP Webcam'
    [ 16.444] (**) HP High Definition 1MP Webcam: always reports core events
    [ 16.444] (**) evdev: HP High Definition 1MP Webcam: Device: "/dev/input/event8"
    [ 16.444] (--) evdev: HP High Definition 1MP Webcam: Vendor 0x4f2 Product 0xb40b
    [ 16.444] (--) evdev: HP High Definition 1MP Webcam: Found keys
    [ 16.444] (II) evdev: HP High Definition 1MP Webcam: Configuring as keyboard
    [ 16.444] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input8/event8"
    [ 16.444] (II) XINPUT: Adding extended input device "HP High Definition 1MP Webcam" (type: KEYBOARD, id 9)
    [ 16.444] (**) Option "xkb_rules" "evdev"
    [ 16.444] (**) Option "xkb_model" "pc104"
    [ 16.445] (**) Option "xkb_layout" "us"
    [ 16.445] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event14)
    [ 16.445] (**) NextWindow Touchscreen: Applying InputClass "evdev touchscreen catchall"
    [ 16.445] (II) Using input driver 'evdev' for 'NextWindow Touchscreen'
    [ 16.445] (**) NextWindow Touchscreen: always reports core events
    [ 16.445] (**) evdev: NextWindow Touchscreen: Device: "/dev/input/event14"
    [ 16.445] (--) evdev: NextWindow Touchscreen: Vendor 0x1926 Product 0x33e
    [ 16.445] (--) evdev: NextWindow Touchscreen: Found absolute axes
    [ 16.445] (--) evdev: NextWindow Touchscreen: Found absolute multitouch axes
    [ 16.445] (II) evdev: NextWindow Touchscreen: No buttons found, faking one.
    [ 16.445] (--) evdev: NextWindow Touchscreen: Found x and y absolute axes
    [ 16.445] (--) evdev: NextWindow Touchscreen: Found absolute touchscreen
    [ 16.445] (II) evdev: NextWindow Touchscreen: Configuring as touchscreen
    [ 16.445] (**) evdev: NextWindow Touchscreen: YAxisMapping: buttons 4 and 5
    [ 16.445] (**) evdev: NextWindow Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 16.446] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/0003:1926:033E.0001/input/input14/event14"
    [ 16.446] (II) XINPUT: Adding extended input device "NextWindow Touchscreen" (type: TOUCHSCREEN, id 10)
    [ 16.446] (II) evdev: NextWindow Touchscreen: initialized for absolute axes.
    [ 16.446] (**) NextWindow Touchscreen: (accel) keeping acceleration scheme 1
    [ 16.446] (**) NextWindow Touchscreen: (accel) acceleration profile 0
    [ 16.446] (**) NextWindow Touchscreen: (accel) acceleration factor: 2.000
    [ 16.446] (**) NextWindow Touchscreen: (accel) acceleration threshold: 4
    [ 16.446] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/mouse2)
    [ 16.446] (II) No input driver specified, ignoring this device.
    [ 16.446] (II) This device may have been added with another device file.
    [ 16.447] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event9)
    [ 16.447] (II) No input driver specified, ignoring this device.
    [ 16.447] (II) This device may have been added with another device file.
    [ 16.447] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/event10)
    [ 16.447] (**) NextWindow Touchscreen: Applying InputClass "evdev pointer catchall"
    [ 16.447] (II) Using input driver 'evdev' for 'NextWindow Touchscreen'
    [ 16.447] (**) NextWindow Touchscreen: always reports core events
    [ 16.447] (**) evdev: NextWindow Touchscreen: Device: "/dev/input/event10"
    [ 16.447] (--) evdev: NextWindow Touchscreen: Vendor 0x1926 Product 0x33e
    [ 16.447] (--) evdev: NextWindow Touchscreen: Found 3 mouse buttons
    [ 16.447] (--) evdev: NextWindow Touchscreen: Found absolute axes
    [ 16.447] (--) evdev: NextWindow Touchscreen: Found x and y absolute axes
    [ 16.447] (--) evdev: NextWindow Touchscreen: Found absolute touchscreen
    [ 16.447] (II) evdev: NextWindow Touchscreen: Configuring as touchscreen
    [ 16.447] (**) evdev: NextWindow Touchscreen: YAxisMapping: buttons 4 and 5
    [ 16.447] (**) evdev: NextWindow Touchscreen: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 16.448] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.2/0003:1926:033E.0003/input/input10/event10"
    [ 16.448] (II) XINPUT: Adding extended input device "NextWindow Touchscreen" (type: TOUCHSCREEN, id 11)
    [ 16.448] (II) evdev: NextWindow Touchscreen: initialized for absolute axes.
    [ 16.448] (**) NextWindow Touchscreen: (accel) keeping acceleration scheme 1
    [ 16.448] (**) NextWindow Touchscreen: (accel) acceleration profile 0
    [ 16.448] (**) NextWindow Touchscreen: (accel) acceleration factor: 2.000
    [ 16.448] (**) NextWindow Touchscreen: (accel) acceleration threshold: 4
    [ 16.448] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/js0)
    [ 16.448] (II) No input driver specified, ignoring this device.
    [ 16.448] (II) This device may have been added with another device file.
    [ 16.449] (II) config/udev: Adding input device NextWindow Touchscreen (/dev/input/mouse0)
    [ 16.449] (II) No input driver specified, ignoring this device.
    [ 16.449] (II) This device may have been added with another device file.
    [ 16.449] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/event11)
    [ 16.449] (**) Hewlett Packard HP Wireless Keyboard Kit: Applying InputClass "evdev keyboard catchall"
    [ 16.449] (II) Using input driver 'evdev' for 'Hewlett Packard HP Wireless Keyboard Kit'
    [ 16.449] (**) Hewlett Packard HP Wireless Keyboard Kit: always reports core events
    [ 16.449] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: Device: "/dev/input/event11"
    [ 16.449] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Vendor 0x461 Product 0x4e25
    [ 16.449] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found keys
    [ 16.449] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as keyboard
    [ 16.449] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:0461:4E25.0004/input/input11/event11"
    [ 16.449] (II) XINPUT: Adding extended input device "Hewlett Packard HP Wireless Keyboard Kit" (type: KEYBOARD, id 12)
    [ 16.449] (**) Option "xkb_rules" "evdev"
    [ 16.449] (**) Option "xkb_model" "pc104"
    [ 16.449] (**) Option "xkb_layout" "us"
    [ 16.450] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/event12)
    [ 16.450] (**) Hewlett Packard HP Wireless Keyboard Kit: Applying InputClass "evdev keyboard catchall"
    [ 16.450] (II) Using input driver 'evdev' for 'Hewlett Packard HP Wireless Keyboard Kit'
    [ 16.450] (**) Hewlett Packard HP Wireless Keyboard Kit: always reports core events
    [ 16.450] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: Device: "/dev/input/event12"
    [ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Vendor 0x461 Product 0x4e25
    [ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found 1 mouse buttons
    [ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found scroll wheel(s)
    [ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found relative axes
    [ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Forcing relative x/y axes to exist.
    [ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found absolute axes
    [ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Forcing absolute x/y axes to exist.
    [ 16.450] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found keys
    [ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as mouse
    [ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as keyboard
    [ 16.450] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Adding scrollwheel support
    [ 16.450] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: YAxisMapping: buttons 4 and 5
    [ 16.450] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 16.450] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.1/0003:0461:4E25.0005/input/input12/event12"
    [ 16.450] (II) XINPUT: Adding extended input device "Hewlett Packard HP Wireless Keyboard Kit" (type: KEYBOARD, id 13)
    [ 16.450] (**) Option "xkb_rules" "evdev"
    [ 16.450] (**) Option "xkb_model" "pc104"
    [ 16.450] (**) Option "xkb_layout" "us"
    [ 16.451] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: initialized for relative axes.
    [ 16.451] (WW) evdev: Hewlett Packard HP Wireless Keyboard Kit: ignoring absolute axes.
    [ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) keeping acceleration scheme 1
    [ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration profile 0
    [ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration factor: 2.000
    [ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration threshold: 4
    [ 16.451] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/event13)
    [ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: Applying InputClass "evdev pointer catchall"
    [ 16.451] (II) Using input driver 'evdev' for 'Hewlett Packard HP Wireless Keyboard Kit'
    [ 16.451] (**) Hewlett Packard HP Wireless Keyboard Kit: always reports core events
    [ 16.451] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: Device: "/dev/input/event13"
    [ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Vendor 0x461 Product 0x4e25
    [ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found 3 mouse buttons
    [ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found scroll wheel(s)
    [ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found relative axes
    [ 16.452] (--) evdev: Hewlett Packard HP Wireless Keyboard Kit: Found x and y relative axes
    [ 16.452] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Configuring as mouse
    [ 16.452] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: Adding scrollwheel support
    [ 16.452] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: YAxisMapping: buttons 4 and 5
    [ 16.452] (**) evdev: Hewlett Packard HP Wireless Keyboard Kit: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 16.452] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.2/0003:0461:4E25.0006/input/input13/event13"
    [ 16.452] (II) XINPUT: Adding extended input device "Hewlett Packard HP Wireless Keyboard Kit" (type: MOUSE, id 14)
    [ 16.452] (II) evdev: Hewlett Packard HP Wireless Keyboard Kit: initialized for relative axes.
    [ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) keeping acceleration scheme 1
    [ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration profile 0
    [ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration factor: 2.000
    [ 16.452] (**) Hewlett Packard HP Wireless Keyboard Kit: (accel) acceleration threshold: 4
    [ 16.452] (II) config/udev: Adding input device Hewlett Packard HP Wireless Keyboard Kit (/dev/input/mouse1)
    [ 16.452] (II) No input driver specified, ignoring this device.
    [ 16.452] (II) This device may have been added with another device file.
    [ 16.453] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event6)
    [ 16.453] (II) No input driver specified, ignoring this device.
    [ 16.453] (II) This device may have been added with another device file.
    [ 16.453] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event5)
    [ 16.453] (II) No input driver specified, ignoring this device.
    [ 16.453] (II) This device may have been added with another device file.
    [ 16.453] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event4)
    [ 16.453] (II) No input driver specified, ignoring this device.
    [ 16.453] (II) This device may have been added with another device file.
    [ 16.453] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    [ 16.453] (II) No input driver specified, ignoring this device.
    [ 16.453] (II) This device may have been added with another device file.
    [ 16.454] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event7)
    [ 16.454] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [ 16.454] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
    [ 16.454] (**) HP WMI hotkeys: always reports core events
    [ 16.454] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event7"
    [ 16.454] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
    [ 16.454] (--) evdev: HP WMI hotkeys: Found keys
    [ 16.454] (II) evdev: HP WMI hotkeys: Configuring as keyboard
    [ 16.454] (**) Option "config_info" "udev:/sys/devices/virtual/input/input7/event7"
    [ 16.454] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 15)
    [ 16.454] (**) Option "xkb_rules" "evdev"
    [ 16.454] (**) Option "xkb_model" "pc104"
    [ 16.454] (**) Option "xkb_layout" "us"
    [ 1192.410] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 1811.202] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 5455.421] (II) intel(0): switch to mode [email protected] on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none

    I saw your post, and had found it incredulous that you have a 1920x1080 display.  A bit of research and I found I was wrong.
    So, it appears you are driving the panel at its native resolution.  Unfortunately, trying to determine what you mean by "Fuzzy" is probably going to be like trying to nail Jello to a tree.  But, let's give it a shot.  Is it fuzzy before you start X?  Are lines and shapes fuzzy? Or is it just text that is fuzzy?
    If it is just fonts, it could be a problem with hinting.  Hinting is where the edges of fonts are deliberately fuzzed and feathered to get the kerning correct when the physical pixels of the display don't quite line up.  This works well, unless the thing doing the hinting does not understand the geometry of the display.  In a color LCD, each pixel is actually made up of smaller sub pixels, generally three -- A red, a green, and a blue.  Green is usually in the middle.  Some displays have Two greens per pixel, arranged RGBG.  Some displays even have yellow subpixels.  Sometimes the subpixels are arranged left to right, sometimes they are arranged top to bottom.  Long story short, if you have hinting enabled, but the geometry is configured incorrectly, bad things happen.   Take a look at this wiki article

Maybe you are looking for