DMP 4310 display autodetection failed

Dear All,
We currently test DMP 4310G to display digital signage to displays, but somehow HDMI autodetection failed on most of the displays.
We have LCD NEC, Samsung, EX90, and CTS500 as display.
When we connect DMP4310 via HDMI to NEC, Samsung and CTS500, they just blank (even the boot page where IP address is usually shown).
DMPDM shows that the autodetection is failed.
But when we connect DMP4310 to EX90, it can display content perfectly.
I tried to disable autodetection and enter resolution manually ( i checked the datasheet for native resolution of each display ) but still no results.
I also find this document on Cisco:
DMP 4310G Notice Regarding HDMI/DVI Effects on Autodetection
A corner case exists that is mildly disruptive. It is not likely to affect your organization. To understand
this corner case, assume that all of the following statements are true simultaneously.
• Your DMP model is 4310G.
• Your presentation system’s media signal interface is DVI, not HDMI.
• EDID data in the firmware for your presentation system misrepresents its native resolution.
• The falsely claimed resolution is an HDMIstandard instead ofa VESA standard.
In this case, your DMP 4310G proceeds as if the native resolution is low, to ensure that your digital sign
shows anything at all.
Any comments are really appreciated
Best Regard
Imad

We've run into troubles with faulty RS232 cables. Many of our DMPs were wired, but they just weren't receiving commands.
You might want to try the NEC PDComms tool, which you can download from here:
http://www.necdisplay.com/support-and-services/pdcommstool/Overview
With it, you can send RS232 commands from your computer, and view any response from your device. Then you can trouble shoot, at least ruling out the possibility of a faulty peripheral.
We didn't have any trouble with the 4310 5.4 when we isolated our trouble down to bad cables.
Good luck!
-Michael

