Results 1 to 4 of 4

Thread: xmessage: "could not sync environment to dbus"

  1. #1

    Default xmessage: "could not sync environment to dbus"

    Looking at the various posts, there doesn't seem to be one single solution to this problem. Some threads suggest dumping this file: .xsession-errors-:0 It is 1200+lines. I have an intel GPU, but don't use the intel drive since it locks up. Hardware is a Dell Latitude E6400
    Linux linux-0u81 4.4.114-42-default #1 SMP Tue Feb 6 10:58:10 UTC 2018 (b6ee9ae) x86_64 x86_64 x86_64 GNU/Linux

    Complete xsession-errors-:0 file here:
    https://pastebin.com/7pAGccrB

    Here is the .xsession-errors-;0 file, truncated.
    Code:
    startkde: Starting up...
    Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/keyboard.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/ktimezoned.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/filenamesearchmodule.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/device_automounter.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/appmenu.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/proxyscout.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/statusnotifierwatcher.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/networkmanagement.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/recentdocumentsnotifier.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/kscreen.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/solidautoeject.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/networkstatus.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/freespacenotifier.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/soliduiserver.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/remotedirnotify.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/khotkeys.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/networkwatcher.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/bluedevil.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/remotenotifier.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/desktopnotifier.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/ksysguard.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/baloosearchmodule.so"
    Initializing  "kcm_access" :  "kcminit_access"
    Initializing  "kded_touchpad" :  "kcminit_touchpad"
    Width:  717  height:  537
    Approx. resX:  7  resY:  10
    Final resolution x: 10  y: 10
    Initializing  "kcm_kgamma" :  "kcminit_kgamma"
    Initializing  "kcm_input" :  "kcminit_mouse"
    Initializing  "kcm_style" :  "kcminit_style"
    kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing.
    Qt: Session management error: networkIdsList argument is NULL
    detected kglobalaccel restarting, re-registering all shortcut keys
    detected kglobalaccel restarting, re-registering all shortcut keys
    Configuring Lock Action
    ksmserver: "/run/user/1000/KSMserver"
    ksmserver: KSMServer: SetAProc_loc: conn  0 , prot= local , file= @/tmp/.ICE-unix/2976
    ksmserver: KSMServer: SetAProc_loc: conn  1 , prot= unix , file= /tmp/.ICE-unix/2976
    ksmserver: KSMServer::restoreSession  "saved at previous logout"
    kscreen.kded: Config KScreen::Config(0x27a21d0) is ready
    ksmserver: Starting autostart service  "/etc/xdg/autostart/baloo_file.desktop"
    kscreen.kded: PowerDevil SuspendSession action not available!
    kscreen.kded: "The name org.kde.Solid.PowerManagement was not provided by any .service files"
    ksmserver: Starting autostart service  "/etc/xdg/autostart/kdeconnectd.desktop"
    ksmserver: Starting autostart service  "/etc/xdg/autostart/krunner.desktop"
    ksmserver: Starting autostart service  "/etc/xdg/autostart/plasmashell.desktop"
    ksmserver: Starting autostart service  "/etc/xdg/autostart/polkit-kde-authentication-agent-1.desktop"
    kscreen.kded: Applying config
    kscreen.kded: Applying known config "4307a00b03d5bd3e16bf4870bf702ec8"
    kscreen.kded: Finding a mode for QSize(1280, 800) @ 60.0019
    kscreen.kded:   Found:  "73"   QSize(1280, 800) @ 60.0019
    kscreen.kded: doApplyConfig()
    ksmserver: Starting autostart service  "/etc/xdg/autostart/xembedsniproxy.desktop"
    ksmserver: Autostart 0 done
    kscreen.kded: Config applied
    kscreen.kded: Monitor for changes:  true
    kscreen: Requesting missing EDID for outputs (65)
    ksmserver: Kcminit phase 1 done
    Session path: "/org/freedesktop/login1/session/_34"
    ksmserver: Starting autostart service  "/etc/xdg/autostart/pulseaudio.desktop"
    ksmserver: Autostart 1 done
    kscreen.kded: Change detected
    kscreen.kded: KScreen::Output( 65   "LVDS-1" connected enabled QPoint(0,0) QSize(1280, 800) "73" )
    kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing.
    kdeconnect.core: KdeConnect daemon starting
    completeShutdownOrCheckpoint called
    "\"fsrestore1\" - conversion of \"0,0,0,0\" to QRect failed"
    kscreen.kded: Saving current config to file
    kscreen.kded: Config saved on:  "/home/mrg/.local/share/kscreen/4307a00b03d5bd3e16bf4870bf702ec8"
    kscreen.kded: KScreen::Output( 65   "LVDS-1" connected enabled QPoint(0,0) QSize(1280, 800) "73" )
    New PolkitAgentListener  0x21890e0
    Adding new listener  PolkitQt1::Agent::Listener(0x21944b0) for  0x21890e0

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,681
    Blog Entries
    3

    Default Re: xmessage: "could not sync environment to dbus"

    I'm not sure what you are asking. I'm thinking that you are just asking what to do about that file ("xsession-errors-:0"). So I will comment on that.

    What I normally do about that file, is nothing. I ignore it.

    Occasionally -- very rarely -- something goes wrong on my desktop. Maybe an application crashes unexpectedly. When that happens, I will look at that file for any relevant error message. I would normally look near the end of the file.

    Basically, the file gets error messages, debugging messages, etc from Xwindows applications.

    If you logout, then login again, the file gets recreated. So it will be a short file. It grows over time while you are logged in.

    Deleting the file -- doesn't actually do much. The file stays there, and still takes up disk space. But the directory entry will be gone so you won't be able to look at the file. If you do that by mistake, no big deal. A logout and login will give you a fresh start.

    If it is filling up your disk (if you are tight on space for "/home") -- then logout and login again, maybe a bit more often than you are doing.

    Otherwise ignore the file unless something happens where you need to look.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  3. #3

    Default Re: xmessage: "could not sync environment to dbus"

    I get this situation where sometimes the notebook doesn't finish the boot. I does that "loading ram" message but ends up with a blank screen.

    I posted the Xmessage because some threads indicated that was useful for diagonstics. But the dbus not connecting to environment was the actual error message.

    I have done two successful boots at this point.

  4. #4

    Default Re: xmessage: "could not sync environment to dbus"

    Now I have the:
    Could not start D-bus. Can you call qdbus-qt5?

    Well yeah, I can. I had two or three successful boots without this problem. Is there some sort of timing issue?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •