MBA TBtoVGA dongle projector display connect fail

latest macbook air 13" (MBA) with thunderbolt (TB) adapter
OSX 10.7.2
official apple TB to VGA adapter
6 foot VGA cable to projector
EPSON projector (older model)
turn on projector
turn on MBA
connect VGA cable to projector
connect VGA other end to VGA adapter
plug in the TB end of adapter into MBA
expected: projector seamlessly connects and resolves the resolution (this happens for windows based laptops where resolution on projector is automatically resized)
actual result: laptop tries to connect, LCD on MBA flickers, projector is recognized by the MBA but projector display still stays in idle mode and shows nothing as if nothing is connected to the projector.
please help, i've seen only one thread about this exactly same issue when running windows7 dualboot on mac.  updating drivers resolved this problem but there is nothing available on MBA for display updates and no other solutions have been provided. 
Note: i was able to connect to another projector and that worked flowlessly.

I did finally manage to resolve this. I ended up purchasing a smattering of connectors from Monoprice, and their standard Mini-DisplayPort-to-VGA connecter has connected without a hitch to every display which was previously causing trouble. Why this should work where the officially supported adapter did not, I cannot say.

Similar Messages

  • I recently connected my new MBA to an ACER display using the appropriate Apple hardware to connect to a VGA port. The quality of the ACER display is poor- the image is not clear. How do I achieve the same clarity of picture as my MBA screen?

    I recently connected my new MBA to an ACER display using the appropriate Apple hardware to connect to a VGA port. The quality of the ACER display is poor- the image is not clear. How do I achieve the same clarity of picture as my MBA screen?

    Welcome to the Apple Community.
    AirPlay Mirroring requires a second-generation Apple TV or later, OS X 10.8 or better and is supported on the following Mac models: iMac (Mid 2011 or newer), Mac mini (Mid 2011 or newer), MacBook Air (Mid 2011 or newer), and MacBook Pro (Early 2011 or newer).
    On the basis of the specifications you have given for your set up, mirroring should work.

  • Will an iPad mini with retina display connect to a digital projector?

    Will an IPad mini with retina display connect to a digital projector for presentations?

    Yes, certainly. Depending on the projector's inputs, you'll need one of these adapters:
    http://store.apple.com/us/product/MD826ZM/A/lightning-digital-av-adapter
    http://store.apple.com/us/product/MD825ZM/A/lightning-to-vga-adapter
    or a third-party equivalent.
    Regards.

  • MBA 2012 Windows 8.1 WiFi requires Thunderbolt Ethernet dongle to be connected

    Using MBA (2012 version) with Windows 8.1.  WiFi will not work unless the Thunderbolt Ethernet dongle is physically connected at bootup (even if no actual network cable is connected to it). If the Thunderbolt dongle is not connected at time of bootup (inserting the dongle later has no impact), WiFi is in "disabled" status, cannot be re-enabled, and Windows troubleshooting agent reports a driver problem. Tried different drivers but no luck. The machine seems unable to correctly identify the wireless card unless the Ethernet Thunderbolt dongle is also connected, which is very strage as the two would not seem to be related. When the dongle is inserted during boot, however, WiFi works perfectly. The issue is only in Windows (WiFi worked great on Mac OS). Using latest BootCamp 5 drivers package on a clean Windows 8.1 install (not dual boot - I had to erase the Mac OS partition using disk utilities to have more disk space for Windows and so I could install BitLocker hard disk encryption which did not work when the Mac OS partition was present). Any thoughts?

    I have confirmed that the thunderbolt Ethernet adapter is working on my MacBook Air Mid 2012. You will need the latest Bootcamp 5.1 drivers (found here: Boot Camp Support Software 5.1.5621). Also you will need to update Windows like what doduykhuongsaid.
    FAQ does state that Boot Camp 5.1 does support Thunderbolt
    Boot Camp 5.1: Frequently asked questions - Apple Support
    Thanks guys for the update. It finally worked after quite a few months.

  • Unable to connect to website losing connection and the result is displayed as Secure Connection Failed (Error code: ssl_error_access_denied_alert)

    Secure Connection Failed
    An error occurred during a connection to website name
    Peer received a valid certificate, but access was denied.
    (Error code: ssl_error_access_denied_alert)
    # The page you are trying to view can not be shown because the authenticity of the received data could not be verified.
    # Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.

    Still experiencing this problem and hoping someone may have some ideas to try on the server.

  • Thunderbolt display-connected keyboard fails to wake MacBook Pro

    I'm having intermittent problems with my keyboard when I use my rMacBook Pro in clamshell mode attached to an Apple Thunderbolt Display. With increasing frequency, when I sleep the Mac, close it and attach it to the display, I cannot wake up the computer using the Apple keyboard that is attached (USB) to the display. Unplugging and repluggin the keyboard does nothing.
    I can wake up the computer with a Bluetooth keyboard & login (screensaver), and the Bluetooth keyboard continues to work fine. Nut the wired keyboard never works.
    However, if I simply restart the Mac, the display-connected keyboard always begins working again.
    I belive this rules out a hardware problem, but I'm open to suggestions. (It's happened repeatedly—maybe ten times over the last several months. But with increasing frequency.)
    I can post console logs if that would help.
    Any ideas?

    Clinton,
    Thanks for your interest in my question. I actually own a 27" Apple Thunderbolt Display, which works with other Retina Display Macbook Pro, but not mine anymore... That's why I suppose the problem comes from my laptop's thunderbolt ports.
    Any clue?
    Thanks very much in advance.
    Dominic

  • Creating new Data Source Error - Database connection Failed

    Successfully installed and configured 11.1.1.3.0. Planning and Essbase dev.
    Went to Workspace > Administer > Classing Planning Administration > Manage Data Sources > Create Data Source.
    Entered all info about the application database , etc. Getting error "The database connection failed" (I was able to connect with no problem during the install)
    SQL server 2005 is on the same physical server.
    The diagnostic tool shows database connection passed for planning. A new database was created for the new application.
    The server event viewer shows these errors.
    "Login failed for user 'xxx-hyperion'. The user is not associated with a trusted SQL Server connection."
    Group Policy Error "The client-side extension could not apply computer policy settings for 'Default Domain Policy {xxx}' because it failed with error code '0x80070003 The system cannot find the path specified.' See trace file for more details. "
    The Group Policy client-side extension Group Policy Services failed to execute. Please look for any errors reported earlier by that extension.
    Any help is appreciated.

    Datasource for the application.
    I have created a sql db for this planning application (my datasource). See my first message for more details.
    When you create a new planning application, you need to associate it with a data source. Since this is a new install, I don't have any data sources available yet.
    So, "To create, edit or delete data sources, click Manage Data Source."
    This page lets you validate your connection to the database and essbase server. My essbase server connection validates! The database connection does not validate after I enter all the relevant information.
    SCREEN INFO BELOW
    Fields displayed with an asterisk (*) are mandatory.
    Data Source Name *:
    Data Source Description:
    Select Database Platform
    Microsoft SQL Server
    Application Database
    Server * :
    Port * :
    Database *:
    User *:
    Password *:
    Click "Validate Database Connection"
    ERROR ---> Database connection failed.
    So it does not let me create a data source for my new planning application, so I cannot create a new planning application.
    Thanks in advance.

  • Submit Button error - Data Connection failing

    I am the form designer and am currently testing a new form I have created, however there is an error with my submit button which Saves the form to SharePoint, I receive the following error message:
    InfoPath cannot submit the form.
    An error occurred while the form was being submitted.
    The form cannot be submitted to the following location: http://servername/siteA/siteB/siteC/FormLibrary/FormName.xml
    The file: http://servername/siteA/siteB/siteC/FormLibrary/FormName.xml" is checked out for editing by DOMAIN\MyUserName.
    The operation completed successfully.
    The form is not checked out to me, or open by anybody else, also check out functionality is not forced on this SharePoint library.
    On searching forums I have read about using friendly server names and I am using the server's name in the URL, i.e.
    http://servername instead of the alias
    http://intranet - this had solved the problem in other forms, but not this one.
    Looking closely at the rules on my submit button, the following actions occur:
    1st rule checks the selection of certain fields, if the conditions are right it will set the values of 3 different fields.
    The 2nd rule saves to SharePoint using a data connection (please note this data connection works fine on different submit buttons in different views). The second rule also closes the form.
    To test where the error occurs I added a series of actions to display messages, and the problem is definitely on the data connection rule.
    The data connection is to save to a Sharepoint library, using a field called "filename" as the file name. The data connection allows overwrites. The file name is set the first time a file is saved (it has a condition which checks a field which
    gets set upon any save event - if this field is set to 0 filename gets set and this field gets set to 1 - because this field is now equal to 1, the filename field will nwever get set again).
    I have 2 views on the form, one named phase 1, the other named phase 2. When the custom submit button is pressed on the phase 1 view, my data connection works, but on the save 2 view, the exact same data connection fails with the error message above.
    I am using Windows 7, InfoPath 2010, SharePoint 2010, InfoPath filler form).
    In Windows XP, for a different user, the error messaeg is a little different, and the form does actually save:
    InfoPath cannot submit the form
    An error occurred while the form was being submitted
    The form cannot be submitted to the following location: http://servername/siteA/siteB/siteC/FormLibrary/FormName.xml
    The file is in use by another application or user.
    As I said the form does actually save its changes but still throws up this error message which will be very confusing to end users.
    I've exhausted all avenues that I know of to find the cause of the error messages and I'm at a loss, please help!
    Thanks,
    Ben

    bgvball14. I found that the error was down to the friendly name / server name issue. I have made sure that everything uses the friendly name e.g.
    http://intranet instead of the servername e.g.
    http://servername. I made sure the data connection and all options in the publishing wizard are set to the friendly name. There were still some forms that didn't work though - this was because when trying to fix this problem I had switched several times
    between using the friendly /server names and some forms were looking for the template with the server name (these didn't work), other forms looked for the friendly name (these did work).
    What I did was open my form library in windows explorer view and then drag each form into Notepad so I could see the source code. On the top two lines I could see the reference to the template and in some cases the template weas referenced using the server
    aname, which I changed to the friendly name and this worked. I did have to check every form in the library. Basically, everything should reference the friendly name (e.g.
    http://intranet.
    Ben

  • '"Connection Failed" : The server "rrnas01" may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again' message

    '"Connection Failed" : The server "rrnas01" may not exist or it is unavailable at this time. Check the server name or IP address, check your network connection, and then try again' message keeps displaying whenever I try to open any Adobe CS5 applications (except for Adobe Acrobat Pro). It displays until I click "OK" about 15-20 times or so and then will finally let my program open.
    I have tried deleting files within my Library/Preferences folder and turning off/deleting login items within my system preferences as other forums suggested but nothing happened. Spending 3.5 hours on the phone with Adobe and completely uninstalling and then reinstalling the entire CS5 Master Collection didn't work either.
    Also, it may be helpful to know that my programs worked fine for about three weeks then when we got internet and changed the password (the join, not the adminstrative password) with the wireless network "ScubaSteve" (which I've used with no problems at my old apartment) it started acting up. I have never seen "rrnas01" before so I don't know at all where it came from. I also installed the free 30 day trial of Suitcase Fusion 3 recently, but thinking that could also be the cause I have uninstalled it, and still no help.
    Please help me! And please keep in mind I don't know all the computer lingo that a lot of the people in these forums seem to know. Thanks in advance for ny help you can give me.

    It may not be possible .. there is a major bug between Mountain Lion and the TC where the TC disk goes off the radar of the computer.
    Lion is also affected but not as badly.
    7.6.4 seems worse than earlier firmware.. so back to 7.6.1 or 7.5.2 if that is possible.
    Obviously that is not a solution for a later Gen5 TC.
    Reset to factory after the firmware downgrade. .use all network names that are short, no spaces and pure alphanumeric.
    If the TC is the main router set the dhcp to a very short lease time.. eg 30min.. and see how it goes, or try a longer lease like 99days.
    I prefer the very short lease but response has been mixed.
    Use ethernet not wireless.. ethernet is always more reliable and stable than wireless.
    And last .. a nightly electric timer that powers off every night at midnight for 1min.. would not be the first device we have suggested a fix that amounts to beat the unit to the punch by forcing it to reboot since it is unstable.

  • Invoking BPEL process from ADF application - webservice connection failed

    Hi,
    I am trying to invoke a Bpel process from ADF page , I deployed the same in Standalone SOA server since I had to display some Human Task Forms.
    I created a webservice data control out of the bpel process and dropped the process method in my page.
    The page on which I dropped the process method stopped rendering and I checked the logs and found that I got the error mesage- webservice connection failed,the webservice url could not be reached and in the logs it also asks us to check if the connections.xml is available in the meta-inf directory. I checked the conections.xml is available in the EAR.
    So any pointers here and any one faced this error anytime?
    is there better ways to invoke the bpel flow from ADF page.
    Thanks,
    Robin

    Hi,
      Check if your wsdl endpoint can accessed properly. If yes, check the soap-binding address is properly pointing to the server hosting the webservice.
    Regards,
    Harikiran.

  • WEB AS connection failed

    Hi,
    i have logon method in User management as SAPLOGON (since we have same userids in Portal as well as in BW systems) and issued the necessary parameters for WEB AS connection as :
    WAS Description BW Development
    WAS Host Name IP address:8000
    WAS Path /sap/bw/bex
    WAS Protocol http
    Also gave the all necessary values in connector property.
    Now if i go to Display - > Connection Test and select the following :
    SAP Web AS Connection
    Connection Test for Connectors
    it is giving the following result:
    Results
    SAP Web AS Connection - Jan 1, 1970 7:27:40 PM
    Test Details:
    The test consists of the following steps:
    1. Check that the system object defines an SAP system
    2. Validate the following parameters: wap.WAS.protocol; wap.WAS.hostname
    3. Check the HTTP/S connection to the defined backend application
    Results
    1. The system object represents an SAP system.
    2. The following parameters are valid: wap.WAS.protocol (http) ; wap.WAS.hostname (ip address:8000)
    3. HTTP/S connection failed. Make sure the protocol, host name, and user mapping are correctly defined.
    Test Connection with Connector - Jan 1, 1970 7:27:40 PM
    Test Details:
    The test consists of the following steps:
    1. Retrieve the default alias of the system
    2. Check the connection to the backend application using the connector defined in this system object
    Results
    Retrieval of default alias successful
    Connection successful
    Even though we dont want to do user mapping (we have similar userids in both ends as mentioned early), i went ahead and did that also, but still WEB AS is failing with above mentioned error.
    Is there any specific patch level need to be there for BASIS or J2EE etc... we have BW 3.5(web as 640- ABAP System), EP 6.0 Patch 9.
    Thanks

    Hi ,
    I have had this problem before . Even though you still got a failure while the connection test , actually whrn you use the system object it works .Pls chaeck all the your parameter are right before you use this object .
    Thanks
    Aneez

  • Im running a web-based CMS, that cycles through a number of pages, and wanted to know if there is an auto reload code option ( not plug-in ) that can restart previous page when connection failed.

    I am running a web-based CMS that cycles through a number of pages, each for different times ( ranging from 40 seconds to 2 minutes )and is displayed in a number of shops. Every now and then our internet drops, and the page errors with connection failed. I’m wondering if there is anyway to auto reload the page as soon as the error connection failed is showing. auto-reload addon is not an option as this will interrupt the sequence.
    The following error was encountered:<br />
    <br />
    <ul><li><b>Connection Failed</b></li></ul><br />
    <br />
    This means:<br />
    <br />
    <pre>

    I am running a web-based CMS that cycles through a number of pages, each for different times ( ranging from 40 seconds to 2 minutes )and is displayed in a number of shops. Every now and then our internet drops, and the page errors with connection failed. I’m wondering if there is anyway to auto reload the page as soon as the error connection failed is showing. auto-reload addon is not an option as this will interrupt the sequence.
    The following error was encountered:<br />
    <br />
    <ul><li><b>Connection Failed</b></li></ul><br />
    <br />
    This means:<br />
    <br />
    <pre>

  • Display Manager fails to launch [SOLVED]

    Hello,
    TL:DR - KDM and other display managers fail to load after major system update, included Xorg.0.log and kdm.log for troubleshooting
    I've been using Arch since January 2015 and this is my first major breakage following a pacman -Syu on June 3rd. I'm new to the forums so forgive me if I missed something.
    I primarily use kde and kdm failed to start upon boot. I tried startx and xinit from the console. Xinit failed and startx starts TWM, which is the only windows manager I have working.
    I tried gdm, which hangs on the following output:
    <5>Unable to kill session worker process.
    <5>Child process -##### was already dead.
    <5>Could not start command '/usr/lib/gdm/gdm-session-worker': Too many open files
    <3>GLib: g_child_watch_add_full: assertion 'pid > 0' failed
    <5>Tried to look up non-existent conversation gdm-launch-environment
    <3>GLib: g_hash_table_find: assertion 'version == hash_table->version' failed
    <5>(gdm-display.c:1141):gdm_display_dispose: runtime check failed: (self->priv->status != GDM_DISPLAY_PREPARED)
    I tried lightdm, which returns a shell prompt without doing anything.
    My Xorg.0.log looks like Xorg is working correctly:
    [ 4.504]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 4.504] X Protocol Version 11, Revision 0
    [ 4.504] Build Operating System: Linux 3.19.2-1-ARCH x86_64
    [ 4.504] Current Operating System: Linux 2TALL 3.14.43-2-lts #1 SMP Fri May 22 03:36:10 UTC 2015 x86_64
    [ 4.504] Kernel command line: BOOT_IMAGE=/vmlinuz-linux-lts root=UUID=4fd1bd44-ee9f-4a44-bcd9-58a590eb9390 rw quiet
    [ 4.504] Build Date: 14 April 2015 10:34:18AM
    [ 4.504]
    [ 4.504] Current version of pixman: 0.32.6
    [ 4.504] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 4.504] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 4.504] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 3 21:28:00 2015
    [ 4.509] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 4.509] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 4.510] (==) No Layout section. Using the first Screen section.
    [ 4.510] (==) No screen section available. Using defaults.
    [ 4.510] (**) |-->Screen "Default Screen Section" (0)
    [ 4.510] (**) | |-->Monitor "<default monitor>"
    [ 4.511] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 4.511] (==) Automatically adding devices
    [ 4.511] (==) Automatically enabling devices
    [ 4.511] (==) Automatically adding GPU devices
    [ 4.515] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/OTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 4.515] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 4.515] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 4.515] (II) Loader magic: 0x815d80
    [ 4.515] (II) Module ABI versions:
    [ 4.515] X.Org ANSI C Emulation: 0.4
    [ 4.515] X.Org Video Driver: 19.0
    [ 4.515] X.Org XInput driver : 21.0
    [ 4.515] X.Org Server Extension : 9.0
    [ 4.681] (EE) systemd-logind: failed to get session: PID 398 does not belong to any known session
    [ 4.681] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 5.120] (--) PCI:*(0:0:2:0) 8086:0166:17aa:21fa rev 9, Mem @ 0xf0000000/4194304, 0xe0000000/268435456, I/O @ 0x00005000/64
    [ 5.121] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 5.121] (II) LoadModule: "glx"
    [ 5.123] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 5.141] (II) Module glx: vendor="X.Org Foundation"
    [ 5.141] compiled for 1.17.1, module version = 1.0.0
    [ 5.141] ABI class: X.Org Server Extension, version 9.0
    [ 5.141] (==) AIGLX enabled
    [ 5.141] (==) Matched intel as autoconfigured driver 0
    [ 5.141] (==) Matched intel as autoconfigured driver 1
    [ 5.141] (==) Matched modesetting as autoconfigured driver 2
    [ 5.141] (==) Matched fbdev as autoconfigured driver 3
    [ 5.141] (==) Matched vesa as autoconfigured driver 4
    [ 5.141] (==) Assigned the driver to the xf86ConfigLayout
    [ 5.141] (II) LoadModule: "intel"
    [ 5.141] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 5.145] (II) Module intel: vendor="X.Org Foundation"
    [ 5.145] compiled for 1.17.1, module version = 2.99.917
    [ 5.145] Module class: X.Org Video Driver
    [ 5.145] ABI class: X.Org Video Driver, version 19.0
    [ 5.145] (II) LoadModule: "modesetting"
    [ 5.145] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 5.146] (II) Module modesetting: vendor="X.Org Foundation"
    [ 5.146] compiled for 1.17.1, module version = 1.17.1
    [ 5.146] Module class: X.Org Video Driver
    [ 5.146] ABI class: X.Org Video Driver, version 19.0
    [ 5.146] (II) LoadModule: "fbdev"
    [ 5.146] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 5.146] (II) Module fbdev: vendor="X.Org Foundation"
    [ 5.146] compiled for 1.17.0, module version = 0.4.4
    [ 5.146] Module class: X.Org Video Driver
    [ 5.146] ABI class: X.Org Video Driver, version 19.0
    [ 5.146] (II) LoadModule: "vesa"
    [ 5.147] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [ 5.147] (II) Module vesa: vendor="X.Org Foundation"
    [ 5.147] compiled for 1.17.0, module version = 2.3.2
    [ 5.147] Module class: X.Org Video Driver
    [ 5.147] ABI class: X.Org Video Driver, version 19.0
    [ 5.147] (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
    [ 5.148] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
    [ 5.148] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
    [ 5.148] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
    [ 5.148] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 5.148] (II) FBDEV: driver for framebuffer: fbdev
    [ 5.148] (II) VESA: driver for VESA chipsets: vesa
    [ 5.148] (++) using VT number 7
    [ 5.154] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20080730
    [ 5.155] (WW) Falling back to old probe method for modesetting
    [ 5.155] (WW) Falling back to old probe method for fbdev
    [ 5.155] (II) Loading sub module "fbdevhw"
    [ 5.155] (II) LoadModule: "fbdevhw"
    [ 5.155] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 5.155] (II) Module fbdevhw: vendor="X.Org Foundation"
    [ 5.156] compiled for 1.17.1, module version = 0.0.2
    [ 5.156] ABI class: X.Org Video Driver, version 19.0
    [ 5.156] (WW) Falling back to old probe method for vesa
    [ 5.156] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 4000
    [ 5.156] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
    [ 5.156] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 5.156] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 5.156] (==) intel(0): RGB weight 888
    [ 5.156] (==) intel(0): Default visual is TrueColor
    [ 5.157] (II) intel(0): Output LVDS1 has no monitor section
    [ 5.157] (--) intel(0): Found backlight control interface intel_backlight (type 'raw') for output LVDS1
    [ 5.157] (II) intel(0): Enabled output LVDS1
    [ 5.157] (II) intel(0): Output VGA1 has no monitor section
    [ 5.157] (II) intel(0): Enabled output VGA1
    [ 5.157] (II) intel(0): Output HDMI1 has no monitor section
    [ 5.157] (II) intel(0): Enabled output HDMI1
    [ 5.157] (II) intel(0): Output DP1 has no monitor section
    [ 5.157] (II) intel(0): Enabled output DP1
    [ 5.157] (II) intel(0): Output HDMI2 has no monitor section
    [ 5.157] (II) intel(0): Enabled output HDMI2
    [ 5.157] (II) intel(0): Output HDMI3 has no monitor section
    [ 5.157] (II) intel(0): Enabled output HDMI3
    [ 5.157] (II) intel(0): Output DP2 has no monitor section
    [ 5.157] (II) intel(0): Enabled output DP2
    [ 5.157] (II) intel(0): Output DP3 has no monitor section
    [ 5.157] (II) intel(0): Enabled output DP3
    [ 5.157] (--) intel(0): Using a maximum size of 64x64 for hardware cursors
    [ 5.157] (II) intel(0): Output VIRTUAL1 has no monitor section
    [ 5.157] (II) intel(0): Enabled output VIRTUAL1
    [ 5.157] (--) intel(0): Output LVDS1 using initial mode 1366x768 on pipe 0
    [ 5.157] (==) intel(0): TearFree disabled
    [ 5.157] (==) intel(0): DPI set to (96, 96)
    [ 5.157] (II) Loading sub module "dri2"
    [ 5.157] (II) LoadModule: "dri2"
    [ 5.157] (II) Module "dri2" already built-in
    [ 5.157] (II) Loading sub module "present"
    [ 5.157] (II) LoadModule: "present"
    [ 5.157] (II) Module "present" already built-in
    [ 5.157] (II) UnloadModule: "modesetting"
    [ 5.157] (II) Unloading modesetting
    [ 5.157] (II) UnloadModule: "fbdev"
    [ 5.158] (II) Unloading fbdev
    [ 5.158] (II) UnloadSubModule: "fbdevhw"
    [ 5.158] (II) Unloading fbdevhw
    [ 5.158] (II) UnloadModule: "vesa"
    [ 5.158] (II) Unloading vesa
    [ 5.158] (==) Depth 24 pixmap format is 32 bpp
    [ 5.161] (II) intel(0): SNA initialized with Ivybridge (gen7, gt2) backend
    [ 5.161] (==) intel(0): Backing store enabled
    [ 5.161] (==) intel(0): Silken mouse enabled
    [ 5.162] (II) intel(0): HW Cursor enabled
    [ 5.162] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 5.163] (==) intel(0): DPMS enabled
    [ 5.163] (==) intel(0): display hotplug detection enabled
    [ 5.163] (II) intel(0): [DRI2] Setup complete
    [ 5.163] (II) intel(0): [DRI2] DRI driver: i965
    [ 5.163] (II) intel(0): [DRI2] VDPAU driver: i965
    [ 5.163] (II) intel(0): direct rendering: DRI2 enabled
    [ 5.163] (II) intel(0): hardware support for Present enabled
    [ 5.163] (--) RandR disabled
    [ 5.227] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 5.227] (II) AIGLX: enabled GLX_ARB_create_context
    [ 5.227] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 5.227] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 5.227] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 5.227] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 5.227] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 5.227] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 5.227] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 5.227] (II) AIGLX: enabled GLX_ARB_create_context_robustness
    [ 5.227] (II) AIGLX: Loaded and initialized i965
    [ 5.227] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 5.230] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 5.250] (II) intel(0): Setting screen physical size to 361 x 203
    [ 5.369] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 5.369] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 5.369] (**) Power Button: Applying InputClass "libinput keyboard catchall"
    [ 5.369] (II) LoadModule: "libinput"
    [ 5.370] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
    [ 5.374] (II) Module libinput: vendor="X.Org Foundation"
    [ 5.374] compiled for 1.17.1, module version = 0.10.0
    [ 5.374] Module class: X.Org XInput Driver
    [ 5.374] ABI class: X.Org XInput driver, version 21.0
    [ 5.374] (II) Using input driver 'libinput' for 'Power Button'
    [ 5.374] (**) Power Button: always reports core events
    [ 5.374] (**) Option "Device" "/dev/input/event2"
    [ 5.374] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
    [ 5.374] (II) input device 'Power Button', /dev/input/event2 is a keyboard
    [ 5.430] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
    [ 5.430] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 5.431] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
    [ 5.431] (II) input device 'Power Button', /dev/input/event2 is a keyboard
    [ 5.431] (II) config/udev: Adding input device Video Bus (/dev/input/event3)
    [ 5.431] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 5.431] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
    [ 5.431] (II) Using input driver 'libinput' for 'Video Bus'
    [ 5.431] (**) Video Bus: always reports core events
    [ 5.431] (**) Option "Device" "/dev/input/event3"
    [ 5.431] (II) input device 'Video Bus', /dev/input/event3 is tagged by udev as: Keyboard
    [ 5.431] (II) input device 'Video Bus', /dev/input/event3 is a keyboard
    [ 5.470] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input3/event3"
    [ 5.470] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 5.471] (II) input device 'Video Bus', /dev/input/event3 is tagged by udev as: Keyboard
    [ 5.471] (II) input device 'Video Bus', /dev/input/event3 is a keyboard
    [ 5.471] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
    [ 5.471] (II) No input driver specified, ignoring this device.
    [ 5.471] (II) This device may have been added with another device file.
    [ 5.471] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
    [ 5.471] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 5.471] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
    [ 5.471] (II) Using input driver 'libinput' for 'Sleep Button'
    [ 5.471] (**) Sleep Button: always reports core events
    [ 5.471] (**) Option "Device" "/dev/input/event1"
    [ 5.472] (II) input device 'Sleep Button', /dev/input/event1 is tagged by udev as: Keyboard
    [ 5.472] (II) input device 'Sleep Button', /dev/input/event1 is a keyboard
    [ 5.540] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1/event1"
    [ 5.540] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
    [ 5.540] (II) input device 'Sleep Button', /dev/input/event1 is tagged by udev as: Keyboard
    [ 5.540] (II) input device 'Sleep Button', /dev/input/event1 is a keyboard
    [ 5.541] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4013 (/dev/input/event5)
    [ 5.541] (**) Logitech Unifying Device. Wireless PID:4013: Applying InputClass "evdev pointer catchall"
    [ 5.541] (**) Logitech Unifying Device. Wireless PID:4013: Applying InputClass "libinput pointer catchall"
    [ 5.541] (II) Using input driver 'libinput' for 'Logitech Unifying Device. Wireless PID:4013'
    [ 5.541] (**) Logitech Unifying Device. Wireless PID:4013: always reports core events
    [ 5.541] (**) Option "Device" "/dev/input/event5"
    [ 5.542] (II) input device 'Logitech Unifying Device. Wireless PID:4013', /dev/input/event5 is tagged by udev as: Mouse
    [ 5.542] (II) input device 'Logitech Unifying Device. Wireless PID:4013', /dev/input/event5 is a pointer caps
    [ 5.610] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.2/0003:046D:C52B.0003/0003:046D:C52B.0004/input/input6/event5"
    [ 5.610] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:4013" (type: MOUSE, id 9)
    [ 5.610] (**) Option "AccelerationScheme" "none"
    [ 5.610] (**) Logitech Unifying Device. Wireless PID:4013: (accel) selected scheme none/0
    [ 5.610] (**) Logitech Unifying Device. Wireless PID:4013: (accel) acceleration factor: 2.000
    [ 5.610] (**) Logitech Unifying Device. Wireless PID:4013: (accel) acceleration threshold: 4
    [ 5.611] (II) input device 'Logitech Unifying Device. Wireless PID:4013', /dev/input/event5 is tagged by udev as: Mouse
    [ 5.611] (II) input device 'Logitech Unifying Device. Wireless PID:4013', /dev/input/event5 is a pointer caps
    [ 5.611] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4013 (/dev/input/mouse0)
    [ 5.611] (II) No input driver specified, ignoring this device.
    [ 5.611] (II) This device may have been added with another device file.
    [ 5.612] (II) config/udev: Adding input device Integrated Camera (/dev/input/event16)
    [ 5.612] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
    [ 5.612] (**) Integrated Camera: Applying InputClass "libinput keyboard catchall"
    [ 5.612] (II) Using input driver 'libinput' for 'Integrated Camera'
    [ 5.612] (**) Integrated Camera: always reports core events
    [ 5.612] (**) Option "Device" "/dev/input/event16"
    [ 5.612] (II) input device 'Integrated Camera', /dev/input/event16 is tagged by udev as: Keyboard
    [ 5.612] (II) input device 'Integrated Camera', /dev/input/event16 is a keyboard
    [ 5.670] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input18/event16"
    [ 5.670] (II) XINPUT: Adding extended input device "Integrated Camera" (type: KEYBOARD, id 10)
    [ 5.671] (II) input device 'Integrated Camera', /dev/input/event16 is tagged by udev as: Keyboard
    [ 5.671] (II) input device 'Integrated Camera', /dev/input/event16 is a keyboard
    [ 5.671] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event8)
    [ 5.671] (II) No input driver specified, ignoring this device.
    [ 5.671] (II) This device may have been added with another device file.
    [ 5.672] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event15)
    [ 5.672] (II) No input driver specified, ignoring this device.
    [ 5.672] (II) This device may have been added with another device file.
    [ 5.672] (II) config/udev: Adding input device HDA Intel PCH Dock Mic (/dev/input/event14)
    [ 5.672] (II) No input driver specified, ignoring this device.
    [ 5.672] (II) This device may have been added with another device file.
    [ 5.672] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event13)
    [ 5.672] (II) No input driver specified, ignoring this device.
    [ 5.672] (II) This device may have been added with another device file.
    [ 5.673] (II) config/udev: Adding input device HDA Intel PCH Dock Headphone (/dev/input/event12)
    [ 5.673] (II) No input driver specified, ignoring this device.
    [ 5.673] (II) This device may have been added with another device file.
    [ 5.673] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event11)
    [ 5.673] (II) No input driver specified, ignoring this device.
    [ 5.673] (II) This device may have been added with another device file.
    [ 5.673] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event10)
    [ 5.673] (II) No input driver specified, ignoring this device.
    [ 5.673] (II) This device may have been added with another device file.
    [ 5.674] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=8 (/dev/input/event9)
    [ 5.674] (II) No input driver specified, ignoring this device.
    [ 5.674] (II) This device may have been added with another device file.
    [ 5.674] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event4)
    [ 5.674] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 5.674] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
    [ 5.674] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
    [ 5.674] (**) AT Translated Set 2 keyboard: always reports core events
    [ 5.674] (**) Option "Device" "/dev/input/event4"
    [ 5.674] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event4 is tagged by udev as: Keyboard
    [ 5.674] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event4 is a keyboard
    [ 5.760] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input4/event4"
    [ 5.760] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
    [ 5.760] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event4 is tagged by udev as: Keyboard
    [ 5.760] (II) input device 'AT Translated Set 2 keyboard', /dev/input/event4 is a keyboard
    [ 5.761] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event17)
    [ 5.761] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 5.761] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 5.761] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 5.761] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
    [ 5.761] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 5.761] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 5.761] (II) LoadModule: "synaptics"
    [ 5.761] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 5.763] (II) Module synaptics: vendor="X.Org Foundation"
    [ 5.763] compiled for 1.17.1, module version = 1.8.2
    [ 5.763] Module class: X.Org XInput Driver
    [ 5.763] ABI class: X.Org XInput driver, version 21.0
    [ 5.763] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 5.763] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 5.763] (**) Option "Device" "/dev/input/event17"
    [ 5.910] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
    [ 5.910] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5768 (res 65)
    [ 5.910] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 5062 (res 136)
    [ 5.910] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 5.910] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 5.910] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
    [ 5.910] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 5.910] (**) Option "AreaBottomEdge" "82%"
    [ 5.910] (**) Option "ClickPad" "1"
    [ 5.910] (**) Option "EmulateMidButtonTime" "0"
    [ 5.910] (**) Option "VertScrollDelta" "122"
    [ 5.910] (**) Option "VertTwoFingerScroll" "1"
    [ 5.910] (**) Option "HorizTwoFingerScroll" "1"
    [ 5.910] (**) Option "TapButton1" "1"
    [ 5.910] (**) Option "TapButton2" "1"
    [ 5.910] (**) Option "TapButton3" "1"
    [ 5.910] (**) Option "PalmDetect" "1"
    [ 5.910] (**) Option "TapAndDragGesture" "1"
    [ 5.910] (**) Option "SoftButtonAreas" "5000 0 4220 0 0 0 0 0"
    [ 5.910] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 5.910] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 5.990] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input9/event17"
    [ 5.990] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
    [ 5.990] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 5.990] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 5.990] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.035
    [ 5.990] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 5.990] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 5.990] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 5.990] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 5.990] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 5.991] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
    [ 5.991] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 5.991] (II) config/udev: Adding input device PC Speaker (/dev/input/event7)
    [ 5.991] (II) No input driver specified, ignoring this device.
    [ 5.991] (II) This device may have been added with another device file.
    [ 5.992] (II) config/udev: Adding input device ThinkPad Extra Buttons (/dev/input/event6)
    [ 5.992] (**) ThinkPad Extra Buttons: Applying InputClass "evdev keyboard catchall"
    [ 5.992] (**) ThinkPad Extra Buttons: Applying InputClass "libinput keyboard catchall"
    [ 5.992] (II) Using input driver 'libinput' for 'ThinkPad Extra Buttons'
    [ 5.992] (**) ThinkPad Extra Buttons: always reports core events
    [ 5.992] (**) Option "Device" "/dev/input/event6"
    [ 5.992] (II) input device 'ThinkPad Extra Buttons', /dev/input/event6 is tagged by udev as: Keyboard
    [ 5.992] (II) input device 'ThinkPad Extra Buttons', /dev/input/event6 is a keyboard
    [ 6.020] (**) Option "config_info" "udev:/sys/devices/platform/thinkpad_acpi/input/input7/event6"
    [ 6.020] (II) XINPUT: Adding extended input device "ThinkPad Extra Buttons" (type: KEYBOARD, id 13)
    [ 6.020] (II) input device 'ThinkPad Extra Buttons', /dev/input/event6 is tagged by udev as: Keyboard
    [ 6.020] (II) input device 'ThinkPad Extra Buttons', /dev/input/event6 is a keyboard
    [ 6.025] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event13)
    [ 6.025] (II) No input driver specified, ignoring this device.
    [ 6.025] (II) This device may have been added with another device file.
    [ 6.025] (II) config/udev: Adding input device HDA Intel PCH Dock Mic (/dev/input/event14)
    [ 6.025] (II) No input driver specified, ignoring this device.
    [ 6.025] (II) This device may have been added with another device file.
    [ 6.025] (II) config/udev: removing device Integrated Camera
    [ 6.100] (II) UnloadModule: "libinput"
    [ 6.100] (II) config/udev: Adding input device Integrated Camera (/dev/input/event16)
    [ 6.100] (**) Integrated Camera: Applying InputClass "evdev keyboard catchall"
    [ 6.100] (**) Integrated Camera: Applying InputClass "libinput keyboard catchall"
    [ 6.100] (II) Using input driver 'libinput' for 'Integrated Camera'
    [ 6.100] (**) Integrated Camera: always reports core events
    [ 6.100] (**) Option "Device" "/dev/input/event16"
    [ 6.101] (II) input device 'Integrated Camera', /dev/input/event16 is tagged by udev as: Keyboard
    [ 6.101] (II) input device 'Integrated Camera', /dev/input/event16 is a keyboard
    [ 6.160] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input18/event16"
    [ 6.160] (II) XINPUT: Adding extended input device "Integrated Camera" (type: KEYBOARD, id 10)
    [ 6.160] (II) input device 'Integrated Camera', /dev/input/event16 is tagged by udev as: Keyboard
    [ 6.160] (II) input device 'Integrated Camera', /dev/input/event16 is a keyboard
    [ 6.161] (II) config/udev: Adding input device HDA Intel PCH Dock Headphone (/dev/input/event12)
    [ 6.161] (II) No input driver specified, ignoring this device.
    [ 6.161] (II) This device may have been added with another device file.
    [ 6.161] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event15)
    [ 6.161] (II) No input driver specified, ignoring this device.
    [ 6.161] (II) This device may have been added with another device file.
    [ 6.162] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
    [ 6.162] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 6.162] (II) config/udev: removing device SynPS/2 Synaptics TouchPad
    [ 6.220] (II) UnloadModule: "synaptics"
    [ 6.220] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event17)
    [ 6.220] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 6.220] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 6.220] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 6.220] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "libinput touchpad catchall"
    [ 6.220] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 6.220] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 6.220] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 6.220] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 6.220] (**) Option "Device" "/dev/input/event17"
    [ 6.360] (II) synaptics: SynPS/2 Synaptics TouchPad: found clickpad property
    [ 6.360] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5768 (res 65)
    [ 6.360] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 5062 (res 136)
    [ 6.360] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 6.360] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 6.360] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left double triple
    [ 6.360] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 6.360] (**) Option "AreaBottomEdge" "82%"
    [ 6.360] (**) Option "ClickPad" "1"
    [ 6.360] (**) Option "EmulateMidButtonTime" "0"
    [ 6.360] (**) Option "VertScrollDelta" "122"
    [ 6.360] (**) Option "VertTwoFingerScroll" "1"
    [ 6.360] (**) Option "HorizTwoFingerScroll" "1"
    [ 6.360] (**) Option "TapButton1" "1"
    [ 6.360] (**) Option "TapButton2" "1"
    [ 6.360] (**) Option "TapButton3" "1"
    [ 6.360] (**) Option "PalmDetect" "1"
    [ 6.360] (**) Option "TapAndDragGesture" "1"
    [ 6.360] (**) Option "SoftButtonAreas" "5000 0 4220 0 0 0 0 0"
    [ 6.360] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 6.360] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 6.420] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input9/event17"
    [ 6.420] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 12)
    [ 6.420] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 6.420] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 6.420] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.035
    [ 6.420] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 6.420] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 6.420] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 6.420] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 6.420] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 6.960] (II) UnloadModule: "synaptics"
    [ 6.960] (II) UnloadModule: "libinput"
    [ 6.960] (II) UnloadModule: "libinput"
    [ 6.961] (II) UnloadModule: "libinput"
    [ 6.961] (II) UnloadModule: "libinput"
    [ 6.961] (II) UnloadModule: "libinput"
    [ 6.961] (II) UnloadModule: "libinput"
    [ 6.961] (II) UnloadModule: "libinput"
    [ 7.745] (II) Server terminated successfully (0). Closing log file.
    My kdm.log reports an issue with dbus:
    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.*.
    klauncher(331) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(325)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(325)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(319) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(313)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(313)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(1028) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(1022)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(1022)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(1623) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(1617)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(1617)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(319) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(313)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(313)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(381) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(375)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(375)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(384) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(378)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(378)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(441) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(417)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(417)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(444) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(420)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(420)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(459) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(446)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(446)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(453) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(441)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(441)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(678) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(672)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(672)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(534) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(516)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(516)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(711) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(705)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(705)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(775) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(757)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(757)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(793) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(775)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(775)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(764) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(740)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(740)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(702) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(692)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(692)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(727) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(713)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(713)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(781) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(757)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(757)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(759) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(747)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(747)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(685) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(679)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(679)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(766) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(748)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(748)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(703) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(692)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(692)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(753) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(735)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(735)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(1230) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(1224)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(1224)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(727) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(707)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(707)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(757) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(743)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(743)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(766) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(748)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(748)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(695) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(689)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(689)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(733) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(727)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(727)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(773) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(755)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(755)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(771) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(753)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(753)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)"
    Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)"
    klauncher(709) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(699)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(699)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)"
    Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)"
    klauncher(760) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(740)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(740)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)"
    Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)"
    klauncher(780) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(762)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(762)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)"
    Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)"
    klauncher(721) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(715)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(715)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(721) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(715)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(715)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(707) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(701)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(701)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(772) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(760)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(760)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    xf86: remove device 0 /sys/devices/pci0000:00/0000:00:02.0/drm/card0
    failed to find screen to remove
    klauncher(761) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(740)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(740)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(753) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(735)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(735)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(773) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(761)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(761)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(831) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(819)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(819)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(759) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(726)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(726)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(961) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(944)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(944)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(775) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(765)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(765)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(779) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(771)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(771)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(1012) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(1006)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(1006)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(872) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(859)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(859)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(888) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(866)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(866)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(1179) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(1165)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(1165)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(909) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(899)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(899)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(926) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(920)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(920)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(910) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(899)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(899)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(911) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(900)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(900)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(924) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(911)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(911)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(951) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(925)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(925)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(931) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(917)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(917)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(931) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(917)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(917)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(903) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(893)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(893)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(857) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(834)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(834)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(710) 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
    (II) Server terminated successfully (0). Closing log file.
    klauncher(720) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(708)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(708)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(752) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(730)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(730)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    klauncher(709) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(701)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(701)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (EE) client bug: Invalid path /dev/input/event18
    [dix] couldn't enable device 14
    (II) Server terminated successfully (0). Closing log file.
    klauncher(763) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(738)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(738)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(752) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(730)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(730)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(752) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(730)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(730)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    (II) Server terminated successfully (0). Closing log file.
    klauncher(766) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(744)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(744)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
    klauncher(725) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
    kdeinit4: Communication error with launcher. Exiting!
    kdmgreet(698)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
    kdmgreet(698)/kdecore (K*TimeZone*): No time zone information

    snoopyddogg wrote:startx starts TWM
    Can you start KDE using `startx` if you set up ~/.xinitrc correctly?
    https://wiki.archlinux.org/index.php/Xinitrc
    https://wiki.archlinux.org/index.php/Pl … ng_xinitrc

  • OS X 10.8.4 wifi says "connection failed", but connects anyway; cannot save password

    I am using OS X 10.8.4 that came with my MBP. When I connect to my home wifi that requires a WPA 2 password, it says "Connection Failed", but anyway connects to the internet. Also, my password is not being saved, and I need to enter it everytime.
    After reading several forums, I have already tried the following:
    1. removing airport preference list from Library/Preferences/SystemConfiguration
    2. Removing network password from the keychain
    3. Using Keychain first aid
    4. Using disk utility and doing repair disk.
    5. Doing DHCP release in Network Preferences.
    6. Removing my network from the preferred network list and connecting again.
    I am using a D-link modem. It should not be a problem, because the same MBP could remember the password before. The problem happened when I tried to fix my wifi because it would take long to connect after waking from sleep, when I deleted the airport preferences list, and removed the keyring.

    Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
    Step 1
    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
    Enter the following command in the Terminal window in the same way as before (triple-click, copy, and paste):
    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
    This time you'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
    Step 2 (optional)
    Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
    Boot into Recovery. When the OS X Utilities screen appears, select
    Utilities ▹ Terminal
    from the menu bar. A Terminal window will open.
    In the Terminal window, type this:
    res
    Press the tab key. The partial command you typed will automatically be completed to this:
    resetpassword
    Press return. A Reset Password window will open. You’re not  going to reset a password.
    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
    Select your username from the menu labeled Select the user account if not already selected.
    Under Reset Home Directory Permissions and ACLs, click the Reset button.
    Select
     ▹ Restart
    from the menu bar.

  • FormsGraph: open HTTP connection failed

    I have the forms 9i demos installed and they work fine. However when I put my own form into the bigraph\forms directory and try to run it, the form itself runs but I have no chart. The implementation class is the same as in the FormsGraph demo.
    I have copied the [bigraph] config information in forms90demo.cfg to my own config, changing only the fmx name and the userid. However, the java console shows
    ..java.lang....open HTTP connection failed
    followed by a number of java classes.
    What could be going wrong?
    Adrian

    Frank, this is from the java console
    proxyHost=null
    proxyPort=0
    connectMode=HTTP, native.
    Forms Applet version is : 90290
    java.lang.ClassNotFoundException: java.io.IOException: open HTTP connection failed.
         at sun.applet.AppletClassLoader.getBytes(Unknown Source)
         at sun.applet.AppletClassLoader.access$100(Unknown Source)
         at sun.applet.AppletClassLoader$1.run(Unknown Source)
         at java.security.AccessController.doPrivileged(Native Method)
         at sun.applet.AppletClassLoader.findClass(Unknown Source)
         at sun.plugin.security.PluginClassLoader.findClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at sun.applet.AppletClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClass(Unknown Source)
         at java.lang.ClassLoader.loadClassInternal(Unknown Source)
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Unknown Source)
         at oracle.forms.handler.UICommon.instantiate(Unknown Source)
         at oracle.forms.handler.UICommon.onCreate(Unknown Source)
         at oracle.forms.handler.JavaContainer.onCreate(Unknown Source)
         at oracle.forms.engine.Runform.onCreateHandler(Unknown Source)
         at oracle.forms.engine.Runform.processMessage(Unknown Source)
         at oracle.forms.engine.Runform.processSet(Unknown Source)
         at oracle.forms.engine.Runform.onMessageReal(Unknown Source)
         at oracle.forms.engine.Runform.onMessage(Unknown Source)
         at oracle.forms.engine.Runform.sendInitialMessage(Unknown Source)
         at oracle.forms.engine.Runform.startRunform(Unknown Source)
         at oracle.forms.engine.Main.createRunform(Unknown Source)
         at oracle.forms.engine.Main.start(Unknown Source)
         at sun.applet.AppletPanel.run(Unknown Source)
         at java.lang.Thread.run(Unknown Source)
    and this is the forms90demo.cfg, which I have
    modified to make sure I hadn't missed anything
    for FormsGraph capabilities
    (I have stripped out the other named configs)
    # Forms 9i Samples and Demos Configurations
    # Generic settings for the Demos and Samples
    # SYSTEM PARAMETERS
    # These have fixed names and give information required by the Forms
    # Servlet in order to function. They cannot be specified in the URL query
    # string. But they can be overriden in a named configuration (see below).
    # Some parameters specify file names: if the full path is not given,
    # they are assumed to be in the same directory as this file. If a path
    # is given, then it should be a physical path, not a URL.
    baseHTML=demo90base.html
    baseHTMLie=demo90baseie.html
    baseHTMLJInitiator=demo90basejini.html
    HTMLdelimiter=%
    # WorkingDirectory defaults to <oracle_home>/forms90 if unset.
    workingDirectory=
    envFile=forms90demo.env
    # The next parameter specifies how to execute the Forms applet under
    # Microsoft Internet Explorer 5.x.
    # The Demos want to use JInitiator as we ahve many demos that need a 1.3 JVM
    IE=JInitiator
    # These settings support running and debugging a form from the Builder:
    otherparams=debug=%debug% buffer_records=%buffer% debug_messages=%debug_messages% array=%array% query_only=%query_only% quiet=%quiet% render=%render% host=%host% port=%port% record=%record% tracegroup=%tracegroup% log=%log% term=%term%
    debug=no
    buffer=no
    debug_messages=no
    array=no
    query_only=no
    quiet=yes
    render=no
    host=
    port=
    record=
    tracegroup=
    log=
    term=
    # Values for the Forms applet parameters:
    serverURL=/forms90demo/l90servlet
    codebase=/forms90demo/java
    imageBase=DocumentBase
    formsMessageListener=
    recordFileName=
    serverApp=default
    # General Shared settings which define the Look and feel of the Demos
    width=675
    height=480
    separateFrame=false
    splashScreen=no
    lookAndFeel=oracle
    colorScheme=blue
    background=/forms90demo/images/blue.gif
    logo=/forms90demo/images/Forms9i.gif
    # Other settings
    scripting=false
    # Default JARs
    archive=f90all.jar,/forms90demo/jars/demo90.jar
    archive_jini=f90all_jinit.jar,/forms90demo/jars/demo90.jar
    archive_ie=f90all.cab,/forms90demo/jars/demo90.cab
    # Jinitiator and iAS general settings
    # Number of times client should retry if a network failure occurs. Only
    # change after having read the documentation.
    networkRetries=0
    # 4) Parameters for JInitiator (used with Windows clients)
    # Page displayed to Netscape users to allow them to download JInitiator.
    # If you create your own page, you should set this parameter to point to it.
    jinit_download_page=/forms90demo/jinitiator/us/jinit_download.htm
    # Parameters related to the version of JInitiator.
    jinit_classid=clsid:CAFECAFE-0013-0001-0013-ABCDEFABCDEF
    jinit_exename=jinit.exe#Version=1,3,1,13
    jinit_mimetype=application/x-jinit-applet;version=1.3.1.13
    # EM config parameter
    # Set this to "1" to enable Enterprise Manager to track Forms processes
    em_mode=0
    [qt]
    userid=capel/james@bond
    form=portfoliomanager.fmx
    #width=960
    #height=1200
    #baseHTML=qtbase.htm
    #baseHTMLjinitiator=qtbasejini.htm
    #baseHTMLjpi=qtbasejpi.htm
    #baseHTMLie=qtbaseie.htm
    archive=f90all_jinit.jar,/forms90demo/jars/demo90.jar,/forms90demo/jars/FormsGraph.jar
    archive_jini=f90all_jinit.jar,/forms90demo/jars/demo90.jar,/forms90demo/jars/FormsGraph.jar
    #background=NO
    #look-and-feel=Generic
    #logo=NO
    imagebase=codebase
    # End
    Even when I replace graph90.fmx in the [bigraph] named configuration with my portfoliomanager.fmx I still get these errors. This leads me to think there is something wrong with the form itself. The demos work fine.

Maybe you are looking for

  • Document Security Not Retaining Permissions

    I have created a form in 7.0 and published it to my repository on my hard drive. I've uploaded the form to my site for my users. The form has three signature boxes as it's used in a workflow. I have full blown Acrobat 7 but my users don't. I can sign

  • Receiving a "missing ; before statement" error message

    I cannot see what I'm missing on this one.  This is an Adobe form testing a checkbox (New) and if it has been checked it is required that at least one of the following checkboxes (A or B) is checked. If not, an error is to display on the form to the

  • Planning Method in Item attribute

    dear expert, can anyone explain, may be by example, the purpose of using MRP/MPP, MPS/MPP, or others planning method in item attribute MPS/MRP Planned. Regards

  • Help with a software update please

    I have tried on loads of occasions to update the software on my iphone 4 through my itunes, it takes forever for itunes to download the update, and then when it tries to update my phone it comes up with an error and doesnt update.  Has anyone else ha

  • Help needed with buttons

    Hi, I know how to create an invisible button to place over text in order to make the text linkable to a URL, but what about if the text is dynamic text within a scrollable area? Is there a way to make a word in this text hotlinked to a URL? Thanks. B