Similar Messages

  • DMP 4310 5.4 with LG display

    Hi everyone,
    We've got a problem with Cisco DMP 4310 (v. 5.4) and LG display 42WS50. We try to use "Display power on/off" commands via RS-232 but it doesn't work.
    We tried built-in commands for Cisco_32N and also tried to create new system tasks with RS-232 hex codes 6b612030312030310d/
    6b612030312030300d. Prior to sending these commands we enabled RS-232 control but nothing worked.
    Does anyone know maybe there are some issues in new DMP's firmware version?

    We've run into troubles with faulty RS232 cables. Many of our DMPs were wired, but they just weren't receiving commands.
    You might want to try the NEC PDComms tool, which you can download from here:
    http://www.necdisplay.com/support-and-services/pdcommstool/Overview
    With it, you can send RS232 commands from your computer, and view any response from your device. Then you can trouble shoot, at least ruling out the possibility of a faulty peripheral.
    We didn't have any trouble with the 4310 5.4 when we isolated our trouble down to bad cables.
    Good luck!
    -Michael

  • How can I create a folder on internal storage of DMP 4310?

    Hi. I'm a junior engineer in Korea.
    I have a question about DMP 4310 with creating a folder of internal storage.
    I can acess the internal storage but, I cannot make a folder or file uploading.
    I already checked about Access mode - read and write, and also DMP management - FTP Server On, and password too.
    It's enable to read but, unable to make a file or a folder.
    when It rejected my order, I saw a message on my screen like this.
    "550 Create directory operation failed."
    I searched this letters, but couldn't get any information to handle this issue except for showing of permision error message of linux.
    now, I am begging for your kindness.
    what am I suppose to do?

    I checked my permission, and I got the result.
    By the result, I cannot make any folders or files except for path of /usb_1/
    So, I can upload file to /usb_1/ and play it. that's it.
    self question, and self answer... so sad to less people to answer this DMS section...

  • Black border around playlist DMP 4310

    I'm using a playlist for html assets with the DMP 4310, but they all render with a black border. Is there any way to get rid of that?
    EDIT: In DMS 5.3, the DMP 4310 was not able to render html, but we upgraded to 5.4 and are now able to render with this player, but not without black boxes around everything.       

    Hi Jackob,
    I have just done a quick test with 3 playlists containing your hello page. I actually don't see the issue at all in the preview, all is white with no borders; however, I do indeed see the black borders on the DMP screen when deploying the presentation.
    The only workaround I could find is as per previous suggestion, if you overlap the border of two media playlists, then that black border does not appear anymore.
    An alternative, probably quicker option could be to create a container web page with inside your widget pages (inside frames components), then display that container web page full screen, so you would avoid the borders completely.
    If you want to pursue further if those black border are actually expected or not and look for other potential workarounds, I would recommend you to raise a TAC Service Request so that this can be tested further.
    Best Regards,
    Marco

  • DMP 4310 load swf with flashvars

    Hi,
    I am using dmp 4310 and i want to load a swf file using flashvars. This swf is loaded through another swf (a wrapper swf) with the "MovieClip Loader Object" (AS2). When i load the swf using http request i do not have any prblems (eg clipLoader.loadMovie("http://10.0.0.1/swfTest.swf?flashVar1=test1")). The problem is that i cannot get the flashvars by loading the same swf file locally (eg clipLoader.loadMovie("file:///tmp/ftproot/usb_1/files/swfTest.swf?flashVar1=test1")). Is there any way to get the flashvar? Also, is there any way to access the swf file (with the flashvars) using the internal http service (eg http://localhost/...swfTest.swf?flasvar1=test1  -- where localhost is the player itself).
    Thank you in advance for your response!

    Suddenly that code in the following gives me some error
    var langPath = root.LoaderInfo.parameters["xmlFilePath"]+root.LoaderInfo.parameters["lang"];
    my_ssp.xmlFilePath = langPath;
    var fileType = root.LoaderInfo.parameters["xmlFileType"];
    my_ssp.xmlFileType = fileType;
    Access of possibly undefined property LoaderInfo through a reference with static type flash.display:DisplayObject.
    The only code snippet works is
    var paramObj:Object = LoaderInfo(this.root.loaderInfo).parameters;
    for (var param in paramObj) {
       if (param == "xmlFilePath") {
          my_ssp.xmlFilePath = paramObj[param];
       if (param == "xmlFileType") {
          my_ssp.xmlFileType = paramObj[param];

  • 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

  • Macbook pro retina display is failing to play youtube videos.

    Macbook pro retina display is failing to play youtube videos. I am currently using google chrome canary, but also when I try on safari it says "blocked plug in". I have downloaded and properly installed adobe flash player multiple times and it still isnt working. Does anyone else have this problem? And, is there anything I can do about this? Oh, and Ive tried updating both browsers. it has temporarily fixed the problem beofre but then eventually it comes back and I cant use youtube.

    Wrong forum... you need the MacBOOK Pro forum.

  • Display test failed in BB virtual expert what to do please help cell is new 2 months old

    Dear All, 
    3 Months back i had purchased BBZ30. and today i had downloaded virtual expert software to run the health test. All features are working fine but display test failed. It is showing cracked. However my cell phone is working fine and even display is also fine. but due to this result i am really tensed. Please help what should i do..
    Sumit-

    Hello,
    Your next step would be warranty support, to have your device properly evaluated by a qualified technician. See your warranty service provider for that.
    Good luck!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Equium P200-178 - backlight on the display has failed

    A friend of mine has an Equium P200-178 and the backlight on the display has failed.
    Unfortunately, the machine is three weeks out of its warranty and we are very, very far from a Service Depot.
    Googling the problem indicates that the inverter may have failed but how do you get to it?
    I have removed every screw that I can see on the case but it still won't come apart. I don't want to risk breaking it.
    Any help very gratefully received!
    Cheers.

    Hi
    The FL inverter is a small part which controls the screens backlighting and its placed near the TFT screen.
    Usually its not advisable to disassemble such hi-tech notebooks because such procedure is tricky and you could damage other parts.
    However, it seems you are already on the task and the notebooks covers are already removed.
    Well, I googled a little bit and found this page:
    [Taking apart Toshiba Satellite P205 display panel and removing LCD screen and inverter.|http://www.irisvista.com/tech/laptops/toshiba-satellite-p205/take-apart-display-panel-1.htm]
    Its about P205 but its very similar to the P200 notebook model.
    But note; everything what you do is your own risk!!!!

  • Display Driver Failing?

    Let me start out by saying I am far from computer literate when it comes to the actual computer, so any solutions you offer need to be in layman's terms or I'll probably mess up. (;
    I have Windows 8 on an HP Pavilion tx2500, model #2510us
    I got it for Christmas where it was previously owned but purchased from a computer store where I guess it did not initially have Windows 8 but their guy decided to install it before sending it back out.
    I haven't had much problem with it until now when visiting a website and my computer display went crazy!! The screen got little blue lines all over and a litle pop-up in the corner said something about the display driver failing. The computer restarted, and when it came back up it was still not right so I restarted again and it came up as if it were installing an update.
    I thought that was the end of it, but then the same thing happened again, with the screen going black with blue lines and crashing, although this time it did not say it was installing updates.
    Does anyone know if there is anything I can do to fix this? Any help is appreciated, as I know the computer is no longer under warranty and Windows 8 is not tested for my notebook, so I don't know who else to ask.

    Your best option would be to find a way to get Windows 7 installed back on it. More than likely the graphic card doesn't support Windows 8 and that is why you are experiencing these issues. 
    -------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------

  • Display suddenly failed. How to acquire bulb?

    My display suddenly failed. In the right room light, I can see the display working very, very, very faintly. So I'm thinking (hoping) it's just a backlight. If so, where can I get a replacement, how much should it cost, and where can I find installation directions?
    If this is too costly or difficult, I would consider buying a screen or entire computer. If I choose this route, is it possible to upgrade my 17" monitor w/ a 20" monitor if I can find one?
    Please advise.
    Thanks in advance.
    -Don!

    The part for that one is a 922-5298, and they are easy to replace as they are located in the display assembly along one side of it. You do not have to open the base or disconnect the arm to replace one. They are likely available for $ 49.00 or so: contact me at the electronic mail address in my Public Profile for help in obtaining one.
    You cannot swap display assemblies or arms, as the larger displays are cabled and terminated differently, and will not mate with the logic board or one end or the display assembly on the other.

  • Cisco DMP 4310 with standard power injector.

    Hi,
    I am trying to use a Cisco DMP 4310 with a standard power injector (PRJ3) but it seems that the DMP doesn't start.
    I tried using the power injector with a phone and also with a wireless access point, it is working.
    I also tried to plug the DMP to a POE switch, the dmp starts.
    Is the DMP 4310 compliant with standard power injector ?
    Thanks.

    Hi,
    It seems that the Power Injector delivers enought power but I will try with a PoE+ power injector. In the power injector's datasheet there is nothing about a 802.3af (standard for PoE) compliance so I will try with a compliant power injector. I will let you know if I found the answer.
    Thanks.

  • Cable autodetection failed. WARNING:iMPACT:923

    I am trying to program E2LP development board with Spartan 6, but it seems iMPACT has some issues with connecting. I have drivers from  E2LP Installer, and E2LP Config Utility is able to establish connection with the board. Still iMPACT does not see the cable.
    This is my autoconnect log:
    GUI --- Auto connect to cable...
    INFO:iMPACT - Digilent Plugin: Plugin Version: 2.4.4
    INFO:iMPACT - Digilent Plugin: no JTAG device was found.
    AutoDetecting cable. Please wait.
    *** WARNING ***: When port is set to auto detect mode, cable speed is set to default 6 MHz regardless of explicit arguments supplied for setting the baud rates
    PROGRESS_START - Starting Operation.
    Connecting to cable (Usb Port - USB21).
    Checking cable driver.
    Source driver files not found.
    The Platform Cable USB is not detected. Please connect a cable.If a cable is connected, please disconnect
    and reconnect to the usb port, follow the instructions in the 'Found New Hardware Wizard', then retry
    the Cable Setup operation.
    Cable connection failed.
    Connecting to cable (Parallel Port - LPT1).
    Checking cable driver.
    Driver windrvr6.sys version = 11.5.0.0. WinDriver v11.5.0 Jungo Connectivity (c) 1997 - 2014 Build Date: Jan 26 2014 x86_64 64bit SYS 13:30:18, version = 1150.
    LPT base address = 0378h.
    ECP base address = FFFFFFFFh.
    LPT port is already in use. rc = 0h
    Cable connection failed.
    Connecting to cable (Parallel Port - LPT2).
    Checking cable driver.
    Driver windrvr6.sys version = 11.5.0.0. WinDriver v11.5.0 Jungo Connectivity (c) 1997 - 2014 Build Date: Jan 26 2014 x86_64 64bit SYS 13:30:18, version = 1150.
    Cable connection failed.
    Connecting to cable (Parallel Port - LPT3).
    Checking cable driver.
    Driver windrvr6.sys version = 11.5.0.0. WinDriver v11.5.0 Jungo Connectivity (c) 1997 - 2014 Build Date: Jan 26 2014 x86_64 64bit SYS 13:30:18, version = 1150.
    Cable connection failed.
    Connecting to cable (Parallel Port - LPT4).
    Checking cable driver.
    Driver windrvr6.sys version = 11.5.0.0. WinDriver v11.5.0 Jungo Connectivity (c) 1997 - 2014 Build Date: Jan 26 2014 x86_64 64bit SYS 13:30:18, version = 1150.
    Cable connection failed.
    PROGRESS_END - End Operation.
    Elapsed time = 2 sec.
    Cable autodetection failed.

    I reinstalled them few times already.
    My colleague who uses same development board with same software claims, that he has no issues with programming, and there was no need to use iMPACT. He has Win 8 while I have Win 7.
    Config utility still says that it failed to execute iMPACT script. I run it as admin of course.

  • DMP 4310 v5.4: HTML site not responsive to touch

    I am using a 4310 DMP with an ECO display. So far, I have succesfully verified touch interaction works with a flash application on the DMP. Therefore, I can rule out faulty hardware or misconfiguration as the problem. The problem occurs when going to a URL such as htttp://www.google.com on the DMP. When the DMP is pointed to an html site I am unable to interact with it. At the moment, the browser renders the html sites fine, but I am unable to interact with it via the touchscreen. Any thoughts on how to get the html site to respond through the DMP and touchscreen?
    I have tried three ways of pointing the DMP to an html site to verify touch works with it.
    1.(Go To) URL - Tasks with a URL entry to http://www.google.com
    2.media startup: file:///tmp/ftproot/usb_1/simpleLink.html
    3.Media Playlist with a URL entry to http:///www.google.com

    My understanding of the 4310g ver 5.4 is that the web browser is embedded in a flash pane. Consequently, there is limited functionality on any web page with the exception of three HTML 5 tags, these being audio, video, and canvas.
    As such, it would make sense that any external website that you request via the 4310 would not have basic interactive capabilities that you'd get with a regular computer. I'd suggest trying to set up a basic HTML page using the canvas tag to see if you can achieve touch interactivity.
    Flash is handled differently by the DMP, so I'm not suprised to hear that flash works without a problem.
    Just my thoughts.
    Good luck.
    -Michael

  • 4310 display issues

    I currently have created new content for my 4310 to run, but it is having some issues.  At first I thought that maybe I had to much going on at once because I have a flash image slideshow, a rss feed, weather widget, and a date time clock all attempting to run.  But, I have it running on my test unit at my desk which is the 4400 model.  Anybody have any ideas as to why the 4310 unit would be blank but the older model can run it?
    thanks

    Nicolas,
    thanks for the reply, the problem I am having is that the screen displays nothing at all.  All there is, is a blank screen with the IP address showing.  I have tried removing pieces of presentation in hopes that it may work but I have had no luck.  Both versions also run 5.2.2 so I don't believe that to be the problem.
    Also, the old presentation I had pushed to the dmp worked fine with no complications.  The only difference between the two really was the weather widget which is why I tried removing it from the new one.
    Thanks,
    Colin

Maybe you are looking for

  • Report of result recording for multiple batches in a given time span .

    Dear team , I am looking for a standard SAP report that gives the details of result recording with all the characteristics for mulitple batches in a given span of time . The MICs will show the actual values recorded for each of the batches. The colum

  • ITunes Match has reverted my library

    Imagine my surprise when I went to listen to music this afternoon only to find that iTunes Match for some inexplicable reason has deleted all playlists I created within the last 3 weeks from all of my devices, it has also resurrected playlists I dele

  • Content Migration of PI 7.0 to PI 7.1

    Hi Experts, We have to PI installations within our company - PI 7.0 and PI 7.1. The plan is to migrate the contents of PI 7.0 to PI 7.1 and eventually shutdown 7.0. Does anybody have any views on how this is best achieved. At the moment we have 2 mig

  • Partition with Leopard Install Disc before install on drive?

    I have been trying to install Leopard but I want to partition my drive before I install so I can do a clean install and not mess up my current OS and apps. I have been booting from the install disc and going to disc utilities to partition... it goes

  • Sometimes the screen is full-screen or smaller than minimum, same for Thunderbird

    Every now and then the window-size is collapsed, and can only be maximized. (Firefox 8.0) This also happens at Thunderbird 8.0